SEPM 11.0.5RU2 - Reporting/Login Error Server 2008 R2 and SQL 2008

[Migration User]

Hi all,
I am receiving the infamous "unable to connect to the reporting component" error on a new installation. I have installed SEPM Servers throughout our domain on different occasions, and have very seldom ever had an installation actually work after one attempt. They always seem to require some tweaking of IE, reinstallation of SEPM,etc but I have always been able to figure it out. 
Now however I am having a terrible time tying to get SEPM to run on a new server that is not as easily remedied.. 

Server Configuration 
Windows Server 2008 R2 Standard x64
SQL Server 2008 x64

Does anyone else have SEPM running on Server/SQL 2008??  I have followed the procedures to make SEPM run on Server 208, but still no go..

Any info is appreciated. Thanks

[Migration User]

Title: 'Unable to Communicate with Reporting Component error when logging into SEPM under Windows 2008 server while using SQL 2005 for database'
Document ID: 2009070915000448
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009070915000448?Open&seg=ent

[Rafeeq]

i would like you to test the odbc connection following 64 bit OS
this should fix the issue

Unable to communicate with the reporting component after logging into the Symantec Endpoint Protection Manager
http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

make sure you have network service added in the gpedit.msc as per this document

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

[Migration User]

OK, I am humbled. I read this document, but did not compare the native (admin tools)  and sysWOW64 ODBC connections. Sure enough there was no database specified on the sysWOW64 version of SymantecEndpointSecurityDSN... An error on my part, thanks for the assist!