Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Unable to communicate with the reporting component (AGAIN)

Updated: 21 May 2010 | 11 comments
maskishe@gmail.com's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hi Everyone!!!

After new installation of SEPM 11.0.5002 we got "Unable to communicate with the reporting component " error on login to SEPM.

Details:
SEPM server OS: Windows 2008 R2
SQL server OS: Windows 2003 R2
SQL DB: MS SQL 2005 SP3 (cluster)
We use Windows Authentication to SQL on installation phase (it is critical for us).

We try all solutions which mention on following USLs but they didn't help
http://service1.symantec.com/SUPPORT/ent-security....
http://service1.symantec.com/SUPPORT/ent-security....

  After enabling PHP errors in php.ini  we get following error after login (http://localhost:8014/Reporting).
 

Fatal error: Uncaught exception 'com_exception' with message 
'<b>Source:</b> Microsoft OLE DB Provider for ODBC 
Drivers<br/><b>Description:</b> [Microsoft][ODBC SQL Server 
Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.' in 
C:\Program Files (x86)\Symantec\Symantec Endpoint Protection 
Manager\Inetpub\Reporting\Common\ado.php:39 Stack trace: #0 C:\Program Files 
(x86)\Symantec\Symantec Endpoint Protection 
Manager\Inetpub\Reporting\Common\ado.php(39): com->Open('DSN=SymantecEnd...', 
'-password', 'p??MW') #1 C:\Program Files (x86)\Symantec\Symantec Endpoint 
Protection Manager\Inetpub\Reporting\Common\connectdb.php(55): 
ado_connect(Object(com), 'SymantecEndpoin...', '-password', 'p??MW', NULL, NULL) 
#2 C:\Program Files (x86)\Symantec\Symantec Endpoint Protection 
Manager\Inetpub\Reporting\Login\curl_funcs.php(360): connectnav(Object(com)) #3 
C:\Program Files (x86)\Symantec\Symantec Endpoint Protection 
Manager\Inetpub\Reporting\Login\curl_funcs.php(98): 
doProcessLoginResponse('admin', '<?xml version="...' in C:\Program Files 
  (x86)\Symantec\Symantec Endpoint Protection 
  Manager\Inetpub\Reporting\Common\ado.php on line 39

Thanks,
MasK
 

Comments

clems's picture
19
Jan
2010
1 Vote +1
Login to vote

From this

From this log:

[Microsoft][ODBC SQL Server 
Driver][SQL Server]Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON

Check your ODBC configuration.

Symantec STS SEP 11

Rafeeq's picture
19
Jan
2010
0 Votes 0
Login to vote

hi

your password is :-password'
i think its not taking " - " charector
try changing your dba password and configure odbc
should work

Symantec Endpoint Protection: How to change the database password to a non complex password for use with the Management Server Reconfiguration Wizard

http://service1.symantec.com/support/ent-security.nsf/docid/2008011823355248
configure odbc
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101811190348

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

Visu310's picture
20
Jan
2010
0 Votes 0
Login to vote

Hey,

Quick question, was the ODBC connection succesful? ... Since you are using SQL... when you configure ODBC .. check the drop down box in the ODBC configuration...for server... It will have both the server name and the servername\instance .... choose the latter.... and then test the connectivity... :) ... Also, if you have changed the SQL ports to anything else than 1433, do mention it in client configuration.... and as far as the SQL client tools are installed, they need to be on the local drive... UNC may be accepted but wont work.... :)

Cheers,
Visu.

Cheers,
Visu.

I came, I saw, I err ;)

maskishe@gmail.com's picture
21
Jan
2010
0 Votes 0
Login to vote

Hello!

1) We don't use Embedded Database.
  2) ODBC connection is successful for SQL user.
3) SQL tools installed locally. bcp.exe connection to DB is successful. 

We don't  change SQL ports or use special characters in SQL user password (only letters and nums).

How can we change pass for SQL user with Windows Authentication?
Is there any guide which describe installation of SEPM with SQL 2005 DB and Windows Authentication?

I think the problem is in Windows Authentication. As I know it is a new feature for RU5.

Cheers,
MasK

no one knows me, even I.

AravindKM's picture
21
Jan
2010
0 Votes 0
Login to vote

From your SEPM try to login

From your SEPM try to login to SQL Server using the SQL client which is present in SEPM 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

maskishe@gmail.com's picture
21
Jan
2010
0 Votes 0
Login to vote

How can I do it? I'm able to

How can I do it?
I'm able to open "Admin" - "Local Site" - "SQL DB host". The page displays info about SQL server. 

no one knows me, even I.

AravindKM's picture
21
Jan
2010
0 Votes 0
Login to vote

In

In SEPM
Start---->programs---->microsoft sql 2005---->SQL server management studio
Server type database engine 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Visu310's picture
21
Jan
2010
0 Votes 0
Login to vote

Hey,

If its a problem with windows authentication, You will have to check whether the windows account you use has correct read /write permissions on the Symante'c DB .. also, kindly check if that user's 'member of' under AD users ... You should be a member of SQL admin groups... As, aravind said... Try to RDP into the SQL server and then to the SQL studio and check if you can access the symantec's db ...

Cheers,
Visu.

Cheers,
Visu.

I came, I saw, I err ;)

Rafeeq's picture
21
Jan
2010
0 Votes 0
Login to vote

hi

run the management server configuration wizard, i think its not taking your password, coz its not windows standard passwod policy, check that again

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

maskishe@gmail.com's picture
25
Jan
2010
0 Votes 0
Login to vote

We solve this problem after

We solve this problem after reinstalling SEPM with standart SQL account and switching to Windows Authentication account.

no one knows me, even I.