OBIEE Admin tool fails to start

Hi,
We have installed OBIEE 10.3.3.2 and app 7.9.4 in windows 2003 server. We will not start anything on this windows box, but will open the Administration and change rpd file in offline mode. But when I am going to Start->All Programs->OBI->Administration , it's throwing error message "The Application has failed to start because the application configuration is incorrect". I have uninstalled and reinstalled the entire application, but the same issue persist. All other applications like DAC client etc are coming up properly.
Any help or pointer to this issue will be highly appreciated.
Thanks,
Sudipto

I have read the README.txt file which suggests the port numbers might be in conflict. I have changed them several times in the "webcache.xml" file and this did NOT help. I don't think the problem is the port numbers.
What other conditions could cause this problem?
Also, I am not seeing any log files getting generated, but it does create a "core" file. This is on a 4-CPU Solaris box with lots of hard disk space and other physical resources, so I don't think it is a resource problem.

Similar Messages

OBIEE Admin Tool and Hyperion ADM issue

I'm trying to connect to one HFM Application from OBIEE admin tool, I have installed in Server1 OBIEE and ADM Link and Server2 HFM
Products Installed: OBIEE 11.1.1.7.0 (Win Server 2008 R2/ Server1), ADM Link 11.1.2.2 (Win Server 2008 R2/ Server1), HFM 11.1.2.2 (Win Server 2008 R2/ Server 2)
But i can't import metadata objects, in the connection I got this error message:
[nQSError: 77031] Error occurs while calling remote service ADMImportService. Details: Details: [[
Failed to connect to ADM.
com.hyperion.ap.APException: [1033] Native: -2147221164 Error Reference Number: {059E2017-60C8-42C7-855A-F165AF034A40}<BR>Num: 0x80040154;Type: 1;DTime: 11/6/2013 12:01:55 PM;Svr: TEST;File: CHITRegistryWrapper.cpp;Line: 24;Ver: 11.1.2.2.000.3609;<BR>Num: 0x80040154;Type: 0;DTime: 11/6/2013 12:01:55 PM;Svr: TEST;File: CHsxClient.cpp;Line: 4023;Ver: 11.1.2.2.000.3609;<BR>Num: 0x80040154;Type: 0;DTime: 11/6/2013 12:01:55 PM;Svr: TEST;File: HsvADMDriverSessionInternal.cpp;Line: 326;Ver: 11.1.2.2.000.3609;
at com.hyperion.ap.adm.HssEnvironment.createException(HssEnvironment.java:195)
at com.hyperion.ap.adm.HssConnSession.HssAdmGetErrors(HssConnSession.java:612)
at com.hyperion.ap.adm.HssConnSession.OpenConnection(HssConnSession.java:2544)
at com.hyperion.ap.adm.HssConnSession.HssConnOpenConnection(HssConnSession.java:923)
at com.hyperion.ap.adm.HssConnSessionWrapper.HssConnOpenConnection(HssConnSessionWrapper.java:1483)
at com.hyperion.ap.adm.HssAdm.openConnection(HssAdm.java:912)
at com.hyperion.ap.adm.HssAdm.internal_openConnection(HssAdm.java:1799)
at com.hyperion.ap.adm.HssAdm.openConnection(HssAdm.java:1065)
at oracle.bi.integration.admimport.service.ADMImportClient.openConnection(ADMImportClient.java:64)
at oracle.bi.integration.admimport.service.ADMImportService.openConnection(ADMImportService.java:159)
at oracle.bi.integration.admimport.service.ADMImportService.executeDataSources(ADMImportService.java:146)
at oracle.bi.integration.admimport.service.ADMImportService.execute(ADMImportService.java:67)
at oracle.bi.integration.javahost.ServiceRpcCall.processMessageInternal(ServiceRpcCall.java:55)
at com.siebel.analytics.javahost.AbstractRpcCall.processMessage(AbstractRpcCall.java:251)
at com.siebel.analytics.javahost.MessageProcessorImpl.processMessage(MessageProcessorImpl.java:193)
at com.siebel.analytics.javahost.Listener$Job.run(Listener.java:223)
at com.siebel.analytics.javahost.standalone.SAJobManagerImpl.threadMain(SAJobManagerImpl.java:207)
at com.siebel.analytics.javahost.standalone.SAJobManagerImpl$1.run(SAJobManagerImpl.java:155)
at java.lang.Thread.run(Thread.java:662)
My data connection are the folow:
Connection Type: Hyperion ADM
URL:adm:native:HsvADMDriver:SERVER:HFM_APLLICATION
User Name:admin
Password: xxxxxxxx
Please I hope someone can help me.

Login to Oracle Enterprise Manager Goto -> Business Intelligence -> coreapplication
Click - Capicity Managment Tab in Right side -> Performance -> Check Disable Disallow Online RPD Updates
http://docs.oracle.com/cd/E14571_01/bi.1111/e10541/querycaching.htm#BCGCACHF
If helps pls mark

ESSBASE + OBIEE Dashboards or OBIEE ADMIN TOOL + OBIEE Dashboards.

Hi all,
Hi all,
I am currently working on the proposal for a Financial BI reporting project for a company in the UK and would like to know the advantages of using ( ESSBASE + OBIEE Dashboards) solution over (OBIEE ADMIN TOOL + OBIEE Dashboards).
As the project has complex data model the client is insisting on Essbase; will ESSBASE give me more flexibility over BI Admin tool in data modeling and cube designing?
Appreciate your thoughts.
Regards
B
Edited by: Bees on Oct 27, 2010 9:32 AM

Hi,
OBIEE has infinitely superior reporting functionality to Essbase.
Essbase is absolutely excellent if you want to give your users data input and intuitive drill features. For financial projects Essbase is excellent for budgeting, planning, forecasting etc where you want a good deal of user input on a flexible and intuitive basis for data modelling from a large end user audience.
Essbase is a highly complimentary product for OBIEE as OBIEE fills its reporting needs, modelling Essbase cubes in the repository is brilliantly fast and Essbase' cubes create things like dimension hierarchies purely by dragging physical cubes into the business model layer.
11g features like asymmetrical drilling, ragged hierarchies etc could have been built with Essbase in mind - and MOLAP was definitely built with Essbase in mind.
I would recommend looking at the Oracle by Example for Hyperion (which has Essbase at its core) for a feel of what Essbase can do for you.
regards,
Robert.

Patching OBIEE Admin tool to 11.1.1.6.1

Hi I've successfully patched my OBIEE server on linux to 11.1.1.6.1 but I still need to work on my client(Administration Tool) on Windows, which remains 11.1.1.6.0, does the full OBIEE server patch on Windows will work for my client only? Or is there a standalone patch for the Administration Tool.

user483999 wrote:
is patch p13952743 required to upgrade the OBIEE Admin Tool on a PC ?I believe you are talking about upgrading the client tool on a standalone client only installation right? Based on what type of installation, you have done, you will need to go through different process. Refer to this article on MOS for complete details:
How to update the OBI client Tools with Patch 11.1.1.6.4 (Client Installers and MapViewer) [ID 1503872.1]
Thanks,
-A.Y

Upgrade OBIEE Admin Tool to 11.1.1.6.4

is patch p13952743 required to upgrade the OBIEE Admin Tool on a PC ?

user483999 wrote:
is patch p13952743 required to upgrade the OBIEE Admin Tool on a PC ?I believe you are talking about upgrading the client tool on a standalone client only installation right? Based on what type of installation, you have done, you will need to go through different process. Refer to this article on MOS for complete details:
How to update the OBI client Tools with Patch 11.1.1.6.4 (Client Installers and MapViewer) [ID 1503872.1]
Thanks,
-A.Y

OBIEE Admin Tool (11g) takes very long to start up

I am running on Windows 8.1, on a new, fairly powerful desktop machine, and launching the BI Admin Tool takes much longer than (I feel) it should. I haven't timed it but it's in the ballpark of 15-30 minutes. I double-click the shortcut and immediately I see a black console window with the title "BI Administration", but it takes such a long period of time to eventually open a GUI window. I can observe via Task Manager that the CPU appears to be utilized constantly during this startup time. Could I have something configured incorrectly? Any advice on solving this problem would be much appreciated.

Hi,
If you look at the certification matrix for OBIEE you will see the Admin Tool is currently not officially supported on Windows 8.1, for now it's only up to Windows 7 (and starting from Windows XP if not wrong).
Making it work on Windows 8.1 is a workaround (I remind I read it require the 32bit version even on a 64bit OS) so you can't complain if it's taking long or not working at all.
For a perfectly working Admin Tool stay on supported environment => use a virtual machine.

Unable to Open the OBIEE Admin Tool (RPD) 10.1.3.4.2 after Installation

Hi,
I have installed obiee 10g (10.1.3.4.2) in windows server 2008. After installing, when I tried to open the Admintool it is giving me the below error.
The application has failed to start because its side by side configuration is incorrect. Please see the application event log or use the command-line sxtrace.exe tool for more details
Restarting the machine also does not work. Presentation Services were not started. When tried to start the services, it is throwing error like asking to check the system log. Is this stopping Admin tool to open..?
What could be the wrong with presentation services. I havent changed anything. I have reinstalled and restarted the machine, still same problem
Please help...
Thanks in advance

HI,
I see there are totally 3 programs listed with the naming convention --
"'MS VC++ 2005 Redistributable(x64)"
"'MS VC++ 2008 Redistributable(x64) x86 9.0.30729.4148"
"'MS VC++ 2008 Redistributable(x86) x86 9.0.30729.4148"
I am not sure which one to uninstall and reinstall out of these listed programs.
Is this causing the issue to display error while opening the Admin tool ?
Please help with your inputs
Thanks

OBIEE Admin tool Crashing

We have two OBIEE environment running with the 11.1.1.6 version of OBIEE. We have developed a .rpd in one of the environment and able to run it in that envioronment. Using the Admin tool we have taken a copy of that .rpd file to an another enviornment . But when I am trying to open the .rpd file using the Admin tool it is gettting crashed.
We are seeing the following error in the Windows Eventviewer log.
Faulting application name: admintool.exe, version: 11.1.1.6, time stamp: 0x4f04f7b8
Faulting module name: nqutilitysslall.dll, version: 0.0.0.0, time stamp: 0x4f04fa78
Exception code: 0xc0000005
Fault offset: 0x000ac63f
Faulting process id: 0x1164
Faulting application start time: 0x01cef736470f2c7f
Faulting application path: D:\Oracle Business Intelligence Enterprise Edition Plus Clientnew\oraclebi\orahome\bifoundation\server\bin\admintool.exe
Faulting module path: D:\Oracle Business Intelligence Enterprise Edition Plus Clientnew\oraclebi\orahome\bifoundation\server\bin\nqutilitysslall.dll
Report Id: a19ffe92-6329-11e3-8a85-00188b0e12e9
Working Admin Tool Version 11.1.1.6.0.120104.1244.000
Crashing Admin Tool Version 11.1.1.6.0.120104.0152.000

I have installed the 11.1.1.6.12 version.
Still I am getting the same error
Faulting application name: admintool.exe, version: 11.1.1.6, time stamp: 0x5212398b
Faulting module name: nqutilitysslall.dll, version: 0.0.0.0, time stamp: 0x52123be0
Exception code: 0xc0000005
Fault offset: 0x000ac63f
Faulting process id: 0xc7c
Faulting application start time: 0x01cefa25a5fe94ea
Faulting application path: D:\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orahome\bifoundation\server\bin\admintool.exe
Faulting module path: D:\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orahome\bifoundation\server\bin\nqutilitysslall.dll
Report Id: 2d2d4a4c-6619-11e3-8e60-00188b0e12e9

Essbase dimension cannot loaded into OBIEE admin tools

Hi All,
I have some problem with my OBIEE..
I'm using OBIEE version 10.1.3.3.2 and Essbase version 9.3.1..
In my Essbase's, I've 4 dimensions..
Let say..Dimension A, Dimension B, Dimension C, and Dimension D (as the measure).
I've created a connection in my Admin Tools..but there is some problem here..
Only Dimension D was read at the Admin Tools...
Do anyone have a suggestion to solve this problem..??
Thanks..
Regards,
~V13N~

This is a known bug and not fixed till 11G of OBIEE so here is a work around!
Please follow these steps to resolve this problem:
1. On Windows machine where OBIEE Administrator is installed go to Start -> Run -> Regedit.
2. Choose File -> Export (save registry file to backup location).
3. Then expand:
\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
4. Look on right side of screen for the parameter named "MaxUserPort" and change the value to 65534.
5. If MaxUserPort is not defined, create a DWORD property under "Parameters" called "MaxUserPort" and set value to 65534.
6. Close registry file (saving changes).
7. restart the machine
8. open their existing rpd - delete the hyperion (essbase cube) from physical/logical/presentation
9. Save
10. Reimport the cube - drag & drop to create the logical model
11. The import should now show all expected dimensions and measures.
So check if Account is imported. (that was the original problem on why we were generating queries using Measures -which does not exist in the cube.)
NOTE:
If you have already tried to import a particular cube and did not get all the expected dimensions,
please drop the existing physical and logical objects related to this cube.
Then do a fresh import of the cube into the repository file.
12 . connect from Answers - check the queries in the log file for any errors returned from Essbase.

Obiee admin tool with Windows 8

Hi,
is there way to run obiee client admin tool under windows 8?
thanks

This installation will be logged here : \Program Files\Oracle\Inventory\logs\ check if its error'ing out or trace files will be helping.
No GUI when you running the runinstaller.exe and admin and compatible mode ? BTW What is your OS, Java and System config's
Also read through : http://techforum4u.com/entry.php/3498-Solution-For-quot-OBIEE-11-1-1-6-Installation-Fails-or-Hangs-At-Configuration-Progress-Step-quot
I have not installed or tried installing on Windows 8 so i would say may be installing a oracle vm with downgraded os version of windows 7/below and run the OBI client installation or wait until Oracle releases a supported installer version.
HTH,
SVS

WebLogic Admin server fails to start after reboot

Hi Gurus,
Weblogic Admin server won't start up after a server reboot. Note that weblogic was gracefully shutdown before the restart.
Also note that the following files were accidentally deleted after the reboot (but I don't think that should cause an issue..):
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT
/opt/shared/apps/hyperion/Oracle/Middleware/user_projects/domains/EPMSystem/servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
Looking at the AdminServer.log:
*####<Oct 11, 2012 11:27:53 AM EDT> <Critical> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969273846> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: weblogic.management.provider.EditFailedException:*
java.lang.AssertionError: weblogic.management.provider.EditFailedException:
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:79)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: weblogic.management.provider.EditFailedException:
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1754)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:83)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:233)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:155)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:27)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused By: org.xml.sax.SAXParseException: Premature end of file.
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
     at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
     at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
     at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
     at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:235)
     at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:284)
     at weblogic.xml.jaxp.RegistryDocumentBuilder.parse(RegistryDocumentBuilder.java:163)
     at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
     at weblogic.management.provider.internal.ConfigReader.convert(ConfigReader.java:106)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:70)
     at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:64)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTree(EditAccessImpl.java:1917)
     at weblogic.management.provider.internal.EditAccessImpl.loadBeanTreeFromPending(EditAccessImpl.java:1807)
     at weblogic.management.provider.internal.EditAccessImpl.ensureBeanTreeLoaded(EditAccessImpl.java:1740)
     at weblogic.management.provider.internal.EditAccessImpl.getCurrentDomainBean(EditAccessImpl.java:241)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.<init>(DomainRuntimeServiceMBeanImpl.java:76)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl$SINGLETON.getInstance(DomainRuntimeServiceMBeanImpl.java:68)
     at weblogic.management.mbeanservers.domainruntime.internal.DomainRuntimeServiceMBeanImpl.getDomainConfiguration(DomainRuntimeServiceMBeanImpl.java:132)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.initAppDeploymentRuntimes(DeploymentManagerImpl.java:239)
     at weblogic.management.deploy.internal.DeploymentManagerImpl.<init>(DeploymentManagerImpl.java:81)
     at weblogic.management.deploy.internal.DeploymentServerService.initializeDeploymentManager(DeploymentServerService.java:256)
     at weblogic.management.deploy.internal.DeploymentServerService.startAdminServerDeploymentService(DeploymentServerService.java:232)
     at weblogic.management.deploy.internal.DeploymentServerService.init(DeploymentServerService.java:154)
     at weblogic.management.deploy.internal.DeploymentPreStandbyServerService.start(DeploymentPreStandbyServerService.java:26)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274051> <BEA-000365> <Server state changed to FAILED>
