Solved

SQL server and SQL agent will not start on both nodes in Active to Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 x64 after applying KB958644

Posted on 2009-05-20
9
2,111 Views
Last Modified: 2013-11-29
Hello,
Apologies if this has already been posted but I cannot find it anywhere. My SQL server and SQL agents will not start on both nodes in my Active / Active SQL 2005 SP3 x64 Enterprise cluster on Windows 2008 Enterprise SP1  x64 after applying KB958644 which is the conficker patch. This is the second time I have built the cluster and I tested it and it worked perfectly prior to applying the KB. Has anyone seen this issue before and do they have a fix? Basically not patching the 2 servers is a no go and I have already patched 2 separate clusters with KB958644 and they worked fine, those clusters were W2k3 R2 SP2 2 node with SQL 2005 SP2 and Windows 2008 Enterprise File and Print cluster with 5 nodes.

Whats happening is all the services on both nodes come online except SQL server and sql agent. The are all connected to EMC2 sans via fibre channell cable on HP DL380 G5 with 32 gb RAM and 2 x Quad core 3 ghz CPUs. When I look in cluster event log I get the following errors:
event ID 1069: Cluster resource 'Cluster Disk 5' in clustered service or application 'Cluster Group' failed.
and Cluster resource 'SQL Server (servername1)' in clustered service or application 'clusterservicename' failed.

In the event viewer on Windows 2008 I get these 3 errors:
event id: 19019 [sqsrvres] OnlineThread: Error 1 bringing resource online. (more info in code)
event id: 19019 [sqsrvres] OnlineThread: service stopped while waiting for QP.
event id: [sqsrvres] CheckServiceAlive: Service is dead

I got the above error with KB958644 installed and as I said before the cluster was working perfectly prior to the patch. I tried uninstalling the patch but the same error happens above. I need to get this working with the patch installed otherwise I will have to recommend going back to Windows 2003. If anyone can shed some light on this I would appreciate it and if you require any more information please let me know. thanks Bruce
System 

 

  - Provider 

 

   [ Name]  MSSQL$ExcelicareReport 

 

  - EventID 19019 

 

   [ Qualifiers]  16384 

 

   Level 2 

 

   Task 3 

 

   Keywords 0x80000000000000 

 

  - TimeCreated 

 

   [ SystemTime]  2009-05-20T16:19:36.000Z 

 

   EventRecordID 10475 

 

   Channel Application 

 

   Computer clw-carsql-001.dirone.imperial.nhs.uk. 

 

   Security 

 

 

- EventData 

 

   [sqsrvres] OnlineThread: Error 1 bringing resource online.  

   4B4A0040010000000E00000063006C0077007600630061007200730071006C00300030003400000000000000 

 

 

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

 

Binary data:

 

 

In Words

 

0000: 40004A4B 00000001 0000000E 006C0063 

0008: 00760077 00610063 00730072 006C0071 

0010: 00300030 00000034 00000000  

 

 

In Bytes

 

0000: 4B 4A 00 40 01 00 00 00   KJ.@....

0008: 0E 00 00 00 63 00 6C 00   ....c.l.

0010: 77 00 76 00 63 00 61 00   w.v.c.a.

0018: 72 00 73 00 71 00 6C 00   r.s.q.l.

0020: 30 00 30 00 34 00 00 00   0.0.4...

0028: 00 00 00 00               ...

 

 

- System 

 

  - Provider 

 

   [ Name]  MSSQL$ExcelicareReport 

 

  - EventID 19019 

 

   [ Qualifiers]  16384 

 

   Level 2 

 

   Task 3 

 

   Keywords 0x80000000000000 

 

  - TimeCreated 

 

   [ SystemTime]  2009-05-20T16:19:36.000Z 

 

   EventRecordID 10474 

 

   Channel Application 

 

   Computer clw-carsql-001.dirone.imperial.nhs.uk. 

 

   Security 

 

 

- EventData 

 

   [sqsrvres] OnlineThread: service stopped while waiting for QP.  

   4B4A0040010000000E00000063006C0077007600630061007200730071006C00300030003400000000000000 

 

 

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

 

Binary data:

 

 

In Words

 

0000: 40004A4B 00000001 0000000E 006C0063 

0008: 00760077 00610063 00730072 006C0071 

0010: 00300030 00000034 00000000  

 

 

In Bytes

 

0000: 4B 4A 00 40 01 00 00 00   KJ.@....

0008: 0E 00 00 00 63 00 6C 00   ....c.l.

0010: 77 00 76 00 63 00 61 00   w.v.c.a.

0018: 72 00 73 00 71 00 6C 00   r.s.q.l.

0020: 30 00 30 00 34 00 00 00   0.0.4...

0028: 00 00 00 00               ....

 

 

- System 

 

  - Provider 

 

   [ Name]  MSSQL$ExcelicareReport 

 

  - EventID 19019 

 

   [ Qualifiers]  16384 

 

   Level 2 

 

   Task 3 

 

   Keywords 0x80000000000000 

 

  - TimeCreated 

 

   [ SystemTime]  2009-05-20T16:19:36.000Z 

 

   EventRecordID 10473 

 

   Channel Application 

 

   Computer clw-carsql-001.dirone.imperial.nhs.uk. 

 

   Security 

 

 

- EventData 

 

   [sqsrvres] CheckServiceAlive: Service is dead  

   4B4A0040010000000E00000063006C0077007600630061007200730071006C00300030003400000000000000 

 

 

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

 

Binary data:

 

 

In Words

 

0000: 40004A4B 00000001 0000000E 006C0063 

0008: 00760077 00610063 00730072 006C0071 

0010: 00300030 00000034 00000000  

 

 

In Bytes

 

0000: 4B 4A 00 40 01 00 00 00   KJ.@....

0008: 0E 00 00 00 63 00 6C 00   ....c.l.

0010: 77 00 76 00 63 00 61 00   w.v.c.a.

0018: 72 00 73 00 71 00 6C 00   r.s.q.l.

0020: 30 00 30 00 34 00 00 00   0.0.4...

0028: 00 00 00 00               ....

Open in new window

0
Comment
Question by:bmac000
  • 7
  • 2
9 Comments
 

Author Comment

by:bmac000
Comment Utility
I guess my next question is due to the lack of response, Does anyone have the same setup above with KB958644 installed and working? thanks
0
 

Author Comment

by:bmac000
Comment Utility
I have also noticed that the sql server and sql agent services are not started in SSCM on the active node and when I try to manually start them I get the same 3 error messages as above:
event id: 19019 [sqsrvres] OnlineThread: Error 1 bringing resource online. (more info in code)
event id: 19019 [sqsrvres] OnlineThread: service stopped while waiting for QP.
event id: [sqsrvres] CheckServiceAlive: Service is dead
0
 

Author Comment

