February 19, 2013 at 4:55 am
Colleagues,
could you please give me a bit of advice.
We have one server with 2 SQL Server 2008 R2 instances running on it. Yesterday we installed SP2. Today one instance from time to time refuses to accept new connections.
The symptoms are:
1. If the connection is open, everything works perfectly. E.g. if we have open the SSMS window, it has never ceased to work: you can enter different queries in it, they will work.
2. If the operation requires new connection to be established, it fails. We get the meassage "A severe error occurred on the current command. The results, if any, should be discarded."
3. It can be cured for some time by the instance restart.
4. The second instance works perfectly.
I do not know what causes this error. I cannot reproduce it.
No traces in error logs. I have no idea where to look and what to search for. DBCC CHECKDB on master gives no errors.
Any ideas will be really appreciated.
February 19, 2013 at 4:57 am
Is there any errors reported in the SQL Server Error log within management in SSMS or any errors written to the windows event logs?
MCITP SQL 2005, MCSA SQL 2012
February 19, 2013 at 5:02 am
RTaylor2208 (2/19/2013)
Is there any errors reported in the SQL Server Error log within management in SSMS
No.
or any errors written to the windows event logs?
No. Or I do not see any.
February 19, 2013 at 11:39 pm
Today I know MUCH more.
The problem arises when Replication agents start from their schedules. It never arises if I start the same agents from the Replication Monitor or 'View synchronization status" then everything is OK.
Looks like something is really wrong with my SQL Agent configuration.
Or perhaps something is wrong with the replication. I am going to drop and recreate it - then we'll see.
BTW, I would appreciate any resources telling what the SQL Agent permissions should be.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply