2 sqlservr.exe processes on same server, overhead!

  • We have a Sql Server 2005 cluster, active active, on eache node runs usually one instance. Last friday has begun a series of apparently unexplicable problems. First, node1 switched to node2, and after about 2 hours node2 switched to node1. We manually moved the groups relative to node2 on node2. After this, node2 was heavily under stress. The strange thing I noticed is that in the windows processes there were 2 sqlservr.exe running, and on node1 there was 1 process correctly.

    After restarting node2 the situation was ok (1 process).

    From then we have here and there instance switches, and plenty of different errors in windows applogs, some of which:

    1

    Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

    2

    The operating system returned error 21(error not found) to SQL Server during a read at offset 0x00000000262000 in file 'N:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\DbName.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

    3

    Internal Microsoft Distributed Transaction Coordinator (MS DTC) transaction failed to commit: 0x8004d019(error not found).

    I've checked all dbs without finding errors.

    Can anyone suggest a solution or controls to get?

    Thanks in advance.

    sb

  • I forgot to say that in previous days we installed, for a trial period, FogLight monitor. The Sql Server cluster's nodes were the hosts monitored.

    Has anyone experienced similar problems with FogLight? This is the only change it was made on servers before problems has begun.

    Thanks, sb.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply