Java Token Client throwing error 40039
2 years ago
Originally Published: 2014-12-10
Article Number
000049722
Applies To
RSA Data Protection Manager Java Client
Issue
DPM Java Client fails to initialize with the following error:
2014-06-23 11:38:55,741 [WebContainer : 2] FATAL rsa.RSAClientTokenContext - DPM Exception: 40036 
com.rsa.token.BusinessServiceException 
at com.rsa.token.w.ad.c(Unknown Source) 
at com.rsa.token.w.ad.g(Unknown Source) 
at com.rsa.token.w.as.e(Unknown Source) 
at com.rsa.token.TokenConfig.d(Unknown Source) 
at com.rsa.token.TokenConfig.a(Unknown Source) 
at com.rsa.token.TokenConfig.<init>(Unknown Source) 

The error code 40036 refers to the C client constant named TC_ERR_REG_STORE_FAILED with the following documentation associated with it:
Indicates that the client is not able to write data in registration file. 
 
Cause
In one particuliar scenario, the error was caused by multiple IBM WebSphere instances all starting at the same time. Two of which running a webapp doing tokenization and / or detokenization and one instance running DPM server. DPM server had unattended restart locked, waiting for a user to provide the HSM PIN. After re-enabling unattended restart, the same use case of starting multiple WebSphere instances simultaneously was successful.

Related Articles

Trending Articles

Don't see what you're looking for?