Hi,
I am trying to start the integration server 9.10 and i am getting the following error which i have attached .
I have attached the log files which are present in my installation directory:–
C:\SoftwareAG\profiles\IS_default\logs

And only three log files have been generated namely :-
wrapper.log
platform.log
sag-osgi.log

There is not any server.log file.

Please help me out as i have got no clue whatsoever as to what is happening.
Its urgent.
platform.log (5.1 KB)
sag-osgi.log (35.7 KB)
wrapper.log (15.9 KB)

Share your OS details.

After starting the IS server check the server.log present at location :SoftwareAG\IntegrationServer\instances\default\logs

Do you see any errors in server.log?

Hi Mahesh,
Thank you for quick response…As per your instruction i have started IS and i am attaching the screen shot of both the console and server.log .
My OS Details are:-
64-bit, Windows10,2 GB RAM,*64-based processor.

.Kindly help me out here.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/231ddd0cda9ec6c01bde0a4227b0357c26c32f45_2_1035x235.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/231ddd0cda9ec6c01bde0a4227b0357c26c32f45.jpeg 2x" data-dominant-color="EFEFEF">

server.jpg1067×244 53.2 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/2e7b4982f57f2ea082b25ffec4f2e5c26a1cccb6_2_1035x252.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/2e7b4982f57f2ea082b25ffec4f2e5c26a1cccb6.jpeg 2x" data-dominant-color="0D0D0D">

sag1.JPG1116×272 72.6 KB

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/81433f93a697f4b0fb1e8c24fa5deea9b9276d4a_2_1035x684.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/81433f93a697f4b0fb1e8c24fa5deea9b9276d4a.jpeg 2x" data-dominant-color="0C0C0C">

sag.JPG1089×720 160 KB

Hi Atul,

unfortunately, the server.log seems not to be a plain text file.

Can you verify that, please?

Regards,
Holger

Attach the correct Server.log file to assist you further. If you face any errors in server log find to search the same error on TechCommunity I am sure you will find a resolution.

Hi all,
Apologies for the wrong file.
I am pasting the contents of server.log here :-

2016-08-21 09:02:59 IST [ISS.0025.0001C] Integration Server 9.10.0.0 Build 106
2016-08-21 09:03:12 IST [ISS.0025.0006I] License Manager started
2016-08-21 09:03:38 IST [ISS.0025.0050W] The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it.
2016-08-21 09:04:04 IST [ISS.0025.0041I] FIPS mode not initialized
2016-08-21 09:05:10 IST [ISS.0025.0017I] Repository Manager started
2016-08-22 08:38:44 IST [ISS.0025.0001C] Integration Server 9.10.0.0 Build 106
2016-08-22 08:38:51 IST [ISS.0025.0006I] License Manager started
2016-08-22 08:39:06 IST [ISS.0025.0050W] The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it.
2016-08-22 08:39:22 IST [ISS.0025.0041I] FIPS mode not initialized
2016-08-22 08:39:57 IST [BAS.0123.0001I] FSData full consistency check is being performed. Db:WmRepository4\RepoV4
2016-08-22 08:40:09 IST [ISS.0025.0017I] Repository Manager started
2016-08-23 08:28:04 IST [ISS.0025.0001C] Integration Server 9.10.0.0 Build 106
2016-08-23 08:28:08 IST [ISS.0025.0006I] License Manager started
2016-08-23 08:28:10 IST [ISS.0025.0050W] The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it.
2016-08-23 08:28:16 IST [ISS.0025.0041I] FIPS mode not initialized
2016-08-23 08:28:35 IST [BAS.0123.0001I] FSData full consistency check is being performed. Db:WmRepository4\RepoV4
2016-08-23 08:28:46 IST [ISS.0025.0017I] Repository Manager started
2016-08-23 08:29:33 IST [ISS.0096.0004E] JDBCConnectionManager: embedded database objects not created: java.sql.SQLException: Failed to create database ‘embedded’, see the next exception for details.
2016-08-23 08:29:33 IST [ISS.0096.0004E] JDBCConnectionManager: embedded database objects not created: java.sql.SQLException: Failed to create database ‘embedded’, see the next exception for details.
2016-08-23 08:29:33 IST [ISS.0096.0002W] JDBCConnectionManager: creating Embedded Pool Alias for ISInternal.
2016-08-23 08:29:37 IST [ISS.0096.0005C] JDBCConnectionManager: initialization failed with exception Failed to create database ‘embedded’, see the next exception for details.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ActiveTransfer functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for Adapters functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for CentralUsers functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for DocumentHistory functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISCoreAudit functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for MobileSupport functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessAudit functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessEngine functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for TN functional alias, check configuration.
2016-08-23 08:29:37 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for Xref functional alias, check configuration.
2016-08-23 08:29:38 IST [ISS.0095.0026W] The AuditConfig.xml file was not found and is being created. The audit logging system is using default settings.
2016-08-23 08:29:38 IST [ISS.0095.0025W] The auditing.cnf file was not found and is being created.
2016-08-23 08:29:38 IST [ISS.0095.0025W] The transient.sql.errors.xml file was not found and is being created.
2016-08-23 08:32:39 IST [ISS.0095.0013I] Audit Logging initialized.
2016-08-23 08:32:49 IST [ISS.0017.0080I] Migrated the SoftwareAG-IS-MFT.xml cache manager configuration to the Ehcache 2.8.x format.
2016-08-23 08:33:21 IST [ISS.0033.0168C] Cluster Node Name: atul-pc.
2016-08-23 08:33:42 IST [ISS.0025.0021I] ACL Manager started
2016-08-23 08:33:55 IST [ISS.0025.0008I] State Manager started
2016-08-23 08:33:56 IST [ISS.0025.0010I] Service Manager started
2016-08-23 08:33:56 IST [ISS.0025.0020I] Validation Processor started
2016-08-23 08:33:56 IST [ISS.0025.0022I] Statistics Processor started
2016-08-23 08:33:56 IST [ISS.0025.0018I] Invoke Manager started
2016-08-23 08:33:59 IST [ISS.0025.0012I] Cache Manager started
2016-08-23 08:34:01 IST [ISS.0098.0121I] The default Broker was not detected while initializing the dispatch.cnf file. Broker Settings will automatically be disabled.

