Tech Support > Microsoft Windows > Windows CRM > Report
Report
Posted by KA 04-1 on December 14th, 2006


Hi, I make a custom report called "Report A", but when I run it in microsoft
CRM application, there is error dialog like this :


-----------------------------------------------------------------------
Reporting Services Error :
An error has occured during report processing .(rsProcessingAborted)
Cannot create a connection to data source 'mi-crm' .
(rsErrorOpeningConnection)
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
-----------------------------------------------------------------------

For information, the user open the report is CRM user (user Liau). Liau was
a member of ReportingGroup in active directory, and then i try to add
ReportingGroup group to SQL Server for dbowner role. Anyone help me ?

Posted by Ieuan on December 17th, 2006


Well, ANONYMOUS is probably not going to have sufficient authority to access
reporting services; so that bit makes sense, at least. What appears to be
happening is that your custom data source is not passing through the user
identity. You've gotten far enough into the reporting services layer to find
the report and run it, which implies that the Kerberos setup is correct.

When you set up your data source, did you pick 'Use Windows Authentication
(Integrated Security)'? If you're not sure, check the following:
1) open the report in Visual Studio
2) Go to the Data tab
3) Click on the button with '...' on it, to the right of the Dataset
4) Click on the button with '...' on it, to the right of the data source on
the Query Tab
5) Go to the Credentials tab.

If this is using Integrated Security, then the implication is that the login
ID is being droppped between CRM and the report. Are you running the report
from the reports menu? If not, if you're running it from a custom button or
similar, then potentially you could be having kerberos / delegation issues.
Try running it from the server that CRM is hosted on (assuming it's not a
multi-server environment), and if that works then chances are there's
something broken in the Kerberos / SPN / Trust-for-delegation setup.

Hope this helps
Ieuan

"KA 04-1" wrote: