Endpoint Protection

I just upgraded two of my SEPM servers to 12.1.5 from 12.1.4.They run on Server 2008 R2 SP1, 64 bit.

Replication keeps failing and I see this in the scm-server log file

2014-10-09 08:59:43.795 THREAD 121 WARNING: Return code: 1; Message: SQLState = S1000, NativeError = 0
Error = [Microsoft][SQL Native Client]Unable to open BCP host data-file
 
2014-10-09 08:59:44.103 THREAD 121 SEVERE:  in: com.sygate.scm.server.replication.ReplicationTask
java.sql.SQLException: Failed to load data: SQLState = S1000, NativeError = 0
Error = [Microsoft][SQL Native Client]Unable to open BCP host data-file

I've tried removing the replication partner and readding with no change.

Where is the BCP host data-file supposed to be stored? I'm not sure where to go from here.
 

 

try running the management server configuration wizard once

I've done that as well. No change.

Even more awesome fun now.

I stopped the SEPM services, made a copy of the conf.properties file and changed scm.log.loglevel from WARNING to FINEST, started the SEPM service and get "Failed to connect to server" when logging in. I stopped the service, tried to open the conf.properties file and was denied access unlike the first time I tried changing it. Deleted that file and renamed the conf.properties.old back to conf.properties. I can log into the console again.

How did this installation get so messed up? I've repaired the SEPM installation and run the mgmt config wizard but still not working correctly.

If we hadn't just wasted $$$ on buying an additional 6000 licenses, I'd be scrapping this junk in favor of LANDesk AV.

 

Upgraded the SQL Client tools from 2005 to 2008 R2, still getting the same message.

Looks like I'll be opening a case with Symantec on Monday.

Is it possible that I screwed something up because I forgot to disable replication prior to upgrading each of the servers?

High possibility. Because during the replication, best practise its to break the replication for time being since the data base schema upgrades(applies for embedded db) , when Sql doing the service of the other SEPM Will work.

High possibility. Because during the replication, best practise its to break the replication for time being since the data base schema upgrades(applies for embedded db) , when Sql doing the service of the other SEPM Will work.

I started another thread about an ACL issue with another server I'm trying to get setup and I think the issue I have posted here is related. It seems something has changed for version 12.1.5, requiring a specific security privilege that hasn't been an issue for us before.

 

http://www.symantec.com/business/support/index?page=content&id=TECH223311&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D141321321279701NP7fQcXweF44D5xza6xY78lvE3i8w3a3Ass

I checked what it mentions in the Technet article and they're all set correctly but I'm still missing the SeSecurityPrivelege....trying to figure out if it's something on our domain preventing me from having that access.

I had a similar issue with replication. I am using a Windows Domain ID to authenticate to the SQL database. The upgrade from SEP 12.1.4 to SEP 12.1.5 Management server changed the ACL on the data directory and now the process inserting the replicated data can not read it out of the data/replication/inbox folder

I fixed it by granting permission to the domain-id that the SEPM uses to connect to SQL database.

From a command prompt run as administrator, I changed to the folder where the data directory is (usually C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager)

icacls data /grant domain\sqluser:(oi)(ci)(f)

I did this on all my SEPMs involved in replication and it fixed the issue

 

HUGE thank you to nickyc!!!! That worked perfectly and has fixed the issue for us.