Video Screencast Help

Failed to copy data when running Management Server Config Wizard

Created: 03 Mar 2014 • Updated: 05 Mar 2014 | 30 comments
This issue has been solved. See solution.

I am trying to run the Managament Server Configuration Wizard on my SEPM 12.1.4. When the setup gets to Step One: Database Server Authentication I get this error.

3-3-2014 11-40-57 AM.png

I checked the hard drive space on the SEPM and there is 117 GB free. How can I get past this error?

Thank you.

Operating Systems:

Comments 30 CommentsJump to latest comment

.Brian's picture

Is this on 12.1.4 or 12.1.4a?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

.Brian's picture

Can you see how much space you have on the system reserve partition (should be hidden)?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

bspore's picture

There is 70 MB free on the system reserved partition. The capacity is 100 MB.

Rafeeq's picture

its complainng about OS drive space...whats the free space you have on C?

Rafeeq's picture

are you using embedded or sql DB?

if you are connecting remote, try the same with console session

mstsc /v:ip address of server /admin

mstsc /console

 
bspore's picture

I am using a SQL database.

I've have tried connecting using the console session with no luck.

 

 

bspore's picture

When I check the Data Sources (ODBC) it shows nothing under the System DSN tab.

3-3-2014 1-56-16 PM.png

Here is the contents of the scm-server0.log.

2014-03-03 13:51:32.469 THREAD 12 SEVERE: ================== Server Environment ===================
2014-03-03 13:51:32.469 THREAD 12 SEVERE: os.name = Windows Server 2008 R2
2014-03-03 13:51:32.469 THREAD 12 SEVERE: os.version = 6.1
2014-03-03 13:51:32.469 THREAD 12 SEVERE: os.arch = x64
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.version = 1.7.0_25
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.vendor = Oracle Corporation
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.vm.version = 23.25-b01
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2014-03-03 13:51:32.469 THREAD 12 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2014-03-03 13:51:32.469 THREAD 12 SEVERE: java.user = null
2014-03-03 13:51:32.469 THREAD 12 SEVERE: user.language = en
2014-03-03 13:51:32.469 THREAD 12 SEVERE: user.country = US
2014-03-03 13:51:32.469 THREAD 12 SEVERE: scm.server.version = 12.1.4013.4013
2014-03-03 13:51:35.220 THREAD 12 SEVERE: Database Schema Version = 12.1.4.0, Server Schema Version = 12.1.4.0
2014-03-03 13:51:35.673 THREAD 12 SEVERE: FIPS mode configuration is false
2014-03-03 13:51:35.688 THREAD 12 SEVERE: License state = SEPE_PAID
2014-03-03 13:51:35.688 THREAD 12 SEVERE: License status on SEPM = Good
2014-03-03 13:51:35.735 THREAD 12 SEVERE: resetAgentOfflineState=true
2014-03-03 13:51:35.798 THREAD 12 SEVERE: ================== StartClientTransport ===================
2014-03-03 13:51:35.813 THREAD 12 SEVERE: [12] Initializing Tomcat ClientTransport Key for Secars...
2014-03-03 13:51:36.063 THREAD 12 SEVERE: startClientTransport>>resetAgentToOfflineState=true
2014-03-03 13:51:36.063 THREAD 12 SEVERE: startClientTransport>>start set agent offline
2014-03-03 13:51:37.063 THREAD 12 SEVERE: startClientTransport>>start set agent offline
2014-03-03 13:51:38.235 THREAD 12 SEVERE: Schedule is started!
2014-03-03 13:51:38.360 THREAD 12 SEVERE: SEPM Service started
2014-03-03 13:51:49.673 THREAD 152 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:51:49.783 THREAD 157 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:52:37.545 THREAD 43 WARNING: Log table switched to: AGENT_TRAFFIC_LOG_2, old table estimated row count: 50224, to add row count in new table: 4611, last switch time: 2014-03-03 13:18:12
2014-03-03 13:53:10.489 THREAD 153 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:53:30.096 THREAD 151 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:54:10.667 THREAD 157 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:54:12.495 THREAD 154 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=>
2014-03-03 13:54:12.495 THREAD 154 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileSequence,Value=>
2014-03-03 13:54:31.024 THREAD 157 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:54:56.832 THREAD 152 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:54:56.837 THREAD 154 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:55:30.209 THREAD 151 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:55:30.317 THREAD 147 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:55:50.298 THREAD 155 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:55:50.489 THREAD 157 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:55:50.539 THREAD 155 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:10.487 THREAD 152 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=09>
2014-03-03 13:56:10.566 THREAD 155 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:10.736 THREAD 154 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:11.051 THREAD 148 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:11.088 THREAD 154 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:28.942 THREAD 31 WARNING: Log table switched to: SERVER_CLIENT_LOG_2, old table estimated row count: 10170, to add row count in new table: 223, last switch time: 2014-03-03 13:16:37
2014-03-03 13:56:30.315 THREAD 157 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:56:30.669 THREAD 153 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:57:10.398 THREAD 155 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:57:10.580 THREAD 149 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
2014-03-03 13:57:50.451 THREAD 151 SEVERE: com.sygate.scm.server.statereader.av.DataHandler: Line number=1,org.xml.sax.SAXParseException: Invalid numerical value: <Parameter=PatternFileRevision,Value=08>
 
bspore's picture

I can open the ODBC Data Source Administrator just fine. Its when I click on the System DSN tab that it shows no User Data Sources.

bspore's picture

Yes, when I open odbcad32.exe from C:\Windows\SysWOW64 it shows nothing under the System DSN tab. There is nothing listed for System Data Sources.

Rafeeq's picture

Strange :) is this a fresh install/ upgrade from earlier version, was it running before?

 

bspore's picture

It was running before. I've been experiencing issues with the SEMP so I needed to do a repair on it. 

Rafeeq's picture

Open the odbc

  1. Double-click Data Sources (ODBC)
  2. Select the System DSN tab
  3. Click on Add select SQL name it as
  4. SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
    • Name: SymantecEndpointSecurityDSN
    • Description:<Anything>
    • Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
    • Login ID: sa
    • Password: <password>

       

  5. Leave the defaults for the rest of the items and click Finish
  6. Click Test Data Source on the next page and ensure it states "Success"
  7. Click OK
  8.  
bspore's picture

I added SymantecEndpointSecurityDSN to the ODBC and I am still receiving the error about not enough disk space when I run the Management Server Configuration Wizard.

Rafeeq's picture

tried a repair of SEPM? 

can you run the upgrade.bat", which is typically located in the SEPM bin folder:

"C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\

bspore's picture

When I run a repair it completes successfully. It is when the Management Server Configuration Wizard runs is where it fails. It fails after I enter in the database credentials and click Next. It says the databse is being created and intialized and copying data folder . . . Then I get the error Failed to copy data to folder C:\Program Files(x86)\Symantec Endpoint Protection Manager\data, not enough free disk space.

Rafeeq's picture

enable the loggin to finest and past the scm and catalina.out file

if you could zip all the logs it would be great

http://www.symantec.com/business/support/index?pag...

bspore's picture

I enabled logging to finest and have attached the logs.

AttachmentSize
logs.zip 8.04 KB
bspore's picture

I updated the SEPM to version 12.1.4a to see if that would fix the issue but it did not.

Rafeeq's picture

This is what I saw in the catalina.out

### Error updating database.  Cause: org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Network error IOException: Connection refused: connect)
### The error may exist in file [C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps_ws\sepm\WEB-INF\classes\com\symantec\sepm\server\module\dashboard\dashboard_mapper_ibatis.xml]
its not able to connect to the DB.
 
are you able to start the sepm service from services.msc? is it already started?
 
Did you get connection successful when u ran the odbc configuration I linked earlier?
 
try this
http://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=TECH181655
 
bspore's picture

The SEPM service is starting just fine.

I did get a Test Completed Successfully when I test the ODBC connection.

Rafeeq's picture

Check these permisions on your SEM5.db

http://www.symantec.com/business/support/index?pag...

whats the size of your SEM5.db..

there was a thread where someone said, the free space should be 3 times the size of the DB. I dont know how much its true..

Rafeeq's picture

RSAKA managed to fix the same issue after adding systemdsn in odbc ,wondering why its not happening on your case

https://www-secure.symantec.com/connect/forums/fai...

bspore's picture

I ended up rebuilding my SEPM server. Now I am experiencing a different issue with LiveUPdate not working properly but that is a different issue.

SOLUTION