by:bmac000
Comment Utility
some more info, this is what i got from the sql agent error logs:
2009-05-21 08:59:39 - ! [298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
2009-05-21 08:59:39 - ! [000] Unable to connect to server 'CLWVCARSQL003\EXCELICARELIVE'; SQLServerAgent cannot start
2009-05-21 08:59:39 - ! [298] SQLServer Error: 18452, Login failed for user ''. The user is not associated with a trusted SQL Server connection. [SQLSTATE 28000]
2009-05-21 08:59:39 - ! [382] Logon to server 'CLWVCARSQL003\EXCELICARELIVE' failed (DisableAgentXPs)
2009-05-21 08:59:39 - ? [098] SQLServerAgent terminated (normally)

this is what i get from from the error log off sql:
2009-05-21 11:05:58.04 Server      Microsoft SQL Server 2005 - 9.00.4035.00 (X64)
      Nov 24 2008 16:17:31
      Copyright (c) 1988-2005 Microsoft Corporation
      Enterprise Edition (64-bit) on Windows NT 6.0 (Build 6001: Service Pack 1)

2009-05-21 11:05:58.04 Server      (c) 2005 Microsoft Corporation.
2009-05-21 11:05:58.04 Server      All rights reserved.
2009-05-21 11:05:58.04 Server      Server process ID is 5916.
2009-05-21 11:05:58.04 Server      Authentication mode is WINDOWS-ONLY.
2009-05-21 11:05:58.04 Server      Logging SQL Server messages in file 'H:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-05-21 11:05:58.04 Server      This instance of SQL Server last reported using a process ID of 6000 at 5/21/2009 10:54:17 AM (local) 5/21/2009 9:54:17 AM (UTC). This is an informational message only; no user action is required.
2009-05-21 11:05:58.04 Server      Registry startup parameters:
2009-05-21 11:05:58.04 Server             -d H:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-05-21 11:05:58.04 Server             -e H:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-05-21 11:05:58.04 Server             -l H:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-05-21 11:05:58.04 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-05-21 11:05:58.04 Server      Detected 8 CPUs. This is an informational message; no user action is required.
2009-05-21 11:05:58.04 Server      Cannot use Large Page Extensions:  lock memory privilege was not granted.
2009-05-21 11:05:58.12 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2009-05-21 11:05:58.15 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-05-21 11:05:58.23 spid1s      A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 40812, committed (KB): 187776, memory utilization: 21%.
2009-05-21 11:06:02.68 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2009-05-21 11:06:02.68 Server      Database mirroring has been enabled on this instance of SQL Server.
2009-05-21 11:06:02.69 spid4s      Starting up database 'master'.
2009-05-21 11:06:02.75 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-05-21 11:06:02.82 spid4s      SQL Trace ID 1 was started by login "sa".
2009-05-21 11:06:02.84 spid4s      Starting up database 'mssqlsystemresource'.
2009-05-21 11:06:02.85 spid4s      The resource database build version is 9.00.1399. This is an informational message only. No user action is required.
2009-05-21 11:06:02.96 spid9s      Starting up database 'model'.
2009-05-21 11:06:02.96 spid4s      Server name is 'CLWVCARSQL003\EXCELICARELIVE'. This is an informational message only. No user action is required.
2009-05-21 11:06:02.96 spid4s      The NETBIOS name of the local node that is running the server is 'CLW-CARSQL-001'. This is an informational message only. No user action is required.
2009-05-21 11:06:03.04 spid9s      Clearing tempdb database.
2009-05-21 11:06:03.14 spid9s      Starting up database 'tempdb'.
2009-05-21 11:06:03.15 Server      A self-generated certificate was successfully loaded for encryption.
2009-05-21 11:06:03.18 Server      Server is listening on [ 10.157.95.195 <ipv4> 61059].
2009-05-21 11:06:03.20 spid12s     The Service Broker protocol transport is disabled or not configured.
2009-05-21 11:06:03.20 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2009-05-21 11:06:03.20 Server      Server is listening on [ 10.157.95.195 <ipv4> 1433].
2009-05-21 11:06:03.20 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\EXCELICARELIVE ].
2009-05-21 11:06:03.20 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\clwvcarsql003\MSSQL$ExcelicareLive\sql\query ].
2009-05-21 11:06:03.22 spid12s     Service Broker manager has started.
2009-05-21 11:06:03.23 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-05-21 11:06:03.24 spid4s      Starting up database 'msdb'.
2009-05-21 11:06:03.29 spid4s      Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2009-05-21 11:06:03.29 spid4s      Recovery is complete. This is an informational message only. No user action is required.
2009-05-21 11:06:03.40 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.40 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.41 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.41 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.41 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.41 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.42 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.42 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.42 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.42 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.42 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.42 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.43 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.43 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.43 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.43 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.43 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.43 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.44 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.44 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:03.44 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:03.44 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.44 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.44 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.45 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.45 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.45 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.45 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.45 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.45 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.46 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.46 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.46 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.46 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.46 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.46 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.47 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.47 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.47 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.47 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.48 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.48 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:05.48 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:05.48 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.48 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.48 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.49 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.49 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.49 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.49 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.49 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.49 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.50 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.50 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.50 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.50 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.50 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.50 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.51 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.51 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.51 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.51 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.51 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.51 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:07.52 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:07.52 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.52 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.52 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.52 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.52 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.53 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.53 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.53 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.53 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.54 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.54 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.54 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.54 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.54 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.54 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.55 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.55 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.55 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.55 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.55 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.55 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:09.56 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:09.56 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.56 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.56 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.56 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.56 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.57 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.57 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.57 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.57 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.57 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.57 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.58 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.58 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.58 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.58 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.58 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.58 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.59 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.59 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.59 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.59 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:11.59 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:11.59 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.60 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.60 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.60 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.60 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.61 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.61 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.61 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.61 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.61 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.61 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.62 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.62 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.62 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.62 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.62 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.62 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.63 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.63 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.63 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.63 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:13.63 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:13.63 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.64 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.64 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.64 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.64 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.64 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.64 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.65 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.65 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.65 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.65 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.66 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.66 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.66 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.66 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.66 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.66 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.67 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.67 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.67 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.67 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:15.67 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:15.67 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.68 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.68 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.68 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.68 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.68 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.68 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.69 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.69 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.69 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.69 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.69 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.69 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.70 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.70 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.70 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.70 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.70 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.70 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.71 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.71 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:17.71 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:17.71 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.71 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.71 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.72 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.72 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.72 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.72 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.73 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.73 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.73 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.73 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.73 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.73 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.74 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.74 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.74 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.74 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.74 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.74 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.75 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.75 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:19.75 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:19.75 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.75 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.75 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.76 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.76 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.76 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.76 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.76 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.76 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.77 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.77 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.77 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.77 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.77 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.77 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.78 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.78 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.78 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.78 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.78 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.78 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:21.79 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:21.79 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.79 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.79 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.79 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.79 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.80 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.80 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.80 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.80 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.80 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.80 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.81 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.81 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.81 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.81 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.81 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.81 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.82 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.82 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.82 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.82 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:23.83 Logon       Error: 18456, Severity: 14, State: 11.
2009-05-21 11:06:23.83 Logon       Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 10.157.95.197]
2009-05-21 11:06:25.87 spid12s     Service Broker manager has shut down.
2009-05-21 11:06:25.89 spid4s      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.
2009-05-21 11:06:25.89 spid4s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
0
 

