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 ADSelfService Plus?
Related Articles
Application startup issue due to mismatch in java
A startup issue after the upgrade to the version 14.3 Error message: "Application startup halted due to mismatch in java". Issue: After a JRE upgrade, typically, if the "jre_old" folder exists, it will be deleted. Then, the "jre" folder will be ...Error - Sanity Failed - Upgrade from 8121 to 11
While upgrading from 8121 to 11, after executing Updatemanager.bat and if the update fails, You need to check the Updatemanager logs in the path < Support Center Plus Application path -> Server-> Default-> Logs > . And if you find the below ...Mail fetching failed - PKIX path building failed.
Cause: If the SSL Certificate in mail server is a self signed certificate then it is not imported in the ServiceDeskPlus-MSP java environment while using the POPS/IMAPS protocol. Error Trace in logs: javax.net.ssl.SSLHandshakeException: ...Upgrade failure from 1420X to 14300.
Error trace: 5 Sep, 2023 6:08:56 PM [com.adventnet.tools.update.installer.Unzipper] [INFO] : lib/phantomjs/linphantomjs/phantomjs 25 Sep, 2023 6:08:56 PM [com.adventnet.tools.update.installer.Unzipper] [SEVERE] : ERR:Exception while writing ...Upgrade Failure due to the presence of CtrlZ Failure
This issue (SD-118352) in fixed in version 14710. Post this release, these characters are handled in the migration itself. If you are planning to migrate from version less than 14610 to 14610, then you can directly migrate to 14710, to handle this ...