100% utilization and lockup

[Jim Krebs]

In the past week I have had two instances where the server became unusable.
When I can finally get logged in far enough to bring up Task Manager (that
took about 15 minutes) I see Project Server and SQL splitting the processor
at about 45 - 47% of the processor. I killed the processes and rebooted.
Right back to 100%. Last week it finally came back and worked, today I can't
get it to stay released. Errors in the event log begin with one that says "a
transport-level error has occcurred when recieving results from the server"
but help center returns "no results were found for your query." The errors
switch to a SQL exception talking about a transport-level error and finally
switch to Project Server has encountered an underlying SQL exception. Tried
those two with help center and again no information is available.

Anyone have any idea what is going on here?

 

[Ray McCoppin]

Have you check the SQL Configuation and made sure that it is not configured
for Named Pipes. Named Pipes is very old and should not be used. Configure
SQL to use TCPIP only. TCPIP is faster connecting and better for Project
Server use.

Hope this helps
--
Ray McCoppin

http://www.randsmanagement.com
Project Server 2007 Automation Tools
Project Server 2007 Archive Tool
SRS gantt charts

 

[Jim Krebs]

I'm running this on the same server as the SQL server and have "Shared
Memory" as the only enabled protocol on the server protocols and in the
client protocols first choice is shared memory and TCP/IP is second. Named
pipes is disabled.

 

[Gary Chefetz]

Jim:

This really sounds like a SQL issue or possibly a server OS issue. (I'm
strongly opposed to running SQL on the same server, btw) You might try
asking about these errors on the SQL newsgroups. You don't mention what
version of the applications you are using, so it's very difficult to give
you specific advice, but if you're using 2007 with SQL 2005, I strongly
suggest that you patch SQL to SP3 if you haven't already done so.