Endpoint Protection Manager Configuration Error on Windows 2008 R2 with SQL 2008 R2

Updated: 13 Dec 2010 | 22 comments

Venik

0 0 Votes

This issue has been solved. See solution.

I am unable to complete the Symantec EndPoint Protection Configuration Wizard due to errors:

Here are the configurations for the the last three wizard screens before the errors appear:

Database Type: Microsoft SQL Server

Create a new database

Database Server: ServerName\InstanceName
SQL Server Port: 1433
Database Name: sem5
Authentication: Windows Authentication
User: sem
Password: ***************
Confirm Password: ***************
SQL Client Folder: C:\Program Files\Microsoft SQL Server\100\Tools\Binn
Database data folder:

If I click the the Default button next to the Database data folder field, this error appears:

Failed to connect to database

If I specify a data folder C:\Program Files\Microsoft SQL Server\MSSQL10_50.InstanceName\MSSQL\DATA then this error appears:

Error 11501: Unable to create the database for Symantec Enpoint Protection Manager. Please click here for more information.

I've already searched the support site and forums for resolution to these error messages. No previous posts applied or resolved the issues.

The Installation documentation (if you can call it that) equivocates on if the "user" account should already exist. I tried installing under two scenarios: account exist and account not exist. Under the account exist scenario, the sem account had local admin rights and was also a login account with sysadmin rights in the SQL Serve Management Studio.

Server Notes:

Windows 2008 R2 with SQL 2008 R2 Installed
Symantec_Endpoint_Protection_11.0.6_MP2_Trialware_Xplat_EN
Workgroup (not part of a domain)
Using Remote Desktop to connect to server (since it is in another state)
Windows Firewall Enabled (corporate policy)
Configured Windows Firewall to Allow SQL Exception (see http://support.microsoft.com/kb/968872 )
Configured SQL to enable TCP/IP for InstanceName on port 1433

Discussion Filed Under:

Security, Endpoint Protection (AntiVirus) - 11.x, Endpoint Protection (AntiVirus), Configuring, Error messages, Installing, SQL, Windows

Comments RSS Feed

Comments

Dec

2010

0 Votes 0

Rafeeq

hi

have you installed the sql client?

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

Dec

2010

0 Votes 0

Venik

Microsoft SQL Server Native

Microsoft SQL Server Native Client 10.0 is installed when you install SQL Server 2008 R2 or the SQL Server tools. (see http://msdn.microsoft.com/en-us/library/ms131321.aspx)

And I installed the server tools.

Dec

2010

0 Votes 0

AravindKM

Are you able to login to SQL

Are you able to login to SQL server from SEPM server using the SQL client which is present in SEPM ?

Try by using SQL authentication.....

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Dec

2010

0 Votes 0

Venik

I'm not sure if this is

I'm not sure if this is answering your question, but I can log in to the SQL Server Management using Windows Authencation. When i instlaled, SQL 2008 R2 I used Windows Authentication.

Also I don't know what you mean by:

Are you able to login to SQL server from SEPM server using the SQL client which is present in SEPM ?

The SQL Server and the SEPM are the same server. Also the Management Console was installed via SQL, not the SEPM. Is there another client instlaled? If so how can I access it?

Dec

2010

0 Votes 0

Prashant Bharadwaj

Symantec Employee

To my best knowledge, SEP

To my best knowledge, SEP Manager do not support database on SQL Server 2008 R2. It should install well with SQL Server 2008 verions.

Just to be sure, may you please run a pre-install check with the SEP tool?

Please download the tool from the link below,

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

Prashant Bharadwaj, CEH, MCTS Windows Server 2008 Active Directory, Configuration, SCS Symantec Endpoint Protection 11.0

Dec

2010

0 Votes 0

Venik

Ran the tool and it seemed

Ran the tool and it seemed successful. Here the results:

Error

Unable to communicate with the reporting component after logging to the Symantec Endpoint Protection Manager

Tests Error The user identity for the DefaultAppPool is set to User in UserNameWAM. It should be set to Network Service or Local System

Subcategory Ports
Click for more -> Which communication ports does the Symantec Endpoint Protection Manager 11.x use?

Tests
Error No applications are using Tomcat's configured port of '8005' with a state of 'Listen'
Error No applications are using Remote Console Logon's configured port of '9090' with a state of 'Listen'

Seems like neither of these should prohibit a SQL connection/DB creation.

Should I attach the full data report?

Dec

2010

0 Votes 0

Pawel Lakomski

Accredited

Certified

It is not supported but onthe

It is not supported but onthe other hand I see no reason why it should not install correctly...

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

Dec

2010

1 Vote -1

Pawel Lakomski

Accredited

Certified

User: sem has got all

User: sem has got all necessary rights and permissions to create a DB?

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

Dec

2010

0 Votes 0

Venik

The 'sem' account has

The 'sem' account has 'sysadmin' rights in SQL. Is that sufficient?

Dec

2010

0 Votes 0

Vikram Kumar-SAV to SEP

Symantec Employee

Accredited

Test ODBC Connection For an

Test ODBC Connection

1. Verify the following:
  - You specified a named instance during installation and configuration. For example: \\<server name>\<instance name>
  - The SQL Server is running and properly configured
  - The network connections between Symantec Endpoint Protection Manager and the SQL database.
2. Test the ODBC connection.
  1. Open Control Panel > Administrator Tools
  2. Double click Data Sources (ODBC)
  3. On the System DSN tab, double-click SymantecEndpointSecurityDSN
  4. 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 , it should return "Success"
  7. Click OK

VMWARE-- SEP 12.1 vs McAfee vs Trend Micro

Dec

2010

0 Votes 0

Venik

ODBC Connection test was

ODBC Connection test was succcessful.

Dec

2010

0 Votes 0

Vikram Kumar-SAV to SEP

Symantec Employee

Accredited

Check this Article

Check this Article once

http://www.symantec.com/business/support/index?page=content&id=TECH96451

VMWARE-- SEP 12.1 vs McAfee vs Trend Micro

Dec

2010

0 Votes 0

Venik

This article was nearly

This article was nearly identical to the Installation Guide (which I initially followed). I double checked all the settings and they were all configured appropriately. I still get the errors.

Dec

2010

0 Votes 0

Pawel Lakomski

Accredited

Certified

Could you pplease paste here

Could you pplease paste here the log:

\Symantec Endpoint Protection Manager\tomcat\logs\catalina.out

please? I suspect it is realted to Java-SQL exception.

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

Dec

2010

0 Votes 0

Venik

The only logs i see in

I don't see a log titled Catalina.out.

The only logs i see in "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\logs" are

backup.err

java.sql.SQLException: Login failed for user 'sem5'.
   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.login(TdsCore.java:591)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:335)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.tools.util.Utility.getConnection(Utility.java:117)
   at com.sygate.scm.tools.DatabaseFrame.getLocalSite(DatabaseFrame.java:545)
   at com.sygate.scm.tools.DatabaseFrame.getBackupButton(DatabaseFrame.java:189)
   at com.sygate.scm.tools.DatabaseFrame.getActionsPanel(DatabaseFrame.java:398)
   at com.sygate.scm.tools.DatabaseFrame.initialize(DatabaseFrame.java:152)
   at com.sygate.scm.tools.DatabaseFrame.<init>(DatabaseFrame.java:137)
   at com.sygate.scm.tools.DatabaseFrame.main(DatabaseFrame.java:1277)

install_log.err

java.sql.SQLException: Network error IOException: Connection refused: connect
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:371)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.btnLoadPath_actionPerformed(SqlPropPanel.java:1119)
   at com.sygate.scm.install.ui.SqlPropPanel.access$200(SqlPropPanel.java:53)
   at com.sygate.scm.install.ui.SqlPropPanel$2.actionPerformed(SqlPropPanel.java:183)
   at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6263)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
   at java.awt.Component.processEvent(Component.java:6028)
   at java.awt.Container.processEvent(Container.java:2041)
   at java.awt.Component.dispatchEventImpl(Component.java:4630)
   at java.awt.Container.dispatchEventImpl(Container.java:2099)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
   at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
   at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
   at java.awt.Container.dispatchEventImpl(Container.java:2085)
   at java.awt.Window.dispatchEventImpl(Window.java:2475)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:275)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:300)
   ... 32 more
java.sql.SQLException: Network error IOException: Connection refused: connect
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:371)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.checkDBConnection(SqlPropPanel.java:972)
   at com.sygate.scm.install.ui.SqlPropPanel.getNextStage(SqlPropPanel.java:538)
   at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:762)
   at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:183)
   at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:617)
   at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
   at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:275)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:300)
   ... 11 more
SqlPropPanel >> CheckDBConnection > Fail to connect to database. Vendor's error code is [0], SEPM's error code is [11501]. Error message is [Network error IOException: Connection refused: connect].
URL link: ["http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.6200.754&language=english&module=Console&error=11501&build=symantec_ent"]
java.sql.SQLException: Network error IOException: Connection refused: connect
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:371)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.btnLoadPath_actionPerformed(SqlPropPanel.java:1119)
   at com.sygate.scm.install.ui.SqlPropPanel.access$200(SqlPropPanel.java:53)
   at com.sygate.scm.install.ui.SqlPropPanel$2.actionPerformed(SqlPropPanel.java:183)
   at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6263)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
   at java.awt.Component.processEvent(Component.java:6028)
   at java.awt.Container.processEvent(Container.java:2041)
   at java.awt.Component.dispatchEventImpl(Component.java:4630)
   at java.awt.Container.dispatchEventImpl(Container.java:2099)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
   at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
   at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
   at java.awt.Container.dispatchEventImpl(Container.java:2085)
   at java.awt.Window.dispatchEventImpl(Window.java:2475)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:275)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:300)
   ... 32 more
java.sql.SQLException: Network error IOException: Connection refused: connect
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:371)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.checkDBConnection(SqlPropPanel.java:972)
   at com.sygate.scm.install.ui.SqlPropPanel.getNextStage(SqlPropPanel.java:538)
   at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:762)
   at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:183)
   at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:617)
   at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
   at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:275)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:300)
   ... 11 more
SqlPropPanel >> CheckDBConnection > Fail to connect to database. Vendor's error code is [0], SEPM's error code is [11501]. Error message is [Network error IOException: Connection refused: connect].
URL link: ["http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.6200.754&language=english&module=Console&error=11501&build=symantec_ent"]
java.sql.SQLException: Network error IOException: Connection refused: connect
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:371)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.btnLoadPath_actionPerformed(SqlPropPanel.java:1119)
   at com.sygate.scm.install.ui.SqlPropPanel.access$200(SqlPropPanel.java:53)
   at com.sygate.scm.install.ui.SqlPropPanel$2.actionPerformed(SqlPropPanel.java:183)
   at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
   at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318)
   at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
   at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
   at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
   at java.awt.Component.processMouseEvent(Component.java:6263)
   at javax.swing.JComponent.processMouseEvent(JComponent.java:3267)
   at java.awt.Component.processEvent(Component.java:6028)
   at java.awt.Container.processEvent(Container.java:2041)
   at java.awt.Component.dispatchEventImpl(Component.java:4630)
   at java.awt.Container.dispatchEventImpl(Container.java:2099)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4574)
   at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
   at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4168)
   at java.awt.Container.dispatchEventImpl(Container.java:2085)
   at java.awt.Window.dispatchEventImpl(Window.java:2475)
   at java.awt.Component.dispatchEvent(Component.java:4460)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.net.ConnectException: Connection refused: connect
   at java.net.PlainSocketImpl.socketConnect(Native Method)
   at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
   at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
   at java.net.Socket.connect(Socket.java:519)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:275)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:300)
   ... 32 more
java.sql.SQLException: Unable to get information from SQL Server: DCFBIWSUS01.
   at net.sourceforge.jtds.jdbc.MSSqlServerInfo.<init>(MSSqlServerInfo.java:91)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:259)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.checkDBConnection(SqlPropPanel.java:972)
   at com.sygate.scm.install.ui.SqlPropPanel.getNextStage(SqlPropPanel.java:538)
   at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:762)
   at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:183)
   at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:617)
   at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
   at java.lang.Thread.run(Thread.java:619)
SqlPropPanel >> CheckDBConnection > Fail to connect to database. Vendor's error code is [0], SEPM's error code is [11501]. Error message is [Unable to get information from SQL Server: DCFBIWSUS01.].
URL link: ["http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.6200.754&language=english&module=Console&error=11501&build=symantec_ent"]
java.sql.SQLException: Unable to get information from SQL Server: DCFBIWSUS01.
   at net.sourceforge.jtds.jdbc.MSSqlServerInfo.<init>(MSSqlServerInfo.java:91)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:259)
   at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
   at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:188)
   at java.sql.DriverManager.getConnection(DriverManager.java:582)
   at java.sql.DriverManager.getConnection(DriverManager.java:154)
   at com.sygate.scm.install.ui.SqlPropPanel.checkDBConnection(SqlPropPanel.java:972)
   at com.sygate.scm.install.ui.SqlPropPanel.getNextStage(SqlPropPanel.java:538)
   at com.sygate.scm.install.ui.MainFrame.nextBtnActionPerformed(MainFrame.java:762)
   at com.sygate.scm.install.ui.MainFrame.access$400(MainFrame.java:183)
   at com.sygate.scm.install.ui.MainFrame$3$1.construct(MainFrame.java:617)
   at com.sygate.scm.install.util.SwingWorker$2.run(SwingWorker.java:121)
   at java.lang.Thread.run(Thread.java:619)
SqlPropPanel >> CheckDBConnection > Fail to connect to database. Vendor's error code is [0], SEPM's error code is [11501]. Error message is [Unable to get information from SQL Server: DCFBIWSUS01.].
URL link: ["http://www.symantec.com/techsupp/servlet/ProductMessages?product=SAVCORP&version=11.0.6200.754&language=english&module=Console&error=11501&build=symantec_ent"]

install_log.out (empty/no data)

smbinstall_log.err (empty/no data)

smbinstall_log.out

Has valid SAV license
Has valid SNAC license
Saving welcome panel data ...
Saving welcome panel data...
Advanced option selected...
Saving company size panel data ...
Checking disk/memory size(Bytes) requirement...
Required disk/memory size(Bytes): 2147483648/268435456
Checking available disk/memory size(Bytes)...
Available disk/memory size(Bytes): 53536727040/12875354112
Saving companySize Panel user settings:
Company size: 3
Content revision number:3
DB backup number: 2
Starting db configuration process...

Dec

2010

0 Votes 0

AravindKM

Whether this is the

Whether this is the case?

Product corruption or failure appears during an installation or migration while using an improperly configured remote session

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Dec

2010

0 Votes 0

Venik

I ran MSInfo32.exe (Start >

I ran MSInfo32.exe (Start > Programs > Accessories > System Tools > System Information) and the User Name = "Not Available".

I've tried to connect to the console session, but haven't been able to. When I try to use TSCon.exe here is the output:

C:\Users\Administrator>tscon.exe 1
Could not connect sessionID 1 to this session, Error code 5023
Error [5023]:The group or resource is not in the correct state to perform the re
quested operation.

Despite this, I was able to install SQL and WSUS on the server. WSUS created a new SQL database just fine. It leads me to believe that this isn't the problem.

Dec

2010

0 Votes 0

Pawel Lakomski

Accredited

Certified

From the logs provided the

From the logs provided the error we have here is:

java.sql.SQLException: Network error IOException: Connection refused: connect

1. Please check again credentials provided when you create the database.

2. Try giving IP address instead of hostname of SQL server during installation.

3. Might be a port conflict. Maybe port 2638 on SQL server is alredy in use?

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

Dec

2010

0 Votes 0

Venik

Credential are correct. Using

Credential are correct.
Using the IP Address in place of the computer named yeilded the same results.
Port 2638? That's a port for SQL Anywhere. The port I'm using is 1433 for Microsoft SQL Server.

Dec

2010

0 Votes 0

Pawel Lakomski

Accredited

Certified

I am sorry, you are right

I am sorry, you are right about ports' numbers. Bu the port on SQL server is set as static, right?

Are you sure remote connection on the SQL server is enabled? The error means that the server is refusing the connection..

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

SOLUTION

Dec

2010

0 Votes 0

Venik

Remote connection wasn't

Remote connection wasn't enabled...

The "SQL Server Browser" service was disabled. So I changed the startup type to Automatic and started the service.

I also changed the Authetication Mode in the Microsoft SQL Server Management Studio for the Instance.

Log into the Microsoft SQL Server Management Studio and connect to the Instance.
Right Click the instance and select Properties.
Select the Security page..
Chagne Server Authentication to SQL Server and Windows Authenication mode.

Restart the Instance.

Now in the setup, I can get past the problem screen and create a system administrator account.

Thanks!!!!

Dec

2010

0 Votes 0

Pawel Lakomski

Accredited

Certified

Told ya ;) Actually my post

Told ya ;)

Actually my post should have been marked as solution but well... ;-) Glad that it works anyway :-)

Cheers,

Symantec Technical Specialist
Symantec Certified Specialist
MCP & MCITP
Cisco Certified Network Associate
Citrix Certified Administrator

Endpoint Protection Manager Configuration Error on Windows 2008 R2 with SQL 2008 R2

Comments

hi

Microsoft SQL Server Native

Are you able to login to SQL

I'm not sure if this is

To my best knowledge, SEP

Ran the tool and it seemed

It is not supported but onthe

User: sem has got all

The 'sem' account has

Test ODBC Connection For an

ODBC Connection test was

Check this Article

This article was nearly

Could you pplease paste here

The only logs i see in

Whether this is the

I ran MSInfo32.exe (Start >

From the logs provided the

Credential are correct. Using

I am sorry, you are right

Remote connection wasn't

Told ya ;) Actually my post

Links

Technical Support

Symantec.com

Store

Community Stats

Endpoint Protection Manager Configuration Error on Windows 2008 R2 with SQL 2008 R2

Comments

Would you like to reply?

Links

Technical Support

Symantec.com

Store

Community Stats