####<Oct 11, 2012 11:27:54 AM EDT> <Error> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274053> <BEA-000383> <A critical service failed. The server will shut itself down>
####<Oct 11, 2012 11:27:54 AM EDT> <Notice> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274069> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274138> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.domainruntime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274140> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.edit .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMX> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274141> <BEA-149513> <JMX Connector Server stopped at service:jmx:iiop://3.56.11.196:7001/jndi/weblogic.management.mbeanservers.runtime .>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274146> <BEA-220028> <Web Service reliable agents are suspended.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebService> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274153> <BEA-220029> <Web Service reliable agents are shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <MessagingBridge> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274318> <BEA-200001> <The messaging bridge service has successfully shut down.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274426> <BEA-040308> <JMS service is suspending.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274506> <BEA-040107> <Undeployed 8 default connection factories.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JMS> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274510> <BEA-040015> <JMS shutdown is complete.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274530> <BEA-001144> <Force Suspending the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274536> <BEA-001146> <Force suspend of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274538> <BEA-001147> <Shutting down the JDBC service.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <JDBC> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274552> <BEA-001149> <Shutdown of the JDBC service completed.>
####<Oct 11, 2012 11:27:54 AM EDT> <Info> <WebLogicServer> <tnsq08041.energy.ge.com> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1349969274694> <BEA-000236> <Stopping execute threads.>
Kindly guide me with this. Thanks!
Edited by: Kent Pawar. on Oct 11, 2012 8:51 AM

