Message CTGAZ0001E: possible explanations and solutions
Albook 120000625S Visits (6380)
While trying to create or update applications in APM UI 7.7, one of the most frequent error messages you may experience is
CTGAZ0001E: The application cannot be saved because the application repository is not applicable.
This simply means that for some reasons SCR was not able to complete initialization or it stopped working.
It can happen for example because SCR server is using a wrong apmadmin password, or because of bad connection configuration.
A very useful technote about this matter is:
Furthermore, some time ago I published another blog article talking about SCR initialization failure, in such case related to a wrong
encryption key used to encode the database password.
It worth to have it a look as well in case you are experiencing error CTGAZ0001E:
The information contained in the above articles take in consideration possible misconfiguration in one of the APM UI services.
There is anyway a chance that the problem lies instead on external services used by APM UI or SCR servers.
If the root causes and solutions proposed in the above links do not fit your scenario, you should look at the scrserver.log file.
Most of the time it contains error messages that helps identifying the failing element.
In one of the most recent cases I worked on, the scrserver.log showed the message:
10 Jun 2016 11:45:57,573 ERROR [ScrInitServlet] initmeta - Exception:
SCR is using a local DB2 server as application repository database, but as per above message, the SCR did not complete initialization because it failed connecting
Most of the time it occurs because the needed DB2 instance is not running or because the port used by SCR (actually by the DB2 client) to connect the DB2 server was instead in use by another process, or because the expected database called SCR is not present into the target database instance.
If you find the same error message, first of all verify that DB2 instance is up and running and verify that the port used by SCR to connect database (in my case 50000) is actually listening and belongs to the expected process (DB2).
You can do it by executing
#ps -ef | grep db2
to verify the running db2 processes, and
#netstat -an | grep 50000
to verify if the target port is really listening.
If database instance is not running, use command db2start to start it and repeat above commands to check that all is working fine.
If instead the DB2 instance is running and the target port is already listening, then the failure may be related to an unexpected status of the user account used
to connect the database and specified into the SCR server.xml file.
Try to connect the database from CLI using:
db2 connect to SCR user <userID used into SCR server.xml> (it will then ask for the password)
Enter current password for <user>:
Enter current password for <user>:
Then this is the root cause for the problem that SCR is experiencing: the user account is locked or restricted.
You need to verify with database administrator the reason for it and then re-enable the userID, in case also changing the password.
It is possible that, in case the password has been previously changed, the current userID has been disabled because of too many
attempts done using the old/wrong password.
In this case you may need to issue this command to reset the unsuccessful login count:
Please remember that, if you changed the user password, you also need to update the related information in SCR.
In that case, you should proceed as follow.
4) Now restart the APM UI and SCR services.
Error Message CTGAZ0001E is gone and you are now able to create and update applications in APM UI.
Subscribe and follow us for all the latest information directly on your social feeds: