Migration to Endpoint Protection Manager 12.1.4 (RU4) MP1 fails when size of filegroup FG_CONTENT is greater than 30000 MB


Article ID: 159154


Updated On:


Endpoint Protection


Migration of the Symantec Endpoint Protection Manager (SEPM) from 12.1 RU4 to 12.1 RU4 MP1 fails when the size of the filegroup FG_CONTENT is greater than 30000MB, and the filegroup's maximum file size is set to Unlimited.

The following error can be seen in Upgrade-0.log:

  • [date/time] THREAD 28 INFO: Database Schema has been upgraded.
  • [date/time] THREAD 28 INFO: Upgrading from 12 RU4 to 12 RU4MP1
  • [date/time] THREAD 28 INFO: UpgradeStep >> checkUpgradeStatus.
  • [date/time] THREAD 28 INFO: Start to increase CONTENT DB file maximum size.
  • [date/time] THREAD 28 INFO: The current size is: 0MB.
  • [date/time] THREAD 28 SEVERE: java.sql.SQLException: MODIFY FILE failed. Size is greater than MAXSIZE.
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
  • [date/time] THREAD 28 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1166)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.db.util.DbUtil.updateDBFileMaxSize(DbUtil.java:1054)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.Schema12RU4To12RU4MP1.increaseContentDBFileSize(Schema12RU4To12RU4MP1.java:77)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.Schema12RU4To12RU4MP1.upgrade(Schema12RU4To12RU4MP1.java:51)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.SchemaUpgrade.execute(SchemaUpgrade.java:84)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:1061)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:127)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:138)
  • [date/time] THREAD 28 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
  • [date/time] THREAD 28 SEVERE: at java.lang.Thread.run(Thread.java:744)


To work around this issue:

  1. Stop the following services:
    • Symantec Endpoint Protection Manager
    • Symantec Endpoint Protection Manager Webserver
  2. Login to the SQL Management Studio.
  3. Right-click the SEPM database (default name: sem5).
  4. Click Properties.
  5. Click Files.
  6. Next to the Filegroup FG_CONTENT, note the value in Initial Size (MB).
  7. Under "Autogrowth" or "Autogrowth/Maxsize" click the button next to the Filegroup FG_CONTENT.
  8. Click Limited to (MB).
  9. Enter a value to the right of Limited to (MB) which is 10,000 larger than the Initial Size (MB) value you noted earlier. For example, if Initial Size (MB) was 35000, enter 45000.
  10. Click OK.
  11. Click OK. It may take several minutes for this setting to be applied.
  12. On the SEPM computer, launch Upgrade.bat (default location: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin).
  13. When the wizard opens, click Next to attempt migration again.

After following these steps and the SEPM has been upgraded, you can change the Maximum File Size setting back to Unlimited.