Looking for solution to Process ID 174:102 owns resources that are blocking processes on Scheduler 2.
We recently installed our Lucent Vitalnet app with SQL 2000. it runs fine for 2-3 days, then the app stops when the above SQL error message occurs. Rebooting the server temporarily fixes the problem until another 2 days.
Also Tried upgrading to 2005. Upgrade appears successful with no complaints but SQL comes up and still uses 2000.
Server we're using has those multiple CPUs in it. Are there any issues with having multiple CPUs with SQL ?
Windows Server 2003 SP2 Dell Xeon(R) CPU X5560 @ 2.80GHz 2.79 gHz, 23.9 GB of RAM
September 10, 2010 4:15 PM
September 10, 2010 4:22 PM