Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you print or print-preview a report in Microsoft Dynamics SL: "System Message 7011"

Error message when you print or print-preview a report in Microsoft Dynamics SL: "System Message 7011"

View products that this article applies to.

Symptoms

Consider the following scenario. You print or print-preview reports in any one of the following modules:
  • Purchasing in Microsoft Dynamics SL
  • Order Management in Microsoft Dynamics SL
  • Inventory in Microsoft Dynamics SL
  • Time and Expense for Projects in Microsoft Dynamics SL


When you take this action, you receive one of the following series of error messages:

Series 1:
System Message 7011- ROI Get RIPARAM failed for CRPERC. Error=.
After you receive this message, you receive the following error message:
System Message 7011- ROI Get RIPARAM failed for CRPEMSGCNT. Error=.
See Cause 1, 2, 3, and 4.

Series 2:
CRPEHLPR MFC Application has encountered a problem and needs to close. We are sorry for the inconvenience.
Followed by:
System Message 7011- ROI Get RIPARAM failed for CRPERC. Error=.
Followed by:
System Message 7011 - ROI Get RIPARAM failed for CRPEMSGCNT. Error=.
See Cause 5.


Series 3:
Microsoft Visual C++ Runtime Library Runtime Error! Program: The application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information.
Followed by:
System Message 7011- ROI Get RIPARAM failed for CRPERC. Error=.
Followed by:
System Message 7011 - ROI Get RIPARAM failed for CRPEMSGCNT. Error=.
See Cause 6.


↑ Back to the top

Cause

This problem occurs for one of the following reasons.

Cause 1

The Data Execution Prevention (DEP) feature blocks some files from successfully running when Microsoft Dynamics SL or Microsoft Business Solutions - Solomon program files are on a computer that is running one of the following operating systems:
  • Windows Server 2008 or Windows Server 2008 R2
  • Windows 7
  • Windows Server 2003 with Service Pack 1 (SP1)
  • Windows Vista with Service Pack 1 (SP1)
  • Windows XP Professional with Service Pack 2 (SP2)

Cause 2:

There are corrupted records in the Microsoft Dynamics SL application database or in the Microsoft Business Solutions - Solomon application database.

Cause 3:

The Capicom.dll file was registered incorrectly.


Cause 4:

Microsoft Dynamics SL uses Crystal Reports 10. This version of Crystal Reports is an upgrade from an earlier version. Therefore, some program settings are no longer compatible.

Cause 5:

This problem occurs because there is a supression formula on a subreport that is associated with the report that you are trying to print.

Cause 6:

The MSDSL application role or the E7F575915A2E4897A517779C0DD7CE SQL user is not synchronized correctly with the Microsoft Dynamics SL databases. Or, both the role and the user are not synchronized correctly. This situation can occur if the following conditions are true:
  • You select the Synchronize All Ownership and Security update scenario in the Database Maintenance (98.290.00) screen and the Database Maintenance (98.290.00) screen is from an earlier version of Microsoft Dynamics SL.
  • You run the update scenario on any database that exists on the same instance of SQL Server as a Microsoft Dynamics SL 7.0 database.

↑ Back to the top

Resolution

To resolve this problem, use the appropriate resolution.

Resolution 1


Set the Data Execution Prevention feature to enable the Crpehlpr.exe file and the Roi.exe file to run. To do this, follow these steps:
  1. Right-click My Computer, and then click Properties.

  2. In Windows Server 2003 or Windows XP, click the Advanced tab. In Windows Vista, Windows 7, or Windows Server 2008, click the Advanced system settings link.
  3. In the Performance section, click Settings.

  4. On the Data Execution Prevention tab, click Add.

    Note The default option is Turn on DEP for all programs and services except those I select.
  5. Browse to the Microsoft Dynamics SL program installation directory or the Microsoft Business Solutions - Solomon program installation directory. If you have an additional drive that is a mapped drive to this installation directory, you must add the file through both paths.

    For example, you install Microsoft Dynamics SL 7.0 to the following folder:
    C:\Program Files\Microsoft Dynamics\SL\Applications
    On the same computer, you map the S drive to the following folder:
    C:\Program Files\Microsoft Dynamics\SL
    When you follow this step, you must add the files by using both of the following paths:
    • C:\Program Files\Microsoft Dynamics\SL\Applications\
    • S:\Applications\
  6. Locate and then click to select the following file:
    Crpehlpr.exe
    .
  7. Click Open, click Apply, and then click OK.
  8. Repeat step 1 through step 7 for the Roi.exe file.

Resolution 2


Delete the corrupted records from the Microsoft Dynamics SL application database or from the Microsoft Business Solutions - Solomon application database. To do this, follow these steps.

Note Before you follow the instructions in this article, make sure that you have a complete backup copy of the database that you can restore if a problem occurs.
  1. Make sure that all Microsoft Dynamics SL users or all Microsoft Business Solutions - Solomon users are logged off.
  2. Start Microsoft SQL Query Analyzer. Or, start Microsoft SQL Server Management Studio.
  3. Connect to the appropriate Microsoft Dynamics SL application database or to the Microsoft Business Solutions - Solomon application database.
  4. Run the following statements. 
    Delete from Roidetail
    Delete from Rptcompany
    Delete from Rptruntime

Resolution 3


To resolve this problem, manually register the Capicom.dll file. To do this, follow these steps:
  1. Locate the Capicom.dll file on the local computer. By default, this file is in the following folder:
    SystemDrive:\Windows\System32
  2. Verify that the version of the Capicom.dll file is 2.1.0.1 or a later version. To do this, follow these steps:
    1. Right-click the Capicom.dll file, and then click Properties.
    2. On the Version tab, verify that the file version is 2.1.0.1 or a later version.
    3. Click OK.

  3. Right-click the Capicom.dll file, and then click Open With.
  4. In the Windows dialog box, click Select the program from a list, and then click OK.
  5. In the Open With dialog box, click Browse.
  6. Locate, and then open the following folder:
    SystemDrive :\Windows\System32
  7. Double-click the Regsvr32.exe file, and then click OK.
  8. Click OK when you receive the following message:
    RegSvr32 - DllRegisterServer in SystemDrive:\windows\system32\capicom.dll succeeded.
Note If you experience the"System Message 9827" error message on any workstation computerbefore you register the Capicom.dll file, you must rerun Synchronize All Ownership and Security update scenario in the Database Maintenance (98.290.00) screen.

Resolution 4:


To resolve this problem, select the No Printer check box in the report file in Business Objects Crystal Reports. To do this, follow these steps:
  1. Open Crystal Reports, and then click the report file to open it.
  2. Click File.
  3. Click Printer Setup.
  4. Click to select the No Printer check box, and then click OK.
  5. Click Save.

Resolution 5:


Change the report in Business Objects Crystal Reports to remove the suppression on the subreport.
  1. In Business Objects Crystal Reports, open the report file that is producing the error.
  2. If there is a subreport within any section of the report, right-click the subreport. Note: If there is no subreport, this resolution will not work.
  3. Click Format Sub-Report. The Suppress Formula button that appears should contain red text. The presence of this red text indicates that there is a suppression formula. When the formula uses variables from the parent report, the variables must be removed. Notes
    • If you do not receive indication that a suppression formula exists, this resolution will not work.
    • If the suppression formula uses a combination of subreport variables and parent report variables, these variables must be separated so that the parent report variables can be removed.
    • If the section that contains the subreport also contains other displayed variables, the variables must be separated.
    • If the section that contains the subreport already has a suppression formula, you must decide whether to merge the formulas and how to do this.
  4. Click Suppress Formula to open the Format Editor dialog box, and then click Select All on the Edit menu.

    Notes: If the suppression formula uses only variables from the subreport, this workaround will not work.
  5. On the Edit menu, click Copy to copy the formula.
  6. Delete the formula.
  7. Click OK to close the Format Editor dialog box.
  8. Right-click the left section of the screen where the subreport appears, and then click Section Expert.
  9. In the Section Expert dialog box, click Suppress Formula, and then click Paste on the Edit menu to paste the formula.
  10. Click Save and Close, and then click OK.
  11. On the File menu, click Save.

Resolution 6:

Click here to view or hide detailed information

Synchronize the user. To do this, follow these steps:
  1. Use SQL Server Management Studio to run the following statement against the Microsoft Dynamics SL system database: 
    DELETE FROM RPTExtra
  2. Select the Synchronize All Ownership and Security update scenario in the Database Maintenance (98.290.00) screen, and then click Begin Processing.

↑ Back to the top

Keywords: kbexpertiseinter, kbexpertisebeginner, kbfreshness2007, kbmbspartner, kberrmsg, kbmbsmigrate, kbprb, kbmbspilot, kb

↑ Back to the top

Article Info
Article ID : 905595
Revision : 1
Created on : 1/7/2017
Published on : 4/24/2012
Exists online : False
Views : 411