Endpoint Protection

I'm creating a new SEP 12 environment:

1 SQL server - Windows 2008 R2 w/ SQL 2012

2 SEPM's - Windows 2008 R2

The SEPM part of the installation works until I get to the database creation stage - I enter the details for Step One - it allows me to connect to the database

I enter the details for Step Two, as soon as I click next I'm given an 'Unexpected Error'

I've tried this on both SEPM's with the same result - I've submitted the troubleshooting logs to Symantec support with nothing obvious showing in those.

Any thoughts/ideas?

Cheers,

Mike

Hi,

Can you provide Error screen shot ?

Please find it attached - it's not the most intuitive of screenshots.

Hi,

What do you mean by Step One and Step Two?  Does step One means Installation of Symantec Endpoint Manager and Step Two means Configuring the Manger? If yes, then exactly on which step you are getting this Unexpected Error?

Hi Ajit,

I've attached a screenshot of the the screen in question (with the details removed), you enter details in the top section, click connect to database, if it can authenticate correctly it opens up the bottom section - populate that, when I click next it gives the error attached in previous post:

Cheers,

Mike

Hi,

Check this

https://www-secure.symantec.com/connect/videos/symantec-endpoint-protection-manager-121-fresh-install-sql-database

Please check this artical and follow steps

https://www-secure.symantec.com/connect/articles/sepm-121-fresh-install-sql-database-graphical-overview

mthorpe,

Just Onemore thing i require, that is Application Log, please export it in txt format and Upload it.

Hi

Please check the database port

Regards

Hello,

Check these Articles:

Installing and configuring Symantec Endpoint Protection Manager with a SQL Server database

http://www.symantec.com/docs/HOWTO17973

How to install the Symantec Endpoint Protection Manager using Windows Authentication and SQL Server 2008

http://www.symantec.com/docs/HOWTO36029

Hope that helps!!

Ashish,

I'll check that work through shortly.

SameerU

I've confirmed the port with the DBA and double-checked it myself.

Hi Mthorpe.

Please try these workarounds for Unexpected error at this point of Installation.

Verify database connectivity using below Symantec article.

http://www.symantec.com/business/support/index?page=content&id=TECH105218 

or

Need to check the permisions where we have installed Symantec Endpoint Protection Manager.

- Domain account which has been used to access the SQL database should have "Local Administrator" rights on the Server where we have installed Symantec Endpoint Protection Manager console .

I'm getting a stuck on the part those don't show, the second step of the new database creation.

Cheers,

Mike

I can't see that linked document...

I'm not sure I follow what you mean with that last bit - I'm using a SQL account to access SQL from the SEPM.

Hi

You have to check SQL client tool is installed on SEPM server or not and also checked that authentication mode (SQL/ Window).

Regards,

Kamran

Mithun,

That's pretty much exactly how I've set this up..

The config screen in the second document looks different to the on I get, is that for an older version of SEP?

SQL is installed on a totally seperate server - it's also running in mixed mode.

Hmm, here the steps to Verify communication to the SQL Database.

1. Verify that you have specified a named instance during installation and configuration. Example: \\\
2. Verify SQL Server is running and properly configured.
3. Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.
4. Test the ODBC connection.
   1. Click Start> Control Panel
   2. Open Administrator Tools
   3. Double-click Data Sources (ODBC)
   4. Select the System DSN tab
   5. Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
      • Name: SymantecEndpointSecurityDSN
      • Description:
      • Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
      • Login ID: sa
      • Password: <SA Password>  
   6. Leave the defaults for the rest of the items and click Finish
   7. Click Test Data Source on the next page and ensure it states "Success"
   8. Click OK

Are you trying to install on new instance or already existing one?

Do you have sql tools installed on this server? do you see anything under binn folder

There was no ODBC connection, I've justed created one (on the SEPM) the test comes back as successfull, it's made no difference to the issue.

Rafeeq,

It's a completely new instance - SQL tools are installed on the SQL server (step one of the configuration requires the path for bcp.exe before it allows progression to step two).

Please see below screenshot for items under the binn folder

if you dont know the SQL tool is install, You can verify this by ensuring that bcp.exe exists in the following directory:

C:\Program Files\Microsoft SQL Server\100\Tools\Binn\bcp.exe

If bcp.exe is not in this location, then you need to go back through the client tools installation and ensure you've checked the following:

Client Tool Connectivity
Client Tools Backward Compatibility
Client Backwards Compatibility

Kamran,

In the screenshot I've attached above I can see that bcp.exe is definitely present on the SQL server.

Hi,

Better i will say, wait for the Technician to come up with the solution as you have already raised a Techincal Case on this issue, If the Front End Technician is unable to ressolve it you can always escalte to Advance Team for more in depth Troubleshooting.

Please check or do the follwowing steps.

Configure the SQL Server port binding.  

• From the Start Menu, select, all programs> SQL Server 2008>SQL Server Configuration Manager
• Expand SQL Network Configuration >Protocols for SEP01 (where SEP01 is the name of the instance you created in the SQL setup).
• Ensure TCP/IP is enabled.

• Double-click on TCP/IP
• Select the IP address tab.
• Scroll all the way to the bottom and under IPAll, enter 1433 for TCP Port.

Please note that you must use TCP Port here as the SEPM cannot connect to the SQL Server using Dynamic ports.
• Click OK.
• You will need to restart then SQL Server Service.

This was intentionally set to another port - I've just changed to 1433, restarted the server service - this has not made any difference.

You need to install the SQL tools on the SEPM server. I believe you are referring to SQL tools on the SQL server which is on different Server. Please install the tools on the SEPM server

check this document.

http://www.symantec.com/business/support/index?page=content&id=HOWTO36029

Rafeeq,

That appears to have nailed it - after installing SQL tools locally it's now working.

Ta very muchly.

Hi mthorpe,

Please check the Comment from Kamran before the Comment made from Rafeeq, he has also mentioned about the same SQL tool on SEPM. You should mark his comment as Solution. This is not fare.