Support Tip: Windows Cell Manager starting

0 Likes
1 month ago

Windows DP CM, when starting the GUI:- 12:1613 CS API must be initialized

On a Windows Cell Manager when starting the Data Protector GUI there is an error... <br> 12:1613 CS API must be initialized before using CS API calls <br>After clicking OK there is a second error... <br> Unable to get Authentification token. 

Windows DP CM, when starting the GUI:- 12:1613 CS API must be initialized

Summary
On a Windows Cell Manager when starting the Data Protector GUI there is an error... 12:1613 CS API must be initialized before using CS API calls After clicking OK there is a second error... Unable to get Authentification token. Check if Appserver is running. After clicking OK there is a third error... 12:1604 Cannot reach the CRS on the Cell Manager system. CRS on the Cell Manager host is not reachable or is not up and running.
Problem:
On a Windows Cell Manager (CM) when starting the Data Protector (DP) GUI there is an error... 
   12:1613 CS API must be initialized before using CS API calls

After clicking OK there is a second error...
   Unable to get Authentification token. Check if Appserver is running.

After clicking OK there is a third error...
   12:1604 Cannot reach the CRS on the Cell Manager system.
   CRS on the Cell Manager host is not reachable or is not up and running.
  
Checking the status of Data Protector  with `omnisv -status` may show many are not running.

Trying to start DP at the cli gives
C:\Users\Administrator>omnisv -start
Cannot start "crs" service, system error:
[1069] The service did not start due to a logon failure.
Cannot start "hpdp-idb" service, system error:
[1069] The service did not start due to a logon failure.
Cannot start "hpdp-idb-cp" service, system error:
[1069] The service did not start due to a logon failure.
Cannot start "hpdp-as" service, system error:
[1069] The service did not start due to a logon failure.


Problem confirmed on DP 10.70 and 10.91.
Very likely to be similar on other DP 10.x0 versions.

Possible Cause:
A common cause of this problem is that the account password has been changed.

Solution:
In Services edit the following four services
   Data Protector Application Server
   Data Protector CRS
   Data Protector IDB
   Data Protector IDB connection pool
to enter the new account password.   

Labels:

Support Tip
Comment List
Anonymous
Related Discussions
Recommended