最近需要使用CRM报表快照的功能,发现按需运行的报表能够顺利地生成快照,但是按计划运行的报表却无法自动生成快照。所以就进行了测试,情况如下:
在一台SQL2003 Enterprise 的机器上安装CRM环境(Domain Controller、SQL Server 2005 Enterprise、CRM)
(1) 情况一:本地系统帐号方式
1:SQL Server Reporting Services 采用安装SQL Server的默认配置)。
SQL Server 自动启动帐号“本地系统帐号”;
SQL Server Agent 自动启动帐号“本地系统帐号”
SQL Server FullText Search 自动启动帐号“本地系统帐号”
SQL Server Reporting Services 自动启动帐号“本地系统帐号”
在这种情况下CRM按需和按计划的报表能够顺利运行。
(2)情况二:域管理员方式
1:删掉SQL Server 上的ReportServer和ReportServerTempDB数据库。
2:重新进行Reporting Services的 配置。
SQL Server 自动启动帐号“域管理员”;
SQL Server Agent 自动启动帐号“域管理员”
SQL Server FullText Search 自动启动帐号“域管理员”
SQL Server Reporting Services 自动启动帐号“域管理员”
此处的域管理员为安装SQL Server和CRM的域管理员用户,在这种情况下CRM按需和按计划的报表能够顺利运行;如果只是具有域管理员角色的域用户,计划报表不能执行。
(3)情况三:域用户方式
1:建立域用户(SQLAdmin) ,添加其到本地管理员组。
2:删掉SQL Server 上的ReportServer和ReportServerTempDB数据库。
3:重新进行Reporting Services的 配置。
SQL Server 自动启动帐号“域用户(SQLAdmin)”;
SQL Server Agent 自动启动帐号“域用户(SQLAdmin)”
SQL Server FullText Search 自动启动帐号“域用户(SQLAdmin)”
SQL Server Reporting Services 自动启动帐号“域用户(SQLAdmin)”
该域用户(SQLAdmin)具有本地管理员权限所以可以启动相关SQL服务,在这种情况下CRM按需报表能够执行,按计划的报表不能执行。
针对第三种情况,察看Reporting Services的日志发现提示信息如下:
ReportingServicesService!processing!4!2009/12/29-13:04:13:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。, ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmConfigObjectNotFoundException: User Was Not Found
在 Microsoft.Crm.ServerLocatorService.GetCrmUserIdFromDatabase(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.ServerLocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.LocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
ReportingServicesService!processing!4!2009/12/29-13:04:13:: e ERROR: Data source 'CRM': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmConfigObjectNotFoundException: User Was Not Found
在 Microsoft.Crm.ServerLocatorService.GetCrmUserIdFromDatabase(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.ServerLocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.LocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
ReportingServicesService!processing!4!2009/12/29-13:04:13:: e ERROR: An exception has occurred in data source 'CRM'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmConfigObjectNotFoundException: User Was Not Found
在 Microsoft.Crm.ServerLocatorService.GetCrmUserIdFromDatabase(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.ServerLocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.LocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
ReportingServicesService!processing!4!2009/12/29-13:04:13:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
ReportingServicesService!processing!4!2009/12/29-13:04:13:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。, ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmConfigObjectNotFoundException: User Was Not Found
在 Microsoft.Crm.ServerLocatorService.GetCrmUserIdFromDatabase(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.ServerLocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.LocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
--- 内部异常堆栈跟踪的结尾 ---
ReportingServicesService!library!4!2009-12-29-13:04:13:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
ReportingServicesService!library!4!2009-12-29-13:04:14:: e ERROR: Schedule 02651656-3f9c-4e10-84ab-91a094529cab failed. Error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmConfigObjectNotFoundException: User Was Not Found
在 Microsoft.Crm.ServerLocatorService.GetCrmUserIdFromDatabase(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.ServerLocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.LocatorService.GetCrmUserId(Guid organizationId, String authenticationInfo)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.AbortHelper.ThrowAbortException(Int32 reportUniqueName)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.CheckAndThrowIfAborted()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.Process(ParameterInfoCollection parameters, Boolean mergeTran)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, ProcessingContext context)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, Boolean snapshotProcessing, Boolean processWithCachedData, GetReportChunk getChunkCallback, ErrorContext errorContext, DateTime executionTime, CreateReportChunk cacheDataCallback, ProcessingContext& context)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateSnapshot(DateTime executionTimeStamp, GetReportChunk getChunkCallback, ProcessingContext pc)
在 Microsoft.ReportingServices.Library.CreateSnapshotExecutor.CallProcessing(Boolean unattended, Boolean permanent, Boolean isForHistory)
在 Microsoft.ReportingServices.Library.CreateSnapshotExecutor.CreateSnapshot(Boolean unattended, Boolean permanent, Boolean isForHistory)
在 Microsoft.ReportingServices.Library.UpdateExecutionSnapshotAction.InternalUpdateSnapshot()
在 Microsoft.ReportingServices.Library.UpdateExecutionSnapshotCancelableStep.Execute()
在 Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
在 Microsoft.ReportingServices.Library.UpdateExecutionSnapshotAction.PerformActionNow()
在 Microsoft.ReportingServices.Library.RSSoapAction`1.Execute()
在 Microsoft.ReportingServices.Library.ReportExecutionSnapshotScheduleEventHandler.PerformActionHandler(ICatalogQuery catalogQuery, ArrayList reportActions)
在 Microsoft.ReportingServices.Library.ScheduleFireEventHandlerBase.HandleScheduleEvent(ICatalogQuery catalogQuery, String eventData, PerformEventActions handleFunction)
ReportingServicesService!dbpolling!4!2009-12-29-13:04:14:: i INFO: EventPolling finished processing item 5b22654c-f031-4260-ae0e-724531b75e92
ReportingServicesService!dbpolling!c!2009-12-29-13:06:54:: e ERROR: Polling caught an exception, restarting polling. Error Message System.Data.SqlClient.SqlException: 在向服务器发送请求时发生传输级错误。 (provider: 共享内存提供程序, error: 0 - 管道的另一端上无任何进程。)
在 System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
在 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
在 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
在 System.Data.SqlClient.TdsParserStateObject.WriteSni()
在 System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
在 System.Data.SqlClient.TdsParserStateObject.ExecuteFlush()
在 System.Data.SqlClient.TdsParser.TdsExecuteSQLBatch(String text, Int32 timeout, SqlNotificationRequest notificationRequest, TdsParserStateObject stateObj)
在 System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
在 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
在 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
在 System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
在 System.Data.SqlClient.SqlCommand.ExecuteReader()
在 Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteReader()
在 Microsoft.ReportingServices.Library.DBPoll.PollingFunction()
在 Microsoft.ReportingServices.Library.DBPoll.PollingStartFunction().
分析可能是由于域用户SQLAdmin的权限不足导致,最后将该域用户添加到以下CRM安装的默认权限组中:
1:PrivReportingGroup
2:PrivUserGroup
3:ReportingGroup
4:SQLAccessGroup
中之后问题得到了解决。这样在一台机器上模拟出“通过域用户启动SQL Services”来进行计划的报表快照的方法了。 下面就是在生产环境中进行验证了。
生产环境情况CRM是按照角色安装的,大致如下:
1:CRMAPP(包含CRM 网站和相关帮助)。
2:CRMPFM(包含CRM异步服务)。
3:CRMDPL(包含CRM部署服务) 。
4:CRMDB(包含CRM业务数据库、配置数据库、CRM报表数据库和SQL Database Service、SQL Server Agent、SQL Server FullText Search服务),服务启动帐号为具有CRMDB本地管理员权限的域用户。
5:CRMRPT(包含SQL Reporting Services) ,服务启动帐号为具有CRMDB本地管理员权限的域用户。
在这种情况下用上面的第三种情况进行域用户的配置,发现执行计划报表的时候SQL Reporting Services的错误提示如下:
ReportingServicesService!processing!4!2009/12/29-14:08:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。, ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal
在 Microsoft.Crm.CrmException.Assert(Boolean condition, String message)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
ReportingServicesService!processing!4!2009/12/29-14:08:28:: e ERROR: Data source 'CRM': An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal
在 Microsoft.Crm.CrmException.Assert(Boolean condition, String message)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
ReportingServicesService!processing!4!2009/12/29-14:08:28:: e ERROR: An exception has occurred in data source 'CRM'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal
在 Microsoft.Crm.CrmException.Assert(Boolean condition, String message)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
ReportingServicesService!processing!4!2009/12/29-14:08:28:: i INFO: Merge abort handler called for ID=-1. Aborting data sources ...
ReportingServicesService!processing!4!2009/12/29-14:08:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。, ;
Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal
在 Microsoft.Crm.CrmException.Assert(Boolean condition, String message)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
--- 内部异常堆栈跟踪的结尾 ---
ReportingServicesService!library!4!2009-12-29-14:08:28:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
ReportingServicesService!library!4!2009-12-29-14:08:29:: e ERROR: Schedule 7c883f28-a1fa-4c68-9759-2ec94ea681d3 failed. Error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: 处理报表时出错。 ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: 无法与数据源“CRM”建立连接。 ---> Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal
在 Microsoft.Crm.CrmException.Assert(Boolean condition, String message)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.ValidateCaller(Guid systemUserId, Guid organizationId)
在 Microsoft.Crm.Reporting.DataConnector.SrsExtConnection.Microsoft.ReportingServices.DataProcessing.IDbConnection.Open()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.OpenConnection(DataSource dataSourceObj, ReportProcessingContext pc)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ReportRuntimeDataSourceNode.Process()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RuntimeDataSourceNode.ProcessConcurrent(Object threadSet)
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessingContext.CheckAndThrowIfAborted()
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.Merge.Process(ParameterInfoCollection parameters, Boolean mergeTran)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.ProcessReport(Report report, ProcessingContext pc, ProcessingContext context)
在 Microsoft.ReportingServices.ReportProcessing.ReportProcessing.CreateSnapshot(DateTime executionTimeStamp, GetReportChunk getChunkCallback, ProcessingContext pc)
在 Microsoft.ReportingServices.Library.CreateSnapshotExecutor.CallProcessing(Boolean unattended, Boolean permanent, Boolean isForHistory)
在 Microsoft.ReportingServices.Library.CreateSnapshotExecutor.CreateSnapshot(Boolean unattended, Boolean permanent, Boolean isForHistory)
在 Microsoft.ReportingServices.Library.UpdateExecutionSnapshotAction.InternalUpdateSnapshot()
在 Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
--- 内部异常堆栈跟踪的结尾 ---
在 Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
在 Microsoft.ReportingServices.Library.UpdateExecutionSnapshotAction.PerformActionNow()
在 Microsoft.ReportingServices.Library.RSSoapAction`1.Execute()
在 Microsoft.ReportingServices.Library.ReportExecutionSnapshotScheduleEventHandler.PerformActionHandler(ICatalogQuery catalogQuery, ArrayList reportActions)
在 Microsoft.ReportingServices.Library.ScheduleFireEventHandlerBase.HandleScheduleEvent(ICatalogQuery catalogQuery, String eventData, PerformEventActions handleFunction)
ReportingServicesService!dbpolling!4!2009-12-29-14:08:29:: i INFO: EventPolling finished processing item d1b28017-d33f-4fa2-94f3-95ce26d03cc5
ReportingServicesService!library!4!2009-12-29-14:09:58:: Using folder C:\Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\RSTempFiles for temporary files.
ReportingServicesService!library!4!2009-12-29-14:09:58:: i INFO: Cleaned 0 batch records, 0 policies, 2 sessions, 0 cache entries, 1 snapshots, 7 chunks, 0 running jobs, 0 persisted streams
通过检索关键字“Microsoft.Crm.CrmException: Thread.CurrentPrincipal is not a WindowsPrincipal”
发现需要安装http://support.microsoft.com/kb/949256/en-us的补丁。
该补丁需要单独下载安装,安装之后,计划报表就可以快照了。