Issue is :
Caused By: weblogic.management.provider.EditFailedException:
One probable reason can be some change made to the config.xml file . If you have previous backup for the config.xml file then try to replace the config.xml file and restart the server .
Another reason for this exception may be that there were some changes made to configuration through the Admin Console which were not activated completely and Admin Server was restarted . under this scenario weblogic will create a /pendig dir and have a config.xml file created there with the un-activated changes .
some workaround you can try to restore the Admin Server :
Under domain dir ,
\pending directory -- take backup and delete the dir .
Under Admin Server Dir :
data\store --- take backup and delete the dir .
thanks,
Sandeep

Open-vm-tools fail to start

Hi,
I installed open-vm-tools in my Arch x64 installation in VMWare Fusion, added it to rc.conf, but it resists to start properly and gives me a [FAIL] instead
[industrie13@arch64 ~]$ sudo /etc/rc.d/open-vm-tools start
:: Starting Open Virtual Machine Tools [FAIL]
[industrie13@arch64 ~]$ sudo /etc/rc.d/open-vm-tools restart
:: Stopping Open Virtual Machine Tools [BUSY]
ERROR: Module vmhgfs is in use
[FAIL]
:: Starting Open Virtual Machine Tools [FAIL]
Any hints? A re-install didn't help.

This happens to me to sicne I first installed Arch (kernel 2.6.34-1). I gave up on it since I seem to have shared folders regardless.
Meanhwile, In X the new open-vm-tools version seems to have problems dealing with mouse integration. It works intermittently, when before it used to work great. But clipboard sharing works great.
Kernel: 2.6.34-2
Last edited by marfig (2010-08-08 18:18:43)

