I have the same problem but I'm using the embedded database and I have no System DSN entries.

@swade
then add them manually

I really don't have time to go look up how to do that.  Maybe someone will be kind enough to explain it.

Edit: I found some instructions in this thread:

https://forums.symantec.com/syment/board/message?b...

However, my server isn't listed when adding the DSN.  The only driver installed is SQL, is the embedded database SQL?  How do you get the driver?  Why isn't any of this already installed?

Message Edited by swade on 06-26-2008 08:14 AM

If you're running a 64bit OS, you need to open the 32bit ODBC to view the SymantecDSN for the embedded database. 

I am running odbcad32.exe

That is the 32 bit ODBC, yes?

C:\Windows\SysWoW64\Odbcad32.exe

Thanks.

The good news is that I did find the DSN, and I noticed the login information was missing and all the other things as mentioned in the other link I provided above.

The bad news is that after doing this, I now cannot connect to the server AT ALL.

Failed to connect to the server

Make sure you put sem5 as the database name and dba as the user. 

Both settings are correct.  The database currently tests fine (for the first time).  I just can't access the server now when I use the manager (local or remote).

If you're able to successfully test the connection in ODBC but you can't login to the manager now, you could try to run the management server configuration again. 

I did run the Management Server Configuration Wizard again, and everything looked like it installed without any errors, but I still can't connect to the server.

I also restarted IIS, but still can't connect.

You may want to call in and open a case with Symantec then. 

Well I'm going to try removing the software and reinstalling first.

After that, yeah.  Joy.

Everything looks right in there per the instructions on the link above.  It doesn't appear that the reconfiguration changed any of the System DSN settings from what I'd modified them to.

Reinstalling doesn't help.  Additionally I am seeing this in the App Log:

Event Type:    Error
Event Source:    semsrv
Event Category:    None
Event ID:    4096
Date:        6/27/2008
Time:        7:56:31 AM
User:        N/A
Computer:    Server1
Description:
The Java Virtual Machine has exited with a code of -1, the service is being stopped.
 

Ok in a fit of desparation (because I just don't have time to sit on hold with any support) I reinstalled again except instead of using the default website I told the installer to create a custom one.

Not only did the SEM error go away, but my "unable to communicate with the reporting component" went away too.

Everything works fine now.

Go to  the  IIS manager  ,click your  server  ,select  default  smtp server  -properties.Make  sure that  the  no.of  connections  to  be  used  is  atleast  25.

click  OK.

I hade same problem with error "unable to communicate with the reporting component".

Problem was on 11.0.2020 and 11.0.3001.

Sollution> during Install SEPM was't configure ODBC driver in Windows Settings, after setup ODBC is SEPM working.

If you are having the issue "unable to communicate with the reporting component" when logging into the SEP console. Then I suggest you try the following.  

Data Sources ODBC --> System DSN --> (SymantecEndpointSecurityDSN) - Configure

Login Tab - dba / (password set when installing SEPM)

Databse Tab - <servername> Database name: <sem5> (i used embedded DB)

Network Tab: Tick TCP/IP: host=(ip of server)  

Once set go back to the Login tab and click Test Connection. Hopefully successful  

IIS - Set the DefaultAppPool to Predefined:LocalSystem 

Computer Management, IIS, Application Pools, DefaultAppPool, Right click properties

identity tab: Predefined <select Local System>  

Reset Permission on Reporting directory

locate your SEPM  “Inetpub\reporting” folder

open properties of Reporting, Security tab, Advanced Make sure the following accounts are available 

1. The account that IIS uses, in my case, IUSR_<servername> 

2. local System account (used above on the DefaultAppPool) 

3. I also have domain\administrators  

Tick "replace permission entries on all child objects.." Apply, then ok  

Make sure you are only doing this on the Reporting folder, doing on any of the rest will cause the SEPM service to automatic fail. with the eventlog error of "The Java Virtual Machine has exited with a code of -1, the service is being stopped."

restart IIS, cmd iisreset   

Good luck!

If you are like me and have had to remove SEPM and re-install you will need to use the syncdrop tool to update the communication settings on the SEP client.

Syncdrop tool is found on CD2

Log into SEPM

Clients

Select default group, Export Communication Settings, save file on network path.

In login script add the following line

\\network_path\SylinkDrop.exe -silent \\Network_path\MyCompany_DefaultGroup_sylink.xml

This will import the new setting and restart SEP when the user logs in. No reboots are required.