Endpoint Protection

I'm installing a new copy of SQL server 2005 and Symantec Endpoint Protection Manager on an '03 Server and running into issues with connectivity. I am attempting to create a SQL database to use instead of the embedded database which comes with SEPM. Whenever I reach the point in the Server Configuration Wizard during the install of SEPM I get the error 11501, or failure to connect to the database. I have followed the instructions pertaining to that error and enabled the TCP/IP protocol on the SQL server and am able to ping SQL succesfully. What could be causing this issue and how might I go about resolving it?

You may need to disable UAC if it's in play.  Verify the ODBC test passes.

See this thread for a possible solution.

https://www-secure.symantec.com/connect/forums/error-11501-while-installing-symantec-endpoint-protection-manager-console-1105002333-sql-data

Also check this guide 

Error 11501: Unable to create the database for Symantec Endpoint Protection Manager

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/8b9e2bd0d37a098688257603006511ee?OpenDocument

Cheers
Grant

Hi Jake,

The excellent advice above should help you overcome that 11501.  Once that SEPM is successfully using its MS SQL database, do spend a little time ensuring that it is configured well.  Properly configured and maintained, when running on adequate hardware, MS SQL can serve as a brilliant high-performance DB for the SEPM.

First: make sure that you have MS SQL 2005 SP3.  Many people are still using SP2, though Microsoft has retired that version.

Make sure the  client components on the SEPM are the same SP as what's on the SQL server itself.  Upgrade them to SP3, too!

How to exclude MS SQL files and folders using Centralized Exceptions

Create database maintenance plans in MS SQL Server 2005 using SQL Server Integration Services (SSIS)

Improving SEPM Performance with the SEM_GETUSN Stored Procedure

Run Microsoft's free "SQL Best Practices Analyzer" every so often to ensure the SQL server is healthy

Please do keep the community forum up-to-date with your progress!

Thanks and best regards,

Mick