Correction... They did see this in the log files: Error 6 2011-07-20T01:03:08 634467205887687039 Error in UpdateSiteStatuses Enterprise.Console.EnterpriseConsole.UpdateSiteStatuses( Boolean )+3852 System.Data.EntityException: The underlying provider failed on Open. ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
Tech support requested that I ensure that the SQL server *was* running and able to log in as a local account, which it was. They also asked me to schedule a reboot with the console *off*, which proceeded nicely. Obviously something in the console is causing the server to hang. I don't know why. From: Steve Ens [mailto:[email protected]] Sent: Tuesday, July 26, 2011 11:18 AM To: NT System Admin Issues Subject: Re: Vipre console hangs server on reboot Hey CB, Do you think that there might be an underlying issue that is causing a server hang? Perhaps see if you can fix the cause rather than just remedy using a task killer. Why does the server hang with the VEC open? Any clues in your event viewer? Steve ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