https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/29446be68ef4fd069690e761717977f0997ce41b_2_1035x435.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/29446be68ef4fd069690e761717977f0997ce41b.jpeg 2x" data-dominant-color="151515">

console.JPG1077×453 158 KB

Hi All,

For the error:–" The JCE Unlimited Strength Jurisdiction Policy File was not found. Please install it." ,
I have downloaded the latest jce_policy_8 .zip file and have updated the following directories:-
1)C:\SoftwareAG\ppmmashzone\installer_temp\jre\linux64\jre\lib\security
2)C:\SoftwareAG\ppmmashzone\installer_temp\jre\windows64\jre\lib\security
3)C:\SoftwareAG\ppmmashzone\server\jre\lib\security
4)C:\SoftwareAG\jvm\jvm\jre\lib\security
And now it has been resolved with the status message:-The JCE Unlimited Strength Jurisdiction Policy File was found

But at present i have the following error messages which needs solution and i don’t know as to what should be done in this case :-

2016-08-23 10:17:59 IST [ISS.0012.0012E] Authentication of user “null” failed with exception: com.softwareag.security.jaas.principals.SagGeneralSecurityException: SagGeneralSecurityException while parsing assertion com.softwareag.security.jaas.principals.SagGeneralSecurityException: SAML assertion not yet valid
at com.softwareag.security.idp.saml2.SAML2AssertionEngine.parseAssertion(SAML2AssertionEngine.java:315)
at com.wm.app.b2b.server.auth.saml.SAMLOSGiManager.getSagSecurityToken(SAMLOSGiManager.java:152)
at com.wm.app.b2b.server.auth.jaas.SamlOSGiLoginModule.authenticate(SamlOSGiLoginModule.java:88)
at com.softwareag.security.jaas.login.SagAbstractLoginModule.login(SagAbstractLoginModule.java:281)
at com.softwareag.platform.jaas.proxy.ProxyLoginModule.login(ProxyLoginModule.java:35)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:755)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:195)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:682)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:680)
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:587)
at com.wm.app.b2b.server.AuthenticationManager.authenticate_JAAS(AuthenticationManager.java:153)
at com.wm.app.b2b.server.AuthenticationManager.authenticate(AuthenticationManager.java:98)
at com.wm.app.b2b.server.HTTPState.getSAMLAuthenticatedUser(HTTPState.java:1176)
at com.wm.app.b2b.server.HTTPState.getAuthenticatedUser(HTTPState.java:929)
at com.wm.app.b2b.server.HTTPState.processHeader(HTTPState.java:280)
at com.wm.app.b2b.server.Dispatch.processHeader(Dispatch.java:271)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:369)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.softwareag.security.jaas.principals.SagGeneralSecurityException: SAML assertion not yet valid
at com.softwareag.security.idp.saml2.SAML2AssertionEngine.parseAssertion(SAML2AssertionEngine.java:162)
… 24 more
.
2016-08-23 10:18:13 IST [ISS.0137.0006E] Scheduler: Error initializing scheduler: Failed to create database ‘embedded’, see the next exception for details.

Also , I tried adding server details in the designer itself with credentials:-
Username:-Administrator
Password:-manage
It says:- “Unable to validate Integration Server on the specified port”

I am attaching the log files with the latest updates.
Kindly guide me here.
Thanks for your patience to go through this long message ,but i tried to give you the full details of what is happening.
WMERROR_20160823_101052.log (467 KB)
server.log (28.3 KB)
stats.log (6.15 KB)

Hi Atul,

the IS should be available on Ports 9999 (Diagnostics) and 5555 (Standard HTTP).

The unlimited policies are not related to this issue.

More likely you should check what the issue is related to the embedded database as well as if the MWS has been initialized correctly.

Regards,
Holger