Network problem occuring one of sever

[mincharug.shulft]

Hi All,
We have the following configuration
Windows server 2003 x64 service pack2
RAM is 16.0GB
IBM Cognos TM1 9.5.2 is running with two TM1 servers (2 data models)
And on yesterday while we are trying to login onto the windows server via RDP and we had an network problem and we could not able to login .and we have taken server team help and they restarted the server and we are able to get into the server.
And we asked the Rootcause for it and server team came back with following:
100% CPU usage using by the application tm1sd.exe and also we have seen that
Tm1sd.exe -50% CPU usage
Tm1sd.exe -49% CPU usage
Any reason here?
.and actually we are getting the network issue ofenetly due to two tm1 servers are running or any Rootcause?
Please can gentle man’s help would be appreciated.

[jim wood]

We experienced similar issues to this when we had a problem with that was causing the server to run out of non paged memory. Have a look at: http://www.tm1forum.com/viewtopic.php?f=3&t=7334 I'm not it will help but you never know.

[jim wood]

Another thought, did you check the windows event viewer after the restart?

[mincharug.shulft]

hi,
i checked but i didnot find any special activity had.

[George Regateiro]

We experienced this issue with the Lock Pages In Memory that Jim mentioned and through debugging with IBM it was determined that this was causing the server to run out of page file even though everything looked fine on the server. We disabled it since as long as there is some activity on the server this is not really needed. What was happening was the lock pages setting was causing something called the Max Working Set to grow and this was never returned to the OS. It was tricky because if we looked at the task manager we could see plenty of RAM and page file remaining. This parameter was invisible expect through the latest PROCMON available from MS. Disabling the parameter solved all our problems.

[PlanningDev]

We experienced this issue with the Lock Pages In Memory that Jim mentioned and through debugging with IBM it was determined that this was causing the server to run out of page file even though everything looked fine on the server. We disabled it since as long as there is some activity on the server this is not really needed. What was happening was the lock pages setting was causing something called the Max Working Set to grow and this was never returned to the OS. It was tricky because if we looked at the task manager we could see plenty of RAM and page file remaining. This parameter was invisible expect through the latest PROCMON available from MS. Disabling the parameter solved all our problems.

The same exact problem here. Every 5-7 days the machine would think it was out of resources even though it wasn't and you couldn't login through RDP. We had to remote stop the TM1 services from the command line to get back on the machine.

[mincharug.shulft]

Hi,
Thanks for you valuble reply.
and my TM1 server running under virtual michane so
thats means if i could disable the Lock Pages In Memory=F in the conf file NO issues i will expact right .
please suggest me all gentle mans so that i am going to disable.

[mincharug.shulft]

this parameter should it be applicable to virtual mechine or phical machine ?

Lock Pages In Memory=F

[Andy Key]

Given the latest mumblings from IBM I would have LockPagesInMemory=F as your default position on all 64-bit Windows servers, until they change their minds again.