[Solved] ReportNet Service Problem

[nrh]

Following a server failure and subsequent restore of the server, ReportNet has restarted and appears to the user to be working as expected. However, on opening Cognos Config I find that the Local COnfiguration is stopped. Clicking start initiates the start process which is successful but on clicking close the gui still reads 'stopped'.

Looking at the running services I see that the Cognos ReportNet service has a status of 'starting' rather than 'started'. It has been like this for a number of hours.

Looking at the logs I see a number of CBS logs get updated on a regular basis - don't remember this happening before. Don't know what CBS is/does??

Help appreciated.

Many thanks,

nrh.

[JGirl]

Hi,

Do you have admin rights to the machine on which you are running the cognos config?  If you don't have admin privileges to the machine, the local configuration appears to be stopped (even though it is actually running).

I'm not sure how the above problem affects the display of the services - I haven't looked that far into it.

The CBS is the "Cognos Bootstrap Service" - which i think is just the cognos reportnet service - the cbs_* logs will be updated every time reportnet is started or stopped (and maybe more frequently than that).

J

[cognosfreelancer]

nrh

if you look at the crnserver.log file you may find out what is causing the startup problem.

Another good place to look at is Event Viewer assuming you have Windows OS

NKT

[nrh]

It turns out that on occasion (not sure of the cause) the windows OS gets out of synch with the true status of ReportNet. It seems the only way to sort this out is to re-boot the server!! I managed to get this scheduled a few days later and all is now fine.

Hope this helps for anyone getting a similar problem in the futures.

nrh

[sir_jeroen]

Is this topic Solved => Read board rules for status indicators.... Tnx!