Crystal Reports | Schulz Consulting

Slow Crystal Reports for Sage 100 ERP Startup: Solved

April 3, 2014 by Wayne Schulz

We’ve heard several reports from Sage 100 ERP end users and consultants that Crystal Reports XI may take upwards of 2-3 minutes to load initially onto their desktop. After much hunting around it’s been determined that the culprit is an option hanging off the Crystal Reports help menu titled “Check for Updates On Startup”.

Simply navigate to Crystal Reports – select the Help menu and UNCHECK the “Check for updates on startup”.

Your Crystal Reports XI should startup significantly faster from your desktop or if clicked from within Sage 100 ERP Custom Reports or Forms.

Error 1904 commonobjmodel.dll failed to register – HRESULT -2147023898 When Installing Sage 100 ERP (SOLVED)

January 22, 2014 by Wayne Schulz

Several of our consultants ran into this particularly nasty installation bug. We’re not 100% sure why the problem occurs though some speculation is that Windows Server 2003 Small Business could be a major contributor.

Sage 100 Installation Issue:

Error 1904 while installing Sage 100 ERP 2013. This appears to occur during the install/registration of Crystal Reports runtime files and/or DLLs.

Note: Installing the full version of Crystal Reports may appear to complete but the program might not start up.

Resolution:

There can be many causes to this – from the simple (insufficient user rights) to the more complex (conflicting copies of DLL files). Here are several things you can try along with the solution that ultimately worked for two of our consultants in two separate installations.

Although this could be a rights issue there is some indication that it may also be caused by .NET issues or one of the prerequisites failing to load or otherwise conflicting.

Also be sure anti-virus is off and you are installing as administrator

Caution: This has been an especially troublesome issue. Sage has had some difficulty resolving this and on some level it seems like Server 2003 SB might lend itself to the issue through reported non-standard management of DLLs.

Open a case with Sage sooner rather than later.

SOLUTION :

Link: 1534393 – “Error 1904. Module C:\Program Files\SAP BusinessObjects\..\dtsagent.dll failed to register …” when installing Crystal Reports for Visual Studio 2010 MSI runtime

1. Search your system for all instances of cryptocme2.dll.

2. Rename cryptocme2.dll files you find to something like *.org

3. Do NOT rename the cryptocme2.dll files you find the in the subdirectories of C:\Program Files (x86)\SAP BusinessObjects

4. Install the Crystal Reports runtime (CRRuntime_32bit_13_0.msi).

5. Rename cryptocme2.org files back to cryptocme2.dll.

6. The issue is resolved in Service Pack 1 for CRVS2010

7. NOTE – there is one exception;

8. The system environment variable “R_SHLIB_LD_LIBRARY_PATH” can not be overwritten and thus steps above must be applied.

If The Above Does Not Resolve The Issue – Try These Suggestions:

Try loading the .NET 3.5 and C++ prerequisites from the install disk (there’s a folder labeled prerequisites)

Try running this repair utility for .NET

http://www.microsoft.com/en-us/download/details.aspx?id=30135

Instructions:

http://support.microsoft.com/kb/2698555

How to increase the number of dynamic parameters in Crystal Reports

October 30, 2013 by Wayne Schulz

There is a limit to Crystal Dynamic parameters. The limit is 1000 items, which may not be enough if you need all of your inventory items in a report selection criteria field.

Here’s how to change the limit:

Important: As with any changes to the system registry – do so at your own risk and have a backup. Incorrect changes may render your computer or applications inoperable.

Crystal Reports 2011

1. Create a registry key HKEY_HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\DatabaseOptions\LOV.
2. Add a string value “MaxRowsetRecords” and set the value to the maximum number of values that you desire for your report. For example, a value of 2000 will return up to 2000 values in the lowest level of a cascading parameter.
3. After making changes to the registry, restart the affected service or application as required.
NOTE: the registry key on 64 bit Operating Systems is:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\Crystal Reports\DatabaseOptions\LOV

What versions of Crystal Reports are supported by Sage ERP MAS 90 or 200?

January 23, 2011 by Wayne Schulz

What versions of Crystal Reports are supported?

1. MAS 4.40 – Crystal Report 11
2. MAS 4.30 – Crystal Report 10
3 MAS 4.20 – Crystal Report 10
4. MAS 4.10 – Crystal Report 10
5. MAS 4.05 – Crystal Report 8.5
6. MAS 4.00 – Crystal Report 8.5
7. MAS 3.71 – Crystal Report 8.5
8. MAS 3.70 – Crystal Report 8.5
9. MAS 3.61 – Crystal Report 8.5
10. MAS 3.60 – Crystal Report 8.5
11. MAS 3.51 – Crystal Report 8.0
12. MAS 3.50 – Crystal Report 8.0

Note: MAS versions below 3.71 are no longer supported by Sage.

Use of an incorrection version will render forms and reports that are used by the Sage ERP MAS 90 or 200 program (ie – Check Printing, Invoices, Custom Reports, Canned Reports) unusable though the report may appear to function properly outside of the MAS system when run straight through Crystal. There is no way we’ve yet seen to reverse changes made in a higher version of Crystal and save the form to a lower version.

Be sure you work with the proper version of Crystal Reports.

via: Sage KB Resolution ID 513325

How to export a long fixed length string in Crystal Reports

September 16, 2009 by Wayne Schulz

Have you ever tried to create a fixed length export file with Crystal Reports? These are typically files you create to send to some third party like a bank. They’ll give you a fixed length record layout and tell you where each field should go and how long it must be.

Everything works well so long as you don’t have a super long length of text.

Well today I had a client that wanted to export a fixed length line of text that was 200 characters long. Crystal Reports wouldn’t export to text without wrapping the line which would have been a problem for the bank to read.

Exporting to a text file via Crystal Reports appears to have a hard limit of a certain size width that’s keyed into how wide the paper is as defined by your printer..

Smaller fonts can combat this to some extent but in my experience not completely.

Some suggestions were to shrink fonts (works to the extent that the fonts can be made small enough) and try different printer drivers that may support larger paper widths (not all drivers support larger paper and it can be a pain to install and maintain a standard printer driver on every machine).

Here’s what ultimately worked for me to export a very wide Crystal Report to text:

Within Crystal Reports 10 – Instead of selecting txt as the export source I selected “record style columns no space” and checked off both “same number style as in report” and “same date formats as in report”

Have not fully tested against the bank yet but appears ok in the WordPad preview.

Sage 100 Installation Issue:

Resolution:

SOLUTION :

If The Above Does Not Resolve The Issue – Try These Suggestions:

Crystal Reports 2011

Contact Us