User Profiles Synch Service starting failes after "ILM Configuration: Starting services"

Hello guys.
I tried to configure user profiles synchronization and it could not be started without any problems as expected :)
This time I got the following error in logs:
02.05.2013 10:54:03.34 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9q1k
Medium ILM Configuration: Starting services.
0160471f-15fc-4d97-8227-05b86f4d0fc7
02.05.2013 10:54:33.52 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9q15
High UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size
of the argument list.     at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)     at System.String.Format(IFormatProvider provider, String format, Object[] args)     at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.IsStarted(ServiceController
controller)     at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.WaitUntilStarted()     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance
profileSyncInstance). 0160471f-15fc-4d97-8227-05b86f4d0fc7
02.05.2013 10:54:33.52 OWSTIMER.EXE (0x17DC)
0x183C SharePoint Portal Server
User Profiles 9i1u
Medium UserProfileApplication.SynchronizeMIIS: End setup for 'UserProfilesService'.
0160471f-15fc-4d97-8227-05b86f4d0fc7
So, what I have and what I've done:.
1) I have a test 2-servers farm installation (Database server + WFE/Application server); SQL Server 2008 R2 SP2, SHP 2010 SP1 + October 2012 CU; There are no any service applications except default ones(Security Token Service and Application Discovery
and Load Balancer Service Application) as well as there are  no any services started except default :) 
2) I created a site collection and manage path for MySites, created a new UPA and its proxy.
That's all. Now, if I try starting User Profiles Synchronization Service, it stucks on "starting" for about 10 mins and I see the error above in ULS. Hope you can somehow help me.
By the way, I don't want a both sides synchronization this time, I just need to check some stuff with People Search. Will "Read" rights for Managed Account in AD be enough to export profiles from AD? (I mean if I select my farm account as a synchronization
account, will it work?)
Thank's in advance!
Anton.
UPDATED
The problem probably was due to the lack of internet access. As Raymond
Diack said:
"the farm account needs internet access to do a CRL check to these sites:
crl.microsoft.com
ctldl.windowsupdate.com
ctldl.windowsupdate.nsatc.net
www.update.microsoft.com.nsatc.net "

Sure, here is the stack near the error without any filters: 
11:13:11.88 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q1j Medium ILM Configuration: Opening firewall ports. 589d9196-6647-4432-9ab0-a389871310b7
11:13:12.13 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q1k Medium ILM Configuration: Starting services. 589d9196-6647-4432-9ab0-a389871310b7
11:13:12.36 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:80a1f95b-37a3-45f1-89a6-f33de57b678a'
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:80a1f95b-37a3-45f1-89a6-f33de57b678a' 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.36 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.38 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=4,01622273221876 75b52d1d-0e9e-45a6-8122-c578bc8aeaf7
11:13:12.75 OWSTIMER.EXE (0x0AA8) 0x16F0 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job job-timer-locks) ea70e10e-4455-47ea-a3fd-e7cb0f0a9ce4
11:13:12.75 OWSTIMER.EXE (0x0AA8) 0x16F0 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job job-timer-locks). Время выполнения=4,16512433842849 ea70e10e-4455-47ea-a3fd-e7cb0f0a9ce4
11:13:22.52 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:5b799d56-3784-48ff-beaf-6fb6bfeade78'
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:5b799d56-3784-48ff-beaf-6fb6bfeade78' 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 941bbfb5-84aa-411e-b310-74830120b860
11:13:22.52 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=2,92432418086656 941bbfb5-84aa-411e-b310-74830120b860
11:13:26.78 OWSTIMER.EXE (0x0AA8) 0x0894 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job SchedulingUnpublish) 6044b3fe-8ca7-4f76-81b0-ea55e6795d5b
11:13:26.78 OWSTIMER.EXE (0x0AA8) 0x0894 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job SchedulingUnpublish). Время выполнения=2,56094000773841 6044b3fe-8ca7-4f76-81b0-ea55e6795d5b
11:13:32.66 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:f5648c05-71d7-443c-b12d-946eb36bcb3f'
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:f5648c05-71d7-443c-b12d-946eb36bcb3f' 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.66 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.71 w3wp.exe (0x0788) 0x1544 SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:32.72 w3wp.exe (0x0788) 0x1544 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=65,7127512016192 1af7e327-bb71-49f8-a598-2e85ae5ce2a6
11:13:39.79 OWSTIMER.EXE (0x0AA8) 0x0500 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (Timer Job SchedulingApproval) 69e34469-a502-4257-80f4-d8fb990f2bf7
11:13:39.80 OWSTIMER.EXE (0x0AA8) 0x0500 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Timer Job SchedulingApproval). Время выполнения=11,6191443325898 69e34469-a502-4257-80f4-d8fb990f2bf7
11:13:40.33 w3wp.exe (0x1364) 0x0E98 SharePoint Portal Server Runtime 8gp7 Medium Topology cache updated. (AppDomain: /LM/W3SVC/961767364/ROOT-1-130050376913614507)
11:13:42.88 w3wp.exe (0x1364) 0x0CA0 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://hq-tcc-app-02:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:23bdd02e-0716-4697-b55d-55862694ebe1'
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://hq-tcc-app-02.corp.fsk-ees.local:32843/900539dde24c4bc9a0db06a9f9fe6ebf/MetadataWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:23bdd02e-0716-4697-b55d-55862694ebe1' c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc5 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' starting. c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Server Taxonomy fuc6 Medium MetadataWebServiceApplication.GetChanges called on 'Служба управляемых метаданных' completed. c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 w3wp.exe (0x0788) 0x0D2C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (ExecuteWcfServerOperation). Время выполнения=2,88158131829604 c7b0b8bc-dad4-4863-98e0-92838dafa933
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9q15 High UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.     at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)     at System.String.Format(IFormatProvider provider, String format, Object[] args)     at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.IsStarted(ServiceController controller)     at Microsoft.Office.Server.Administration.ProfileSynchronizationServiceInstance.WaitUntilStarted()     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance). 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Portal Server User Profiles 9i1u Medium UserProfileApplication.SynchronizeMIIS: End setup for 'UPS'. 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.89 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. Version: 15232 Ensure: False, HashCode: 11248478, Id: c8e4ed56-ab72-4b99-8532-d282d3f26896, Stack:    at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()     at Microsoft.SharePoint.Administration.SPJobDefinition.Update()     at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)     at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)     at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result) 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.92 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (Timer Job ProfileSynchronizationSetupJob). Время выполнения=161321,353202712 589d9196-6647-4432-9ab0-a389871310b7
11:13:42.96 OWSTIMER.EXE (0x0AA8) 0x0EA8 SharePoint Foundation Topology 8dyx High Deleting the SPPersistedObject, ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. 589d9196-6647-4432-9ab0-a389871310b7

