1 Reply Latest reply on May 24, 2013 8:54 AM by alexn

    i  have a problem from last 7  days my mcafee epo 4.6.5 is not open error on opening http500

      please help me to solve this problem
      

      http 500 internal server error.png

      2013-04-26 19:11:10.73 Server      Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)

                Nov 24 2008 13:01:59

                Copyright (c) 1988-2005 Microsoft Corporation

                Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)

       

       

      2013-04-26 19:11:10.73 Server      (c) 2005 Microsoft Corporation.

      2013-04-26 19:11:10.73 Server      All rights reserved.

      2013-04-26 19:11:10.73 Server      Server process ID is 3304.

      2013-04-26 19:11:10.73 Server      Authentication mode is WINDOWS-ONLY.

      2013-04-26 19:11:10.73 Server      Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

      2013-04-26 19:11:10.73 Server      This instance of SQL Server last reported using a process ID of 1372 at 4/26/2013 7:11:09 PM (local) 4/27/2013 2:11:09 AM (UTC). This is an informational message only; no user action is required.

      2013-04-26 19:11:10.73 Server      Registry startup parameters:

      2013-04-26 19:11:10.73 Server                 -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

      2013-04-26 19:11:10.73 Server                 -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

      2013-04-26 19:11:10.73 Server                 -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

      2013-04-26 19:11:10.75 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

      2013-04-26 19:11:10.75 Server      Detected 4 CPUs. This is an informational message; no user action is required.

      2013-04-26 19:11:11.30 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.

      2013-04-26 19:11:11.51 Server      Database mirroring has been enabled on this instance of SQL Server.

      2013-04-26 19:11:11.51 spid4s      Starting up database 'master'.

      2013-04-26 19:11:11.60 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

      2013-04-26 19:11:11.63 spid4s      SQL Trace ID 1 was started by login "sa".

      2013-04-26 19:11:11.63 spid4s      Starting up database 'mssqlsystemresource'.

      2013-04-26 19:11:11.65 spid4s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.

      2013-04-26 19:11:11.77 spid4s      Server name is 'MCAFEE-SERVER\EPOSERVER'. This is an informational message only. No user action is required.

      2013-04-26 19:11:11.78 spid8s      Starting up database 'model'.

      2013-04-26 19:11:11.78 spid4s      Starting up database 'msdb'.

      2013-04-26 19:11:11.89 spid8s      Clearing tempdb database.

      2013-04-26 19:11:12.03 Server      A self-generated certificate was successfully loaded for encryption.

      2013-04-26 19:11:12.04 Server      Server is listening on [ 'any' <ipv6> 49208].

      2013-04-26 19:11:12.04 Server      Server is listening on [ 'any' <ipv4> 49208].

      2013-04-26 19:11:12.04 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\EPOSERVER ].

      2013-04-26 19:11:12.04 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$EPOSERVER\sql\query ].

      2013-04-26 19:11:12.04 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.

      2013-04-26 19:11:12.04 Server      The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

      2013-04-26 19:11:12.04 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.

      2013-04-26 19:11:12.30 spid8s      Starting up database 'tempdb'.

      2013-04-26 19:11:12.36 spid4s      Recovery is complete. This is an informational message only. No user action is required.

      2013-04-26 19:11:12.36 spid11s     The Service Broker protocol transport is disabled or not configured.

      2013-04-26 19:11:12.36 spid11s     The Database Mirroring protocol transport is disabled or not configured.

      2013-04-26 19:11:12.37 spid11s     Service Broker manager has started.

      2013-04-26 19:11:17.50 Logon       Error: 17806, Severity: 20, State: 2.

      2013-04-26 19:11:17.50 Logon       SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.8]

      2013-04-26 19:11:17.50 Logon       Error: 18452, Severity: 14, State: 1.

      2013-04-26 19:11:17.50 Logon       Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.8]

      2013-04-26 19:11:18.01 Logon       Error: 17806, Severity: 20, State: 2.

      2013-04-26 19:11:18.01 Logon       SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.8]

      2013-04-26 19:11:18.01 Logon       Error: 18452, Severity: 14, State: 1.

      2013-04-26 19:11:18.01 Logon       Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.8]

      2013-04-26 19:11:18.60 Logon       Error: 17806, Severity: 20, State: 2.

      2013-04-26 19:11:18.60 Logon       SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.8]

      2013-04-26 19:11:18.60 Logon       Error: 18452, Severity: 14, State: 1.

      2013-04-26 19:11:18.60 Logon       Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.8]