OBIEE Admin Tool does not allow to modify any object

Hi,
I have this strange problem. I have OBIEE 11.1.1.6.2 client installed on my PC. I am trying to update RPD objects in offline/Online/MUD(I tried all three) mode but the Check Out button is greyed out for me. No matter what changes I do into Tools --> Utility, it stays greyed out. I have reinstalled the Admin tool again and but problem persist. I have admin rights on PC so privileges can't be an issue. From connection pool I can view the data or update the row count but can’t add/delete/modify anything else.
Any idea what’s wrong here? Any pointer for further research.
Thanks in Advance

Login to Oracle Enterprise Manager Goto -> Business Intelligence -> coreapplication
Click - Capicity Managment Tab in Right side -> Performance -> Check Disable Disallow Online RPD Updates
http://docs.oracle.com/cd/E14571_01/bi.1111/e10541/querycaching.htm#BCGCACHF
If helps pls mark

V5.2 Admin-Server fails to start HP-UX 11i

Hi,
I'am installing on HP-UX 11i and everything works fine except of the Admin server.
Executing the "start-admin" results in:
$ ./start-admin
SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 18:28
failure: server terminated (signal 10) (Interrupted system call)
failure: server initialization failed (Interrupted system call)
$
When i go to admin-serv/logs and have a look at the file "errors" all i see is:
[07/Apr/2004:16:55:32] info ( 9038): SunONE-WebServer-Enterprise/6.0SP3 B05/14/2003 18:28
[07/Apr/2004:16:55:32] catastrophe ( 9038): Server crash detected (signal SIGBUS)
[07/Apr/2004:16:55:32] info ( 9038): Crash occurred in NSAPI SAF admin40_check_ds_availability_init
Any help is very apprieciated.
Many thanks in advance.
Carsten

