Can't access datastage designer but still running

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

kjaouhari
Participant
Posts: 325
Joined: Thu Mar 16, 2006 10:22 am

Can't access datastage designer but still running

Post by kjaouhari »

Hello guys !

I'm little bit confused now, datastage server is down. Actually just one windows service is down. this one :
IBM Websphere application server V6 - server_name node 1
the node 2 is running and all other ds services are fine.
When I try to restart it , it start and stop.

And what I don't understand is that my daily scheduled job is still running fine everyday evenv though I can not access to any DS interface. (designer , director, websphere)

Any help we'll be welcome.

Here is what I get :
ADMU7701I: Because server1 is registered to run as a Windows Service, the
request to start this server will be completed by starting the
associated Windows Service.
ADMU0116I: Tool information is being logged in file
C:\IBM\WebSphere\AppServer\profiles\default\logs\server1\startServer.
log
ADMU0128I: Starting tool with the default profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ibm.websphere.management.exception.AdminException: ADMU7704E: Fai
led while trying to start the Windows Service associated with server: server1;
probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWA
SServiceException: ADMU7711E: Unexpected exception associated with WASService.ex
e: exitCode = -1 during processing of server with name: server1
at com.ibm.ws.management.tools.WindowsService.doWASServiceAction(Windows
Service.java:380)
at com.ibm.ws.management.tools.WsServerLauncher.execWithWinService(WsSer
verLauncher.java:157)
at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindow
s(WsServerController.java:128)
at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.ja
va:115)
... 7 more
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
C:\IBM\WebSphere\AppServer/profiles/default\logs\server1 should
contain failure information.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Re: Can't access datastage designer but still running

Post by ArndW »

kjaouhari wrote:...ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
C:\IBM\WebSphere\AppServer/profiles/default\logs\server1 should
contain failure information.
What does that file contain in the way of error messages or information? Is the daily job that runs despite the missing service a server job?
kjaouhari
Participant
Posts: 325
Joined: Thu Mar 16, 2006 10:22 am

Post by kjaouhari »

Thanks for your help, I did check this 2 files but without results. Here is a sample of the systemout.log :

