Skip to main content
Solved

Node Manager Won't Start IFS APP 10

W
Do Gooder (Partner)
Forum|alt.badge.img+6

Hi All,

 

Any suggestions would be appreciated, I have taken a copy of TEST to put on to a new virtual machine. The IFS home builds if I use a new RTM build or a clone of the existing TEST onto the new box. I keep however receiving this error in the node manager logs. It implies it can’t find this file that I can physically see here -

 

 

<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Loading domains file: D:\IFS\IFSExt\IFST\wls_domain\NEW_IFST_PA\nodemanager\nodemanager.domains>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Upgrade> <Setting NodeManager properties version to 12.2.1.3.0>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Upgrade> <Encrypting NodeManager property: CustomIdentityKeyStorePassPhrase>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Upgrade> <Encrypting NodeManager property: CustomIdentityPrivateKeyPassPhrase>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Upgrade> <Saving upgraded NodeManager properties to 'D:\IFS\IFSExt\IFST\wls_domain\NEW_IFST_PA\nodemanager\nodemanager.properties'>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Loading domains file: D:\IFS\IFSExt\IFST\wls_domain\NEW_IFST_PA\nodemanager\nodemanager.domains>
<23-Apr-2021 09:21:39 o'clock BST> <INFO> <Loading identity key store: FileName=D:/IFS/IFSExt/IFST/instance/NEW_IFST_PA/security/truststores/ifs_mws.jks, Type=jks, PassPhraseUsed=true>
<23-Apr-2021 09:21:39 o'clock BST> <SEVERE> <Fatal error in NodeManager server>
weblogic.nodemanager.common.ConfigException: Identity key store file not found: D:/IFS/IFSExt/IFST/instance/NEW_IFST_PA/security/truststores/ifs_mws.jks
    at weblogic.nodemanager.server.SSLConfig.loadKeyStoreConfig(SSLConfig.java:225)
    at weblogic.nodemanager.server.SSLConfig.access$000(SSLConfig.java:33)
    at weblogic.nodemanager.server.SSLConfig$1.run(SSLConfig.java:118)
    at java.security.AccessController.doPrivileged(Native Method)
    at weblogic.nodemanager.server.SSLConfig.<init>(SSLConfig.java:115)
    at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:169)
    at weblogic.nodemanager.server.NMServer.getInstance(NMServer.java:134)
    at weblogic.nodemanager.server.NMServer.main(NMServer.java:589)
    at weblogic.NodeManager.main(NodeManager.java:31)

 

 

Also to note the database has been cloned and put onto a new VM as well which has been upgraded from 12c to 19c pre MWS installation.

 

Many Thanks,

Best answer by Imal Thiunuwan

Hello @WyrAndreM,

• It is recommended to assign a fixed IP address to the server and connect it to the network. Make sure the IP address and hostname are included in the file C:\Windows\System32\drivers\etc\hosts.
• Please make sure that the drive you are installing IFS home supports DOS 8.3 file format.


• If ifs user password contains any of the following characters: #, =, ! you should change the password and remove those characters. In order to do it please us following script <<IFS_HOME>>\instance\<<INSTANCE_NAME>>\bin\change_mws_password.cmd

 
• If you have your installation running on Windows platform, please validate that drive your IFS installation is on supports short names. This can be done by running command (C: here refers to disk drive with IFS installation) 
              
If short names are disabled, you would need to enable them using command:
fsutil 8dot3name set <<DRIVE_LETTER>> 0

Afterwards you can validate if your IFS_HOME has short name representation using dir /x <<DRIVE_LETTER>> command: 
 
• Should you not have short names present you would need to make sure to stop all processes and services running from given IFS_HOME, rename IFS_HOME temporarily and then rename it back to its previous name. After those steps please re-run dir /x command to validate the outcome (Only applies if not a fresh installation)

Thank You.

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

2 replies

Imal Thiunuwan
Superhero (Employee)
Forum|alt.badge.img+16
  • Imal Thiunuwan
  • Superhero (Employee)
  • 117 replies
  • Answer
  • April 23, 2021

Hello @WyrAndreM,

• It is recommended to assign a fixed IP address to the server and connect it to the network. Make sure the IP address and hostname are included in the file C:\Windows\System32\drivers\etc\hosts.
• Please make sure that the drive you are installing IFS home supports DOS 8.3 file format.


• If ifs user password contains any of the following characters: #, =, ! you should change the password and remove those characters. In order to do it please us following script <<IFS_HOME>>\instance\<<INSTANCE_NAME>>\bin\change_mws_password.cmd

 
• If you have your installation running on Windows platform, please validate that drive your IFS installation is on supports short names. This can be done by running command (C: here refers to disk drive with IFS installation) 
              
If short names are disabled, you would need to enable them using command:
fsutil 8dot3name set <<DRIVE_LETTER>> 0

Afterwards you can validate if your IFS_HOME has short name representation using dir /x <<DRIVE_LETTER>> command: 
 
• Should you not have short names present you would need to make sure to stop all processes and services running from given IFS_HOME, rename IFS_HOME temporarily and then rename it back to its previous name. After those steps please re-run dir /x command to validate the outcome (Only applies if not a fresh installation)

Thank You.

NickPorter
F
2 people like this
  • NickPorter
    NickPorter
  • F
    Farrukh Ali
W
Do Gooder (Partner)
Forum|alt.badge.img+6
  • WyrAndreM
  • Author
  • Do Gooder (Partner)
  • 18 replies
  • April 23, 2021

Thanks for the information there were some server features missing which have been installed and the hosts file updated.

Imal Thiunuwan
1 person likes this
  • Imal Thiunuwan
    Imal Thiunuwan
Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings