problem with nt4 server getting stuck at "writing unsaved data to disk"

dear experts

try not to laugh but we still have a number of nt4 servers in our company and recently (over the last 3 weeks or so) we've been experiencing some major issues with all of them.

NB: these servers were all physical and now they have been virtualised (P2V) onto ESX servers.

these servers run an application called emslink and for some bizarre reason the server will run perfectly for about a week and then suddenly the CPU hits 100% and the application that the servers are running fails.  we checked task manager when the application died and we've managed to work out that the CPU hits 100% because the emslink.exe process is using all of the CPU (and then the server runs out of resources and the application fails).

this problem with the emslink.exe process using 100% CPU has been seen before and normally to resolve the problem we would just connect to the server using PCAnywhere and just reboot it, but now we are experiencing a second issue and that is that when you try to reboot the server it gets stuck at "writing unsaved data to the disk" or something like that and won't shutdown / restart.  The only way we can restart the server is to connect to the hypervisor (esx 4.1 / vsphere client) and reset the virtual machine.  

We've not had these issues before and I can't work out what the problem is or why it's happening now.

Please help.

All servers run SP6a and windows nt4 server.

Thanks

Richard S Powell
LVL 2
richardstuartpowellAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Elmar KoschkaSenior System EngineerCommented:
The NTOSKRNL.EXE on the newly converted guest NT4 is a multi-CPU kernel? Replaced with a single CPU kernel, and the issue should be resolved.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
richardstuartpowellAuthor Commented:
hi elmar-h

that sounds interesting ...

please explain exactly what i have to do to change that and why that could be causing the problem.

do you mean the CPU settings in the VM or in windows within in the virtual machine?


thanks !
richardstuartpowellAuthor Commented:
i checked the settings on the vm

edit settings --> CPUs -> 1

is that what you meant?
richardstuartpowellAuthor Commented:
Please can someone help me with this because i'm just not sure what elmar-h meant?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.