Skip to Content
0
Former Member
Jun 26, 2008 at 05:56 PM

MSCS cluster is going offline in Production

161 Views

Hi all,

We have MSCS cluster configured on 2003 sp2 on 64 bit with sqlserver 2005 & ECC 6.0.

Cluster is bringing sqlserver to offline and after 3 hours it's becoming online again, the below log messages found when it's taking sqlserver offline.

We already open the message with Microsoft.. still no proper response.. please suggest whether we have to go for any new security pacthes...

Log file:

SQL Server has encountered 216 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [K:\PBWDATA2\PBWDATA2.ndf] in database [PBW] (5). The OS file handle is 0x00000000000007B8. The offset of the latest long I/O is: 0x00000757c30000

2008-06-23 03:54:52.50 spid3s SQL Server has encountered 2659 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [L:\PBWDATA3\PBWDATA3.ndf] in database [PBW] (5). The OS file handle is 0x00000000000007BC. The offset of the latest long I/O is: 0x000007597a0000

2008-06-23 04:00:43.45 spid3s SQL Server has encountered 586 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [L:\PBWDATA3\PBWDATA3.ndf] in database [PBW] (5). The OS file handle is 0x00000000000007BC. The offset of the latest long I/O is: 0x0000083f530000

2008-06-23 04:00:43.45 spid3s SQL Server has encountered 2036 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [J:\PBWDATA1\PBWDATA1.mdf] in database [PBW] (5). The OS file handle is 0x00000000000000E4. The offset of the latest long I/O is: 0x0000083be30000

2008-06-23 04:00:53.45 spid3s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [J:\TMPDATA1\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x0000000000000AF4. The offset of the latest long I/O is: 0x000000f9a00000

2008-06-23 04:01:28.64 spid3s SQL Server has encountered 301 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [K:\PBWDATA2\PBWDATA2.ndf] in database [PBW] (5). The OS file handle is 0x00000000000007B8. The offset of the latest long I/O is: 0x0000085e450000

2008-06-23 04:02:45.96 spid52 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.

2008-06-23 04:02:50.57 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:02:50.57 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:02:50.57 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:02:50.57 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.77]

2008-06-23 04:02:50.60 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:02:50.60 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:02:50.62 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:02:50.62 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:02:50.64 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.05 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.05 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.77]

2008-06-23 04:03:13.05 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.05 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:03:13.06 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.06 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:03:13.06 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.06 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:03:13.07 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.

2008-06-23 04:03:13.07 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

2008-06-23 04:03:13.07 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.07 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

2008-06-23 04:03:13.18 Logon Error: 18451, Severity: 14, State: 1.

2008-06-23 04:03:13.18 Logon Login failed for user 'SAPPBWDB'. Only administrators may connect at this time. [CLIENT: 10.16.148.54]

Thanks,

Subhash.G