Author Comment

by:bmac000
Comment Utility
here is one link, there are others: http://technet.microsoft.com/en-us/magazine/cc672627.aspx
its about half way down the page.

Enhanced Security Features
Failover Clusters feature several new security enhancements. Perhaps the most significant involves the removal of the requirement for a Cluster Service Account (CSA). In previous versions of the Microsoft Cluster Service, a domain user account was required during the configuration process. This account, which was used to start the cluster service, was added to the local administrators group on each node of the cluster and given the required local user rights to allow the cluster service to function properly. As a domain user account, the CSA was subject to a number of domain-level policies that could be applied to cluster nodes. These policies could adversely impact high availability by causing the cluster service to fail.
The cluster service now runs under a local system account with a specific set of rights on the local cluster node that allows it to function properly. The security context for the cluster has transitioned to the Cluster Name Object (CNO), which is the computer object that is created, by default, in the Computers container in Active Directory® when the cluster is first created. Once a cluster is successfully created and the CNO exists in Active Directory, the user account that was used to install and configure the cluster is no longer needed.
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 
LVL 142

Assisted Solution

by:Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3] earned 40 total points
Comment Utility
My best shot is this:
contact MS help directly for this, eventually through your ms vendor...
this is not a very "common" scenario.

apart from that: do not apply the KB958644...
0
 

Author Comment

by:bmac000
Comment Utility
I have already done this and funny enough MS were connected to my server on Friday for over an hour and could not sort it out. I have sent some config reports and log files and I am waiting to here back from them.

I cannot not apply the patch as our network got hit with conficker and every server we have is patched. Anyway thanks for responding and it would be good for my own peace of mind if someone could post up that they have an active to active windows 2008 enterprise cluster with sql 2005 installed with KB958644 patch installed and everything works fine, just so I know. If no one has this then can someone please set up a test lab, make sure the cluster is working fine and then apply the patch to see if it breaks it and let me know. cheers
0
 
LVL 142

Assisted Solution

by:Guy Hengel [angelIII / a3]
Guy Hengel [angelIII / a3] earned 40 total points
Comment Utility
well, you started the best approach: MS.
they connected to your server, and found a problem they could not solve directly.
now, they HAVE to fix the issue (as I presume they have some SLA given your licensing contract), eventually a given hotfix ...
if someone has the "lab" configuration, it's them.
hope to hear soon that they fixed what they broke :)
0
 

Author Comment

by:bmac000
Comment Utility
we will wait and see and interestingly we don't have a support contract with MS but they have offered to look at my problem for free because this patch broke it.
0
 

Accepted Solution

by:
bmac000 earned 0 total points
Comment Utility
Latest update on this issue is I fixed it myself here is what i did,

Basically we got hit with the conficker virus so we had to patch all our servers with KB958644 and also we applied GPO as per MS site http://support.microsoft.com/kb/962007

So in order to fix my sql cluster issue (and in fact even to install the SQL cluster) you must
> reverse the above GPO if you have already applied it (as simply taking it out of the OU and running gpupdate will not reverse it)
> uninstall KB958644 on both nodes in your cluster, reboot
> now this is the bit that fixed my problem, i ran a command to reset the locat security policy on both servers (nodes) in my cluster which is this for windows 2008 (its slight different for windows 2003) secedit /configure /cfg c:\windows\inf\defltbase.inf /db defltbase.sdb /verbose
> i then rebooted, and made sure my cluster was working again
> then I reapplied the patch kb958644
> then ofcourse the cluster wouldn't start again so I re ran the above command on both nodes in my cluster, rebooted again and it all works

I hope this helps you let me know if you need anything else and I have just got off the phone to MS and explained to them what I did. They had this problem for over a week and couldn't help. cheers
0

Featured Post

Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

Join & Write a Comment

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Join Greg Farro and Ethan Banks from Packet Pushers (http://packetpushers.net/podcast/podcasts/pq-show-93-smart-network-monitoring-paessler-sponsored/) and Greg Ross from Paessler (https://www.paessler.com/prtg) for a discussion about smart network …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now