Symantec Endpoint Encryption Management Server connection issue on SQL Server

Hi Expert,
I installed SQL Server 2014 SP3 Standard edition and it is default instance.I have migrated seemsdb for Symantec endpoint encryption management server and it was side by side migration. using SSMS seemsdb can be connected but could not save connection from symantech endpoint wizard. Here is the following error:--
“Incompatible Symantec Endpoint Encryption Management Server database version – 9.9.3.  

Please help.
Zahid AhamedDatabase AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dfkeCommented:
Hi,

when I read 'incompatible' then maybe there is a version mismatch of some sort?
See if your version of SQL matches up with Symantec.

Cheers
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> I have migrated seemsdb for Symantec endpoint encryption management server and it was side by side migration
>> Incompatible Symantec Endpoint Encryption Management Server database version – 9.9.3.

Few things to clarify here..
As the error clearly says, seemsdb version 9.9.3 has dependencies with your Symantec version 11.1.3 MP1 and if you try to use seemsdb 9.9.3 with some other version of Symantec, then you will get this error.
Hence if you just migrate seemsdb to the new server, then ensure that you have the same Symantec version as that of your old server.
If you wish to upgrade your Symantec version to latest, then please follow the steps below:
https://support.symantec.com/en_US/article.TECH247759.html
Zahid AhamedDatabase AdministratorAuthor Commented:
Thanks for the reply. I have restored the database from old production server latest backup. Here is the more details:--

Old Server:--
Microsoft SQL Server 2014 (SP3-CU1) (KB4470220) - 12.0.6205.1 (X64)
      Nov 30 2018 02:59:03
      Copyright (c) Microsoft Corporation
      Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Database Compatibility level SQL Server 2008 (100)

New Server:--
Microsoft SQL Server 2014 (SP3) (KB4022619) - 12.0.6024.0 (X64)
      Sep  7 2018 01:37:51
      Copyright (c) Microsoft Corporation
      Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)

Database Compatibility level SQL Server 2008 (100)
Amazon Web Services

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Kindly confirm whether the old Server and new Server have the same Symantec version or not..
If same version, it shouldn't have raised that error..

Also make sure that the database restored in New Server has Compatibility level(100) or not once..
If everything is correct, then it would be better to reach out to Symantec support as they can check your environment and recommend better..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Zahid AhamedDatabase AdministratorAuthor Commented:
The problem was related to cryptography in the application server. This has been resolved. Thanks
Zahid AhamedDatabase AdministratorAuthor Commented:
Audit drive has enought space and audit is set to rollover. This will not cause drive fill up issue.

This is not a finding
Zahid AhamedDatabase AdministratorAuthor Commented:
Sorry please ignore the previous comment. Copy paste error.

The problem was related to cryptography TLS 1.1. issue  in the application server. This has been resolved. Thanks
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Thanks, Zahid for the update..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Symantec Endpoint Protection

From novice to tech pro — start learning today.