Endpoint Protection

Hello once again,

I am having some troubles and hope someone can walk me through getting this error removed. I receive it every time I log into the Protection Manager. I read a thread that was similar to this and I checked to see if the "Symantec Embedded Database" service is running and it is. The "dbsvr9.exe" process is listening on ports 2638 and 8005 according to netstat -b from the cmd prompt. However when I go into the System DSN tab, in Data Sources, there is nothing populated there. So what should my next step be? Thanks in advance!

Regards,
Keith

if its 64bit box you need to follow this document

How to work with Data Sources (ODBC) or ODBC connection in 64bit Windows OS

  http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008021900094548

once you fix the odbc the issue should be resolved

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

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

Thanks for the fast reply but now I get Connection failed: Unable to start database server when I try to test the connection. I put "sem5" for the server name, "dba" for username, and the password to log into the Protection Manager for the password. Any other suggestions?

Regards,
Keith

server name will the name of the server not FQDN but just server's name. 

I have similar problem on my replication partner but no solution till date . I am also waiting for the solution. have tried many things syggested by community members.

I've tried that (actual server name) as well with the same results... Anything else we could try?

Regards,
Keith

Try by repairing SEPM from add/remove programs

any errror is present in scm-server-0.log which is present in \program files\symantec\symantec end point protection manager\tomcat\logs?

From today:

2010-01-06 11:33:22 WebappLoader[]: Deploying class repositories to work directory C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\work\scm\localhost\_
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/jcommon-0.9.5.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jcommon-0.9.5.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/jfreechart-0.9.20.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jfreechart-0.9.20.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/jslic.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jslic.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-common-res.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-common-res.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-common.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-common.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-server-res.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-server-res.jar
2010-01-06 11:33:22 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-server.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-server.jar
2010-01-06 11:33:22 ContextConfig[]: Added certificates -> request attribute Valve
2010-01-06 11:33:22 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2010-01-06 11:33:22 StandardManager[]: Seeding of random number generator has been completed
2010-01-06 11:33:25 StandardWrapper[:default]: Loading container servlet default
2010-01-06 11:33:25 StandardWrapper[:invoker]: Loading container servlet invoker
2010-01-06 12:24:02 WebappLoader[]: Deploying class repositories to work directory C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\work\scm\localhost\_
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/jcommon-0.9.5.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jcommon-0.9.5.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/jfreechart-0.9.20.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jfreechart-0.9.20.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/jslic.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\jslic.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-common-res.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-common-res.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-common.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-common.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-server-res.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-server-res.jar
2010-01-06 12:24:02 WebappLoader[]: Deploy JAR /WEB-INF/lib/scm-server.jar to C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\webapps\scm\WEB-INF\lib\scm-server.jar
2010-01-06 12:24:02 ContextConfig[]: Added certificates -> request attribute Valve
2010-01-06 12:24:02 StandardManager[]: Seeding random number generator class java.security.SecureRandom
2010-01-06 12:24:02 StandardManager[]: Seeding of random number generator has been completed
2010-01-06 12:24:04 StandardWrapper[:default]: Loading container servlet default
2010-01-06 12:24:04 StandardWrapper[:invoker]: Loading container servlet invoker

check

1. Verify that the Symantec Embedded Database service is running and that the dbsrv9.exe process is listening on TCP port 2638
2. Test the ODBC connection.
3. Open Control Panel > Administrator Tools
4. Double click Data Sources (ODBC)
5. On the System DSN tab, double-click SymantecEndpointSecurityDSN
6. Go through the wizard to ensure the following settings:
   
   Name: SymantecEndpointSecurityDSN
   Description: <Anything>
   Server: Servername\InstanceName (Can be blank as it is localized, otherwise specify the default: sem5)
   Login ID: dba
   Password: <password>
   
7. Leave the defaults for the rest of the items and click Finish
8. Click Test Data Source , it should return "Success"
9. Click OK

the problem is in configuring ODBC
if we are successful we are done with the issue
how many nic cards on this box?

Weird... How do I fix this?

[sppsvc.exe]
 TCP    0.0.0.0:2638           MGAV01:0               LISTENING
[dbsrv9.exe]
 TCP    0.0.0.0:3389           MGAV01:0               LISTENING
 TermService

It's listening on the wrong port :(

Don't understand but it looks like it might be running on the right port after all. So I guess I'm stuck again.

Active Connections


 [sppsvc.exe]
  TCP    0.0.0.0:2638           MGAV01:0               LISTENING
 [dbsrv9.exe]
  TCP    0.0.0.0:3389           MGAV01:0               LISTENING
  TermService
 [dbsrv9.exe]
  TCP    127.0.0.1:2638         MGAV01:50190           ESTABLISHED
 [dbsrv9.exe]
  TCP    127.0.0.1:2638         MGAV01:50192           ESTABLISHED
 [dbsrv9.exe]
  TCP    127.0.0.1:2638         MGAV01:50227           ESTABLISHED
 [dbsrv9.exe]
  TCP    127.0.0.1:2638         MGAV01:50241           ESTABLISHED
 [dbsrv9.exe]
  TCP    127.0.0.1:8005         MGAV01:0               LISTENING

Try by restarting the server

do u have any other application running on port 2638?
http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/fbeaa0c45477d3d8652573d40062f2b5?OpenDocument

change it if so,

remember, fixing odbc fixes the issue :)

Restarted. Still does not work. I noticed something. At the login screen for Protection Manager, it says "Server: localhost:8443". Does that sound right?

Regards,
Keith

That is ok
But more important is dbsrv9.exe listens on which port
Are you able to start your database service?

Symantec Embedded Database? Yes, it's started but I still get a connection failed in the Data Sources window :(

you have two dbsrv.exe
try to stop one and log in it should work fne

disbale the application running on 8005 and run symantec endpoint

Just one dbsrv9.exe running... And even after I kill that process and try to log in, I get the same error message about the reporting component.

open cmd prompt
type netstat -b
do u see just symantec using port 2638 ?
use netstat /? to know the executables

Looks fine to me, yet it doesnt work.

[dbsrv9.exe]
 TCP    127.0.0.1:2638         MGAV01:49618           ESTABLISHED
[dbsrv9.exe]
 TCP    127.0.0.1:2638         MGAV01:49619           ESTABLISHED
[dbsrv9.exe]
 TCP    127.0.0.1:2638         MGAV01:49620           ESTABLISHED
[dbsrv9.exe]
 TCP    127.0.0.1:49617        MGAV01:2638            ESTABLISHED

 what is this/

[dbsrv9.exe]
 TCP    127.0.0.1:49617        MGAV01:2638            ESTABLISHED

Thats the dbsrv9.exe making a connection from to the server on port 2638 I suppose... Like an incoming/outgoing

Hi Swagger,

Try this and let us know if it helps... First thing, if your SEPM version is RU5, you need to specify SPC_ in frontof the server name in the database tab of ODBC(For some reason, it has been changed with RU5) ...  Even after that if is not helping, try this...

1. stop the database service.
2. make sure you dont have any dbsrv9.exe running in the task manager.
3 Goto manager\asa\win32 and launchdbsrv9.exe
4. browse to the sem5.db under manager\db
(note: there will be another sem5.db under ASA folder... care should be aken that you point to right database)
5. specify the hostname of the server and click on Ok... It would intiate a connection with the database..
6. Once its succesful, it will automatically minimize itself to system tray
7. now goto odbc and provide the same info.. i.e server name and database..
8. If things are right, connection shld be succesful...

Also, like someone previously asked, do you have multiple nic?

To check the port used by dbsrv9.exe goto HKLM\System\CurrentControlSet\Services\ASAny_sem5 \parameters


Cheers,
Visu.

change the dba  port to different port number and try odbc connection

how is the port changed on an embedded database?
http://service1.symantec.com/SUPPORT/ent-security.nsf/2326c6a13572aeb788257363002b62aa/fbeaa0c45477d3d8652573d40062f2b5?OpenDocument 

Hello Visu,

Thanks for the help and I tried everything you suggested, yet it still did not work for me...

Below is the export from the service, it is using 2638 as it should be.

-c 64m -ch 64m -gp 8192 -gc 30 -gr 30 -o "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\out.log" -oe "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\err.log" -os 1m -gn 80 -n MGAV01 "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" -n sem5 -sb 0 -x tcpip(localonly=yes;port=2638)

Regards,
Keith

Rafeeq,

Performed all steps in the link you posted and still get the "Unable to communicate with the reporting component"  error :(

Regards,
Keith

in the odbc tab

LINKS=tcpip(HOST=ip_address;PORT=2638) 

try if thats connecting 

Connection failed: TCPIP requires a server name... Tried putting in localhost and server name as well and still nothing

dont put local host, i dont think it wil resolve the name, can you please post the screen shot of the odbc connection, i think we are missing something here, post a screen shot plz 

Well, it works now... But I'm not exactly sure why...

I went back into the ODBC wizard and nothing was populated as far as login credentials and server name. So I entered in the server name and entered in the credentials... Under the Network tab, HOST=MGAV01;PORT=2639 was filled in next to TCPIP and I hit test connection and it worked! Not sure if it was the line in the Network tab that did it or what but thanks so much to everyone. I'll have a new question here in the coming days on policies!

Regards,
Keith

Thats a great news, it was ODBC as i guessed. 

still not working . I have the same problem . difference is my server is a replication partner only. clients are not mangaed from here