I have seen this problem corrected with a safe recovery, but if that does not work the problem may be with the middleware. If a safe recovery does not work, reinstall the whatever middleware you may be using. This worked for me.
(Embedded
image moved Nils & Gerda De Caster - Torck nilsdc@XS4ALL.BE to file: 09/18/98 12:49 PM
PIC21151.PCX)
This means that you installed Document Agent Server after you installed the repository with supervisor.
You need to do a recovery with supervisor. hope this helps. Nils
I’ve come across this alarming message a few times in the past, but after several more attempts the connection to the Security Server could be established after all… without safe recovery, nor re-installation of the middleware.
This is just to say: don’t panic as soon as you see that message – just keep trying for a while before deciding to do the safe recovery.
I have seen this problem corrected with a safe recovery, but if that does not work the problem may be with the middleware. If a safe recovery does not work, reinstall the whatever middleware you may be using. This worked for me.
(Embedded
image moved Nils & Gerda De Caster - Torck nilsdc@XS4ALL.BE to file: 09/18/98 12:49 PM
PIC21151.PCX)
This means that you installed Document Agent Server after you installed the repository with supervisor.
You need to do a recovery with supervisor. hope this helps. Nils
I eventually found out the source of the problem. It was our SQL server which holds the repository not having any free connections. The error message could be more descriptive , though, Something like: “Not able to connect to Repository”, or the like.
I’ve come across this alarming message a few times in the past, but after several more attempts the connection to the Security Server could be established after all… without safe recovery, nor re-installation of the middleware.
This is just to say: don’t panic as soon as you see that message – just keep trying for a while before deciding to do the safe recovery.
I have seen this problem corrected with a safe recovery, but if that does
not work the problem may be with the middleware. If a safe recovery does not work, reinstall the whatever middleware you may
be using. This worked for me.
(Embedded
image moved Nils & Gerda De Caster - Torck nilsdc@XS4ALL.BE to file: 09/18/98 12:49 PM
PIC21151.PCX)