Error "failed to save database" while Symantec Endpoint Protection Manager's Management Server Configuration Wizard is creating a new database.

Article:TECH104282  |  Created: 2008-01-26  |  Updated: 2008-01-11  |  Article URL http://www.symantec.com/docs/TECH104282
Article Type
Technical Solution


Issue



You get an error "failed to save database" while using Symantec Endpoint Protection Manager's Management Server Configuration Wizard to create a new database.

Symptoms
- You receive the error as shown in the screen shot below:



- sem5 user and database are actually created, but the database has no tables.

- install_log.err in tomcat logs folder (c:\program files\symantec\symantec endpoint manager\tomcat\logs by default) contains messages similar to the following:
-----------------------
java.sql.SQLException: Invalid column name 'type'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:364)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2754)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2195)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:620)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:372)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeQuery(JtdsStatement.java:1176)
at com.sygate.scm.install.ui.MainFrame.querySesmContentCatalog(MainFrame.java:3967)
at com.sygate.scm.install.ui.MainFrame.configureDB(MainFrame.java:770)
at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:594)
at com.sygate.scm.install.ui.MainFrame.access$200(MainFrame.java:182)
at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:385)
at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
at java.lang.Thread.run(Thread.java:595)
------------------------


Cause



This is caused by SQL server instance using a collation that's not supported by Symantec Endpoint Protection Manager (SEPM). SEPM requires a case-insensitive SQL collation.

Solution




To determine which collation the SQL server instance is using

- For SQL 2005, perform the following steps:
1. Launch Microsoft SQL Server Management Studio and connect to the server instance where you are creating SEPM database.
2. Right click the server instance, click Properties.
3. Note Server Collation value in General page. If the value doesn't contain "_CI_", then it's not a case-insensitive collation.

- For SQL 2000, perform the following steps:
1. Launch SQL Server Enterprise Manager and locate the server instance where you are creating SEPM database.
2. Right click the server instance, click Properties.
3. Note Server collation value under General tab

Please change SQL collation to a case-insensitive one to resolve this issue. Please refer to Microsoft SQL documentations on how to perform this task.


References
- Installation Guide for Symantec Endpoint Protection and Symantec Network Access Control, section "Installing Symantec Endpoint Protection Manager with a Microsoft SQL database" starting from page 70

- Microsoft technet article "selecting a SQL collation"




Legacy ID



2008022713482848


Article URL http://www.symantec.com/docs/TECH104282


Terms of use for this information are found in Legal Notices