Article ID: 129369, created on Sep 2, 2016, last review on Sep 2, 2016

  • Applies to:
  • Operations Automation 6.0

Symptoms

An attempt to start PEM service results in the error:

The service did not respond in a timely fashion

The service hangs in starting state afterwards.

The Event Viewer logs the message continuously:

The specified resource type cannot be found in the image file

In fact the error message is not related to the problem, it is just logged every time the service is started, and it is trying to do that in cycle.

PAU service was started successfully, but its log file C:\Program Files (x86)\SWsoft\PEM\jboss-eap-6.2\standalone\log\standalone.log contains the error:

160902 17:32:59 INFO  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 59) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
160902 17:33:00 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 59) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
...
Caused by: java.sql.SQLException: Network error IOException: Connection refused: connect

Cause

MSSQL service is down on the Database Server.

Resolution

  1. On the OA Management Node, open Task Manager and kill watchdog.exe process.
  2. Stop PAU service.
  3. On the MSSQL database server, start MSSQL service.
  4. Start PAU service back.
  5. Start PEM service back.

Search Words

The service did not respond in a timely fashion

Network error IOException: Connection refused: connect

Could not create connection

The specified resource type cannot be found in the image file

system down

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF