When Problems Exist with the Master Password or Outbound Passwords at Startup
If Integration Server detects a problem with the master password or outbound passwords at startup, the server places you in safe mode, which is a special mode from which you can diagnose and correct problems.
When Integration Server is in safe mode, the server displays the Integration Server Administrator, but Integration Server is not connected to any external resources.
When you are placed into safe mode because of problems with the master password or outbound passwords, you will see the following message in the upper left corner of the Server Statistics screen of the Integration Server Administrator:
SERVER IS RUNNING IN SAFE MODE. Master password sanity check failed -- invalid
master password provided.
Important: | When you are in safe mode, do not configure or modify outbound passwords unless they have been reset as part of the Reset All Outbound Passwords task. |
When there is a problem with these passwords, you can correct the problem by restoring the passwords or resetting them. The method you choose depends on the problem with the passwords. There are a number of reasons the Integration Server will automatically go into safe mode.
Passwords are Corrupted or Out of Sync
It is possible that the master password file, outbound password file, or both are corrupted. It is also possible that these files are out of sync with each other. The files are out of synch when the key used to encrypt the contents of the outbound password file is not the key in the master password file. In either case, refer to
Determining Whether You Can Restore
the Passwords for instructions.
You Entered the Wrong Master Password by Mistake
You might be in safe mode because you unintentionally entered the wrong master password when prompted for it at server startup. If you think this is the case, shut down Integration Server and restart it, this time specifying the correct master password when prompted.
Platform Locale Has Changed
Any change to the OS locale or default encoding can render the outbound password and master password files unreadable by Integration Server. For this reason, Software AG recommends that you do not change platform locale after the Integration Server has been installed and started.
Contact Support
|
Community
|
Feedback