Upgrade Pre-Validation error due to 'no AdventnetOper_64 in java.library.path'

Upgrade Pre-Validation error due to 'no AdventnetOper_64 in java.library.path'

Issue :  Upgrade Pre-validation error occurs with trace  'no AdventnetOper_64 in java.library.path'

Possible Causes :
1) Mis-configuration in {ServiceDesk}/bin/scripts/UpdMgr.bat file
2) Applying patch for validation more than once in UpdateManager dialog box.

1) Mis-Configuration in {ServiceDesk}/bin/scripts/UpdMgr.bat file
This issue occur when customer includes parameter to skip backup during upgrade.

In UpdMgr.bat file , we have the following command ,
%JAVA_HOME%\bin\java -Xmx512m  %JAVA_OPTS% -Dtier-type=BE -Djava.library.path=.\lib\native -Dtier-id=BE1 com.adventnet.tools.update.installer.UpdateManager -u server\default\conf %*
In the above command ,  -Djava.library.path=.\lib\native is used to set the library path during upgrade.
We need to ensure that there is a space before and after this command.

Mis-configuration Examples:

1)%JAVA_HOME%\bin\java -Xmx512m  %JAVA_OPTS% -Dtier-type=BE -Djava.library.path=.\lib\native-Dtier-id=BE1 com.adventnet.tools.update.installer.UpdateManager -u server\default\conf %*

Inference: No space after  -Djava.library.path=.\lib\native

2) %JAVA_HOME%\bin\java -Xmx512m  %JAVA_OPTS% -Dtier-type=BE  -DSkipForcedBackUp=true-Djava.library.path=.\lib\native -Dtier-id=BE1 com.adventnet.tools.update.installer.UpdateManager -u server\default\conf %*

Inference: No space before  -Djava.library.path=.\lib\native.
Note : On customer end , this happens frequently as when they add the paramater    -DSkipForcedBackUp=true to skip backup during upgrade.

2) Applying patch for validation more than once in UpdateManager Dialog box.
This issue occurs when the below mentioned steps are made.

Step 1:  Open command prompt as admin and navigate to {ServiceDesk}/bin/ and execute UpdateManger.bat command
Step 2:  Select a ppm file using "browse" in UpdateManager dialog box. Pre-validation of the patch will happen and patch will be allowed to apply
Step 3:  Again select "browse" in UpdateManager dialog box and choose the same ppm file.
Step 4:  Now , an error will be thrown as   "no AdventnetOper_64 in java.library.path"   during Pre-validation of the applied patch.

This can be resolved by closing UpdateManager dialog box and then re-opening again using UpdateManager.bat file.

Note : This is a known issue and framework team is working on it.




                  New to ADManager Plus?

                    New to ADSelfService Plus?