Error: The Congnos gateway is unable to connect to the Cognos BI server

[TBKeys]

Cognos 8 has been running flalwlessly for a long time. This past Monday it went down, we looked at everything an business partner has not been able to resolve either. Nothing has been disturbed on this server. We have gone into IIS manager and try to browse Cognos 8 and it only launches the Splash screen, and it displays the error: The Cognos gateway is unable to connect to the Cognos BI server. The server may be unavailable or the gateway may not be correctly configure. When wee try to run Cognos configuration we get the same splash screen and it locks up.

We're totally stumped.

Please help.

[MFGF]

Cognos 8 has been running flalwlessly for a long time. This past Monday it went down, we looked at everything an business partner has not been able to resolve either. Nothing has been disturbed on this server. We have gone into IIS manager and try to browse Cognos 8 and it only launches the Splash screen, and it displays the error: The Cognos gateway is unable to connect to the Cognos BI server. The server may be unavailable or the gateway may not be correctly configure. When wee try to run Cognos configuration we get the same splash screen and it locks up.

We're totally stumped.

Please help.

I usually see that message when the Cognos 8 (or 10) service isn't running. If you look at your list of services, does the Cognos 8 service show as started? Take a look in cogserver.log also - there may be some info in there that can help pinpoint what the issue is.

If I was a betting man, I'd suspect maybe a java update or corruption has caused issues? Has there been an update to java on the server recently?

If you can let us know what you find in cogserver.log, that would be a good jumping-off point for where to look next...

Cheers!

MF.

[TBKeys]

MFGF you would also be a winning man. Turns out there is a known issue that occasionally for no uncertain reason the Cognos start xml file and a few other files get corrupted. This was not listed anywhere and it took logging a support call with IBM to discover and all of 3 minutes for it to be resolved.

TBKeys