initialization failed while starting server...

[allavivek]

Hi All,

I Installed both client and server on my windows laptop..
While i was starting server its saying "server started but initialization failed"

I looked in to SystemOut log file and found..

[10/16/10 15:45:07:920 ACT] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[10/16/10 15:45:08:604 ACT] 0000000a AdminInitiali A ADMN0015I: The administration service is initialized.
[10/16/10 15:45:10:527 ACT] 0000000a SystemOut O PLGC0057I: Plug-in configuration service is started successfully.
[10/16/10 15:45:11:406 ACT] 0000000a SibMessage I [:] CWSIU0000I: Release: WAS602.SIB Level: o0809.08
[10/16/10 15:45:11:453 ACT] 0000000a SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[10/16/10 15:45:11:618 ACT] 0000000a AuditServiceI A SECJ6004I: Security Auditing is disabled.
[10/16/10 15:45:12:464 ACT] 0000000a distSecurityC A SECJ0413I: The JACC provider is successfully initialized with the following setup. The policy class name is com.ascential.acs.security.jacc.ASBPolicy. The PolicyConfigurationFactory class name is com.ascential.acs.security.jacc.ASBPolicyConfigFactory. The optional RoleConfigurationFactory call name is com.ascential.acs.security.jacc.websphere.ASBRoleConfigurationFactory. The optional initialization class name is <null>.
[10/16/10 15:45:12:476 ACT] 0000000a distSecurityC I SECJ0309I: Java 2 Security is disabled.
[10/16/10 15:45:12:594 ACT] 0000000a Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[10/16/10 15:45:12:629 ACT] 0000000a distSecurityC I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[10/16/10 15:45:12:676 ACT] 0000000a TrustAssociat A SECJ0121I: Trust Association Init class com.ascential.acs.security.auth.interceptor.websphere.ISFTrustAssociationInterceptor loaded successfully
[10/16/10 15:45:12:699 ACT] 0000000a TrustAssociat A SECJ0122I: Trust Association Init Interceptor signature: 1.0
[10/16/10 15:45:12:711 ACT] 0000000a TrustAssociat A SECJ0121I: Trust Association Init class com.ibm.ws.security.web.WebSealTrustAssociationInterceptor loaded successfully
[10/16/10 15:45:12:770 ACT] 0000000a TrustAssociat A SECJ0122I: Trust Association Init Interceptor signature: WebSeal Interceptor Version 1.1
[10/16/10 15:45:12:852 ACT] 0000000a TrustAssociat A SECJ0121I: Trust Association Init class com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus loaded successfully
[10/16/10 15:45:12:864 ACT] 0000000a TAMTrustAssoc I com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlusinitialize(Properties) AWXRB0008E An error occurred retrieving the mandatory property, com.ibm.websphere.security.webseal.loginId, causing initialization to fail.
[10/16/10 15:45:12:864 ACT] 0000000a TAMTrustAssoc I com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlusinitialize(Properties) The Trust Association Interceptor component of embedded Tivoli Access Manager initialization has failed.
[10/16/10 15:45:12:876 ACT] 0000000a TrustAssociat E SECJ0384E: Trust Association Init Error. The Trust Association interceptor implementation com.ibm.ws.security.web.TAMTrustAssociationInterceptorPlus initialization failed. The error status/exception is -1.
[10/16/10 15:45:12:887 ACT] 0000000a distSecurityC I SECJ0240I: Security service initialization completed successfully
[10/16/10 15:45:13:346 ACT] 0000000a ObjectPoolSer I OBPL0007I: Object Pool Manager service is disabled.
[10/16/10 15:45:13:393 ACT] 0000000a J2EEServiceMa I ASYN0059I: Work Manager service initialized successfully.
[10/16/10 15:45:13:440 ACT] 0000000a CScopeCompone I CSCP0002I: Compensation service is disabled.
[10/16/10 15:45:13:534 ACT] 0000000a SibMessage I [:] CWSID0006I: The SIB service was not enabled and will not be started.
[10/16/10 15:45:13:557 ACT] 0000000a ActivitySessi I WACS0045I: ActivitySession service is disabled.
[10/16/10 15:45:13:569 ACT] 0000000a SOAPContainer I WSWS1062I: SOAP Container Service has been initialized.
[10/16/10 15:45:13:628 ACT] 0000000a SchedulerServ I SCHD0036I: The Scheduler Service is initializing.
[10/16/10 15:45:13:663 ACT] 0000000a SchedulerServ I SCHD0037I: The Scheduler Service has been initialized.
[10/16/10 15:45:16:625 ACT] 0000000a StartUpServic I STUP0008I: The Startup Beans service is disabled.
[10/16/10 15:45:16:649 ACT] 0000000a I18nService I I18N0010I: The Internationalization service is created on server1.
[10/16/10 15:45:16:649 ACT] 0000000a I18nServiceSe I I18N0010I: The Internationalization service is disabled on server1.
[10/16/10 15:45:27:443 ACT] 0000000a SASRas A JSAS0001I: Security configuration initialized.
[10/16/10 15:45:28:296 ACT] 0000000a SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM
[10/16/10 15:45:28:296 ACT] 0000000a SASRas A JSAS0003I: Authentication mechanism: LTPA
[10/16/10 15:45:28:309 ACT] 0000000a SASRas A JSAS0004I: Principal name: null/isadmin
[10/16/10 15:45:28:348 ACT] 0000000a SASRas A JSAS0005I: SecurityCurrent registered.
[10/16/10 15:45:30:236 ACT] 0000000a SASRas A JSAS0006I: Security connection interceptor initialized.
[10/16/10 15:45:30:287 ACT] 0000000a SASRas A JSAS0007I: Client request interceptor registered.
[10/16/10 15:45:30:378 ACT] 0000000a SASRas A JSAS0008I: Server request interceptor registered.
[10/16/10 15:45:30:391 ACT] 0000000a SASRas A JSAS0009I: IOR interceptor registered.
[10/16/10 15:45:31:529 ACT] 0000000a CoordinatorIm I HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup.
[10/16/10 15:45:31:606 ACT] 0000000a DCSPluginSing I HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup.
[10/16/10 15:45:32:550 ACT] 0000000a NameServerImp A NMSV0018I: Name server available on bootstrap port 2809.
[10/16/10 15:45:35:524 ACT] 0000000a UserRegistryI A SECJ0136I: Custom Registry:com.ascential.acs.security.directory.custom.websphere.ASBUserRegistry has been initialized
[10/16/10 15:45:51:525 ACT] 0000000f SASRas A JSAS1501E: [{0}] J2EEAuditEventFactory was not initialized.
[10/16/10 15:46:11:439 ACT] 0000000f SASRas A JSAS1501E: [{0}] J2EEAuditEventFactory was not initialized.
[10/16/10 15:46:22:488 ACT] 0000000a LTPAServerObj E SECJ0369E: Authentication failed when using LTPA. The exception is Unable to begin a transaction: [Error opening repository: [CoreRepositoryBindingFactory: Error creating an instance of the implementation class for ISandboxBinding.]].
[10/16/10 15:46:22:571 ACT] 0000000a distContextMa E SECJ0270E: Failed to get actual credentials. The exception is com.ascential.acs.security.repository.ASBRepositoryException: Unable to begin a transaction: [Error opening repository: [CoreRepositoryBindingFactory: Error creating an instance of the implementation class for ISandboxBinding.]]



