• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2097
  • Last Modified:

'Waiting...' error on Windows Server 2008

We have a new HP ML110 G6 server with an Adaptec 1220SA RAID controller that we have just installed Windows Server Standard 2008 on to. It is joined to the existing domain, which runs an ISA firewall.

The server drops randomly during the day, at which point we can ping it but not do much else. Looking at the screen, it looks like the standard Windows Server 2008 logging in screen, but it just says 'Waiting...' - that's it. We have to switch off and reboot the machine for it to function again.

Any ideas as to what this could be?
0
Jim Jones
Asked:
Jim Jones
  • 5
  • 3
1 Solution
 
abt-itCommented:
What's inside Performance and Reliability?

Have a look at http://technet.microsoft.com/en-us/library/cc771692(WS.10).aspx for detailed configuration Options.
0
 
abt-itCommented:
What's inside Performance and Reliability Console?

Have a look at http://technet.microsoft.com/en-us/library/cc771692(WS.10).aspx for detailed configuration Options.
0
 
Jim JonesAuthor Commented:
Nothing conclusive is shown in the Reliability Monitor, all it has logged are 'Disruptive Shutdowns' where we have had to force the machine off when it has the 'Waiting...' screen displayed. The Reliability index is down to 6.9 though.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
abt-itCommented:
what about the perfomance monitor? Can you check for CPU / RAM Usage before the Server hangs?

Did you checkd the Harddrive for errors? Malware check?
0
 
Jim JonesAuthor Commented:
Malware check is clean, performed CPU and RAM stress tests and they passed. Hard drive not yet checked as it would involve downtime.

We have constant monitoring on the server using GFI Max and the CPU / RAM / Network usage doesn't increase when the server is about to hang.
0
 
vguzmanIT ManagerCommented:
Can you check event viewer for errors ?  It could be wrong DNS settings where the server is looking for the DNS server and cannot find it. What happens if you boot it in safe mode ?
0
 
Jim JonesAuthor Commented:
Hi,

The following warnings in the Application event log are listed:

Log Name:      Application
Source:        SRMSVC
Date:          28/04/2010 10:35:16
Event ID:      12317
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xxx
Description:
File Server Resource Manager failed to enumerate share paths or DFS paths.  Mappings from local file paths to share and DFS paths may be incomplete or temporarily unavailable.  FSRM will retry the operation at a later time.

Context:
   Domain: xxx

Error-specific details:
   Error: DfsMapCacheAdd, 0x80070005, Access is denied.

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

Log Name:      Application
Source:        Microsoft-Windows-ApplicationExperienceInfrastructure
Date:          28/04/2010 11:13:31
Event ID:      1
Task Category: None
Level:         Warning
Keywords:      
User:          xxx
Computer:      xxx
Description:
The application (Firewall Client for ISA Server 2004, from vendor Microsoft) has the following problem: Firewall Client for ISA Server 2004 has a known compatibility issue with this version of Windows. For an update that is compatible with this version of Windows, contact Microsoft.


These are the only two problems reported under Application or System. I have confirmed that the DNS servers are set correctly.
0
 
Jim JonesAuthor Commented:
Sorry, there are more errors reported in the System event logs! These seem to appear just as the server becomes unresponsive:

Log Name:      System
Source:        NETLOGON
Date:          27/04/2010 16:29:38
Event ID:      5783
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxx
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller \\DC01 for the domain xxx is not responsive.  The current RPC call from Netlogon on \\SERVER to \\DC01 has been cancelled.

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

Log Name:      System
Source:        Service Control Manager
Date:          27/04/2010 17:26:54
Event ID:      7031
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER.xxx.local
Description:
The Advanced Monitoring Agent service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

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

Log Name:      System
Source:        Service Control Manager
Date:          27/04/2010 17:28:24
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER.xxx.local
Description:
A timeout was reached (30000 milliseconds) while waiting for the Advanced Monitoring Agent service to connect.

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

Log Name:      System
Source:        Service Control Manager
Date:          27/04/2010 17:28:24
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER.xxx.local
Description:
The Advanced Monitoring Agent service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

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

Log Name:      System
Source:        Microsoft-Windows-GroupPolicy
Date:          27/04/2010 17:37:03
Event ID:      1007
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      SERVER.xxx.local
Description:
The processing of Group Policy failed. Windows could not determine the site associated for this computer, which is required for Group Policy processing.
0
 
Jim JonesAuthor Commented:
Replaced the server with one running Windows Server 2003 and all problems went away. The problem seems to be that Windows Server 2008 and ISA 2004 are so incompatible that it brings the server down.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now