Crystal Reports | Schulz Consulting

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.

How to show country names on forms using older MAS 90 and MAS 200 versions

July 30, 2009 by Wayne Schulz

To create country code on MAS90 and MAS 200 forms:

Earlier versions of MAS 90 and MAS 200 (typically prior to version 4.10 or 4.20) did not allow for easy linking of the country code name to the code itself.

While the country code could be placed on forms (Sales Orders, Purchase Orders, Checks) – the name of the country was not as easy to place for a few reasons –mainly that the data file required to pull the name from was not readily linkable.

Below is a workaround solution that you may find useful. It is primarily for MAS90 or MAS200 (it works on both) versions prior to 4.1 – so if you are using a later version you probably don’t need this procedure because Sage has wisely added country name to the tables that your forms are using.

All steps below require using Crystal Report Writer – which is included with your Sage MAS90 or MAS 200 product disks.

These are not beginner instructions – and assume some intermediate level comfort with Crystal Reports. Backup all your

For this example, assume that we are going to create a form for the ship to and bill to codes. The same logic here with slight modification can apply to any form with a bill/ship field.

Note: Technical information on creating a Crystal Sub report that shares variables is available from:

NOTE: Unfortunately links below to Crystal Reports technical documents appear to have been broken since Business Objects was acquired by SAP.

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

1. Create a page header A that is above the main details (Note: It is important that this comes at the top of the page so that the shared variable calculates before the body of the report. If you do not put it at the top the whole thing doesn’t work). You will need to create a new header (Right click in the HEADER section area and select Insert Section Below. Once that section is created, right click on the section area again on the left side and select MOVE – then you can move it up).

2. Create a sub report for each Bill-To/Ship-To code. These will be placed into the page header created above.
a. Cty_ship
b. Cty_bill
c. Note: Link these back to the main table on the report. You’ll probably want to look in the Database – Visual Linking Expert to see what table is being used to hold your address information.

3. Within each of these subreports:

a. Create a formula as follows (Note: Vary the variable name depending on whether you are creating a bill to or ship to)

b. Place the above formula in the body of the subreport in the details section. Once on the report, right click the formula, select format field, then font, change the font to WHITE (or any shade that won’t show on the report)

c. Place the SY_Country.CountryName in the body of the subreport in the details section. Change the font to white so it doesn’t print on the final report.

d. Leave the Details section viewable – all other sections should be suppressed – ie headers/footers. (Note: If you suppress the details section this won’t work – so be sure to leave it viewable. The way to get around seeing the data on the report is to later change the font to white and make the field very tiny).

e. Make sure your subreport is linked from the SO1_SOEntryHeader.ShipToCountry to the SY_Country.CountryCode

f. When you’ve placed both sub reports into the header section you created above, right click on each subreport and de-select the “can grow” checkbox. (Note: If you do not remove the check you may get a “page size exceeded” message)

4. Within the main report create two variables
a. Country_bill
b. Country_ship

5. Now you can put this variable into your main report formula and the value from the subreport is carried over. The following is the example of it being worked into the @ship to address formula which is standard in the Sage SO Order and Invoice form.

6. Sample formula which has been modified with the new variable.

7. Important: Place the new variables onto the report in the main header section (NOT the sub report) – you can make the white fonts so they don’t print. You must make them viewable (Cannot suppress or this does not work).

BACKGROUND NOTES ON THIS ISSUE:

Q: Client wants to display the Country Code in the forms (SO Orders, Invoices, Purchase Orders, Checks).

A: (Prior to version 4.1 and 4.2) There is no simple way to do this in MAS90/MAS200 — though there are two standard approaches.

The first approach to adding MAS90 country names on forms

Use Alias Tables — this would allow for a table to be used in a report more than once. You give each table an “alias” and it would then allow you to link it to separate fields. This would be needed for the Country Code field because it is potentially a different result for either the Bill To or Ship To.

The problem in MAS90 4.x+ with the Alias Tables is that there is a bug of some sort preventing them from linking to the SY_Country field. This is documented in the Sage KB with the workaround to use a subreport (an ok solution but the country name is impossible to properly line up since it is a free floating field).

The better solution is to use shared variables within the report. Basically this involves creating a new section (header) at the top of the report (important because the variable has to be created before the rest of the report). Then you declare the variables as shared and they can be read from the header on down to the main body.

I did this through the SO and it seemed to work.

Here is the link to the Crystal KB article showing how to create shared variables:

http://support.businessobjects.com/library/kbase/articles/c2007600.asp

On the subreport, you have to create a main subreport, a formula (put this on the subreport) and a shared variable (reference this on the main report).

In the main report you have to create a formula, call up the shared variable (see the Crystal KB for syntax) and then use it in the address formula. Do not forget to put the formula itself onto the form or the value won’t compute.

You want to make the font be white on white. Do NOT suppress and printing or the calculation does not work. If you make it very small you can hide it on the form.

IMPORTANT NOTE: This information is being made available “AS-IS”. Prior to making any changes on your system be sure you have a backup of all forms being modified.

Subsequent upgrades to MAS 90 or MAS 200 table structures may render some (or all) of these instructions obsolete. Sage may also fix bugs that we’ve referred to above. These instructions are meant to serve as a starting point for your own use – and not as a detailed step by step guide to resolving any particular issue. We take no responsibility for updating these instructions. We are not able to provide support (except for our own MAS 90 support clients) on implementing these instructions.