and also



[10/16/10 15:46:30:086 ACT] 0000000a SchedulerServ I SCHD0040I: The Scheduler Service is stopping.
[10/16/10 15:46:30:105 ACT] 0000000a SchedulerServ I SCHD0002I: The Scheduler Service has stopped.
[10/16/10 15:46:30:161 ACT] 0000000a AppProfileCom I ACIN0009I: The application profiling service is stopping.
[10/16/10 15:46:30:161 ACT] 0000000a ActivitySessi I WACS0049I: The ActivitySession service is stopping.
[10/16/10 15:46:30:534 ACT] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup
META-INF/ws-server-components.xml
[10/16/10 15:46:30:572 ACT] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: Unable to begin a transaction: [Error opening repository: [CoreRepositoryBindingFactory: Error creating an instance of the implementation class for ISandboxBinding.]]



This is first time iam using both client and server on same machine...

Any help how to make datastage run...///

Thank you...

[ray.wurlod]

Look for each code ending with "E", for example "SECJ0384E", "JSAS1501E", "SECJ0369E", "SECJ0270E" and "WSVR0009E". These tell you where the problem is occurring, in this case (apparently) in the security service, which means that WebSphere Application Server reports a problem.

If none of this means anything to you please involve your official support provider. Diagnosis through DSXchange, where access to all the logs is impractical, would not be a productive use of our time.