Similar Messages

  • Javascript web service calls fail after 10.1.5/11.0.01 updates

    * Update #2 - I've confirmed that we are seeing errors because the HTTP request is being made as a POST using 10.1.5/11.0.01 in Chrome/Firefox/Safari.  Accessing the same file in IE, the request is made using a GET.  Using Reader 9.5.0 in Chrome also uses a GET.  Can someone please explain why the HTTP request is being submitted as a POST following the 10.1.5 update?
    * Update - I have found in my web service log that it is failing with a message that the attempted POST method is not allowed. Could the Reader updates be causing this call to be made as a POST when it was previously a GET?
    I am using PDFs with Reader Extensions enabled that make web service calls via javascript.  These calls have been working correctly in multiple environments for months and only began failing with the latest updates.  After the latest Reader updates, these calls fail when using Chrome, Firefox and Safari. 
    Internet Explorer works correctly.  Saving files locally and opening them in Reader also works correctly.  It is only running 10.1.5 or 11.0.01 in these specific browsers where this issue occurs.  10.1.4 and 11.0.0 do not experience this issue in any browsers. 
    I have tried disabling Enhanced Security and updating Trust Manager to allow Internet Access from PDFs.  Neither change corrected the problem.
    Can someone tell me what may have changed in 10.1.5/11.0.01 that would cause these calls to start failing?
    The javascript at issue looks like this:
    var serviceKeyResult.rawValue = Get(serviceKeyUrl)
    The error we get is "Error: Error attempting to read from file: {URL}"

    Thanks for pointing that out.  The javacript was implemented by a third party, so I was not aware that the function wasn't part of the standard APIs.  I'll get more detail on what is happening inside that method.
    For now we have updated our web services to accept both a GET and a POST to avoid this issue.

  • User Profiles are the wrong style after importing/migrating site collections from other SharePoint versions

    I manage a couple of different version of SharePoint, which we are in the process of migrating to SharePoint 2013. I have a problem which I am not sure how to resolve. We are using MetaLogix to migrate site and site collection data from an older SharePoint
    2007/WSS3.0 server environment into our new SharePoint 2013 environment and we are having a problem with user profiles that get created.
    I have SharePoint 2013 set up for "SharePoint Profile Synchronization" and some of our user's profiles are being created in an older format that shows the user's claims account information, rather than the more fancy profile type that allows us
    to include pictures and click on "follow this person" links. 
    If we manually delete the profile, it will be recreated properly however, as we are migrating many sites and collections over, it is near impossible to do this and keep track of each user so that their profiles can be deleted and recreated.
    Is there some way to change this behavior so that SharePoint will only create the newer style of user profile?

    These 'profiles' are you looking at them in the User Profile Service Application itself or are you looking at site collections? There is a huge difference between the two but people often miss it.
    In most cases you'll have some partial information on the Site Collections but when you click through to their actual profile (not just their User Information List entry) you'll see the prettier version. That information is normally internally synchronised
    by a timer job but that may not have run yet and/or the fact that your users haven't actually used the site may be causing it not to update them (it's an efficiency matter).
    Finally: Drop your sales guy at Metalogix an email, they will bounce it to one of their techies and they'll have seen it a million times.

  • "opmn start failed" after starting infrastrucure as root

    Infrastructure installed and functioning properly until one day I tried to make a startup script to start the infrastructure automaticly every time I restart the computer. After that I cannot start any opmn process.
    After turning the opmn log level to 6, I get this output:
    oracle@infra:~> opmnctl startall
    opmnctl: starting opmn and all managed processes...
    Loading Module libopmnohs callback functions
    Module libopmnohs: loaded callback function opmnModInitialize
    Module libopmnohs: unable to load callback function opmnModSetNumProcs
    Module libopmnohs: unable to load callback function opmnModParse
    Module libopmnohs: unable to load callback function opmnModHelp
    Module libopmnohs: unable to load callback function opmnModDepend
    Module libopmnohs: loaded callback function opmnModStart
    Module libopmnohs: unable to load callback function opmnModReady
    Module libopmnohs: loaded callback function opmnModNotify
    Module libopmnohs: loaded callback function opmnModRestart
    Module libopmnohs: loaded callback function opmnModStop
    Module libopmnohs: loaded callback function opmnModPing
    Module libopmnohs: loaded callback function opmnModProcRestore
    Module libopmnohs: loaded callback function opmnModProcComp
    Module libopmnohs: unable to load callback function opmnModReqComp
    Module libopmnohs: unable to load callback function opmnModInfo
    Module libopmnohs: unable to load callback function opmnModCron
    Module libopmnohs: loaded callback function opmnModTerminate
    and the same errors for every other component
    opmnctl: opmn start failed
    The startup script I wrote:
    #!/bin/bash
    . /etc/rc.status
    rc_reset
    su oracle
    ORACLE_HOME=/opt/oracle/OraInfra
    export PATH=$PATH:$ORACLE_HOME/bin:$ORACLE_HOME/dcm/bin:$ORACLE_HOME/webcache/bin:$ORACLE_HOME/opmn/bin
    export ORACLE_SID=iasdb
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib
    export DISPLAY=10.1.1.201:0.0
    export INFRA=infra.zvs.com.mk
    case "$1" in
    start)
         echo
         echo Starting Listener
         echo -----------------
         $ORACLE_HOME/bin/lsnrctl start
         echo
         $ORACLE_HOME/dbstart
         echo echo Starting all opmnctl controlled processes
         echo -----------------------------------------
         $ORACLE_HOME/opmn/bin/opmnctl startall
         echo
         echo Checking status of app server instances
         echo --------------------------------------Â
         echo Getting status for $INFRA
         $ORACLE_HOME/dcm/bin/dcmctl getState -v -i $INFRA
         echo Starting the EM website
         echo -----------------------
         #$ORACLE_HOME/bin/emctl start oms
         $ORACLE_HOME/bin/emctl start em
    stop)
         echo Stopping the EM website
         $ORACLE_HOME/bin/emctl stop em
         echo Completed
         echo Starting all opmnctl controlled processes
         $ORACLE_HOME/opmn/bin/opmnctl stopall
         $ORACLE_HOME/dbstop
    esac
    rc_exit
    Please help, Borut

    I didn't started any component as root, but I can't finish installing AS 10.1.4.0.1 on Solaris 10 (x86). Tried many times, reinstalling everything, including the OS.
    When I change the log level from 4 to 9, I can see the exact same error messages as you do.
    But the only failing component to me is HTTP_Server.
    No logs under $OH/opmn/log or $OH/Apache/Apache/logs.
    OID and OC4J_SECURITY components are just fine.
    Any help or suggestion would be appreciated.
    Thanks in advance.

  • OBIEE Start/Stop Services failed(After LDAP Configuration)

    Hi ,
    We made some changes(that is we have added new OID
    and configured the new OID based upon the Oracle BI security guide which is in Oracle Site
    ) to the LDAP configuration in OBIEE web console and it prompted for a restart of the OBIEE services . when we tried restarting the services we are not able to stop all the services . Please find the attached log files .
    Note:
    1.unable to kill the process ID
    which is releated to OBIEE 11.1.1.6.0 services..
    2.We have follwed the section 3 in the below link to configure the LDAP : http://docs.oracle.com/cd/E23943_01/bi.1111/e10543/toc.htm.
    Please find the below error details in short form and kindly find the attahced file(file name) for more details
    Error:
    Caused By: oracle.security.jps.service.igf.IGFException: JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one.
    at oracle.security.jps.internal.api.identitystore.IdentityStoreConfigurationUtil.checkIdStoreTypeLater(IdentityStoreConfigurationUtil.java:819)
    at oracle.security.jps.internal.api.identitystore.IdentityStoreConfigurationUtil.getLibOvdLdapPushData(IdentityStoreConfigurationUtil.java:524)
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider$1.run(OvdIGFServiceProvider.java:232)
    at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider$1.run(OvdIGFServiceProvider.java:229)
    at java.security.AccessController.doPrivileged(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <Jan 29, 2013 6:39:05 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Jan 29, 2013 6:39:05 AM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Jan 29, 2013 6:39:05 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state cha
    Error Codes
    Problem Category/Subcategory
    BI EE Platform Administration/Administration Tool
    Uploaded Files
    File: nohup.zip:134848
    Template Question Responses
    1) ### Admin Tool version ###
    2) Are you running Oracle Business Intelligence Enterprise Edition using virtualization or partitioning technologies (for example, VMWare) ?
    No
    3) If yes, please provide the product used and its version.
    4) ### Documentation Used ###
    5) ### Impact on Business ###
    Edited by: 919942 on Jan 31, 2013 5:10 AM

    "JPS-02597: You configured a custom Authentication Provider or WLS generic LDAPAuthenticator, which the libOvd can not recognize. Supply the idstore.type property in jps-config.xml file, or use a specific WLS LDAP Authentication provider that matches your LDAP server instead of a generic one."
    Looks like the config you entered was a tad off. Any chance you can roll back by restoring the original files from before the change?
    $FMWH/user_projects/domains/yourdomain/config/config.xml
    $FMWH/user_projects/domains/yourdomain/config/fmwconfig/jps-config.xml
    In the config.xml, inside the <realm> tag yo ushould find your authenticaiton providers and there's two important things for your new one to check:
    1.) xsi-type="wls:..." <-- This should be your OID type rather than a generic (or wrong) one
    2.) If you're not 100% sure about the config or don't want to immediately shut out native WLS users or want to retain them (both OID and WLS LDAP considered valid), then PLEASE make sure that you run your new authenticator with <sec:control-flag>SUFFICIENT</sec:control-flag> and don't make it REQUIRED since otherwise you won't be able to bring anything up anymore if a single parameter in the authenticator config is off...
    Also, check out what Tony wrote together a while back: http://www.peakindicators.com/index.php/knowledge-base/115-oracle-bi-11g-security-troubleshooting
    Update:
    Should have read the error message more carefully...looks like you actually just slipped by one line in the authenticator config and chose "OracleVirtualDirectory" instead of "OracleInternetDirectory" since it tries to use the libOvd rather than the OID one.
    Edited by: Christian Berg on Jan 31, 2013 2:58 PM

  • Failed to start applications after deployed as Windows service.

    I deployed Administration server as a Windows service. Started Administration server in Windows Serivices control panel. The applications FMW Welcome Page Application (11.1.0.0.0), DMS Application (11.1.1.1.0) failed. I also installed adf-richclient-demo, this application in prepared status.
    It reported "java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter", when I tried to start the applications. However the applications are Ok by starting Administration server with domain\bin\startWebLogic.cmd.
    Do any one know how to solve the issue?
    Thanks!

    I asume you are using NodeManager to start AdminServer when you says "I deployed Administration server as a Windows service".
    If so, make sure the jar file (jar that contains oracle.dms.wls.DMSServletFilter class) is added to CLASSPATH, that NodeManager uses to start the server. Node Manager starts a Server using the startup arguments configured for the Managed Server in the Server—>Configuration—>Server Start tab.
    I suggest restart the NodeManager when you modify this properties.
    Check [http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1144313]

  • After LDAP Configuration Starting biserver1(Managed Server) is getting Fail

    I have Configured the LDAP(OID) by following the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition
    11g Release 1 (11.1.1) (Section 3) Completed sucessfully with out any errors.. Users also imported sucessfully. after that when I am starting the biserver1(Managed Server) I am getting error like
    "Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied"
    was taken from biserver log file. please find the below attachment for the same.
    Please help me for the same
    biserver.log
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Server> <usstuobitest03.diversey.com> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241307> <BEA-002609> <Channel Service initialized.>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241317> <BEA-000406> <PosixSocketMuxer was built on Apr 24 2007 16:05:00>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241339> <BEA-000436> <Allocating 3 reader threads.>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <Socket> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241339> <BEA-000446> <Native IO Enabled.>
    ####<Mar 22, 2012 2:40:41 PM CDT> <Info> <IIOP> <usstuobitest03.diversey.com> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445241572> <BEA-002014> <IIOP subsystem enabled.>
    ####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246302> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
    ####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246667> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
    ####<Mar 22, 2012 2:40:46 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445246944> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_lDqprIBb69IOInpk4TtgfToFVP8=>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247141> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247707> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247719> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Info> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247891> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server bi_server1 for security realm myrealm.>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247892> <BEA-090082> <Security initializing using security realm myrealm.>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Critical> <Security> <usstuobitest03.diversey.com> <bi_server1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332445247908> <BEA-090403> <Authentication for user denied>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Critical> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247909> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
         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:545)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
         at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
         at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
         at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
         at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
         at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
         at com.bea.common.security.internal.service.JAASLoginServiceImpl.login(JAASLoginServiceImpl.java:113)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy36.login(Unknown Source)
         at weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.login(WLSJAASLoginServiceImpl.java:89)
         at com.bea.common.security.internal.service.JAASAuthenticationServiceImpl.authenticate(JAASAuthenticationServiceImpl.java:82)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:57)
         at $Proxy54.authenticate(Unknown Source)
         at weblogic.security.service.WLSJAASAuthenticationServiceWrapper.authenticate(WLSJAASAuthenticationServiceWrapper.java:40)
         at weblogic.security.service.PrincipalAuthenticator.authenticate(PrincipalAuthenticator.java:338)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:930)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
         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:545)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    ####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247917> <BEA-000365> <Server state changed to FAILED>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Error> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247917> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Notice> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247918> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Mar 22, 2012 2:40:47 PM CDT> <Info> <WebLogicServer> <usstuobitest03.diversey.com> <bi_server1> <main> <<WLS Kernel>> <> <> <1332445247923> <BEA-000236> <Stopping execute threads.>

    WebLogic has 2 accounts that were created on install..BISystemUser and weblogic or whatever you may have called that. Are the passwords of BISystemUser the same in EM and WebLogic? Also, I believe you had to create a BISystemUser in OID. That password should match to the BISystemUser in EM and WL.

  • J2EE start fails after changing the instance-number

    Hi,
    we installed a SCS with instance number 41. After a few weeks it was necessary to change it to 44. We changed all property-files and the profiles.
    The SCS started fine, but the J2EE-Server failed starting.
    In dev_server0 is still a line with the former port 3241:
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    I thought I changed everything from 41 to 44.  Does someone have an idea, which I forgot? Thank you for help.
    Here you can see the whole dev_server0:
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 29093
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 14:51:09 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 14:51:09 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=29093
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 14:51:13 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1094003040] Tue May 22 14:54:13 2007
    [Thr 1094003040] JLaunchIExitJava: exit hook is called (rc = -337)
    [Thr 1094003040] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 1094003040] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1094003040] JLaunchCloseProgram: good bye (exitcode = -337)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 30385
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 14:54:15 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 14:54:15 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] Tue May 22 14:54:16 2007
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=30385
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 14:54:18 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:09:19 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 31835
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 15:09:21 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 15:09:21 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=31835
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] Tue May 22 15:09:22 2007
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 15:09:24 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:24:25 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)
    trc file: "/usr/sap/SM1/DVEBMGS40/work/dev_server0", trc level: 1, release: "700"
    node name   : ID401326950
    pid         : 32545
    system name : SM1
    system nr.  : 40
    started at  : Tue May 22 15:24:27 2007
    arguments       :
           arg[00] : /usr/sap/SM1/DVEBMGS40/exe/jlaunch
           arg[01] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[02] : -DSAPINFO=SM1_40_server
           arg[03] : pf=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[04] : -DSAPSTART=1
           arg[05] : -DCONNECT_PORT=60030
           arg[06] : -DSAPSYSTEM=40
           arg[07] : -DSAPSYSTEMNAME=SM1
           arg[08] : -DSAPMYNAME=sm1-ci_SM1_40
           arg[09] : -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
           arg[10] : -DFRFC_FALLBACK=ON
           arg[11] : -DFRFC_FALLBACK_HOST=localhost
    [Thr 182906379008] Tue May 22 15:24:27 2007
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.box.number=SM1DVEBMGS40sm1-ci] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.host=sm1-scs] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.en.port=3241] [jstartxx_mt. 841]
    [Thr 182906379008] *** WARNING => INFO: Unknown property [instance.system.id=40] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties]
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> OS libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sm1-scs
    -> ms port    : 3944
    -> os libs    : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID40132690 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID40132695 : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID401326900          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    -> [01] ID401326950          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/instance.properties
    [Thr 182906379008] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 182906379008] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 1074792800] JLaunchRequestFunc: Thread 1074792800 started as listener thread for np messages.
    [Thr 1076894048] WaitSyncSemThread: Thread 1076894048 started as semaphore monitor thread.
    [Thr 182906379008] SigISetDefaultAction : default handling for signal 17
    [Thr 182906379008] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 182906379008] CPIC (version=700.2006.09.13)
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    [Thr 182906379008] [Node: server0] java home is set by profile parameter
         Java Home: /usr/lib/java
    [Thr 182906379008] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID401326950]
    -> node name          : server0
    -> node type          : server
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/lib/java
    -> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djco.jarm=1 -verbose:gc -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Xmn400M -Xgcpolicy:gencon -Xtrace -Xsoftrefthreshold0
    -> java vm version    : J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20060428 (JIT enabled)
    -> java vm vendor     : IBM J9SE VM (IBM Corporation)
    -> java vm type       : <default>
    -> java vm cpu        : amd64
    -> heap size          : 2048M
    -> init heap size     : 2048M
    -> root path          : /usr/sap/SM1/DVEBMGS40/j2ee/cluster/server0
    -> class path         : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/SM1/DVEBMGS40/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 54021
    -> shutdown timeout   : 120000
    [Thr 182906379008] JLaunchISetDebugMode: set debug mode [no]
    [Thr 1077946720] JLaunchIStartFunc: Thread 1077946720 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [server0]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Djava.security.policy=./java.policy
    -> arg[  4]: -Djava.security.egd=file:/dev/urandom
    -> arg[  5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
    -> arg[  6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
    -> arg[  7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
    -> arg[  8]: -Djco.jarm=1
    -> arg[  9]: -verbose:gc
    -> arg[ 10]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
    -> arg[ 11]: -Xmn400M
    -> arg[ 12]: -Xgcpolicy:gencon
    -> arg[ 13]: -Xtrace
    -> arg[ 14]: -Xsoftrefthreshold0
    -> arg[ 15]: -Dsys.global.dir=/usr/sap/SM1/SYS/global
    -> arg[ 16]: -Dapplication.home=/usr/sap/SM1/DVEBMGS40/exe
    -> arg[ 17]: -Djava.class.path=/usr/sap/SM1/DVEBMGS40/exe/jstartup.jar:/usr/sap/SM1/DVEBMGS40/exe/jvmx.jar:./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.
    -> arg[ 18]: -Djava.library.path=/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/tmp/sapinst_exe.7551.1151567769:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib:/usr/lib:/usr/sap/SM1/DVEBMGS40/j2ee/os_libs:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/DVEBMGS40/exe:/usr/sap/SM1/SYS/exe/run:/sapdb/programs/lib
    -> arg[ 19]: -Dmemory.manager=2048M
    -> arg[ 20]: -Xmx2048M
    -> arg[ 21]: -Xms2048M
    -> arg[ 22]: -DLoadBalanceRestricted=no
    -> arg[ 23]: -Djstartup.mode=JCONTROL
    -> arg[ 24]: -Djstartup.ownProcessId=32545
    -> arg[ 25]: -Djstartup.ownHardwareId=X1817543257
    -> arg[ 26]: -Djstartup.whoami=server
    -> arg[ 27]: -Djstartup.debuggable=no
    -> arg[ 28]: -DSAPINFO=SM1_40_server
    -> arg[ 29]: -DSAPSTART=1
    -> arg[ 30]: -DCONNECT_PORT=60030
    -> arg[ 31]: -DSAPSYSTEM=40
    -> arg[ 32]: -DSAPSYSTEMNAME=SM1
    -> arg[ 33]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 34]: -DSAPPROFILE=/usr/sap/SM1/SYS/profile/SM1_DVEBMGS40_sm1-ci
    -> arg[ 35]: -DFRFC_FALLBACK=ON
    -> arg[ 36]: -DFRFC_FALLBACK_HOST=localhost
    -> arg[ 37]: -DSAPSTARTUP=1
    -> arg[ 38]: -DSAPSYSTEM=40
    -> arg[ 39]: -DSAPSYSTEMNAME=SM1
    -> arg[ 40]: -DSAPMYNAME=sm1-ci_SM1_40
    -> arg[ 41]: -DSAPDBHOST=sm1-db
    -> arg[ 42]: -Dj2ee.dbhost=sm1-db
    [Thr 1077946720] Tue May 22 15:24:28 2007
    [Thr 1077946720] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [server0]
    [Thr 1082288480] Tue May 22 15:24:30 2007
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1082288480] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1082288480] JLaunchISetClusterId: set cluster id 401326950
    [Thr 1077946720] Tue May 22 15:39:31 2007
    [Thr 1077946720] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 1077946720] SigISetIgnoreAction : SIG_IGN for signal 17
    [Thr 1077946720] JLaunchCloseProgram: good bye (exitcode = 0)

    Werner,
    First check the instance.properties file to see if it has picked up the change.  You may need to change it there.
    Also, these need to be changed in your default profile:
    j2ee/scs/host = <host>
    j2ee/scs/system = 44
    j2ee/ms/port = 3944
    Also, you have max heap specified twice, make sure this is only specified once by taking it out of the body of the java parameters.  It can cause other problems being in there twice.
    [Thr 182906379008] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx_mt. 2604]
    -jwise

  • EP starting failed after switching UM datasource to LDAP

    I would like to use Windows 2003 AD as user storage of EP. For this purpose, I completed the necessary configuration steps according to online help but still not able to connect EP to LDAP.
    Test button show me that parameters entered in the LDAP configuration tab is correct. But once I change the UM datasource to dataSourceConfiguration_ADS_readonly_db.xml and restart the J2EE server. The application server won't start up successfully. It indicated problems with a yellow flag on the server node. Clicking the processes will display that some processes is running. Trace file outlines problem as below:
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: No connection to the ldap server, recheck configuration or availability of directory server
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Server not available,recheck configuration or availability of directory server
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialisation of a connection pool failed for UACC please check the configuration or availability of the directory server
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Please recheck the LDAP configuration Initialisation of connection pool failed for UACC
         poolname shaw2k99:389_UACC
         java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
         java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
         java.naming.ldap.version= 3
         connection_pool_name= shaw2k99:389_UACC
         java.naming.security.authentication= simple
         [EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: DataSource CORP_LDAP:Initialisation of connection manager failed because: Initialisation of connection pool failed for UACC
         poolname shaw2k99:389_UACC
         java.naming.provider.url= ldap://shaw2k99:389/CN%3DUsers%2CDC%3Ddimension%2CDC%3Dcom%2CDC%3Dcn
         java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
         java.naming.ldap.version= 3
         connection_pool_name= shaw2k99:389_UACC
         java.naming.security.authentication= simple
         [EXCEPTION: no connection to the ldap server:[LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece ]]
    Jul 15, 2006 11:22:50...        com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_62] Fatal: Initialization of UME persistence adapter "CORP_LDAP" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: Initialisation of connection pool failed for UACC
    Does anyone have clue on this? Thanks!
    My EP version: EP 7.0 SP4
    AD version: 2003

    Hello,
    I don’t think, that the problem is directly related with the usage of SSL. We don’t use SSL and we have the same problem mentioned in the first post of this topic in our portal. We are using EP7 SP8.
    The connection tests in the config-tool and in the UME-configuration of the EP indicates us, that the connection to the LDAP-Server is working correct.  But when we are restarting the portal, then the following exception appears and the server stops to start:
    com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
            poolname <ip-address>:389_UACC
            java.naming.provider.url= ldap:// <ip-address>:389/…
            java.naming.factory.initial= com.sun.jndi.ldap.LdapCtxFactory
            java.naming.ldap.version= 3
            com.sun.jndi.ldap.connect.timeout= 25000
            connection_pool_name= <ip-address>:389_UACC
            java.naming.security.authentication= simple
            [EXCEPTION: No connection to the ldap server: [LDAP: error code 1 - 00000000: LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece]]
            at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initConnectionPools(LDAPConnectionManager.java:777)
            at com.sap.security.core.persistence.datasource.imp.LDAPConnectionManager.initialize(LDAPConnectionManager.java:83)
            at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:453)
    Has anyone a hint how to solve our problem?
    Regards,
    Udo

  • J2EE Start Failed after upgrade

    Hello Guys !
    I Have this problem since upgra SP22.
    #1.5 #005056AA79B8001C00000010000013CC000494B587D8095A#1289407295922#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#com.sap.engine.core.service630.container.ServiceRunner#Plain###Service com.sap.security.core.ume.service error. Nested exception is: com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details: Initialisation of connection pool failed for UACC
         poolname norfloxacino.ems.com.br:389_UACC
         [EXCEPTION: no connection to any server possible]
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
         at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
         at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
         at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:83)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:156)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Initialisation of connection pool failed for UACC
         poolname norfloxacino.ems.com.br:389_UACC
         [EXCEPTION: no connection to any server possible]
         at com.sap.security.core.persistence.datasource.imp.LDAPPersistence.init(LDAPPersistence.java:423)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:440)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
         at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
         at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
         at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
         ... 6 more
    #1.5 #005056AA79B8001C00000012000013CC000494B587D80CC6#1289407295922#/System/Server##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_55##0#0#Error#1#/System/Server#Plain###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    #1.5 #005056AA79B8001C00000014000013CC000494B587D80E8E#1289407295922#/System/Server/Critical##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_55##0#0#Fatal#1#com.sap.engine.core.Framework#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
    Does anyone have any idea about the error above?
    Thank you for your help!

    Hello
    Did the system really work well before the upgrade?
    and during/after the upgarde, did you changed any setting, especially regarding J2EE UME/ LDAP ?
    Could you please help to check the following defaulttrace for more information:
      ../j2ee/cluster/server0/log/defaultTrace.*.trc
    As per the error message you pasted here, the connection from your UME to the LDAP failed, so the core service of com.sap.engine.core.security.ume cannot startup.
    Hence the first check point should be the connectioin to your LDAP, please open the configtool and go to the "UEM LDAP Data" setting there carefully, then you can perform a
    "Test Connection" there.
    If the connection always fails, you can also download a LDAP browser from "http://www.ldapbrowser.com/download.htm", then
    test whether you are able to connect to the LDAP, if it also fails, I would like to suggest you check with your LDAP vendor to verify whether there is any problem at the LDAP server side.
    Thanks
    Thunder

  • Rc-local.service keeps failing after one time success

    Actually it's quite weird, every time rc-local.service was enable successfully with boot but then it keeps failing. However, once I modify /etc/systemd /system/rc-local.service( even something that really doesn't matter ), it will be enabled successfully again. but only ONCE each time.
    [Unit]
    Description=/etc/rc.local compatibility
    [Service]
    Type=oneshot
    ExecStart=/etc/rc.local
    TimeoutSec=0
    RemainAfterExit=yes
    [Install]
    WantedBy=multi-user.target

    All of those things can be done with udev rules.  I had a Momentus XT, which I now no longer have in my system, but my old rule is still there.  It is as follows:
    ACTION=="add", SUBSYSTEM=="block", ATTRS{model}=="ST95005620AS", RUN+="/sbin/hdparm -B 247 /dev/$kernel"
    You could also do something like this to apply it to all rotational disks
    ACTION=="add", KERNEL=="sd[a-z]", ATTR{queue/rotational}=="0", RUN+="/sbin/hdparm -B 254 /dev/$kernel"
    As far as the stuff in /sys, use udevadm to get stuff to put in your rule to identify it.  So something like
    $ udevadm info -a -p /sys/kernel/debug/vgaswiteroo
    I have also used a rule for my backlight setting on boot.  To find stuff, once again use the udevadm
    $ udevadm info -a -p /sys/class/backlight/acpi_video0
    My resulting backlight rule is:
    ACTION=="add", KERNEL=="acpi_video0", SUBSYSTEM=="backlight", SUBSYSTEMS=="pci", DRIVERS=="i915", ATTR{brightness}="2"
    For more info on writing udev rules see http://www.reactivated.net/writing_udev_rules.html but when you get to the part about the udev commands, those no longer apply, as they have now been replaced by the udevadm commands listed above.  The commands are mostly correct, just instead of udevinfo, it is udevadm.
    I hope this helps!
    Last edited by WonderWoofy (2012-11-02 02:59:59)

  • LMS 4.0 Archive Poller starts failing after some working cycles

    Hi,
    We have a LMS 4.0 running in our network with arround 650 nodes.
    We are having problems with the Archive Poller.
    The first few days it worked fine, but then it started to fail for some devices and on the next day it failed to poll all devices. I have restarted the daemon manager after the failure and it came back working fine for another few days. Since then the Change Poller works for a few days, then it degrades polling to a complete failure, a restart of the daemon manager get it working only for a few days.
    Here is some output of a failed node:
    *** Device Details for zagora4-sw *** 
    Protocol ==> Unknown / Not Applicable 
    Selected Protocols with order ==> Telnet,SSH 
    Execution Result:
    Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Admin > Collection Settings > Config > Config Job Timeout Settings
    It seems that the poller is not even trying to poll nodes...?
    Do you think the DB might got corrupted, as I restarted the machine without shutting down the processes some weeks ago...
    Any hints or ideas would be appreciated !

    Hi @ all
    I have the same Problem as Ruslan. Do ansbody have a idea to solve this problem ? Afer some succesfull runs ob the ArchivePoll it stop with the mentioned error...
    *** Device Details for nunw-n30-05-005 ***
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> Telnet,SSH,HTTPS
    Execution Result:
    Unable to get results of job execution for device. Retry the job  after increasing the job result wait time using the option:Admin > Collection  Settings > Config > Config Job Timeout Settings
    I´d tried to increase the "wait time" but notthing happens ...
    HELP Please ...
    Thanks
    Regard Mario

  • Shared Services Registration Failed While Re-Configuring EAS

    Hi
    I was re-configuring EAS and my shared services and deployment failed.I reached out to oracle and they gave me a solution to delete the HBR instances.
    But when I try to open the url in microsoft word it opens in html format .And i am unable to delete any HBR instance.What is the correct way to do it?
    The solution offered by Oracle Support:
    To resolve this issue, do the following steps:
    1. Log into the User management console using the URL http://localhost:58080/interop/index.jsp.
    2. Append the URL to show the files http://localhost:58080.interop/content/files
    3. Copy this URL and open in Microsoft Word. (file->open option in MS Word)
    4. Provide username (admin) and password (password).
    5. Check in AdminProjects, Products and Projects folders for the files and folders related to HBR and delete any occurences.
    6. Save and close the file.
    7. Restart the services.
    8. Configure EAS with Shared Services using the config utility.
    9. For Business Rules to work, go to \Hyperion\AnalyticAdministration\storage\easuser location and delete all contents from the easusers folder.
    10. Restart the EAS server.
    Thanks
    Z

    I never really used the method with word and always used davexplorer which can be downloaded from http://www.davexplorer.org/download.html
    Follow the rest of the instructions which you posted to delete HBR.
    Cheers
    John

  • At least one service session failed during job SM:EXEC SERVICES

    Hello everyone.
    I'm have problem with job "SM:EXEC SERVICES" in my System: SolutionManager 7.1 SPS12.
    Number of sessions to process in parallel: 5
    Child job SM:EXEC_MULT_SES_1 started
    Displaying log of child job SM:EXEC_MULT_SES_1
    Step 001 started (program AGS_SISE_SM_EXEC_PARALL_REPORT, variant &0000000000060, user ID SOLMAN_BTC)
    Trying to perform session EA0010000000001
    Error (shown below) in session EA0010000000001. Hints on analysis in SAP Note 700518
    Error message: An exception occurred that was not caught.
    Session EA0010000000001 not performed
    Step 002 started (program AGS_SISE_SM_EXEC_PARALL_REPORT, variant &0000000000061, user ID SOLMAN_BTC)
    Trying to perform session VE0010000000002
    Error (shown below) in session VE0010000000002. Hints on analysis in SAP Note 700518
    Error message: An exception occurred that was not caught.
    Session VE0010000000002 not performed
    ABAP DUMP "Error analysis":
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_DSVAS_API_SERVICE_SESSION', was
    not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Program for actions in check group &EW_ROOT& version &50079& not found
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SY_PROGRAM_NOT_FOUND", which was raised in the program
    "CL_DSVAS_PROC_CHECK_GROUP=====CP",
    specifically in line 25 of the (include) program
    "CL_DSVAS_PROC_CHECK_GROUP=====CM00A".
    The cause of the exception was:
    Program /1AGS/AEW_ROOT_____________079 does not exist
      An exception occurred which is explained in detail below.
      The exception, which is assigned to class 'CX_DSVAS_API_SERVICE_SESSION', was
       not caught and
      therefore caused a runtime error.
      The reason for the exception is:
      Program for actions in check group &EWAFS_ROOT& version &50007& not found
      The occurrence of the exception is closely related to the occurrence of
      a previous exception "CX_SY_PROGRAM_NOT_FOUND", which was raised in the program
       "CL_DSVAS_PROC_CHECK_GROUP=====CP",
      specifically in line 25 of the (include) program
       "CL_DSVAS_PROC_CHECK_GROUP=====CM00A".
      The cause of the exception was:
      Program /1AGS/AEWAFS_ROOT__________007 does not exist
    i'm was trying find program "/1AGS/AEWAFS_ROOT__________007" and "/1AGS/AEW_ROOT_____________079" in SE80, but to no avail.
    Full job report and dumps in attachment.
    Kernel release    721
    Compilation       Linux GNU SLES-11
    Sup.Pkg lvl.      401
    ABAP Load         1780
    CUA load          39
    Mode              opt
    SAP_BASIS
    702
    0015
    SAPKB70215
    SAP Basis Component
    SAP_ABA
    702
    0015
    SAPKA70215
    Cross-Application Component
    CTS_PLUG
    200
    0013
    SAPK-20013INCTSPLUG
    SAP CTS Plugin
    PI_BASIS
    702
    0015
    SAPK-70215INPIBASIS
    Basis Plug-In
    ST-PI
    2008_1_700
    0011
    SAPKITLRDK
    SAP Solution Tools Plug-In
    BI_CONT
    707
    0007
    SAPK-70707INBICONT
    Business Intelligence Content
    GW_CORE
    200
    0008
    SAPK-20008INGWCORE
    SAP GW CORE 200
    SAP_BS_FND
    702
    0013
    SAPK-70213INSAPBSFND
    SAP Business Suite Foundation
    SAP_BW
    702
    0015
    SAPKW70215
    SAP Business Warehouse
    UISAPUI5
    100
    0007
    SAPK-10007INUISAPUI5
    SAP UI5
    UI_INFRA
    100
    0007
    SAPK-10007INUIINFRA
    SAP UI INTEGRATION INFRASTRUCTURE
    IW_GIL
    100
    0004
    SAPK-10004INIWGIL
    Generic Interaction Layer
    SAP_AP
    700
    0031
    SAPKNA7031
    WEBCUIF
    701
    0012
    SAPK-70112INWEBCUIF
    SAP Web UI Framework
    BBPCRM
    701
    0012
    SAPKU70112
    BBPCRM
    CPRXRPM
    500_702
    0011
    SAPK-50011INCPRXRPM
    SAP Portfolio and Project Management 5.0 (ABAP)
    IW_BEP
    200
    0008
    SAPK-20008INIWBEP
    Backend Event Provider
    IW_FND
    250
    0008
    SAPK-25008INIWFND
    SAP IW FND 250
    ST
    710
    0012
    SAPKITL712
    SAP Solution Manager Tool
    ST-BCO
    710
    0010
    SAPK-71010INSTBCO
    BI Content for SAP Solution Manager
    RTCISM
    100
    0000
    Integration into SAP IT Infrastructure Management
    SOCO
    101
    0003
    SAPK-10103INSOCO
    SAP Solution Composer Server
    ST-A/PI
    01R_700
    0001
    SAPKITAB7N
    Application Servicetools for SolMan 7.0-
    ST-ICC
    200
    0001
    SAPK-20001INSTICC
    Innovation Control Center
    ST-ICO
    150_700
    0043
    SAPK-15087INSTPL
    SAP Solution Manager Implementation Content
    ST-SER
    701_2010_1
    0025
    SAPKITLOSP
    SAP Solution Manager Service Tools

    Hi,
    Try this.
    Run RAGS_DSWP_SERV_CONTENT_RESET in Se38 and seclect "Remove content completely"
    Goto AGS_UPDATE and apply the updates again and make sure that all is are green.
    Open the EWA session that was dumping and reset session component.
    Regards,

  • Create service definition failed while creating a Web Service

    Guru,
    I am trying to develop a Web Service in ECC 6.0 SR3, AIX 5.3+Oracle 10g.
    The followings are my steps:
    1. Create function module, e.g. Z_RFC_DEMO
    2. Activate this function module and also try to run it. It's working.
    3. Then use SE37, Utilities -> More Utilities -> Create Web Service -> From the Function Module, and filles what it really needs to fill. After clicking the complete button, it reports "No Vendor Specified".
    4. From SE80, when activate the Service Definition manually, it reports the same error.
    Is there any body can help me to solve this problem?
    Thanks Advance.

    Guy,
    Thanks for your reply.
    This problem has been solved. Since I haven't turned on everything that to use transaction SOAMANAGER needs. After complete the switch-on works, the problem never happens again.
    Thanks again.

Maybe you are looking for