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: ...10.5 Linux Upgrade failure and solutions
Traces in logs : 1. java.lang.Exception: InitPgsqlScript exited with value :: 1 at com.adventnet.persistence.PostgresPreProcessor.executeInitPgsqlScript(PostgresPreProcessor.java:1733) 2. PGSQL Permission related errors. 3. SDP MSP installed as root ...Normal emails sent from Outlook desktop app is considered as bounced mail due to the blank return-path header value (<>)
Normal emails sent from Outlook desktop app is considered as bounced mail due to the blank return-path header value (<>) Debug: For bounced mail detection, internally we will be checking whether the return-path header value is blank or not. In ...