.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘Report’

FIX: A dump file may be generated in the Reporting Services Logfiles folder and you may receive an error message when you try to render a report in SQL Server 2008 Reporting Services

Symptoms
Consider the following scenario. In Microsoft SQL Server 2008 Reporting Services, you create a report. The report contains a Tablix data region item, a Subreport item, or a Chart item. The item has the NoRowsMessage property set, and there are no rows in the data region. Or, the report contains a Subreport item that displays error messages. The text box that is generated to display the error messages is split across a report page. You try to render the report. In this scenario, a dump file may be generated in the Reporting Services Logfiles folder. Additionally, you may receive an error message that resembles the following:

Assert in function = Microsoft.ReportingServices.Rendering.HPBProcessing.Paragraph.get_SpaceBefore file =line = 0 expression = Unhandled managed exception: Type = System.NullReferenceException, Message = Object reference not set to an instance of an object.
Resolution
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956717?(http://support.microsoft.com/kb/956717/) Cumulative update package 1 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/)The SQL Server 2008 builds that were released after SQL Server 2008 was released

Error message when you view a report in Microsoft Dynamics CRM 3.0: “System.Web.Services.Protocols.SoapException: The feature: “Report history snapshots” is not supported in this edition of Repor …

Symptoms
Consider the following scenario:You install Microsoft Dynamics CRM 3.0 on Microsoft Windows Small Business Server 2003 Release 2 (R2) with Microsoft SQL Server 2005 Workgroup Edition.You view a report in Microsoft Dynamics CRM 3.0.In this scenario, you receive the following error message:

Server Error in ‘/’ Application.
System.Web.Services.Protocols.SoapException: The feature: “Report history snapshots” is not supported in this edition of Reporting Services.
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: “Report history snapshots” is not supported in this edition of Reporting Services. at Microsoft.ReportingServices.Diagnostics.Sku.ThrowIfFeatureNotEnabled(String instanceId, RestrictedFeatures feature) at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory) — End of inner exception stack trace — at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The feature: “Report history snapshots” is not supported in this edition of Reporting Services. —> Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: “Report history snapshots” is not supported in this edition of Reporting Services. at Microsoft.ReportingServices.Diagnostics.Sku.ThrowIfFeatureNotEnabled(String instanceId, RestrictedFeatures feature) at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory) — End of inner exception stack trace — at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory)
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:[SoapException: System.Web.Services.Protocols.SoapException: The feature: "Report history snapshots" is not supported in this edition of Reporting Services. ---> Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Report history snapshots" is not supported in this edition of Reporting Services.at Microsoft.ReportingServices.Diagnostics.Sku.ThrowIfFeatureNotEnabled(String instanceId, RestrictedFeatures feature)at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory)— End of inner exception stack trace —at Microsoft.ReportingServices.WebServer.ReportingService.ListReportHistory(String Report, ReportHistorySnapshot[]& ReportHistory)]System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) +1496System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) +218Microsoft.Crm.ReportingServices.ReportingService.ListReportHistory(String Report) +48Microsoft.Crm.Reports.ReportCache.GetSnapshots(String reportPath) +267Microsoft.Crm.Reports.ReportCache.GetReportSnapshotProperties(String reportName) +194Microsoft.Crm.Web.Reporting.SRSViewer.ConfigurePage() +440Microsoft.Crm.Application.Controls.AppPage.OnPreRender(EventArgs e) +20System.Web.UI.Control.PreRenderRecursiveInternal() +62System.Web.UI.Page.ProcessRequestMain() +1499
Resolution
SQL Server 2005 Workgroup Edition is available withWindows Small Business Server R2. However, this problem occurs because this version of SQL Server does not support the Snapshot feature in SQL Server Reporting Services.

Error message when you try to run a report or upload a report in Microsoft Dynamics CRM: “The request failed with HTTP status 401: Unauthorized” or “Server Error in ‘/’ Application”

Symptoms
Symptom 1When you try to run a report in Microsoft Dynamics CRM 3.0, you receive the following error message:

The request failed with HTTP status 401: Unauthorized.When you try to run a report in Microsoft Dynamics CRM 4.0, you receive the following error message:

An error occurred while trying to add the report to Microsoft Dynamics CRM.
Try this action again.If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization’s Microsoft Dynamics CRM Administrator.Finally, you can contact Microsoft Support.
Error code:0×80048298
Symptom 2Consider the following scenario in Microsoft Dynamics CRM: You build a custom report by using Microsoft Visual Studio 2003 or by using a similar tool.You try to upload the report to the Microsoft Dynamics CRM system. In this scenario, you receive the following error message:

Server Error in ‘/’ Application. Exception of type Microsoft.Crm.CrmException was thrown. If the DevErrors parameter is enabled, you receive this error messageon the screen.
This error message occurs in some configurations. For example, this error message may occur if the following conditions are true:The following products are installed on the same server:Microsoft SQL ServerSQL Server Reporting Services (SRS)Microsoft Dynamics CRM is installed on a separateserver.
Resolution
This problem occurs because the security account for the CRMAppPool application pool does not have the Publisher for Microsoft Dynamics CRM role in Report Manager.

Cumulative hotfix package (build 2153) for SQL Server 2005 is available

Symptoms
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 1 (SP1) hotfix to an installation of SQL Server 2005 SP1. By default, any hotfix that is provided in a SQL Server service pack is included in the nextSQL Server service pack.
SQL Server 2005 SP1 includes all SQL Server 2005 hotfixes up to and including build 9.0.1530. For more information about which SQL Server 2005 hotfixes are included in SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
913090?(http://support.microsoft.com/kb/913090/) A list of the bugs that have been fixed in SQL Server 2005 Service Pack 1 Cumulative hotfix package (build 2153) for SQL Server 2005 contains SQL Server 2005 hotfixes that were not included in SQL Server 2005 SP1.This build roughly corresponds to SQL Server 2005 builds 9.0.1531 through build 9.0.1540.
Note This hotfix rollup build is also known as build 2153.
Important notes about the cumulative hotfix packageSQL Server 2005 hotfixes are now multilanguage. There is only one cumulative hotfix package for all languages.You must install each component package for your operating system.You must enable the SQL Server Management Object (SMO) and SQL Server Distributed Management Object (SQL-DMO) extended stored procedures before you install the hotfix package. For more information about the SMO/DMO XPs option, see SQL Server 2005 Books Online.
Note SQL Server 2005 Books Online notes that the default setting of these stored procedures is 0 (OFF). However, this value is incorrect. By default, the setting is 1 (ON).You must install all component packages in the order in which they are listed in this article. If you do not install the component packages in the correct order, you may receive an error message.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
919224?(http://support.microsoft.com/kb/919224/) FIX: You may receive an error message when you install the cumulative hotfix package (build 2153) for SQL Server 2005To uninstall this hotfix, follow these steps:Click Start, click Control Panel, and then click Add or Remove programs.In the Add or Remove Programs window, click the Add or Remove Programs icon.To see the rollup that is listed under your Microsoft SQL Server 2005 installation, select the Show Updates check box.You must uninstall the component packages in the order in which they are listed in this article.
Resolution
How to obtain the cumulative hotfix package for SQL Server 2005 (build 9.0.2153)Component packages for x86-based operating systemsIf you are running SQL Server 2005 on an x86-based operating system, you must install the following component packages in the order in which they are presented:
SQL Server 2005
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQL2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sql2005-kb918222-x86-enu.exe)
Microsoft SQL Server 2005 Analysis Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/AS2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/as2005-kb918222-x86-enu.exe)
Microsoft SQL Server 2005 Integration Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/DTS2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/dts2005-kb918222-x86-enu.exe)
Microsoft SQL Server 2005 Notification Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/NS2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/ns2005-kb918222-x86-enu.exe)
Microsoft SQL Server 2005 Reporting Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/RS2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/rs2005-kb918222-x86-enu.exe)
SQL Server 2005 Tools
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQLTools2005-KB918222-x86-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sqltools2005-kb918222-x86-enu.exe)Component packages for x64-based operating systemsIf you are running SQL Server 2005 on an x64-based operating system, you must install the following component packages in the order in which they are presented:
SQL Server 2005
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQL2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sql2005-kb918222-x64-enu.exe)
SQL Server 2005 Analysis Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/AS2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/as2005-kb918222-x64-enu.exe)
SQL Server 2005 Integration Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/DTS2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/dts2005-kb918222-x64-enu.exe)
SQL Server 2005 Notification Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/NS2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/ns2005-kb918222-x64-enu.exe)
SQL Server 2005 Reporting Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/RS2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/rs2005-kb918222-x64-enu.exe)
SQL Server 2005 Tools
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQLTools2005-KB918222-x64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sqltools2005-kb918222-x64-enu.exe)Component packages for Itanium-based operating systemsIf you are running SQL Server 2005 on an Itanium-based operating system, you must install the following component packages in the order in which they are presented:
SQL Server 2005
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQL2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sql2005-kb918222-ia64-enu.exe)
SQL Server 2005 Analysis Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/AS2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/as2005-kb918222-ia64-enu.exe)
SQL Server 2005 Integration Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/DTS2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/dts2005-kb918222-ia64-enu.exe)
SQL Server 2005 Notification Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/NS2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/ns2005-kb918222-ia64-enu.exe)
SQL Server 2005 Reporting Services
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/RS2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/rs2005-kb918222-ia64-enu.exe)
SQL Server 2005 Tools
http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/SQLTools2005-KB918222-ia64-ENU.exe(http://download.microsoft.com/download/6/e/8/6e85f7ab-9f6c-4f3c-8f89-da0f78e026dc/sqltools2005-kb918222-ia64-enu.exe)For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591?(http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
SQL Server 2005 Post-SP1hotfixes that are included in SQL Server 2005 build 9.0.2153Note Microsoft Knowledge Base articles that discuss these hotfixes will be released as they become available.
Collapse this tableExpand this table
SQL Bug number Description 410 Dimension security does not support visual totals on a parent attribute that is in a parent-child dimension. 433 If you execute an ALTER DDL statement that removes dimension hierarchies from the database without removing the hierarchies from the cubes, an access violation may occur. 447 Processing performance on multiprocessor computers is somewhat slower than expected. 459 Under very specific and rare circumstances, a deadlock can occur between two or more sessions in SQL Server 2005. In this case, the internal deadlock monitoring mechanism does not detect the deadlock between the sessions. 461 Page breaks may not be respected when a table is rendered in Microsoft Office Excel if that report contains tables with the conditions of NoRows=true and NoRowsMessage=null, and the table contains a table header or footer. 464 The leaf page of a non-clustered index may have only one index row. 491 On a SQL Server 2005 installation that uses Turkish collation, you cannot view job steps that are of SSIS type from SQL Server Management Studio. If a job has SSIS job steps only, you receive an “Index was outside the bounds of the array. (SqlManagerUI)” error message when you click the Steps tab. 499 A Multidimensional Expressions (MDX) query that involves non-trivial custom rollups when it runs complex sum-like aggregate expressions runs much slower on SQL Server 2005 than on SQL Server 2000. 531 When you run a query or a stored procedure in SQL Server 2005, certain conditions can cause the SQL Server optimizer not to be able to produce an execution plan. 541 An ADOMD.NET application that runs through an IXMLA provider is limited to 32 maximum user sessions. 554 When you query the IS_PLACEHOLDERMEMBER member property for a dimension member by using the .Properties(“IS_PLACEHOLDERMEMBER”) function in MDX, the value that is returned is always FALSE. This behavior occurs even for members that are placeholders in the dimension. 584 When a report contains an image that is external or is a resource in Reporting Services and the report uses the interactive sorting functionality, the image is replaced by a red x. 606 The MDSCHEMA_PROPERTIES row set returns the wrong data type for some user-defined properties. 608 If you include a subreport in a group footer and you enable the HideDuplicates property in a detail row on a grouping item, SQL Server 2005 Reporting Services raises an internal error when you try to export the report. The error also occurs when you click Print Preview on the Preview tab in Report Designer. 614 SQL Server 2005 Reporting Services may intermittently display a System.NullReferenceException exception in the ReportSnapshot.EnsureAllStreamsAreClosed procedure. This behavior generates a mini-dump. 615 The SQL Server 2005 Analysis Services service does not start when you use Japanese_Unicode_CI_AS as a collation for the instance of SQL Server 2005 Analysis Services. 617 When you try to run a linked report that uses the User!UserID variable and the execution properties are set to use Snapshots, you receive the following error message:

3wp!library!1!1/27/2006-13:10:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: 627 In the Japanese version of SQL Server 2005, the fulltext schedule creation in SQL Server Management Studio fails, and you receive the following error message:

The specified @category_name (‘フルテキスト’localized string) does not exist. (Microsoft SQL Server, Error: 14262) 636 A memory leak may occur in the common language runtime (CLR) if you pass a CLR user-defined data type as a parameter by using a stored procedure or the sp_executesql procedure. 652 If Y-axis margins are enabled and the minimum Y-value of all data points is a “nice” integer value, the Y-axis minimum value will be adjusted to a lower value. For example, the chart control rounds 4.0 to 4 to create a “nice” integer value. However, the generated Y-axis labels are incorrect. 664 You run SQL Server 2005 Analysis Services builds 9.00.1520 through 9.00.1539 or SQL Server 2005 SP1. In this case, an MDX query that includes a distinct count measure may not return results. This behavior only occurs if the measure group that is queried contains multiple partitions. 708 The SQL Server Integration Services (SSIS) service does not start when you install SQL Server 2005 SP1 752 The MSMQTask.dll and dependencies are deleted when the fix that is described in the Microsoft Knowledge Base article 910070 is applied. 40000100 If the log reader agent and the DBCC DBREINDEX or ALTER INDEX …REBUILD commands run at the same time, the log reader agent may miss some transactions to the distributor. 40000102 When you configure Log Shipping and add two or more secondary servers to Log Shipping, only the secondary server that you added last is monitored by the monitor server and the other secondary servers are not. 40000108 The SQL Server 2005 Database Engine Tuning Advisor may unexpectedly exit if indexed views are part of the workload that is tuned. 40000110 The YTD calculation in cubes that use parent-child dimensions may be incorrect. 50000104 The SqlCommandBuilder.DeriveParameters(SqlCommand) method returns an exception when you execute a stored procedure with an input parameter that is a typed XML type. 50000112 A member of the SQL Server 2005 Analysis Services database administrator role cannot add or delete perspectives. Only a member of the SQL Server 2005 Analysis Services server role can perform such tasks. 50000115 A Report Server Model may use an Analysis Services data source. MDX queries are generated from Report Builder based on the Report Server Model. Dates in the MDX queries have the month and day parts transposed. 50000116 A FETCH operation that uses a KEYSET cursor may be slow if the target table for the cursor has a clustered index and non-clustered indexes. This behavior occurs if the clustered index is the best choice for the FETCH operation and if the SELECT query for the cursor is very simple. 50000120 In SQL Server 2005 Analysis Services, calculated members that are defined in the cube MDX script are resolved before any session or query defined calculations. The only exceptions are certain scenarios with the Aggregate and VisualTotals functions. This behavior is a change from the SQL Server 2000 Analysis Services behavior. In SQL Server 2000 Analysis Services, the Solve Order could be used explicitly to insert a session or a query-defined calculation between two cube level calculations. This change in behavior may cause the query or session scope calculated members not to return the results that you want in SQL Server 2005 Analysis Services. Cumulative hotfix package for SQL Server 2005 (build 9.0.2153) introduces new syntax that allows for control over the scope in which a calculated member is evaluated. 50000151 When you run a SELECT query to return any duplicate rows in a table, incorrect results are returned if the query plan contains a hash aggregation and if one or more of the columns in the table contain a combination of empty strings and undefined characters. 50000154 You may receive a variablelock list error message when you run multiple instances of a package. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
915918?(http://support.microsoft.com/kb/915918/) FIX: The internal deadlock monitor may not detect a deadlock between two or more sessions in SQL Server 2005

BUG: Report Preview with Form’s Name Clears Object Reference

Symptoms
Issuing a REPORT FORM PREVIEW command on a report that has the same filename as a form that is running causes the form to lose its objectreference. If you attempt to reference the form object in code, this errormessage appears:

Object not found
Resolution
If you have a form called Customer and issue the following command, anobject reference named Customer is created for the form:

DO FORM Customer Preview a report named Customer by issuing the following command:

REPORT FORM Customer PREVIEW The customer object now references the Report Preview window. When theReport Preview window is closed, the customer object is released. Workaround this problem by giving your forms a different object reference thanthe reports with the same name. Do this by using the NAME clause in the DOFORM command. For example, to give the Customer Form an object reference ofCustform, you would issue the following command:

DO FORM Customer NAME Custform

Application Has Generated an Exception That Could Not Be Handled…Process id=0×400 (1024), Thread id=0×4c4 (1220)

Symptoms
FRxReportManager.exe – Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0×400 (1024), Thread id=0×4c4 (1220).
Click OK to terminate the application.Click CANCEL to debug the application.
This error occurs when trying to launch Report Manager that is installed as a network client (thin client).
Resolution
This error will occur when the user has insufficient permissions to the Report Manager directory on the server.