I was starting our IS and encountered the errors shown below.
I tried shutting down first but it was giving me an error that it cannot connect to server…
Please help me…what I might have done wrongly? Thanks.
2009-11-02 06:13:00 PST [ISS.0025.0001C] Integration Server 7.1.2.0 Build 124
2009-11-02 06:13:00 PST [ISS.0025.0006I] License Manager started
2009-11-02 06:13:00 PST [ISS.0025.0041I] FIPS mode not initialized
2009-11-02 06:13:04 PST [ISS.0025.0049I] The Unlimited Policy File was found
2009-11-02 06:13:04 PST [BAP.0001.0011I] PasswordManagerFactory - unable to set parameter, no such method: setUseGUI
2009-11-02 06:13:09 PST [BAS.0123.0001I] FSData full consistency check is being performed. Db:WmRepository4/RepoV4
2009-11-02 06:13:14 PST [ISS.0025.0017I] Repository Manager started
2009-11-02 06:16:03 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for DocumentHistory functional alias, check configuration.
2009-11-02 06:35:49 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISInternal functional alias, check configuration.
2009-11-02 06:38:37 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for Xref functional alias, check configuration.
2009-11-02 06:58:24 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISCoreAudit functional alias, check configuration.
2009-11-02 07:01:11 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for CentralUsers functional alias, check configuration.
2009-11-02 07:20:58 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for DocumentHistory functional alias, check configuration.
2009-11-02 07:23:45 PST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessAudit functional alias, check configuration.
verify whether the the functional alias DocumentHistory ,ISInternal functional alias etc have properly associated with the Pool Alias defination.
Go to Administrator , Settings–>JDBC Pools
If you are not associted the Pool Alias defination to the DocumentHistory ,ISInternal ,etc functional aliases, just click on the edit and associate the pool defination and test.
Thanks for the response.
I was able to have our IS running, but then again had another series of errors:
Adapter Runtime: Facility 1 - JDBCAdapter registered with bundle com.wm.adapter.wmjdbc.JDBCAdapterResourceBundle.
[ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ADA.1.204] Cannot connect to the database with DataSource class “oracle.jdbc.pool.OracleDataSource”.Io exception: The Network Adapter could not establish the connection
[ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
[ADA.1.204] Cannot connect to the database with DataSource class “oracle.jdbc.pool.OracleDataSource”.
Io exception: The Network Adapter could not establish the connection
[ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ADA.1.204] Cannot connect to the database with DataSource class “oracle.jdbc.pool.OracleDataSource”.Io exception: The Network Adapter could not establish the connection
[ART.0114.1007E] Adapter Runtime: Error Logged. See Error log for details. Error: [ART.114.13] Adapter Runtime: Error occurred while Adapter Runtime was loading adapter type “JDBCAdapter”.
[ART.114.9] Adapter Runtime: Error(s) while registering adapter type JDBCAdapter.
[ISS.0028.0013E] Startup service exited with the following error: com.wm.pkg.art.error.DetailedServiceException: [ART.114.13] Adapter Runtime: Error occurred while Adapter Runtime was loading adapter type “JDBCAdapter”.
[ART.114.9] Adapter Runtime: Error(s) while registering adapter type JDBCAdapter.