Ok, lets get this blog started then...
I've been playing with a new install of OBIEE 12c on Windows 2012 and I couldn't get the bi server to start correctly. I kept on getting the following error:
Error: oracle business intelligence has stopped working
Problem signature:
Problem Event Name: BEX64
Application Name: sawserver.exe
Application Version: 12.2.1.0
Application Timestamp: 5616f0d2
Fault Module Name: yod.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50ff431d
Exception Offset: 000000000001e940
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 2057
Additional Information 1: d406
Additional Information 2: d406e47b17f73b5fc03376291226207b
Additional Information 3: 7458
Additional Information 4: 74581c46e97a8bc42cd289645d01850b
and this error:
Error: nqsserver.exe has stopped working
Problem signature:
Problem Event Name: BEX64
Application Name: nqsserver.exe
Application Version: 0.0.0.0
Application Timestamp: 561bb059
Fault Module Name: yod.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50ff431d
Exception Offset: 000000000001e940
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 2057
Additional Information 1: d92a
Additional Information 2: d92afc5ed82d4e5d1dbbd90e1ee4ae90
Additional Information 3: 0ed0
Additional Information 4: 0ed072c3fcb2518b6476270391ad9386
It turns out the issue was due to OBIEE picking up the wrong version of the yod.dll library.
What made my environment different from others?
My server also had the full EPM 11.1.2.4 stack installed, The EPM instance contains several different versions of the yod.dll and my OBIEE biserver was picking up the wrong version of yod.dll because of the Windows path entries added by the EPM installer.
To fix the issue I created a batch script which sets only the Windows related paths and then calls the OBIEE start.cmd:
set PATH=C:\ProgramData\Oracle\Java\javapath;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
call E:\Oracle\OBIEE\Oracle_Home\user_projects\domains\bi\bitools\bin\start.cmd
After this OBIEE started without any issues.
I've been playing with a new install of OBIEE 12c on Windows 2012 and I couldn't get the bi server to start correctly. I kept on getting the following error:
Error: oracle business intelligence has stopped working
Problem signature:
Problem Event Name: BEX64
Application Name: sawserver.exe
Application Version: 12.2.1.0
Application Timestamp: 5616f0d2
Fault Module Name: yod.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50ff431d
Exception Offset: 000000000001e940
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 2057
Additional Information 1: d406
Additional Information 2: d406e47b17f73b5fc03376291226207b
Additional Information 3: 7458
Additional Information 4: 74581c46e97a8bc42cd289645d01850b
and this error:
Error: nqsserver.exe has stopped working
Problem signature:
Problem Event Name: BEX64
Application Name: nqsserver.exe
Application Version: 0.0.0.0
Application Timestamp: 561bb059
Fault Module Name: yod.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 50ff431d
Exception Offset: 000000000001e940
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 2057
Additional Information 1: d92a
Additional Information 2: d92afc5ed82d4e5d1dbbd90e1ee4ae90
Additional Information 3: 0ed0
Additional Information 4: 0ed072c3fcb2518b6476270391ad9386
It turns out the issue was due to OBIEE picking up the wrong version of the yod.dll library.
What made my environment different from others?
My server also had the full EPM 11.1.2.4 stack installed, The EPM instance contains several different versions of the yod.dll and my OBIEE biserver was picking up the wrong version of yod.dll because of the Windows path entries added by the EPM installer.
To fix the issue I created a batch script which sets only the Windows related paths and then calls the OBIEE start.cmd:
set PATH=C:\ProgramData\Oracle\Java\javapath;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem
call E:\Oracle\OBIEE\Oracle_Home\user_projects\domains\bi\bitools\bin\start.cmd
After this OBIEE started without any issues.
Guillaume, Great advice. Thank You!
ReplyDeleteGuillaume, many thanks. You saved me a couple of hours of figuring out what went wrong.
ReplyDeleteHi Ziga, thanks for the comment. I'm glad it's helped someone out.
DeleteThank you so much Guillaume, your solution worked for me.
ReplyDeleteThanks Siva
DeleteHi Guillaume slee,
ReplyDeletei got this error pls help me out
problem event name APPCRASH
Application Name sawserver.exe
reply soon
thanks in advance
Application version 12.2.1.0
Application Timestamp 5616f0d2
Fault module name nqutilitygeneric64.dll
Dear Guillaume Slee,
ReplyDeleteI go through your blog you have explained about nqsserver.exe has stopped working solution.
I am using OBIEE 12.2.1.0.0 in my Windows Server 2012 R2 Essentials.
When I start the BI services I got the pop up error message like given attached file.
But whatever you have explained about setting i.e., already set up in my environment. Still I am getting the same error when I stop and start the BI services.
Please could you help me about this.
Waiting for your kind reply.
Thanks and Regards-
Sadashiv
this problem happens with me. i was installing OBIEE 12.2 with Database 12.2.1, i changed the database to 12.1 , the problem cleared.
Delete"nqsserver.exe" has stopped working
ReplyDeleteProblem signature:
Problem Event Name: APPCRASH
Application Name: nqsserver.exe
Application Version: 0.0.0.0
Application Timestamp: 561bb059
Fault Module Name: nqsphysical64.dll
Fault Module Version: 12.2.1.0
Fault Module Timestamp: 561bbae4
Exception Code: c0000005
Exception Offset: 00000000000887b9
OS Version: 6.3.9600.2.0.0.305.50
Locale ID: 1033
Additional Information 1: eac0
Additional Information 2: eac091ce02a8d357122c8a4bd8873035
Additional Information 3: c026
Additional Information 4: c026b305eccedc7f5950a86cf806212a
Sadashiv, did you solve this - nqsphysical64 crashing?
DeleteThankyou
I have the same problem ,Fault Module Name: nqsphysical64.dll Did you resolved this?
DeleteGuys, did you install Admintool on the server?
DeleteHi Guillaume,
ReplyDeleteWe too got this error, but for us fault module name is bi_metadata_rt.dll.
The workaround you mentioned is not working for us.
Problem signature:
Problem Event Name: APPCRASH
Application Name: nqsserver.exe
Application Version: 0.0.0.0
Application Timestamp: 561bb059
Fault Module Name: bi_metadata_rt.dll
Fault Module Version: 6.3.9600.18202
Fault Module Timestamp: 569e7d02
Exception Code: c0000135
Exception Offset: 00000000000ecdd0
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1033
Additional Information 1: ac05
Additional Information 2: ac0507478d1c5bd693cfc4fe3987e900
Additional Information 3: ac05
Additional Information 4: ac0507478d1c5bd693cfc4fe3987e900
Do you have any idea on this issue.
Thanks,
Pratishtha
Did you fix this problem?
DeleteThanks Bruv! I've added a link to my blog! This saved me xxx loads of time!
ReplyDeleteThanks Steve, hope you're well
DeleteSyntax:
ReplyDeleteBusiness Intelligence Services
Excellent Design,Given Great Posting On Oracle Business Intelligence Then Go Through This Blog Started .
Someone found the solution for: Fault Module Name: nqsphysical64.dll?
ReplyDeleteI have win7 pro, Oracle DB XE, and obiee 12c, 8Gb Ram, Corei7.
For unknow reason, when I start services for obiee NQSSERVER.exe crashes.
Same as Sadashiv Dhulashetti15 March 2016 at 05:34 said.
Hi,
ReplyDeleteI am stuck with bi startup, starting all servers, not completed,
I am started this in manually then bi publisher not working, some times gets oracle business intelligence has stopped working,
APPCRASH
sawserver.exe
How to resolve these startup problem,
Please replay me,
Thanks,
Faulting application name: sawserver.exe, version: 12.2.1.2, time stamp: 0x57e5d2f9
ReplyDeleteFaulting module name: sawbedrock643r.dll, version: 12.2.1.2, time stamp: 0x57e5c663
Exception code: 0xc0000005
Fault offset: 0x00000000000259a5
Faulting process id: 0x1830
Faulting application start time: 0x01d332e44e6cf5c4
Faulting application path: D:\OBIEE12.2.1.2\bi\bifoundation\web\bin\sawserver.exe
Faulting module path: D:\OBIEE12.2.1.2\bi\bifoundation\web\bin\sawbedrock643r.dll
Report Id: 9d9de2b4-9efc-11e7-80d4-005056a315b3
Faulting package full name:
Faulting package-relative application ID:
Any clue what to do?
missing file bi_metadata_rt.dll.
ReplyDeletecopy and paste bi_metadata_rt.dll in \Oracle\Middleware\Oracle_Home\domains\bi\bitools\bin.
issue resolved.
thank you for sharing with us , keep
ReplyDeleteposting learn more about BI Tools Tableau Online Training
HI Guillaume,
ReplyDeleteYou are a champ!!
This comment has been removed by the author.
ReplyDeleteI enjoy what you guys are usually up too. This sort of clever work and coverage! Keep up the wonderful works guys I’ve added you guys to my blog roll. Surya Informatics
ReplyDeleteGreat idea its very informative and keep sharing Surya Informatics
ReplyDeleteMaking use of as many online tools as possible to promote the business or product intended is one way to start the enhancement of the marketing skills venture. click here
ReplyDeletePerde Modelleri
ReplyDeleteNUMARA ONAY
mobil ödeme bozdurma
NFT NASIL ALİNİR
Ankara evden eve nakliyat
trafik sigortasi
dedektör
Web Sitesi Kurmak
aşk kitapları
çekmeköy beko klima servisi
ReplyDeleteüsküdar samsung klima servisi
beykoz mitsubishi klima servisi
üsküdar mitsubishi klima servisi
pendik vestel klima servisi
tuzla samsung klima servisi
tuzla mitsubishi klima servisi
kadıköy daikin klima servisi
pendik beko klima servisi
We are facing this issue with OBIEE : Faulting application name: nqsserver.exe, version: 0.0.0.0, time stamp: 0x622fcdcf
ReplyDeleteFaulting module name: arora28.DLL, version: 8.0.2.2083, time stamp: 0x5a32af5c
Exception code: 0xc0000005
Fault offset: 0x00000000000972cb
Faulting process id: 0x2cd8
Faulting application start time: 0x01d8c0a3ab02e5f6
Faulting application path: C:\Oracle\Middleware\Oracle_Home\bi\bifoundation\server\bin\nqsserver.exe
Faulting module path: C:\Oracle\Middleware\Oracle_Home\bi\modules\oracle.bi.datadirect.odbc\8.0.2\Drivers\arora28.DLL
Report Id: 593eabf2-1de4-46ea-9a4f-fa1a5136b848
Faulting package full name:
Faulting package-relative application ID:
Good content. You write beautiful things.
ReplyDeletevbet
mrbahis
sportsbet
sportsbet
mrbahis
vbet
hacklink
korsan taksi
hacklink
başakşehir
ReplyDeletebayrampaşa
beşiktaş
beykoz
beylikdüzü
İOOİ
Samsun
ReplyDeleteUrfa
Erzincan
Mersin
Kayseri
WRİL
yalova
ReplyDeleteyozgat
elazığ
van
sakarya
D1İJX
adıyaman
ReplyDeletesakarya
yalova
tekirdağ
amasya
V2BD
394D1
ReplyDeletereferans
FD418
ReplyDeletepancakeswap
yearn
trust wallet
metamask
avax
poocoin
arbitrum
trezor suite
aave
D7EBD
ReplyDeletesatoshivm
phantom wallet
dexview
quickswap
dao maker
debank
dappradar
poocoin
pinksale
شركة مكافحة حشرات بالاحساء hqIaGqYk0M
ReplyDelete