Osajus
asked on
Symantec Endpoint Unable to communicate with the reporting component
I have recently installed (and re-installed to attempt to fix) Symantec Endpoint on a Windows 2008 machine. I continue to receive the error:
Unable to communicate with the reporting component
I have tried both articles:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/32a9ac7fc1ff64b8882574fa007a946b?OpenDocument
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101711103548
I am able to connect to the ODBC database. I have tried other methods mentioned and am still getting the error. The only thing I can think that might be an issue is in IIS when testing authentication, I get this:
The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
I added the computer name (with the $), LOCAL SERVICE, and NETWORK SERVICE and still get this particular error as well as the Symantec error. I have tried to switch to a domain admin and password which solves the IIS error, but the Symantec error persists.
Thanks in advance
Unable to communicate with the reporting component
I have tried both articles:
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/32a9ac7fc1ff64b8882574fa007a946b?OpenDocument
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101711103548
I am able to connect to the ODBC database. I have tried other methods mentioned and am still getting the error. The only thing I can think that might be an issue is in IIS when testing authentication, I get this:
The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
I added the computer name (with the $), LOCAL SERVICE, and NETWORK SERVICE and still get this particular error as well as the Symantec error. I have tried to switch to a domain admin and password which solves the IIS error, but the Symantec error persists.
Thanks in advance
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
and you re ran the tool after you made all the changes?
can you post the logs?
thanks
can you post the logs?
thanks
ASKER
I did re-run the tool with the same result. I'm also having problems deploying and having the clients connecting to the server. I just uninstalled it from this server and moved it to another server where it appears to be going better.
Thanks for the suggestions
Thanks for the suggestions
ASKER