FIX: A "System.NullReferenceException" exception may be logged in the Reporting Services log when you try to create a snapshot report in SQL Server 2005 Reporting Services (917494)



The information in this article applies to:

  • Microsoft SQL Server 2005 Reporting Services

Bug: #614 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 Reporting Services fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 Reporting Services fix release.

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for installing this hotfix package
  • Whether you must restart the computer after you apply this hotfix package
  • Whether this hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply this hotfix package
  • The files that are contained in this hotfix package

SYMPTOMS

When you try to create a snapshot report in Microsoft SQL Server 2005 Reporting Services, the following exception may be logged in the Reporting Services log:
System.NullReferenceException
Additionally, you may experience the following problems:
  • You may notice that mini-dump files have been created in the LogFiles folder for Reporting Services. By default, the path of the LogFiles folder is as follows:

    C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles

    Note The folder name MSSQL.3 is a placeholder because this folder name may vary, depending on which SQL Server services you have installed.
  • The mini-dump files are created at a fixed interval.
Note You may also experience these problems in Microsoft SQL Server 2000 Reporting Services.

RESOLUTION

Note The hotfix that is discussed in this article is only for SQL Server 2005 Reporting Services. If you are experiencing a similar problem in SQL Server 2000 Reporting Services, see the "Workaround" section.

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2005 Reporting Services service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

There are no prerequisites for this hotfix.

Restart information

You do not have to restart your computer after you apply this hotfix.

Registry information

You do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that this article lists.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Autoadmin90.dll2005.90.1537.0898,77604-Apr-200612:56x86
Dtspipeline.dll2005.90.1537.0600,28004-Apr-200612:55x86
Dundaswebchart.dll9.0.1537.0752,34404-Apr-200612:56x86
Dundaswinchart.dll9.0.1537.0797,40004-Apr-200612:56x86
Microsoft.datatransformationservices.vsintegration.dll9.0.1537.0330,45604-Apr-200612:55x86
Microsoft.datawarehouse.vsintegration.dll9.0.1537.0637,65604-Apr-200612:56x86
Microsoft.reportingservices.designer.dll9.0.1537.04,778,71204-Apr-200612:55x86
Microsoft.reportingservices.diagnostics.dll9.0.1537.0604,88804-Apr-200612:55x86
Microsoft.reportingservices.excelrendering.dll9.0.1537.0330,45604-Apr-200612:55x86
Microsoft.reportingservices.processingcore.dll9.0.1537.01,665,75204-Apr-200612:56x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.1537.0113,36804-Apr-200612:54x86
Microsoft.sqlserver.replication.dll2005.90.1537.01,608,40804-Apr-200612:56x86
Microsoft.sqlserver.smo.dll9.0.1537.01,559,25604-Apr-200612:56x86
Microsoft.sqlserver.sqlenum.dll9.0.1537.0895,70404-Apr-200612:56x86
Microsoft.sqlserver.tabletransfergeneratortask.dll9.0.1537.043,73604-Apr-200612:55x86
Microsoft.visualstudio.vspsqlenum.dll9.0.1537.0862,93604-Apr-200612:56x86
Msadomdx.dll9.0.1537.0502,48804-Apr-200612:55x86
Msmdlocal.dll9.0.1537.015,599,83204-Apr-200612:55x86
Msmdpp.dll9.0.1537.03,827,41604-Apr-200612:55x86
Msmdpump.dll9.0.1537.03,915,48004-Apr-200612:55x86
Msmdredir.dll9.0.1537.03,929,81604-Apr-200612:55x86
Msmdspdm.dll9.0.1537.0154,32804-Apr-200612:55x86
Msmdsrv.exe9.0.1537.014,577,36804-Apr-200612:55x86
Msmgdsrv.dll9.0.1537.05,937,36804-Apr-200612:55x86
Msolap90.dll9.0.1537.04,205,27204-Apr-200612:55x86
Nsservice.exe9.0.1537.018,64804-Apr-200612:54x86
Osql.exe2005.90.1537.051,41604-Apr-200612:55x86
Replrec.dll2005.90.1537.0781,01604-Apr-200612:56x86
Reportingserviceslibrary.dll9.0.1537.01,030,87204-Apr-200612:56x86
Reportingservicesnativeserver.dll2005.90.1537.0130,26404-Apr-200612:54x86
Reportingservicesservice.exe9.0.1537.014,55204-Apr-200612:54x86
Reportingserviceswebserver.dll9.0.1537.01,321,68804-Apr-200612:56x86
Reportingserviceswebuserinterface.dll9.0.1537.01,231,57604-Apr-200612:56x86
Rsclientprint.dll2005.90.1537.0572,63204-Apr-200612:55x86
Sqlaccess.dll2005.90.1537.0349,40004-Apr-200612:55x86
Sqlca.dll2005.90.1537.03,207,38404-Apr-200612:55x86
Sqldiag.exe2005.90.1537.0960,21604-Apr-200612:56x86
Sqldiscoveryapi_s.dll2005.90.1537.0527,06404-Apr-200612:55x86
Sqlmanagerui.dll9.0.1537.06,048,47204-Apr-200612:55x86
Sqlncli.dll2005.90.1537.02,208,52804-Apr-200612:56x86
Sqlservr.exe2005.90.1537.028,780,30404-Apr-200612:55x86
Txbestmatch.dll2005.90.1537.0430,29604-Apr-200612:55x86

WORKAROUND

To work around this problem, follow these steps in Visual Studio 2005:
  1. On the File menu, point to Open, and then click File. In the Open File dialog box, click Report.rdl, and then click Open.
  2. On the View menu, click Code.
  3. Locate the following code.
    <DataSources>
        <DataSource Name="AdventureWorks">
    
  4. Replace the code that you located in step 3 with the following code.
    <DataSources>
        <DataSource Name="AdventureWorks">
          <Transaction>true</Transaction>
    

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbfix kbBug kbsql2005rs kbHotfixServer kbQFE kbpubtypekc KB917494 kbAudITPRO kbAudDeveloper