[7/15/09 9:54:56:232 CEST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info.
[7/15/09 9:54:57:170 CEST] 0000000a AdminInitiali A ADMN0015I: The administration service is initialized.
[7/15/09 9:54:59:107 CEST] 0000000a SystemOut O PLGC0057I: Plug-in configuration service is started successfully.
[7/15/09 9:54:59:232 CEST] 0000000a PMIImpl A PMON1001I: PMI is enabled
[7/15/09 9:54:59:842 CEST] 0000000a SibMessage I [:] CWSIU0000I: Release: WAS602.SIB Level: o0618.10
[7/15/09 9:54:59:904 CEST] 0000000a SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[7/15/09 9:54:59:967 CEST] 0000000a AuditServiceI A SECJ6004I: Security Auditing is disabled.
[7/15/09 9:55:00:514 CEST] 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 <null>. The optional initialization class name is <null>.
[7/15/09 9:55:00:514 CEST] 0000000a distSecurityC I SECJ0309I: Java 2 Security is disabled.
[7/15/09 9:55:00:623 CEST] 0000000a Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[7/15/09 9:55:00:654 CEST] 0000000a distSecurityC I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[7/15/09 9:55:00:685 CEST] 0000000a distSecurityC I SECJ0240I: Security service initialization completed successfully
[7/15/09 9:55:01:060 CEST] 0000000a ObjectPoolSer I OBPL0007I: Object Pool Manager service is disabled.
[7/15/09 9:55:01:076 CEST] 0000000a J2EEServiceMa I ASYN0059I: Work Manager service initialized successfully.
[7/15/09 9:55:01:123 CEST] 0000000a CScopeCompone I CSCP0002I: Compensation service is disabled.
[7/15/09 9:55:01:685 CEST] 0000000a SibMessage I [:] CWSID0021I: Configuration reload is enabled for bus ISF_defaultBus.
[7/15/09 9:55:01:904 CEST] 0000000a ActivitySessi I WACS0045I: ActivitySession service is disabled.
[7/15/09 9:55:01:920 CEST] 0000000a SOAPContainer I WSWS1062I: SOAP Container Service has been initialized.
[7/15/09 9:55:01:951 CEST] 0000000a SchedulerServ I SCHD0036I: The Scheduler Service is initializing.
[7/15/09 9:55:01:982 CEST] 0000000a SchedulerServ I SCHD0037I: The Scheduler Service has been initialized.
[7/15/09 9:55:02:482 CEST] 0000000a StartUpServic I STUP0008I: The Startup Beans service is disabled.
[7/15/09 9:55:02:498 CEST] 0000000a I18nService I I18N0010I: The Internationalization service is created on server1.
[7/15/09 9:55:02:498 CEST] 0000000a I18nServiceSe I I18N0010I: The Internationalization service is disabled on server1.
[7/15/09 9:55:04:107 CEST] 0000000a SASRas A JSAS0001I: Security configuration initialized.
[7/15/09 9:55:04:342 CEST] 0000000a SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM
[7/15/09 9:55:04:342 CEST] 0000000a SASRas A JSAS0003I: Authentication mechanism: LTPA
[7/15/09 9:55:04:342 CEST] 0000000a SASRas A JSAS0004I: Principal name: null/admin.datastage
[7/15/09 9:55:04:357 CEST] 0000000a SASRas A JSAS0005I: SecurityCurrent registered.
[7/15/09 9:55:06:607 CEST] 0000000a SASRas A JSAS0006I: Security connection interceptor initialized.
[7/15/09 9:55:06:639 CEST] 0000000a SASRas A JSAS0007I: Client request interceptor registered.
[7/15/09 9:55:06:717 CEST] 0000000a SASRas A JSAS0008I: Server request interceptor registered.
[7/15/09 9:55:06:717 CEST] 0000000a SASRas A JSAS0009I: IOR interceptor registered.
[7/15/09 9:55:07:498 CEST] 0000000a CoordinatorIm I HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup.
[7/15/09 9:55:07:545 CEST] 0000000a DCSPluginSing I HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup.
[7/15/09 9:55:07:748 CEST] 0000000a NameServerImp A NMSV0018I: Name server available on bootstrap port 2809.
[7/15/09 9:55:08:592 CEST] 0000000a UserRegistryI A SECJ0136I: Custom Registry:com.ascential.acs.security.directory.custom.websphere.ASBUserRegistry has been initialized
[7/15/09 9:55:15:654 CEST] 0000000a SystemOut O [org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl] ERROR: Error getting Connection from DriverManager with url (jdbc:ibm:sqlserver://GUYADWH25634:1433;DatabaseName=XMETA) and driver (com.ibm.isf.jdbc.sqlserver.SQLServerDriver)
[7/15/09 9:55:15:654 CEST] 0000000a SystemOut O [IBM][SQLServer JDBC Driver][SQLServer]Login failed for user 'xmeta'. Reason: The account is disabled.
[7/15/09 9:55:15:670 CEST] 00000012 SASRas A JSAS1501E: [{0}] J2EEAuditEventFactory was not initialized.
[7/15/09 9:55:15:717 CEST] 0000000a SystemOut O 0 ERROR [Thread-1] basic.BasicPersistence - BasicPersistece initialize failed
com.ascential.xmeta.persistence.orm.PersistentEObjectPersistenceException: com.ascential.xmeta.persistence.orm.ObjectStorageException
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.getBroker(OjbPersistentEObjectPersistence.java:178)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.getBroker(OjbPersistentEObjectPersistenceRegistry.java:301)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.loadPackageCache(OjbPersistentEObjectPersistenceRegistry.java:350)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistenceRegistry.initialize(OjbPersistentEObjectPersistenceRegistry.java:131)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.initialize(OjbPersistentEObjectPersistence.java:331)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistence.initialize(BasicPersistence.java:410)
at com.ascential.xmeta.persistence.impl.basic.BasicPersistenceManager.initialize(BasicPersistenceManager.java:75)
at com.ascential.xmeta.repository.core.impl.DefaultSandbox.<init>(DefaultSandbox.java:132)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44)
at java.lang.reflect.Constructor.newInstance(Constructor.java(Compiled Code))
at java.lang.Class.newInstance3(Class.java:367)
at java.lang.Class.newInstance(Class.java:305)
at com.ascential.xmeta.repository.core.CoreRepositoryFactory.createSandbox(CoreRepositoryFactory.java:97)
at com.ascential.xmeta.client.repository.core.impl.DefaultSandboxPOJOClient.initialize(DefaultSandboxPOJOClient.java:83)
at com.ascential.xmeta.client.repository.core.CoreRepositoryClientFactory.createSandboxClient(CoreRepositoryClientFactory.java:125)
at com.ascential.acs.security.repository.ASBRepositoryImpl.getSandbox(ASBRepositoryImpl.java:520)
at com.ascential.acs.security.repository.ASBRepositoryImpl.begin(ASBRepositoryImpl.java:128)
at com.ascential.acs.security.directory.custom.ASBDirectoryImpl.getRepository(ASBDirectoryImpl.java:81)
at com.ascential.acs.security.directory.custom.ASBDirectoryImpl.checkPassword(ASBDirectoryImpl.java:130)
at com.ascential.acs.security.directory.custom.ASBDirectory.checkPassword(ASBDirectory.java:72)
at com.ascential.acs.security.directory.custom.websphere.ASBUserRegistry.checkPassword(ASBUserRegistry.java:90)
at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296)
at com.ibm.ws.security.ltpa.LTPAServerObject.authenticate(LTPAServerObject.java:573)
at com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:437)
at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java:351)
at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631)
at javax.security.auth.login.LoginContext.login(LoginContext.java:557)
at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376)
at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1049)
at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:889)
at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:880)
at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2166)
at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928)
at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341)
at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298)
at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101)
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:570)
Caused by: com.ascential.xmeta.persistence.orm.ObjectStorageException
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbObjectPersistence.getBroker(OjbObjectPersistence.java:132)
at com.ascential.xmeta.persistence.orm.impl.ojb.OjbPersistentEObjectPersistence.getBroker(OjbPersistentEObjectPersistence.java:175)
... 65 more
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

