Symptoms: When you try to add references to your project, only a few of the ActiveReports version 7 references are available.

Cause: The project's target framework is set to an old version of the .NET framework that does not support the new assemblies.

Solution:

1. In the Solution Explorer, right click the project and choose Properties.
2. On the Application tab in C# projects (or the Compile tab, then the Advanced Compile Options button in Visual Basic projects), drop down the Target framework box and select .NET Framework 4.0.

Symptoms: When you open a project created with a previous build of ActiveReports after installing a new build, there are errors related to being unable to find the previous build.

Cause: Visual Studio has a property on references called Specific Version. If this property is set to True, the project looks for the specific version that you had installed when you created the report, and throws errors when it cannot find it.

Solution: For each of the ActiveReports references in the Solution Explorer, select the reference and change the Specific Version property to False in the Properties Window.

Symptoms: The web project does not work in the application pool if Integrated Managed Pipeline Mode is enabled.

Cause: The application configuration is incorrect for being used in Integrated mode.

Solution: Migrate the application configuration. Here is a sample command.

"%SystemRoot%\system32\inetsrv\appcmd migrate config YourWebSite/"

Symptoms: The GrapeCity.ActiveReports.Interop64.v9.dll is not available in the default "Add Reference" dialog.

Cause: The GrapeCity.ActiveReports.Interop64.v9.dll is located in the distribution folder.

Solution: The GrapeCity.ActiveReports.Interop64.v9.dll is located in C:\Program Files (x86)\Common Files\ComponentOne\ActiveReports 9\redist.

Symptoms: When adding ActiveReports to a Web site project that is bound to TFS (where reports are added to the App_Code folder), the report does not open in the designer in Visual Studio.

Cause: The FileAttributes.xml file that contains attribute information to associate ActiveReports files with the Designer is usually loaded and maintained in memory when a new ActiveReports file is added. However, if a Web site is bound to TFS, the FileAttributes.xml file is not maintained in memory. As a result, Visual Studio treats all the newly added files as normal code files.

Solution: Add the newly added reports to FileAttributes.xml manually.

1. From the Website menu, select Add New Item.
2. Select ActiveReports 9 Section Report (code-based) and click OK.
3. Close the project.
4. From Windows Explorer, open the FileAttributes.xml file in an editor and add the new ActiveReports file, setting the subtype to Component, using code like the following.

   Note: The FileAttributes.xml is located at C:\Documents and Settings\[username]\Local Settings\Application Data\Microsoft\WebsiteCache\[WebSite1]\ (Windows XP), or at C:\Users\[username]\AppData\Local\Microsoft\WebsiteCache\[WebSite1]\ (Windows 7).

   XML code. Paste inside FileAttributes.xml	Copy Code
   <?xml version="1.0" encoding="utf-16" ?> <DesignTimeData> <File RelativeUrl="App_Code/NewActiveReport1.cs" subtype="Component" /> <File RelativeUrl="Default.aspx.cs" subtype="ASPXCodeBehind" codebehindowner="Default.aspx" /> <File RelativeUrl="Default.aspx" subtype="ASPXCodeBehind" /> </DesignTimeData>

5. Save the FileAttributes.xml file.
6. Reopen the Web site project.

Symptoms: The SystemNotSupportedException occurs when running ActiveReports with scripts on .NET Framework 4.0.

Cause: This exception occurs because of the CAS policy, which is obsolete in the .NET Framework 4.0.

Solution: To resolve this issue, the configuration file needs to be updated. To do this, in the Solution Explorer, open the app.config file (for Windows Forms applications) or the Web.config file (for ASP.NET Web applications) and add the following code.

<configuration>
  <runtime>
    <NetFx40_LegacySecurityPolicy enabled="true"/>
  </runtime>
</configuration>

<system.web>
   <trust legacyCasModel="true"/>
</system.web>

Symptoms: Microsoft Access OLE DB provider, Microsoft.Jet.OLEDB.4.0 does not work on a 64-bit system.

Cause: In Visual Studio 2008, by default, projects are set to use 32 bit or 64 bit, depending on the environment on which they are run. The Microsoft Access OLE DB provider, Microsoft.Jet.OLEDB.4.0, is not compatible with 64 bit, so it fails with Visual Studio 2008 on a 64-bit system.

