Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE12c Appcrash problem sawbedrock643r.dll

11
Views
2
Comments
3068122
3068122 Rank 4 - Community Specialist
edited Aug 13, 2024 6:18PM in Oracle Analytics Cloud and Server

Hi all ,

yesterday i could open hostname:9502/analytics and could login to obiee without any error.

However today , when try to open hostname:9502/analytics , i got "Error 500-- Internal Server Error".


Then i checked the server machine , i faced "Oracle Business Intelligence has stopped working." error message window. Also , I checked status of all services and all services are "RUNNING"


Error message's detail at the server machine is 


Problem signature:

  Problem Event Name: APPCRASH

  Application Name: sawserver.exe

  Application Version: 12.2.1.0

  Application Timestamp: 5616f0d2

  Fault Module Name: sawbedrock643r.dll

  Fault Module Version: 12.2.1.0

  Fault Module Timestamp: 5616e91c

  Exception Code: c0000005

  Exception Offset: 0000000000008c2c

  OS Version: 6.2.9200.2.0.0.400.8

  Locale ID: 1055

  Additional Information 1: 433f

  Additional Information 2: 433f78dbc18b2fb3f7d3585c14db75d3

  Additional Information 3: 4278

  Additional Information 4: 42780981f6905e48ca0c191230c1119b

Is there anyone who face the same error or who has any suggestion to solve ?

Regards


Comments

  • OBI_Kenobi
    OBI_Kenobi Rank 2 - Community Beginner

    Hey 3068122, I have observed the exact same behavior in my new OBIEE 12c environment a handful of times now over the past couple months... Very frustrating, not much of anything in the logs that I can find either...

    Have you resolved your issue somehow or worked around it?

    Jeremy

  • rmoff
    rmoff Rank 6 - Analytics Lead

    Jeremy - it's best to start a new thread for problems, and you can reference back to any others you've found for info.

    That way you can start with a good description of your problem and environment (http://catb.org/~esr/faqs/smart-questions.html#beprecise)

    In terms of logs, check the sawlog and saw-diagnostic log, as well as any coredumps written (not sure if that applies to Windows though). After that - raise an SR. You pay for the support, OBIEE has crashed -> it's a bug, so raise a ticket.