kjaouhari wrote:[7/15/09 9:55:15:654 CEST] 0000000a SystemOut O [IBM][SQLServer JDBC Driver][SQLServer]Login failed for user 'xmeta'. Reason: The account is disabled.
...
kjaouhari
Participant
Posts: 325
Joined: Thu Mar 16, 2006 10:22 am

Post by kjaouhari »

Thanks ArndW
Any clue on where I can enable it ?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Is it an ORACLE repository? If yes, the DBA should do an "alter user xmeta account unlock;". But you will need to find out who is trying to login with the wrong password since that error is bound to occur again.
kjaouhari
Participant
Posts: 325
Joined: Thu Mar 16, 2006 10:22 am

Post by kjaouhari »

it's an SQL server, ok I'm going to find out and let you know
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

"alter login xmeta enable;" might do the trick.
kjaouhari
Participant
Posts: 325
Joined: Thu Mar 16, 2006 10:22 am

Post by kjaouhari »

Thanks very much ArndW, I've checked with my dba and that's now ok. :P

Happy to have fixed this issue without reinstalling
anudako
Participant
Posts: 20
Joined: Tue Aug 24, 2010 5:21 am
Location: Kerala

same issue db2 repository-but not able start WAS

Post by anudako »

hi,

i am facing the same issue.can not log in to datastage designer,administrator and director and not able to start the application server.
Saw the reason as xmeta is disables and mine is db2 repository.
Could yiou please help me on enabling my db2 xmeta?
anudako
Participant
Posts: 20
Joined: Tue Aug 24, 2010 5:21 am
Location: Kerala

same issue db2 repository-but not able start WAS

Post by anudako »

hi,

i am facing the same issue.can not log in to datastage designer,administrator and director and not able to start the application server.
Saw the reason as xmeta is disables and mine is db2 repository.
Could yiou please help me on enabling my db2 xmeta?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

What is wrong with trying my suggestion in my last post?
anudako
Participant
Posts: 20
Joined: Tue Aug 24, 2010 5:21 am
Location: Kerala

unlock xmeta-db2

Post by anudako »

[quote="ArndW"]What is wrong with trying my suggestion in my last post? ...[/quote]
thanks ArndW for the reply..

it was given- can use "alter user xmeta account unlock;" if it is oracle repository.
Mine is Db2 and this command is not working.
We don't have a DBA and DB2 is installed as part of datastage installation.

That is the confusion.
anudako
Participant
Posts: 20
Joined: Tue Aug 24, 2010 5:21 am
Location: Kerala

unlock xmeta-db2

Post by anudako »

[quote="ArndW"]What is wrong with trying my suggestion in my last post? ...[/quote]
thanks ArndW for the reply..

it was given- can use "alter user xmeta account unlock;" if it is oracle repository.
Mine is Db2 and this command is not working.
We don't have a DBA and DB2 is installed as part of datastage installation.

That is the confusion.
anudako
Participant
Posts: 20
Joined: Tue Aug 24, 2010 5:21 am
Location: Kerala

Post by anudako »

[quote="ArndW"]What is wrong with trying my suggestion in my last post? ...[/quote]
''alter login xmeta enable'' also not working
Post Reply