OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server

Hi,
We are working on BPC 7.0NW. Recently we encountered the below error while we login to BPC for Admin. Earlier it was working fine. We didnt do any major configuration or changes to the system. Not sure why we are getting this error suddenly. Please suggest how we can resolve this error.
Error popup- 'OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server'
thanks/regards,
Lokesh Nandula

Hi Lokesh,
Please try out the following option. Not sure whether it will work or not.
Go to Server manager on the app box.
delete the encryption key. (backup first if you like)
re-create the encryption key
register msolap90.dll on both servers
I don't have the text for this handy. I think it's: regsvr32 "C:\xxx\xxx\xxxx\xxx\msolap90.dll"
Note: you must use the quotes!
reboot the DB box
reboot the App box
or
To register the DLL Follow the below steps:
1) From the Application server go to the run option in the start menu and enter the below command
2) regsvr32 "c:\program files\common files\system\ole db\msolap90.dll"
3) Hit Enter
4) You should get a confirmation that the Dll was registered
Hope this helps.

Similar Messages

  • System Exception:OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin

    Hi Experts,
    While logging into the BPC admin client, we are facing the following errors:
    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: OSoftResSvrAdm.Handle Creat ActiveX Object Error at Admin Server
       at OSoft.Services.Webservice.AdminMainService.AdminMainService.GetText(Int64 intStringNum, String& strReturnString, String sParam1, String sParam2, String sParam3, String sParam4, String sParam5)
       at OSoft.Services.Webservice.AdminMainService.AdminMainService.LoadRes()
       at OSoft.Services.Webservice.AdminMainService.AdminMainService..ctor()
       --- End of inner exception stack trace ---}
    We have been facing this issue since the time the server was restarted after changing the admin password.
    Please help us in resolving this issue.
    Thanks in advance.
    Meera

    So you changed the pwd for installation user of SAP BPC.
    After you performed this change did you open Server Manager and go to Reset Credential link?
    There you have to input the new pwd for installation user.
    After that try to login again using BPC client.
    Regards
    Sorin Radulescu

  • How to create Activex object for my Visual C++ object

    Hi,
    I am working on development on Acrobat 9.0 SDK. I am facing problem is that I can compiled Visual C++ source code to an api. I can test functions on this api on Acrobat 9.0 windows, but I could not test it on IE web browser, because I don't know how to create Activex object from my Visual C++ source code or its api.
    I read Acrobat 9 SDK document and found under C:\Acrobat 9 SDK\Version 1\PluginSupport\Tools\Visual Studio App Wizard has two files: Acro9PIWizInstaller.msi and setup.exe. I am not very sure those file are the key to help me to create Activex objects for my api.  Are they the one I need to create Activex object? If not, could you please advise me how to create Activex object for my api or C++ codes.
    Thanks a lot for any of your comments or advices.
    Thai

    Hi lrosenth,
    Thanks a lot for your information.
    My question is, on Javascript how do I call a function from .api. Below is my very simple test.
    I got a function on BasicPlugin.cpp under C:\Acrobat 9 SDK\Version 1\PluginSupport\Samples\BasicPlugin. See below.
    I added BasicPlugin.api on C:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins
         ACCB1 int ACCB2 MyPluginCommand() {
              int num = 5;
              return num;
    On my HTML file, I create an <Object> below:
        <OBJECT id="acrobatapp"
                classid="clsid:85DE1C45-2C66-101B-B02E-04021C009402">
        </OBJECT>
        <OBJECT id="acrobatpdf"
                classid="clsid:CA8A9780-280D-11CF-A24D-444553540000"   >
            <Param name="SRC" value="http://www.adobe.com/devnet/acrobat/pdfs/acrobat_digital_signature_appearances_v9.pdf">
       </OBJECT>
    On my Javascript. I call function MyPluginCommand() as below, but it is not working. How do I call function MyPluginCommand() on Javascript?
         var acrobatapp= document.getElementById("acrobatapp");
         var num= acrobatapp.MyPluginCommand();
         alert(num);
    Thanks for your support,
    Thai

  • Is LabVIEW able to create ActiveX Object for other sw to use?

    I would like to create some ActiveX object from LabVIEW that VB could use it. How do I do it? I only find info about labVIEW use ActiveX created by other SW. Please let me know if LabVIEW has such ability. Thanks.

    You cannot create a new kind of ActiveX object in LabVIEW, but you can use ActiveX to control LabVIEW (or a LabVIEW-built EXE) and run your VIs programmatically from other development environments.
    Below is a modified excerpt from an example provided by NI on running a LabVIEW VI from Visual Basic:
    Dim lvapp As Object
    Dim vi As Object
    Dim paramNames(4), paramVals(4)
    Set lvapp = CreateObject("LabVIEW.Application")
    viPath = lvapp.AppDir + "\examples\apps\freqresp.llb\Frequency Response.vi"
    Set vi = lvapp.GetVIReference(viPath)
    vi.FPWinOpen = True
    paramNames(0) = "Amplitude"
    paramNames(1) = "Number of Steps"
    paramNames(2) = "Low Frequency"
    paramNames(
    3) = "High Frequency"
    paramNames(4) = "Response Graph"
    paramVals(0) = cwnAmplitude
    paramVals(1) = cwnNumSteps
    paramVals(2) = cwnLowFreq
    paramVals(3) = cwnHighFreq
    ' paramVals(4) will contain the value of Response Graph after running the vi.
    Call vi.Call(paramNames, paramVals)

  • Certificate error while admin server startup (solaris 8, wls 8.1.4)

    HI All,
    I am getting the following error while starting up my admin server using startWebLogic.sh.
    <Feb 5, 2010 7:51:19 AM GMT> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server "BOS1-ADMIN" for domain "BOS1">
    java.io.IOException: Inconsistent security configuration, Certificate expired: [
    Version: V3
    Subject: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
    Key: com.sun.net.ssl.internal.ssl.JSA_RSAPublicKey@672
    Validity: [From: Thu Feb 03 11:25:08 GMT 2005,
    To: Tue Feb 02 11:25:08 GMT 2010]
    Issuer: EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00
    Certificate Extensions: 3
    [1]: ObjectId: 2.5.29.14 Criticality=false
    SubjectKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    [2]: ObjectId: 2.5.29.35 Criticality=false
    AuthorityKeyIdentifier [
    KeyIdentifier [
    0000: E9 1E E1 30 86 89 7E 1A 67 A2 58 5B 9D 8A 9E 7A ...0....g.X[...z
    0010: C1 CF C4 DA ....
    EMAILADDRESS=******************, CN=***********, OU=********, O=************, L=*******, ST=*******, C=**
    SerialNumber: 00]
    [3]: ObjectId: 2.5.29.19 Criticality=false
    BasicConstraints:[
    CA:true
    PathLen:2147483647
    Algorithm: MD5withRSA
    Signature:
    0000: 74 15 DF 05 54 27 1D 1D D5 35 F4 99 24 1A 84 1C t...T'...5..$...
    0010: BF 93 25 FA 50 D7 1E 36 66 7F 30 1A EF 67 2A 79 ..%.P..6f.0..g*y
    0020: 4A 72 FD C1 3B 33 05 61 D0 52 92 2D 15 89 68 67 Jr..;3.a.R.-..hg
    0030: E8 13 A6 60 18 38 16 53 16 22 CC 4D 87 19 9F 30 ...`.8.S.".M...0
    0040: 28 F3 3C C0 4C C2 C4 34 69 D3 BA 5C B2 4D 8A FF (.<.L..4i..\.M..
    0050: AA DD BD 04 96 AF 69 05 73 77 8D 93 89 90 5D 23 ......i.sw....]#
    0060: E9 D0 CA 02 5A 20 39 40 85 12 A9 67 04 ED 7B 59 ....Z [email protected]
    0070: 34 FB 31 E7 AD F6 C0 AE E4 5E 66 BB 8E 7D 45 72 4.1......^f...Er
    at weblogic.t3.srvr.SSLListenThread.initSSLContext(SSLListenThread.java:205)
    at weblogic.t3.srvr.SSLListenThread.<init>(SSLListenThread.java:139)
    at weblogic.t3.srvr.T3Srvr.initializeListenThreads(T3Srvr.java:1637)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:890)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
    at weblogic.Server.main(Server.java:32)
    Any thoughts to share mates????
    I have already posted this topic in general discussion forum and as suggested by faisal posting here as well..Please let me know how to renew certificates????
    Cheers,
    Dinesh

    Hi Dinesh,
    Below are the steps to renew / get new certificates.
    Step A -- Create a Keystore file
    1. Using keytool, enter the following:
    keytool -genkey -alias server -keyalg RSA -keystore your_domain.jks
    'your_domain' in the command above should be the name of the domain you are securing. If you are ordering a Wildcard Certificate, do not include the * in the filename as it is not a valid filename character.
    2. You will be prompted to enter the information for your certificate.
    Please note: When prompted for the first and last name, DO NOT enter your first and last name. Instead, enter the name to which the certificate is being issued (e.g., www.yourdomain.com, mail.yourdomain.com, *.yourdomain.com).
    3. When prompted, enter 'y' or 'yes' to confirm. You will next be asked for a password. You will need to use this same password when generating a CSR and importing your certificates.
    Step B -- Generate a CSR from your new keystore
    1.     Use keytool to create a Certificate Signing Request from your keystore:
    keytool -certreq -alias server -keyalg RSA -file your_domain.csr -keystore your_domain.jks
    Again, 'your_domain' is the name of the domain you are securing. (without the * character if you are ordering a Wildcard Certificate).
    2.     Enter the keystore password.
    3.     Submit the CSR to the Certificate Authority for the certificates.
    Step C: Import and Install the Certificates.
    1.     First you will need to install the Root CA Certificate into your keystore. Copy-and-paste the root certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as trustroot.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the root certificate geotrustroot.pem into your keystore using the following command:
    keytool -import -alias geotrustca -keystore mykeystore -file geotrustroot.pem
    The command should be typed on one line. This command imports the GeoTrust Root CA Certificate into the keystore named mykeystore.
    Step D: Import and Install the SSL Server Certificate
    1.     Next install your SSL Server Certificate (public key) into your keystore. Copy-and-paste the server certificate from the body of the fulfillment email into a simple text editor such as Notepad.
    2.     Save the file to your server as public.pem in the same directory where your keystore was created.
    3.     Using the java keytool command line utility, import the SSL server certificate public.pem into your keystore using the following command:
    keytool -import -alias tomcat -keystore mykeystore -file public.pem
    The command should be typed on one line. This command imports the SSL server certificate into the keystore named
    mykeystore.
    Step E: Configuring Keystores
    1.     Both the GeoTrust root CA and SSL server certificates are now installed on your server. Next you will need to configure the keystores by following the instructions in the WebLogic documentation section Configuring Keystores.
    2.     Restart the WebLogic server.
    Hope the information helps.
    Regards,
    Raj

  • Problem creating a domain w/ one Admin Server and Managed Server

    I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error:
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-280061> <The persistent store "pfProliferationJMSStore" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource portalFrameworkPoolNeverXA: javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328289> <BEA-141197> <The deployment of pfProliferationJMSStore failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.naming.NameNotFoundException: Unable to resolve 'portalFrameworkPoolNeverXA'. Resolved ''; remaining name 'portalFrameworkPoolNeverXA'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:251)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:205)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:100)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <JMS> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-040123> <Failed to start JMS Server "pfJMSServer" due to weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist.
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Warning> <Management> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328368> <BEA-141197> <The deployment of pfJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server pfJMSServer: weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:198)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.management.DeploymentException: The persistent store "pfProliferationJMSStore" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:296)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:184)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:237)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:590)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:451)
         at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:431)
         at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:97)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Deployer> <BLUDAF222452> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1217466328461> <BEA-149231> <Unable to set the activation state to true for the application 'pf-proliferation-jms'.
    weblogic.application.ModuleException: ERROR: Could not activate pf-proliferation-jms!pfProliferationQueue
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    weblogic.messaging.kernel.KernelException: The Messaging Kernel pfJMSServer has not yet been opened
         at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
         at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
         at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1633)
         at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
         at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1809)
         at weblogic.jms.backend.BEDestinationImpl.start(BEDestinationImpl.java:609)
         at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:235)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1717)
         at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
         at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
         at weblogic.jms.module.JMSModule.activate(JMSModule.java:332)
         at weblogic.jms.module.ModuleCoordinator.activate(ModuleCoordinator.java:182)
         at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:42)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:187)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >

    I am using the default db the installation uses which is PointBase. I am not using any specific db, JDBC Datasource/Connection pool Configuration.
    Just to try something different, I tried creating a domain w/ one Admin and Managed Server which uses a Cluster and I did not get any errors. From what I read, a cluster is not necessary but not sure why it works without errors w/ a cluster.
    I will try commenting out the datasource from the config and see what happens and will let you know.

  • Error starting Admin Server in a OSB Cluster installation

    Greetings
    I have an environment with two osb nodes in cluster, when I start the Admin server the server start succesfully and the osb servers also works fine, but I got the following messages starting the admin server:
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    I am worried because I see in the deployment screen that the applications File Transport Provider, SFTP Transport Provider, Ftp Transport Provider and Email Transport Provider are not running.
    How can I solve this issue?
    My installation is osb 11.1.1.6 and my operating system is solaris 11 (64 bits)
    Thanks!

    Hi Charan,
    if your ManagedServers are not in Configured for MSI Mode (Managed Server Indepence Mode) then you wont be able to start your Servers until the AdminServer is Already Running. I can see that the Exception u pasted that...your AdminServer is not reachable....It may be due to AdminServer Vs ManagedServer BOX Network Issue or Your AdminServer might be down when u tried to start the ManagedServer.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

  • Error Installation Admin Server

    Hi All,
    i've tried to install Directory und AdminServer JES2.
    I'm getting the following error after the installtion of the packages:
    Configuration of the server(s) succeeded.
    Directory Server Configuration Succeeded ...
    Configuration succeeded for : DirectoryServ32
    *** End configuring DirectoryServ32***
    *** Start configuring AdminServ... ***
    AdminServConfigurator::configure() called ...
    Command //usr/sbin/mpsadmserver configure -f /tmp/adminserv.statefile generated the follwing outputs :
    Output Log:
    The UNIX user and group specified in the Server Root (/var/opt/mps/serverroot)
    do not match values from silent installation configuration file.
    Admin Server Configuration Failed ...
    Configuration failed for : AdminServ
    *** End configuring AdminServ***
    where do i have to look?
    thanks

    Are you installing DS as non root and AS as root? Then it might be bug 5040383.
    If so, you can install as root and follow the instructions in the bug how to change it back later.
    Also you can open a case so we can add the customer to the bug report.

  • Task TS16900003 - Create NB object Error

    Hi                                                                               
    We are using the Extended Requisition Request form - SRQ2, Notification.  The Hiring Manager sends the form successfully with a notification number. The approver approves the form. After this step, the workflow generates an error on the Task - TS16900003.     
    Error message:           
    CL_HRMSS_RECRUITING_WF method CREATENBOBJECT cannot be executed.  "Requisition object NB has been created in EREC System for form".  However, this statement is incorrect as the requisition object NB is not created. 
    WF-Batch user has a CP & NA created and has the correct authorisations.
    We are on SAP ECC 6.0
    Your assistance will be highly appreciated.
    Regards.
    Bongisa

    Hi Divya
    Thank you for your response.
    WF-BATCH has a BP, CP, NA & P linked. The error is still generated.
    "Object CL_HRMSS_RECRUITING_WF method CREATENBOBJECT cannot be executed"
    Hope you can assist further.
    Regards.
    Bongisa

  • Failed to read parameter object error in BO server XI

    We have the enterprise edition of Business Objects server XI, which is available in the Solaris 10 machine. We try to upload the rpt file using the Central  Management Console Log in, at the time we got the following error.
    There was an error while retrieving data from the server: Failed to read data from report file /var/tmp/data_gen_letter.rpt63065d888163420.  Reason: Failed to read parameter object.
    Can anybodies help me on this, why this error has came.
    Thanks in advance.
    Regards,
    Vel.

    Hi,
    the problem has to do with the permissions on dynamic prompts. Eventually you can solve this by setting the permissions on the prompts using the Business View Manager. (CrystalBVM.exe: to be found in BOBJ client installations on windows)
    Do your report fetch data from an SAP R/3 system?
    Regards,
    Stratos

  • Problem in creating the ADODB.Connection object Error Number returned:-2147024770

    Hi,
    We are migrating our applications from Windows 2003 to 2008 application server. We have vbs script in a job which is invoked from Tivoli Workload Scheduler (Windows)/JOBLNCH 8.5.1. We are getting the error while creating ADOBD object (Error Number returned:-2147024770).
    The error does not occur when we directly run the job on the 2008 server, but only when invoked throught the TWS scheduler. Also, this error is not occurring on 2003 server when run through the TWS.
    Here is the code snippet used to create object.
    set oSrcConnect = CreateObject("ADODB.Connection")
    Could you please help us identify if any settings need to be changed to avoid this error. Many Thanks for looking into the question.

    Hi,
    Error -2147024770 = hex 8007007E
    Least significant 32 bits are hex 7E = decimal 126
    C:\>net helpmsg 126
    The specified module could not be found.
    This usually indicates that the COM object you're using is trying to load a DLL that is not installed.
    Based on only this error message, there's no way we can tell you how to fix your script.
    Bill

  • Lock Object error during batch load

    Batch load was delayed about an hour. First error message in the Server Log said "Object is already locked by user""Error 1053010 processing request [Lock Object]-Disconnecting"Then it went through a series of "Object locked by user admin" and "received client request: create Temporary Object(from user admin)"It did this several times until connection.Although from time to time we have had problems with Objects getting locked and preventing maintenance in the Application Manager. This is the first time that is has prevented a batch load. Does anyone know what could have triggered this during the load process?

    This happened to us a lot, I think it's due to people opening objects, then letting their session time out, leaving a phantom lock.We solved the problem by calling the UNLOCKOBJECT function before any dimbuilds. 99.9% of the time this raises an error, "..object x is not locked..", but the rare time that the otl is inadvertently locked, it prevents the script from failing.<br><br>HTH,<br><br>Jeff McAhren<br>Dallas, Texas<br><br>ex to unlock the outline for app/db flash:<br><br>UNLOCKOBJECT 1, "FLASH" "FLASH" "FLASH"

  • Cannot Create Automation Object

    Hi All,
    I have essentially two problems are occuring the first is with Crystal
    Reports 8.5 whereby running reports simeltaneously, one after the other
    after the other, will intermittently after the 3rd or 4th report cause
    windows to lock up and Notes 8 client will start to consume upwards of 100mb
    of ram (in a minimum 1.25gb ram machine) and then 98-99% CPU Usage.
    Assuming this was a problem with an older version of Crystal Reports, we
    have upgraded and tested both Crystal Reports 9 Professional and Crystal
    Reports 12 and thats where the "cannot create automation object" has
    occured - this particular error will happen whenever we attempt to run any
    report what so ever
    Now that we've upgraded to Crystal Reports 9.0 Pro, we'd like to try and solve
    the "cannot create automation object" error message we receive.
    Have tried to communicate this problem with IBM, they insist the problem is crystal
    related and not a problem with lotus notes.
    Environment:
    1. Lotus Domino Server, Release 8.0 for Windows/32
    2. Windows 2003 Server (x86 edition) Service Pack 2
    3. IBM Lotus Notes Version 8
    4. Windows XP w/Service Pack 3
    5. Symantec AntiVirus Full Version 10.1.5.5000
    5a. Crystal Reports 9 for Reporting
    Fault:
    1. First Observed 18/07/2008
    2. See above description
    3. For the first problem with Crystal Reports version 8.5 - we upgraded our
    client and server in test environment to Domino 8 and Notes 8 from Domino
    6.5 and Notes 6.5, for the second problem it occured after we upgraded from
    Crystal Reports 8.5 to Crystal Reports 9 & 12 versions.
    4.  Reinstalled Crystal Reports 8.5, no effect on first problem, installed
    version 12 (from IBM website), second error, un-installed, reinstalled 8.5,
    first error reappeared, reinstalled version 12 complete installation, same
    problem (second error) uninstalled and installed version 9 trial and same
    problem (second error)
    Any help would be greatly appreciated.

    Is this happening in the Report Designer or in an application?
    Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
    http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

  • Weblogic admin server error.

    Hi Team,
    I am trying to started weblogic admin server from windows i am getting below error from admin server logs.
    but I am able to start weblogic from the command prompt.
    I verified classpath are same in command prompt and windows services and Node Manager also working fine from windows services.
    Please help me on this.it is urgent for me .
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000436> <Allocating 2 reader threads.>
    ####<Nov 14, 2012 8:31:26 PM GMT+05:30> <Info> <Socket> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905286929> <BEA-000446> <Native IO Enabled.>
    ####<Nov 14, 2012 8:31:27 PM GMT+05:30> <Info> <IIOP> <mindview> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905287039> <BEA-002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288695> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288898> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_9V5rIdcvntKDauQNwFIW41HchnU=>
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Info> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090511> <The following exception has occurred:
    com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Error> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified..
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:341)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.ServiceInitializationException: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: com.bea.common.engine.SecurityServiceRuntimeException: [Security:097533]SecurityProvider service class name for IAMSuiteAgent is not specified.
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:42)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)
         at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:46)
         at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:299)
         at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:220)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1785)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:28 PM GMT+05:30> <Notice> <Security> <mindview> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1352905288992> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Critical> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289023> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:916)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FAILED>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Error> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Notice> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Nov 14, 2012 8:31:29 PM GMT+05:30> <Info> <WebLogicServer> <mindview> <AdminServer> <main> <<WLS Kernel>> <> <> <1352905289039> <BEA-000236> <Stopping execute threads.>
    Thanks in advance.
    Regards,
    Ravi.

    Hi,
    Check this link :
    Re: myrealm error when start through node manager

  • Error 500--Internal Server Error in a Project Gantt Chart portlet

    Hi All
    I am getting Error 500--Internal Server Error in a Project Gantt Chart portlet of Corporate Dashboard.
    We have recently installed the Primavera EPPM 8.1, here are the steps we followed to setup the Primavera EPPM 8.1
    1) We have created the database schemas by using automatic database setup(by clicking on dbsetup.bat on the media files)
    2) Installed Weblogic server 11gR1(10.3.4)
    3)Created web logic domain as admin server
    4) Installed P6 Web access and deployed on weblogic domain
    5)Made changes to setEnvDomain file of weblogic domain to increase the Java Heap size and to locate the location of p6.war file
    6)Reastred the weblogic domain
    Now we can access the Primavera but in one of the portlet we are getting Error 500--Internal Server Error.
    Please le me know if I miss any thing while installing or should I modify P6 configuration settings through p6 admin confiuration console.
    Also it would be greatful if any one provide me th best practice to setup Primavera EPPM 8.1.
    Thanks & Best Regards
    Pradeep

    Hello Pradeep
    please delete a folder called fmwconfig in the path yourdomain\config\ for a folder called fmwconfig
    restart P6 and try again

Maybe you are looking for