The command unims -register returns "Unable to connect to UVMS: error 300 (-1)" in case of a timeout
search cancel

The command unims -register returns "Unable to connect to UVMS: error 300 (-1)" in case of a timeout

book

Article ID: 85660

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

When trying to register a node ( when installing or registering somewhere else), the command unims -register throws the error 300.
It is impossible to know wether the issue is related to a wrong login / password or a timeout on the reply from the uvms to the request.

Error Message :
In case there is an error in the registration of a DUAS on a UVMS, the error message does not provide useful information to the user:
Examples:
$UNI_DIR_EXEC/unims -register -mshost uvms.domain.com -msport 4184 -login <incorrect username> -pwd password--> Incorrect login
$UNI_DIR_EXEC/unims -register -mshost uvms.domain.com -msport 4184 -login <correct username>-pwd wrong_password--> Incorrect password


The same error on the command unims -register appears after a timeout of 15 seconds in case there is a network issue between the UVMS and the node.
Unable to connect to UVMS: error 300 (-1)

Environment

Component: Dollar Universe

Component version: 6.x

Cause

Cause type: Defect

Resolution

Solution:

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Dollar Universe
Sub-Component: Application.Server
Dollar Universe 6.7.21 - Available

 

Solution details:

The command unims -register will now throw an error 205 for timeout errors when waiting for the reply of the UVMS.

The new output of the command in case of a timeout is:


Unable to connect to UVMS: error 205 (check U_UVMS_TIMEOUT parameter) (-1)


Therefore, you will need to increase the value of the variable U_UVMS_TIMEOUT (15 seconds by default).

For that, you can launch the following command to increase it to 120 seconds:

$UNI_DIR_EXEC/unisetvar U_UVMS_TIMEOUT 120

Additional Information

In case the node is already registered, make sure to delete it from the node list before trying to register it.