Endpoint Protection

There is a new issue came up in out SEP stup. The SEPM server goes to hang state very frequently. The problem gets resolved only after REBOOTING THE SQL DB SERVER.

As per my finding - There are some SQL DB related issue.... See the Application below -

Anyone can assist me on this to resolve the issue.

Event Type: Error
Event Source: SQLISPackage
Event Category: None
Event ID: 12291
Date:  2/17/2010
Time:  10:45:28 AM
User:  NT AUTHORITY\SYSTEM
Computer: SEP-SE-DB01
Description:
The description for Event ID ( 12291 ) in Source ( SQLISPackage ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: production_backup_log.


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 18204
Date:  2/17/2010
Time:  10:45:22 AM
User:  NT AUTHORITY\SYSTEM
Computer: SEP-SE-DB01
Description:
The description for Event ID ( 18204 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: BackupDiskFile::OpenMedia, E:\Backup\SEP_SE\SEP_SE_backup_201002170614.trn, open, 2(The system cannot find the file specified.).
Data:
0000: 1c 47 00 00 10 00 00 00   .G......
0008: 0c 00 00 00 53 00 45 00   ....S.E.
0010: 50 00 2d 00 53 00 45 00   P.-.S.E.
0018: 2d 00 44 00 42 00 30 00   -.D.B.0.
0020: 31 00 00 00 00 00 00 00   1.......


Event Type: Error
Event Source: MSSQLSERVER
Event Category: (6)
Event ID: 3041
Date:  2/17/2010
Time:  10:44:13 AM
User:  NT AUTHORITY\SYSTEM
Computer: SEP-SE-DB01
Description:
The description for Event ID ( 3041 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: BACKUP LOG SEP_SE.
Data:
0000: e1 0b 00 00 10 00 00 00   á.......
0008: 0c 00 00 00 53 00 45 00   ....S.E.
0010: 50 00 2d 00 53 00 45 00   P.-.S.E.
0018: 2d 00 44 00 42 00 30 00   -.D.B.0.
0020: 31 00 00 00 07 00 00 00   1.......
0028: 53 00 45 00 50 00 5f 00   S.E.P._.
0030: 53 00 45 00 00 00         S.E... 





Thanks

It would be great if you could let us know the following :-

SEPM Version

The OS of the machine hosting SQL

The version of SQL

You can check whether the machine was recently patched with any Windows update.

SEPM Version - 11.0.4202.75 ( MR4 MP2)

The OS of the machine hosting SQL - Windows 2003 R2 Ent. Edition 64bit - SP2

The version of SQL - SQL 2005 - SP2

Whether both SEPM and SQL server is in the same LAN? 

Yes! SQL DB and SEPM server in the same LAN.

It's an simple issue.

UNC versus mapped drives! The manual process uses your credentials, which has a mapped drive reference.  The job uses the SQL Server Agent account, which does not.

http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/b203daa3-cafc-4df9-9712-a8724b8aa910


HTH.

Just an extra recommendation: apply the SP3 for MS SQL 2005.  The database server will benefit from the many available fixes and improvements in that latest Service Pack.

Thanks and best regards,

Mick