crudlet.org

Home > Symantec Endpoint > Symantec Endpoint 11 Unable To Communicate With The Reporting Component

Symantec Endpoint 11 Unable To Communicate With The Reporting Component

Nach erheblichem ausprobieren habe ich dann schlussendlich die Lösung gefunden. o Verify that the "Symantec Embedded Database" service is running and that the dbsrv9.exe process is listening on TCP port 2638. 1. Trenches, and more. On the Network tab ensure TCP/IP is checked. 8. Source

Another thought would be that something like the XP firewall settings are blocking a port.Below copied from Symantec:The Symantec Policy Manager uses two web servers: Internet Information Services (IIS) and Tomcat. 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 log off SEPM, go to start, control panel, administrative tools, ODBC, system DNS, config, client configuration and uncheck dinamically determinate port, write 1433 below, make acept, make test success to finish If the SPC_ prefix is not included, you will receive the error: "Database Server Not Found") On the Login tab, supply the user ID and password for the Symantec Embedded Database https://www.symantec.com/connect/forums/sepm-unable-communicate-reporting-component-1

When attempting to load its properties from the control panel i get the message "Windows firewall cannot run because another program or service is that might use the network address translation From accounting app support through to highly available solutions for accounting firms we've got it covered. 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 To do this do the following: Go to %systemroot%\Windows\SysWoW64 folder (Example - Click Start -> Run -> C:\Windows\Syswow64 and click on OK) Locate Odbcad32.exe & double click on the file Click

PST on Dec. 30th with the primary email address on your Experts Exchange account and tell us about yourself and your experience. This article details the known solutions or troubleshooting methods. The toolkit is available from Microsoft at: http://www.microsoft.com/downloads/details.aspx?familyid=9BFA49BC-376B-4A54-95AA-73C9156706E7&displaylang=en Verify the DefaultAppPool identity is set to 'Network Service' Open the IIS Administrator Expand > Application Pools Right-click DefaultAppPool and select Verify that Enable Anonymous Access is checked. 7.

By the local securiyt policy on the SEPM server do you mean the console or the actual servers group policy? So you have to do the best with what you got. :) 0 Message Active today Author Comment by:tobe1424 ID: 352430522011-03-29 Thanks for the help. Windows 7 Install on a Toshiba Tecra S1 M1.7GHz 51... https://www.symantec.com/connect/forums/sepm-unable-communicate-reporting-component I have the ports configured to port 80 Thanks, Rob 0 Message Active today Author Comment by:tobe1424 ID: 353246592011-04-05 Anyone? 0 LVL 12 Overall: Level 12 Anti-Virus Apps 11

It generates an output file for Symantec support. Lots covered from Greenfield to Migration. That's why DefaultAppPool in IIS needed to be updated. Then check out Philip's Guide.

Thanks, Rob 0 Message Active today Author Comment by:tobe1424 ID: 353928402011-04-14 I need to get this resolved in order to move on to the next project. To check the port being used... 1. Double-click on Adjust memory Quotas for a Process and Replace a process-level token and verify that the "NETWORK SERVICE" is listed. SBS 2003 to SBS 2008 Migration Begins Tomorrow OWN Off-Site Backup Experiences Off-Site Backup Services with OWN With Windows 7 and SharePoint, Who Needs A VPN?

The Stats Are In on the Presentation - Needs Focus... this contact form Need to ask a question: E-mail: Blog Question. Click Start> Run. 2. I check a few things out in IIS like the KB's mentioned ie make sure anonymous user was checked..

Is that the port you're using? Check that Password Strength Tool BES 5.0 and SBS 2008 - No Go For Now BES 5.0 on SBS 2008 - So far a no go … SBS 2008 - Symantec If you're new to the TechRepublic Forums, please read our TechRepublic Forums FAQ. have a peek here It first states: -Verify the defaultapppool identity is set to network service Step 5 states the following: -If Network Service is listed then try adding the Local System.

Right-click DefaultAppPool and select Properties 4. Please attach the file here so I can review it. I was able to remove to errors relating to the network and local service.

Join Now For immediate help use Live now!

I need this solved so I can move on to other things. Double click on the 'Replace a process level token' policy and confirm LOCAL SERVICE and NETWORK SERVICE are listed. 4. I am not sure what else to check. The application, particularly the management components, has been buggy and, although it's in a "good phase" currently, it still never hurts to be sure you have the most recent updates. 0

In the Windows Control Panel, open Data Sources (ODBC). 2. Run dbvalidator.bat in the \Program Files\Symantec\Symantec Endpoint Protection Manager\Tools folder and post back results. EnergizeIT Windows 7 Install Fest - Edmonton Windows 7 XP Pro Mode - Requires a Physical Box wi... ► April (53) ► March (48) ► February (33) ► January (38) ► Check This Out Refreshing the console may help temporarily but it is only a workaround and not a solution.

The console is sluggish. 0 Message Active today Author Comment by:tobe1424 ID: 351932592011-03-22 Like mentioned before, I now log in and don't receive the message. Nach der Installation von Symantec Endpoint Protection Manager (wieso ist der Produktname so lang?) habe ich den Manager gestartet. 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. Covered by US Patent.

Restart the IIS Admin service to update any changes Verify Authentication and Access Control. Enter the IP address of the computer that runs Symantec Endpoint Protection Manager into the TCP/IP field. 9. Thanks, Rob 0 LVL 12 Overall: Level 12 Anti-Virus Apps 11 Anti-Spyware 1 Message Expert Comment by:jmlamb ID: 352017472011-03-23 It's not the SST that runs on 8014, but the Symantec If the version displayed here does not match the version installed with SEPM (step 7), then there is a problem (version mismatch).

after reseting the IIS. Education Services Maximize your product competency and validate technical knowledge to gain the most benefit from your IT investments. SBS 2008 Setup Checklist V1.2.0 Released SBS 2003 to 2008 Migration Stall - Event 1001 SBSS... Please advise.

Border