Windows command script extensions stop working which causes weblogic scripts to fail
Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 10.3 to 10.3.6
Microsoft Windows x64 (64-bit)
When trying to run setDomainEnv in the Windows command shell to set the weblogic environment, it is seen that key environment variables get randomly corrupted in that the true path is corrupted to a random string of letters and numbers :
WL_HOME=C:\oracle\WL9421~1\WLSERV~1.3 instead of WLS_HOME=C:\oracle\WLS1036pwd\wlserver_10.3\server
JAVA_HOME=C:\oracle\WL9421~1\JDK160~1 instead of JAVA_HOME=C:\oracle\WLS1036pwd\jdk160_29
WEBLOGIC_CLASSPATH=C:\oracle\WL9421~1\patch_wls1036(...) instead of JAVA_HOME=C:\oracle\WLS1036pwd\jdk160_29(...)
This is seen after running setDomainEnv from the windows command prompt, followed by running 'set' which shows all the environment variables.
Microsoft updates were recently loaded and the computer rebooted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms