Article ID: 955206 - Last Review: February 12, 2009 - Revision: 2.0 A report snapshot is not created when you try to schedule a report in Microsoft Dynamics CRM 4.0
SYMPTOMSWhen you try to schedule a report to generate a snapshot in Microsoft Dynamics CRM 4.0, the snapshot is not created. If you view the log file for Reporting Services, you may find an error message that resembles the following: ReportingServicesService!library!8!6/26/2008-23:59:09:: e ERROR: Schedule d7b0cd76-4a4c-45b6-ae5b-805e75263553 failed. Error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: An error has occurred during report processing. Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'CRM'. Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal C:\Program files\Microsoft SQL Server\Mssql\Reporting services\LogFiles RESOLUTIONThis problem is fixed in the latest cumulative update rollup for Microsoft Dynamics CRM 4.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
949256
(http://support.microsoft.com/kb/949256/
)
Microsoft Dynamics CRM 4.0 updates and hotfixes
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates
For more information about Microsoft Business Solutions CRM software hotfix and update package terminology, click the following article number to view the article in the Microsoft Knowledge Base:
887283
(http://support.microsoft.com/kb/887283/
)
Microsoft Business Solutions CRM software hotfix and update package naming standards
| Article Translations
|
Back to the top
