RADSKMAN – error codes and fixes

RADSKMAN EXIT CODE [0] – request completed successfully

RADSKMAN EXIT CODE [109]
Cause: No applications available in the software catalog. Please contact your system administrator for assistance.
Fix: Check if nvdkit.exe is missing from Program files\Novadigm or there are no assignments for that particular machine

RADSKMAN EXIT CODE [200]
Cause: Radia was unable to perform the requested action due to a network connection failure with the Radia server
Fix: Check if Radia server may be shutdown, disconnected from network, or RCS service not started

RADSKMAN EXIT CODE [209]
Cause: A transmission error occurred when transferring the application files from RCS
Fix: Check whether SAP.EDM is missing from Novadigm\Lib folder.
Check whether network is busy and whether local RPS or RCS do not have requested resource files for download

RADSKMAN EXIT CODE [650]
Cause: Server stopped application configuration
1. Workstation fails to resolve the policy
2. Invalid policy assignment.
3. RCS server not available or the RCS service would have hanged

Fix:
1. Workstation fails to resolve the policy if the user assigned to the workstation doesn’t exists. Need to remove the policy for the user.

2. While assigning the policy for the user if there is a typo error in the ZSTRING name or with the DOMAIN name the client wouldn’t able to get the desired policy state and hence throws the 650 error. Removing/correcting the invalid policy will solve the issue.

3. Get the server back to network. In case of RCS service hang restart the RCS service. Wait for 15 minutes for the DB to come up.

RADSKMAN EXIT CODE [653]
Cause: Server is down for maintenance, updating database.

Fix: During the final phase of synchronization the RCS server DB in the target server will get hard locked while committing the changes. The DB will get locked like this only for 5-10 minutes. Please try to perform a connect after few minutes the connect will run fine.

RADSKMAN EXIT CODE [111]
Application Name/ Command wrong or package does not exist/capture in Radia Server

RADSKMAN EXIT CODE [709]
Cause: This application failed to install correctly. Please contact your system administrator for assistance.

Fix: Search for the error code in relevant log and ZSTRING mapped to it. Delete the ZSERVICE catalogs for the particular applications from C:\Program Files\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE and run the machine connect to get the application installed properly

– Also check whether nvdkit.exe exists in the novadigm folder and wscript.exe exists in the windows system folder

RADSKMAN EXIT CODE [833]
Cause: Error uninstalling service.
Fix: Delete the ZSERVICE catalog for the particular application from C:\Program Files\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE and run the machine connect in case of problem with machine connect.

Fix: Delete the ZSERVICE catalog from C:\Program Files\Novadigm\Lib\HOMEBOX\RADIA\SOFTWARE\ZSERVICE and run the user connect in case of problem with user connect. (Have to navigate to ROAMING folder under LIB in case of roaming user). In general the HOMEBOX folder or the ROAMING folder from LIB directory can be renamed and the user can be triggered to solve the problem.

RADSKMAN EXIT CODE [860]
Cause: Process Timed Out

Fix: When the server PM component is busy or unwanted worker queue is running client will be thrown with this error. Connect can be performed later or restarting the PM Service in the RCS will solve the issue immediately.

Advertisements

~ by iFFa on December 4, 2012.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: