Home > Symantec Error > Symantec Error Unable To Communicate With The Reporting Component

Symantec Error Unable To Communicate With The Reporting Component

HELP! -Thanks 0 LVL 12 Overall: Level 12 Anti-Virus Apps 11 Anti-Spyware 1 Message Expert Comment by:jmlamb ID: 353550972011-04-08 SST is the SEP Support Tool you've been running to discover A DRAC, Or Any Other Remote Management Tool Will O... Create a SymAccount now!' "Unable to communicate with the reporting component" error when logging in to the Symantec Endpoint Protection Manager and Service Unavailable (HTTP 503) in the Reporting web page Need to ask a question: E-mail: Blog Question. navigate here

I've rung a number of times for quite advanced problems, having eliminated the obvious, to be told - uninstall & reinstall. Java can be a memory hog and competing with Active Directory isn't going to leave much system resources depending on the hardware being used. If computer name does not work, try the IP number or fully qualified domain name. (Version 11.0.5002.333 or newer, add SPC_ to the beginning of the server name. If you need to add them, restart the SEPM service afterwards. 0 Free Trending Threat Insights Every Day Promoted by Recorded Future Enhance your security with threat intelligence from the web.

SBS Migration DNS and Shaw's Customer Phone Suppor... Ever since I came into the company this has been an issue that no one has tackled. Privacy Policy Site Map Support Terms of Use TechRepublic Search GO CXO Cloud Big Data Security Innovation More Software Data Centers Networking Startups Tech & Work All Topics Sections: Photos Videos

From accounting app support through to highly available solutions for accounting firms we've got it covered. NEED HELP? The default location for the logs is C:\Windows\System32\LogFiles\W3SVC1 In the IIS manager, right click each site where you wish to have the logs, such as Reporting and Secars, and select Log Submit a Threat Submit a suspected infected fileto Symantec.

For an embedded (Sybase) database Verify that the Symantec Embedded Database service is running and that the dbsrv9.exe process is listening on TCP port 2638 Test the ODBC connection. PNY Gets A Little Plug On Intel's Server Configura... Right-click DefaultAppPool and select Properties 4. Microsoft Small Business Specialists Co-Author: SBS 2008 Blueprint Book *All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

On the Network tab ensure TCP/IP is checked. 8. Heartland Payment Systems, Visa, and PCI Complianc... This article details the known solutions or troubleshooting methods. Select Directory Security 5.

Is that the port you're using? In IIS Admin, do you have a Symantec Web Server web site, or is it configured under the Default web site? Open the local security policy on the SEPM server (under Admin Tools) and check that privilege. No sponsorship or monies have been paid to MPECS Inc.

To fix that you would have to reinstall the SEPM software and choose the custom website option that defaults to port 8014. 0 Message Active today Author Comment by:tobe1424 ID: check over here Follow the steps below: Exit SEPM Click Start > Run. I mean, truly dire.It says something that the IT director of Asus was posting on the Symantec Endpoint forums at the time!At the moment, Kaspersky or AVG AV seem to do Loopback address disabled Reporting pages may fail to appear if loopback addresses are disabled on the computer.

If that is not possible you can: Use pcAnywhere Use the switch that Microsoft recommends to shadow a console session within an RDP session. IIS uses port 80/443 and Tomcat uses port 9090/8443. PowerShell Guide $395 PowerShell Guide - 1 Year $695 Get 1 Year of PoSh Updates 2015-11-09: Lots going on with Windows Server vNext. http://mmonoplayer.com/symantec-error/symantec-error-reporting-not-working.html Submit a False Positive Report a suspected erroneous detection (false positive).

Information for: Enterprise Small Business Consumer (Norton) Partners Our Offerings: Products Products A-Z Services Solutions Connect with us: Support

If you're new to the TechRepublic Forums, please read our TechRepublic Forums FAQ. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items… CodeTwo Exchange Outlook Email Software How to Make Price of Configurable Product its working, but its works only one time.

Make a back up of the PHP folder that is not the SEPM version.

A browser page describing the PHP status should display. Add the following line to the file: xxx.xxx.xxx.xx localhost # to log on to reporting functions (where xxx.xxx.xxx.xx is the IP address of your computer) Save and close The version displayed by the php command and the version of the file should match. Please check the appropriate setting if you are utilizing Authenticated Access.

Restart the IIS Admin service to update any changes Verify Authentication and Access Control. Don't have a SymAccount? Intel System Defense Utility Is Not Available? weblink Whether it's 8014, 80 or something entirely different doesn't matter as long as your clients know how to communicate with the SEPM.

What do you guys think? On the ODBC tab, click Test Connection and ensure it states Connection successful 10. Log into SEPM again. Again, I ran the test and connection failed.

So in IIS in the defaultapppool identity tab. Copy the 'phpinfo.php' file to: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting Open the web browser to: http://LocalHost:8014/Reporting/phpinfo.php. Is that sufficient or do you think this can be causing these types of behaviors? Start -> Run -> odbcad32.exe [Enter] UAC: Continue System DSN tab: ODBC: Leave Login: User ID: DBA Password: Same as your SEP Admin Database: Server Name: MY-SBS Network: TCP/IP: SBS IP

It's time I suppose. :) Topic Categories Business Opportunity Business Principles Pearls Clusters Storage Spaces Direct S2D Hyper-V Hyper-V Setup Scale-Out File Server Intel Server Systems System Builder Tips Errors Fixed No Yes logo-symantec-dark-source Loading Your Community Experience Symantec Connect You will need to enable Javascript in your browser to access this site. © 2016 MPECS Inc. In this case, do the following: Close the command prompt. Please attach the file here so I can review it.

To check if there is a version conflict with the version of PHP that SEPM is using: Open a blank document with a text editor (Notepad for example.) Copy/paste the following Check the IIS Configuration Verify IIS permissions and account(s) rights are set correctly Use the Microsoft IIS Diagnostics Toolkit to identify all the rights and permissions on the accounts. Any chance the drive you have the SEPM installed on is near capacity? Regards, Robert 0 LVL 12 Overall: Level 12 Anti-Virus Apps 11 Anti-Spyware 1 Message Expert Comment by:jmlamb ID: 351851732011-03-21 No, 5GB is good.

Verify user rights. For example, on computers running Windows XP, do the following: Change the directory to the location of your hosts file. Close Login Didn't find the article you were looking for? Microsoft purposely denies access to these settings.

On the System DSN tab click Symantec Endpoint Security DSN. 3. Copy the file 'phpinfo.php' to C:\ Click Start > Run. Click Start> Run. 2.