Endpoint Protection

"Your SQL Server login credentials could not be validated. Please re-enter your SQL Server login information."

We had above error at one of the server during upgrade, 'sa' credentials was correct.

Any idea?

We already tried this KB http://www.symantec.com/business/support/index?page=content&id=TECH162182 but alas not working....

Check this KB article

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

Hi Brian,

as mentioned we already tried to follow that KB.....

it were as asking to post database hostname in "server name/instance name" format

still fails

Make sure the servername/instance name is typed exactly as it is case sensitive. I've seen it fail before if "servername" was not capitalised or vice versa when it should've been.

Also, the account your doing it with has full privs?

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

check the instance name, pass on the upgrade log.

Hi Brian,

Yes, i've double checked the 2nd KB also.... priviliges are correct

Also i noticed that we don't actually have an instance name ..... i ran SQL query below

" select @@ServerName  "

it return back with same SQL hostname....

Hi Pete,

Whr can i find the upgrade log?

Thanks

Hi,

Check this artical

http://msdn.microsoft.com/en-us/library/ms190703.aspx

Check this thread

https://www-secure.symantec.com/connect/forums/sepm-12-upgrade-sql-credential-problem

Thanks, already checked both... still same

Also i noticed some diffrent at SQL level, refer attached....

Somehow threre's an 'sa' user in sem5--->security-->users... i compared with other SEPM sql... there are none

Hi,

I checked the Etrack mentioned in the KB article http://www.symantec.com/docs/TECH162182

The workaround to this issue is "before upgrade, reconfigure the server with DB instance name and port"

Even after doing this changes if facing the same issue then need to involve support to investigate further.

Please contact Symantec Technical Support via the support phone numbers listed below

Regional Support Telephone Numbers:
United States: https://support.broadcom.com (407-357-7600 from outside the United States)
Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
United Kingdom: +44 (0) 870 606 6000
Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp   India: Toll-Free 000 800 4401 456                                                                                                       

Technical Support

http://www.symantec.com/business/support/contact_techsupp_static.jsp

check for the upgrade.log if it still fails located under Symantec\Symantec Endpoint Protection Manager\tomcat\logs\

Hi Chetan,

Yes we have already tried that but fails..... we do have case open with support.

Hi Pete,

Attached is upgrade.log .... try to find but didn't found any error related to SQL...

Attachment(s)

upgrade.zip   33 KB 1 version

does not look like its an upgrade log , since i do not see any entries related to server or db version.

Hello,

Did you check this Article:

Symantec Endpoint Protection 12.1: SQL Server login credentials are not accepted when upgrading the Symantec Endpoint Protection Manager

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

Hi Mithun,

Checked that KB already before posting here.... permissions are correct.

Any idea about the 'sa' user in image that i posted?

Hello,

Is the sa account set to Mixed mode authentication??

Check these Articles:

About SQL Server configuration settings

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

About SQL Server configuration settings

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

Account name and password requirements for Symantec Endpoint Protection

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

Hope that helps!!

Answer by support as below:

A login is used for user authentication and a database user account is used for database access and permissions validation. Logins are associated to users by the security identifier (SID). A login is required for access to the SQL Server server. This login must be associated to a SQL Server database user. You use the user account to control activities performed in the database. If no user account exists in a database for a specific login, the user that is using that login cannot access the database even though the user may be able to connect to the SQL Server server.

The original Endpoint Protection Manager had been configured using only the SQL server name,rather than the server_name\instance_name combination.

A non-sa SQL user is attempted to be used to authenticate instead of a user account that has the 'sysadmin' level rights to SQL

So basically we reconfigured the SEPM 11 to use SQL IP instead of  SQL hostname.

In upgrade option we also put SQL IP instead of hostname ...and then only the upgrade wizard able to recognize the 'sa' credentials and finish the upgrade.

Thanks again for input and help.