"SQL" server optimized for 8 concurrent queries, exceeded by 2 1

[nloecke]

Several times per week, overnight, 2 or 3 jobs will fail, saying the Backup Exec Engine was not responding. We are running Backup Exec 9.1 on a WIN 2003 Server, with the "runtime database engine." It is not runnung on a full-blown SQL Server.

The Windows Event Viewer tells me this:
Event Type: Information
Event Source: MSSQL$BKUPEXEC
Event Category: (2)
Event ID: 17055
Date: 5/24/2005
Time: 12:58:34 AM
17052 :
This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 2 queries and performance may be adversely affected.

This is a new PowerEdge SC420 Server: 2.8 GHz P4, 500 MB ram, three 250 Gig drives on a PCI IDE card, backing up around 550 Gigs each night. I'm almost afraid we are simply asking too much of this hardware. Could I look at the timing of these jobs?
Any ideas would be helpful. Thanks for your input!

 

[steveot]

I dont think that the root of the issue. Have you applied Backup Exec SP2? When you get this error above the the job engine die right after?

 

[SQLBill]

One thing to check...in Enterprise Manager, expand to the instance. Right click on the instance, select Properties and go to the Connections tab. What is "Maximum concurrent connections" set for?

-SQLBill

Posting advice: FAQ481-4875

 

[nloecke]

Thanks for your replies.
Steve - I will check on the sequences of the error messages. Also, in conjunction with the failed jobs and the above error message, I will see another error:
17883, Severity 1, State: 0
The Scheduler 0 appears to be hung, SPID 51, ECID 0, UMS Context 0x00C5A798
Don't know what that means, but it does not look good...

Bill - there appears to be no SQL Enterprise Manager. We simply installed Veritas, and it's using whatever exists for that database engine.

 

[nloecke]

Hi again -
I attached to the MSDE from a different SQL 2000 server, and looked at the properties of the Backup Exec box. It was configured for 0, or unlimited, user connections. I didn't change it since it said unlimited. Also was unsure if this was the proper setting, since it said user and you had not, Bill.
Also, I finally noticed that the concurrrent connections error came up about the same time every night, so I changed the scheduling a bit. I will see if that changes anything this weekend.
Thanks for taking the time to help me out!