COGNOiSe.com - The IBM Cognos Community

IE 8 just spins forever.  I think it has to do with loading 'current activities'.  I was able to get an error message once but was unable to get a screen shot.  I think it said something about it 'already being in use'.

I checked our server and there is a java.exe process that seem on the high side ~717,000K on memory usage.  Is something 'off in the weeds'?  I'm hesitant to kill it b/c I'm not 100% sure what will happen, if anything.

Has anyone came across this before?

Hit the dispatcher directly. A java process that high in mem is normal in a default install. If it was 2gig and you haven't got in yet I'd say that's odd.

dispatcher: http://server:port/p2pd/servlet/dispatch
Ex. http://cogserver:9300/p2pd/servlet/dispatch

9300 is the default port.

I entered my dispatcher address in and got a very basic version of Cognos Connection.  However, none of the links or anything worked.  Lots of red 'x's.

Is this what I am looking for?

Yes. That tells you that COgnos side of things is up. You don't have the images in the dispatcher (Unless you copy them in which is a different thread).

So now you have to look at your Webserver config. What are you using? Apache, IIS? And what version?

Usually with IIS it's the config of the virtual directories.

I'm on IIS 6.

There haven't been any changes as far as I know.

I did modify the index.html and default.htm files in the webcontent folder for another unresolved issue.  I just changed the url to reference isapi.  However, that was days ago and this just started yesterday afternoon.

Hi Tsunami,

I have seen this many times before and 99% of the time it's just the load being placed on the content manager/content store instead of any specific error.

Was the reporting system under heavy load at the time or does it continue to happen at times of lower demand?  This maybe especially true if alot of content creation/retrieval (pdf/Excel) is taking place. 


Rgds

Rob

Thanks Rob for the suggestion but it was happening at all times.  We ended up restoring all settings from a backup and everything is working fine now.