Solution: To avoid this situation, change the project settings to use only 32 bit.

1. With the project open in Visual Studio, from the Project menu,  select Project Properties.
2. In the page that appears, select the Compile tab in a VB project, or the Build tab in a C# project.
3. Scroll to the bottom of the page and click the Advanced Compile Options button in VB, or skip this step in C#.
4. Drop down the Target CPU list in VB, or Platform target in C#, (set to use AnyCPU by default) and select x86.
5. Click OK to save the changes, or skip this step in C#.

Symptoms: The printing thread dies before the report is printed.

Cause: If printing is done in a separate thread and the application is shut down right after the print call, the separate thread dies before the report is printed.

Solution: Set the usePrintingThread parameter of the Print() method to False to keep the printing on the same thread. This applies to all Page reports, RDL reports and Section reports.

1. In the project where you call the Print method, add a reference to the GrapeCity.ActiveReports.Viewer.Win.v9 assembly.
2. At the top of the code file where you call the Print method, add a using directive (Imports for VB) for GrapeCity.ActiveReports.
3. Call the Print method with the usePrintingThread parameter (the third parameter) set to false with code like the following.

document.Print(false, false, false);

document.Print(False, False, False)

Symptoms: An exception is thrown when the Viewer.Print method is used to print a report.

Cause: Print method was called before the page was loaded completely.

Solution: Use the Viewer.Print method in the LoadCompleted event.

Symptoms: ActiveReport controls do not appear in the toolbox even when they are added manually using the steps in Adding ActiveReports Controls.

Cause: The project is using .NET 2.0 or lower.

Solution: Confirm if the project is using .NET 3.5 or later. .NET 2.0 is not supported in ActiveReports.

Symptoms: Blank pages are printed between pages of the report.

Cause: This problem occurs when the PrintWidth plus the left and right margins exceeds the paper width. For example, if the paper size were set to A4, the PrintWidth plus the left and right margins cannot exceed 8.27"; otherwise blank pages will be printed. At run time, ActiveReports marks a page overflow by displaying a red line in the viewer at the position in which the breach has occurred.

Solution: Adjust the PrintWidth in the report designer using either the property grid or by dragging the right edge of the report. Adjust page margins, height, and width either through the print properties dialog box (in the Report menu under Settings), or programmatically in the Report_Start event.

Symptoms: A report file copied into a new project has all of its controls piled up at location 0, 0.

Cause: The report has become disconnected from its resource file. When you set a report"s Localizable property to True, the Size and Location properties of the report"s controls are moved to the associated *.resx file, so if you copy or move the report, you must move the *.resx file along with it.

Solution: When you copy a report"s *.vb or *.cs file from one project's App_Code folder into the App_Code folder of a new project, you need to also copy its *.resx file from the original project"s App_GlobalResources folder into the new project's App_GlobalResources folder.

Symptoms: No data appears in a report containing the OleObject control.

Cause: This issue occurs when the Microsoft .NET Framework 4.0 Client Profile or .NET Framework 4.0 Full Profile is used and the useLegacyV2RuntimeActivationPolicy attribute is not set to True.

Solution: Open the app.config file and set the useLegacyV2RuntimeActivationPolicy attribute to true.

<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="MyRunTimeVersion"/>
</startup>
</configuration>

Symptoms: An error message is displayed in the Fields list in the Report Explorer instead of the fields.

Cause: This is an expected error if no default value is given for a parameter. If the field is a data type other than text, memo, or date/time in Access, the report still runs normally.

Solution: To display the fields in the Fields list in the Report Explorer, supply a default value for the parameter in the Properties Window, or in the SQL query as below:

<%Name | PromptString | DefaultValue | DataType | PromptUser%>

Only the Name parameter is required. To use some, but not all, of the optional parameters, use all of the separator characters but with no text between one and the next for unused parameters. For example:

<%Name | | DefaultValue | |%>

Symptoms: When the report is run, an exception like the following occurs: "An unhandled exception of type "System.Data.OleDb.OleDbException" occurred in system.data.dll"

Cause: If the field is a text, memo, or date/time data type in Access, the parameter syntax requires single quotes for text or memo fields, or pound signs for date/time fields. Please note that for different data sources, these requirements may differ.

Solution: To avoid the exception when the report is run against an Access database, use pound signs for date/time values, or single quotes for string values in your SQL query, for example:

#<%InvoiceDate | Choose invoice date: | 11/2/04 | D | True%>#

or

"<%Country | Country: | Germany | S | True%>"

Symptoms: The parameter user interface pops up at run time asking for a value even though the main report is supplying the parameter values for the subreports.

Cause: The default value of the ShowParameterUI property of the report is True.

Solution: Set the ShowParameterUI property of the report to False. This can be done in the property grid or in code in the ReportStart event.

Symptoms: In the viewer, the report renders to a different paper size than the one specified.

Cause: ActiveReports polls the printer driver assigned to the report to check for clipping, margins, and paper sizes supported by the printer. If the paper size specified for the report is not supported by the printer, ActiveReports uses the printer's default paper size to render the report.

Solution: If the report is to be printed, the printer assigned to the report must support the paper size and margins. Please note that any changes to the print settings in code must be made in or before the ReportStart event. To use custom paper sizes not supported by the driver, set the PrinterName to an empty string to use the ActiveReports virtual print driver. This does not allow printing, but is recommended for reports that are only exported or viewed. This prevents ActiveReports from making a call to the default printer driver. Use the following code in the ReportStart event, or just before .Run is called.

this.Document.Printer.PrinterName = '';

Me.Document.Printer.PrinterName = ''

The PaperHeight and PaperWidth properties, which take a float value defined in inches, have no effect unless you set the PaperKind property to Custom. Here is some sample code which can be placed in the ReportStart event, or just before .Run.

this.PageSettings.PaperKind = Drawing.Printing.PaperKind.Custom;
this.PageSettings.PaperHeight = 2; 
//sets the height to two inches 
this.PageSettings.PaperWidth = 4; 
//sets the width to four inches

Me.PageSettings.PaperKind = Drawing.Printing.PaperKind.Custom 
Me.PageSettings.PaperHeight = 2 
'sets the height to two inches 
Me.PageSettings.PaperWidth = 4 
'sets the width to four inches

Symptoms: Custom paper sizes do not work.

Cause: You can create more than one custom paper size, so setting only the PaperKind property is not enough to create a custom paper size.

Solution: In addition to setting the PaperKind property to Custom, you must also set the PaperName property to a unique string.

Symptoms: An expression containing a numeric field name does not display any data at runtime.

Cause: Visual Basic syntax does not allow an identifier that begins with a number.

Solution: Make the numeric field name a string.

Symptoms: Cannot set a dataset field (bound field) in the PageHeader of a RDL report.

Cause: ActiveReports is based on the RDL 2005 specifications, therefore, referencing datasets in the PageHeader of a RDL report is not supported.

Solution: There is no direct way to add a DataField in a PageHeader, however, as a workaround you can create a hidden report parameter that is bound to your dataset and has the default value set to your expression. For example, ="*" & First(Fields!name.Value). You can then use this parameter in the page header.
Alternatively, you can use an Page report instead, which lets you place data fields anywhere on a page.

Symptoms: An exception is raised when Viewer.Document is used with a page report or RDL report.

Cause: Document property is available for section reports only.

Symptoms: Cannot add assembly reference created in .NET Framework 4.0 or above in PageReports/RDLReports of the Standalone Designer application.

Cause: Standalone Designer application has been created in .NET 3.5 framework, therefore it cannot loaad .NET 4.0 assemblies.

Symptoms: With the Flash viewer, my page throws a swfobject is undefined error.

Cause: The ActiveReports Handler Mappings are not set up correctly in IIS 7.0.

Solution: Configure HTTPHandlers in IIS 7.x.

Symptoms: When running the Flash viewer in IIS, an error occurs with the following message: "IOError while loading document. Reason: Error #2032."

Cause: The ActiveReports Handler Mappings are not set up correctly in IIS or in the web.config file.

Solution: Update Configure HTTPHandlers in IIS 7.x or if that is already done, ensure that the handlers are enabled in your web.config file.

Symptoms: When running the Flash viewer in FireFox, reports display white pages, but Internet Explorer renders reports correctly.

Cause: The height and width of the Flash viewer control is set to 100%. FireFox does not support this setting, so it does not resize the Flash Viewer at all.

Solution: Use cascading style sheets (CSS) to set the properties.

To use CSS in your Flash viewer ASPX