5.1SP3 works great on HP-UX.
5.2 will probably run well on HP-UX when 5.2SP3 is released (but first we need SP1 and SP2...)

Weblogic admin console fails to start when commons logging is used.

I have an application that requires commons logging.
I followed the instructions as per the documentation and other forum entries such as How to use log4j into weblogic 10.3 to add the commons logging jar from apache and the weblogic jar specified. Plus I set the system property for the LogFactory.
When I start up the application server I see messages as expected from my application. But when I start up the weblogic Admin console I get and exception and the console fails to start. I even tried to put the jars in my applicaiton instead of the domain/lib directory to try to iscolate the issue but still got issues with starting the Console.
Any ideas on why this is occuring?
See the error below:
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <----------------------------------------Retention Init()---------------------------------------->
####<May 19, 2010 4:16:04 PM EDT> <Notice> <Stdout> <TE001XU-CATOR1> <AdminServer> <Check Retention Schedule Setting> <<WLS Kernel>> <> <> <1274300164672> <BEA-000000> <Thu May 20 05:00:00 EDT 2010>
####<May 19, 2010 4:16:06 PM EDT> <Info> <Health> <TE001XU-CATOR1> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1274300166060> <BEA-310002> <81% of the total memory in the server is free>
####<May 19, 2010 4:35:03 PM EDT> <Info> <WorkManager> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301303146> <BEA-002901> <Creating WorkManager "consoleWorkManager" for module "null" and application "consoleapp">
####<May 19, 2010 4:35:17 PM EDT> <Error> <HTTP> <TE001XU-CATOR1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1274301317582> <BEA-101216> <Servlet: "AppManagerServlet" failed to preload on startup in Web application: "console".
java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: org.apache.commons.logging.LogConfigurationException: The chosen LogFactory implementation does not extend LogFactory. Please check your configuration. (Caused by java.lang.ClassCastException: weblogic.logging.commons.LogFactoryImpl cannot be cast to org.apache.commons.logging.LogFactory)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java:574)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:517)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:254)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.<clinit>(MBeanUtilsInitSingleFileServlet.java:23)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.servlet.AsyncInitServlet.createDelegate(AsyncInitServlet.java:44)
at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:98)
at weblogic.servlet.AsyncInitServlet.init(AsyncInitServlet.java:78)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:531)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1915)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1889)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1807)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54)
at weblogic.application.internal.BackgroundDeploymentService$2.next(BackgroundDeploymentService.java:373)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BackgroundDeploymentService$BackgroundDeployAction.run(BackgroundDeploymentService.java:277)
at weblogic.application.internal.BackgroundDeploymentService$OnDemandBackgroundDeployAction.run(BackgroundDeploymentService.java:336)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Thank you for replying. Yes that is the first place we looked and tried. Actually to be more specific we followed the instrcutions under: "How to Use the Commons API with WebLogic Logging Services" of the same link.
Are you thinking that maybe we are we missing a step somewhere else within the site?
Not sure if I was clear before but we are using Weblogic 10.3 and also tried up to version 10.3.3. And we get the same results.
We prefer to use the method with commons logging for our application.
One more specific here what we did on our last attempt.
1. added this to the startWeblogic script JAVAOPTIONS -Dorg.apache.commons.logging.LogFactory=weblogic.logging.commons.LogFactoryImpl
2. we put the WebLogic-specific Commons classes, $BEA_HOME/modules/com.bea.core.weblogic.commons.logging_1.3.0.0.jar, together with the commons-logging.jar file in one of the following locations: APP-INF/LIB or WEB-INF/LIB directory or DOMAIN_NAME/LIB directory server CLASSPATH
We are still not able to get the Weblogic admin console to start
Any other ideas?
Edited by: user13094648 on May 21, 2010 10:29 AM
Edited by: user13094648 on May 21, 2010 10:37 AM

OBIEE Admin tool fails to start

Similar Messages

Maybe you are looking for