thanks. I followed Gail's performance articles when initially researching this issue and grouped by highest total. I tuned the highest offender with the missing index but it unfortunately did...

Sorry, busy day. At some point between 22:30 last night and 06:30 this morning someone changed the servername. A one letter difference

thanks for the idea, wouldn't it be a different error if it were an authentication error?

Also, I've tested installing additional instances and they all have this same problem.

It is correct. I can query @@servername through sqlcmd and get the correct servername.

edit: yes the service is running. I can connect via sqlcmd

...

TITLE: Connect to Server

------------------------------

Cannot connect to 3MRASSDB1.

------------------------------

ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify...

I agree with you. These are application driven databases. I can't be sure that they won't have special configurations. The restore would come from the latest backup....

I see. That's a little annoying considering the default instance can very well start with a number.

Thanks though!

I got you guys, that was it. The order of the delete statement was off and it should have occurred after the concatenation.

This is part of a database...

hmmmm, I see. I will try.

I don't believe so. Looking through the log at start up I'm not seeing 'Using locked pages for buffer pool

'

SQL Server 2005 Standard. Maybe I didn't apply the cumulative update from this artice correcty?

http://support.microsoft.com/kb/970070

Version says 9.0.4226

super duper old thread, but I found this

http://www.sql-server-helper.com/error-messages/msg-195.aspx

nah, we have a separate job to cleanup thos files

Hi, I initally checked to see if it was trying to delete its own log, but no, this job deletes old backup files. Strange.