WebSphere Application Server & Liberty

 View Only

 Failed to create WAS registry file

トシミ クロサワ's profile image
トシミ クロサワ posted Tue March 04, 2025 06:13 PM
Creating a profile in PMT fails. 
The service works fine and I can log in to the WAS console, but the profile name is not registered in the registry file (XML).
The only error displayed is the profile creation failure at the end.
Please tell me how to deal with this.
I have tried to recreate it many times but it fails.

Even if I run it with a command instead of PMT, it fails.
When creating the second profile, there is a PORT conflict, so I corrected it and started it.
Lars Besselmann's profile image
Lars Besselmann

Please take a look at the profile creation logs at app_server_root/logs/manageprofiles where app_server_root is something like /opt/IBM/WebSphere/AppServer 
You should find a log like xxx_create.log where xxx is the name of the profile that you want to create.
(As you can log into the WAS console, you should already have one profile. So please focus on the new profile.)
There is also a file pmt.log which might contain some details what is failing.

If the logs do not give you a clue, please provide some more details what you want to achieve and what fails.

  • the WebSphere edition and version (e.g. WAS ND 9.0.5)
  • the operating system (Linux, Windows, AIX, z/OS, ...)
  • the kind of profie that you want to create
    • cell - Deployment manager cell (dmgr and default)
    • management - Management. Use in conjunction with the -serverType parameter to indicate the type of management profile.
    • secureproxy- Secure proxy
    • default - Application server
    • managed - Custom
  • the error that you are seeing at the end of the profile creation
  • errors that you have found in the log files mentioned above
  • the lists of profiles that are at the profile registry
    Use the following command  to create the list:
    app_server_root/bin/manageprofiles.sh -listProfiles
    where app_server_root is something like /opt/IBM/WebSphere/AppServer

You can find more details about the command at https://www.ibm.com/docs/en/was-nd/9.0.5?topic=umt-manageprofiles-command

If you want to raise a ticket please take a look at the following information:
Collect troubleshooting data for profile creating problems in WebSphere Process Server

Brian S Paskin's profile image
Brian S Paskin

Hi, you can check the was_home/logs directory.  There may be a sub directory for pmt.

Brian

トシミ クロサワ's profile image
トシミ クロサワ
Dear Lars Besselmann

Thank you for your reply.

I checked the various logs but could not find any specific errors

There is only an error at the end about the profile failing.

What bothers me is that there is a warning in the JAVA-related module.

As a result, the XML file for the profile registry is NULL.

Would the problem be solved if I write the profile name in this XML?
Lars Besselmann's profile image
Lars Besselmann

To modify the registry xml file manually is not a good approach. Instead we should try to find a better way.  But for this I need some more information:

  • the WebSphere edition and version (e.g. WAS ND 9.0.5)
  • the operating system (Linux, Windows, AIX, z/OS, ...)
  • the kind of profile that you want to create
    • cell - Deployment manager cell (dmgr and default)
    • management - Management. Use in conjunction with the -serverType parameter to indicate the type of management profile.
    • secureproxy- Secure proxy
    • default - Application server
    • managed - Custom
  • the error that you are seeing at the end of the profile creation
  • errors that you have found in the log files mentioned above
  • the lists of profiles that are at the profile registry
    Use the following command  to create the list:
    app_server_root/bin/manageprofiles.sh -listProfiles
    where app_server_root is something like /opt/IBM/WebSphere/AppServer
  • You should also check if the directory for profile that you want to create already exists, default path: app_server_root/profiles/<profilename>
    If it exists, delete the directory before trying again to create the profile
  • If you did not create any profile correctly so far, try to delete all profiles with the command
    app_server_root/bin/manageprofiles.sh -deleteAll
    Then delete all directories where the profiles resided, default is:  app_server_root/profiles/<profilename>

After this, try to create the profile using the command line. The command is something like:
app_server_root/bin/manageprofiles.sh -create 
   -profileName profile_name 
   -profilePath profile_root 
   -templatePath template_path 

You can find more details about the command at: 
https://www.ibm.com/docs/en/was-nd/9.0.5?topic=systems-manageprofiles-command

Hope that helps.

Lars

トシミ クロサワ's profile image
トシミ クロサワ
I deleted all the profiles and recreated them with the command, 
but it still failed. The return code is INSTCONFFAILED.
I am setting this up as an administrator in a Windows 2022 environment.
I have also set the environment variables for JAVA and WAS.
Is there a solution?
Lars Besselmann's profile image
Lars Besselmann

It is impossible to give a good recommendation without more details about the error.

Therefore please take a look at the profile creation logs at app_server_root/logs/manageprofiles where app_server_root is something like /opt/IBM/WebSphere/AppServer 
You should find a log like xxx_create.log where xxx is the name of the profile that you want to create.
In the log file, you should find some messages tagged with <level>WARNING</level>, others with <level>SEVERE</level>
Please take a look at those messages to find out what's failing.