<style type="text/css">
html, body, #WebViewer1, #WebViewer1_controlDiv
{
  width: 100%;
  height: 100%;
  margin: 0;
}
</style>

To use an external CSS file

Symptoms: An rdf file is not loaded in Flash Viewer when using client scripting.

Cause: You have to modify the setting of IIS Express to allow an rdf file to load correctly when using client scripting.

Solution: There are two ways to resolve this issue. 

Open a Command Prompt window. Navigate to the IIS Express installation folder (the default location of this folder is C:\Program Files\IIS Express) and run the following command.

appcmd set config /section:staticContent /+[fileExtension='.rdf',mimeType='application/octet-stream']

The other one is to modify the IIS Express configuration file.

1. In your local folders, find the IIS Express configuration file (the default location is C:\Users\[username]\Documents\IISExpress\config\applicationhost.config).
2. Using Notepad, open the file and find the configuration/system.webServer/staticContent element.
3. Add the following content to the staticContent node.

   Paste inside the IIS Express configuration file to the staticContent node	Copy Code
   <mimeMap fileExtension=".rdf" mimeType="application/octet-stream" />

4. Save the IIS Express configuration file.

Symptoms: When using the Silverlight Viewer in Silverlight 5, the JScript error may occur with the following message: "Unhandled Error in Silverlight Application The invocation of the constructor on type 'DataDynamics.ActiveReports.Viewer' that matches the specified binding constraints threw an exception."

Cause: The Silverlight Viewer is based on Silverlight 4, and it adds reference to System.Windows.Controls.dll (2.0.5.0). In Silverlight 5, adding the Silverlight Viewer control does not automatically add reference to System.Windows.Controls.dll to the project because the Silverlight Viewer adds reference to the Silverlight 4 version.

Solution: Add a reference to System.Windows.Controls.dll (in Silverlight 4 SDK or Silverlight 5 SDK) to the project.

Symptoms: Pan Mode does not work in horizontal/vertical directions, if the Silverlight viewer is placed in layout panels such as StackPanel, Canvas etc.

Cause: The default size of the Silverlight viewer is set to infinite according to the layout panel properties.

Solution: Go to the properties window and set a custom value in the Height and Width property of the layout panel.

Symptoms: An rdf file is not loaded in Silverlight Viewer.

Cause: You have to modify the setting of IIS Express to allow an rdf file to load correctly.

Solution: There are two ways to resolve this issue.

Open a Command Prompt window. Navigate to the IIS Express installation folder (the default location of this folder is C:\Program Files\IIS Express) and run the following command.

appcmd set config /section:staticContent /+[fileExtension='.rdf',mimeType='application/octet-stream']

The other one is to modify the IIS Express configuration file.

1. In your local folders, find the IIS Express configuration file (the default location is C:\Users\[username]\Documents\IISExpress\config\applicationhost.config).
2. Using Notepad, open the file and find the configuration/system.webServer/staticContent element.
3. Add the following content to the staticContent node.

   Paste inside the IIS Express configuration file to the staticContent node	Copy Code
   <mimeMap fileExtension=".rdf" mimeType="application/octet-stream" />

4. Save the IIS Express configuration file.

Symptoms: When running the WPF browser application, the TargetInvocationException occurs.

Cause: The WPF browser application does not support Partial Trust.

Solution: Make sure that the WPF browser application uses Full Trust. To do that, in the Visual Studio Project menu, go to YourProject Properties and on the Security tab, under EnableClickOnce security settings, select the option This is a full trust application.

Cause: The report is not being disposed of properly. The incorrect syntax is as follows.

//Incorrect!                
rpt.Dispose();
rpt=null;

'Incorrect!
rpt.Dispose()
rpt=Nothing

Solution: The correct syntax for disposing of a section report is as follows.

//Correct!
rpt.Document.Dispose();
rpt.Dispose();
rpt=null;

'Correct!
rpt.Document.Dispose()
rpt.Dispose()
rpt=Nothing

Cause: Large reports in an ASP.NET application can easily use up the 60% of memory allocated to the ASP.NET worker process by default, which produces an error. In Machine.Config, MemoryLimit specifies the maximum allowed memory size, as a percentage of total system memory, that the worker process can consume before ASP.NET launches a new process and reassigns existing requests.

Solution: Set the CacheToDisk property of the document to True.

