This applies to OBIEE 11G logfiles.
When it comes to hunting down the source of a problem in OBIEE it is a good idea to go through the logfiles to see where an error has occurred. There are a number of OBIEE logfiles, with each component generating it own set.
Assuming that You have installed OBIEE with a middleware home of D:\OBIEE11G then
- the Administration Server has logfiles in: D:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\AdminServer-diagnostic.log
- the Managed Server has logfiles in: D:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\logs\bi_server1-diagnostic.log
- the BI Component logs are in: D:\OBIEE11G\instances\instance1\diagnositc\logs\*
- the OPMN logs are in: D:\OBIEE11G\instances\instance1\diagnositc\logs\OPMN\opmn\*
- the Enterprise Manager logs is in: D:\OBIEE11G\user_projects\domains\bifoundation_domain\sysman\log\emoms.trc
It may be worth putting a shortcut to these files / directories on your desktop.
Also helpful is wintail which allows you to view a logfile and all the writes being made to it without the constraints of notepad etc...
If you have configured windows services for AdminServer and bi_server1 under beasvc, then hopefully you configured them with a logfile. The logfiles from the services help in guiding you to any problems as they are the record of what you would normally see when starting OBIEE manually.
Until next time.