This caches the report to disk instead of holding it in memory. This setting is also detected by the PDF Export, which follows suit, but any other exports still consume memory. Although it is not advised, the ASP.NET worker process memory allocation can also be changed in your Machine.Config file, which is located in a path like: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Config\. Search the Machine.Config file for memoryLimit, which is located in the processModel.

Cause: In some cases, very large reports can consume so much memory that the report never finishes processing. Some of the things that can cause this include:

1. Many non-repeating images, or a high resolution repeating image
2. Instantiating a new instance of a subreport each time the format event of a section fires
3. Using a lot of subreports instead of grouping with joins in the SQL query
4. Pulling in all of the data when only a few fields are needed (e.g. Select * from db instead of Select First, Last, Address from db)

Solution: In cases where the report is too large to run any other way, the CacheToDisk property may be set to True. This property should only be used when there is no other way to run the report to completion. Before resorting to this method, please see the Optimizing Section Reports topic.

Cause: If inflated memory usage is seen in the Task Manager it is not necessarily in use by the code. Task manager indicates the current "working set" of the process and, upon request, other processes can gain access to that memory. It is managed by the Operating System.

Solution: For an example of some working set behavior anomalies (which are considered normal), create a WinForms application and run it. Look in Task Manager at the working set for that process (it should be several megabytes), then minimize and maximize the form and notice that the working set reclaims to <1MB. Obviously, the code was not using all that memory even though Task Manager showed that it was allocated to that process. Similarly, you'll see ASP.NET and other managed service processes continue to gradually grow their working set even though the managed code in that process is not using all of it. To see whether this is the case, try using the two lines of code below in a button Click event after running the project.

System.Diagnostics.Process pc = System.Diagnostics.Process.GetCurrentProcess();
pc.MaxWorkingSet = pc.MinWorkingSet;

If that reclaims the memory then the Operating System trimmed the working set down to the minimum amount necessary and this indicates that the extra memory was not actually in use.

Symptoms: The WebViewer will not automatically print a report without displaying it.

Cause: Only the new FlashViewer ViewerType of the WebViewer offers this functionality.

Solution:

1. Set the ViewerType property to FlashViewer.
2. Expand the FlashViewerOptions property, and expand the PrintOptions subproperty.
3. Under the PrintOptions subproperty, set the StartPrint property to True.

Symptoms: When using Internet Explorer and Acrobat Reader to view a page containing a WebViewer in PDF mode, the resulting PDF always opens in a new window.

Cause: Acrobat Reader is only available in a 32-bit version. When the 64-bit version of Internet Explorer is used, it opens up an instance of the 32-bit version of Internet Explorer so that the plug-in and the PDF can load, rendering the resulting PDF in a new window. 

Solution:

• Install a PDF reader plug-in that is 64-bit compatible.
  OR
• Use the 32-bit version of Internet Explorer.

Symptoms: The report in the HTML viewer type does not look exactly like the other viewer types.

Cause: The HTML format is not WYSIWYG. It does not support the following items:

• Line control
• Control borders
• Shapes (other than filled rects)
• CrossSectionBox and CrossSectionLine controls
• Overlapping controls

Solution: Try to avoid using the above items in reports which are shown in HTML format.

Symptoms: In the WebViewer, reports render correctly with the HTML ViewerType but they show up blank with the AcrobatReader ViewerType on the production web server.

Cause: .ArCacheItem is not set up in your IIS extension mappings.

Solution:

1. From the Start menu, choose Control Panel, then Administrative Tools, then Internet Information Services.
2. Right-click your Default Web Site and choose Properties.
3. On the Home Directory tab, click the Configuration button.
4. On the Mapping tab, check the Extension column to see whether .ArCacheItem appears. If not, click Add.
5. In the Add/Edit Application Extension Mapping dialog that appears, click Browse and navigate to (Windows)\Microsoft.NET\Framework\v2.0.50727 or v3.0 or v3.5.
6. In the Open dialog, change Files of type to Dynamic Link libraries (*.dll).
7. Select aspnet_isapi.dll and click Open.
8. In the Extension textbox type .ArCacheItem.
9. Click the Limit to radio button and type GET,HEAD,POST,DEBUG.
10. Ensure that the Script engine check box is selected and the Check that file exists check box is cleared.
11. Click OK.