When trying to print a Crystal report from Dynamics Report Manager (DRM) on Microsoft Dynamics GP (GP) Version 8.0 or 9.0, you receive the following error message:
Error 429: ActiveX component can’t create object.
The error message indicates the DRM Launcher for Crystal Reports has not been installed on the workstation you are trying to print the report from.
The DRM Launcher for Crystal Reports will need to be installed on each workstation you wish to print reports from. These are the steps to follow to install the DRM Launcher for Crystal Reports:
- Verify you are on the following versions:
- Dynamics Report Manager on Microsoft Dynamics GP versions 8.0 or 9.0.
- Crystal reports versions 9, 10, or 11
- If you are not on the above versions for Dynamics Report Manager and Crystal reports, contact Rockton Software Support.
- If you are on one of the above versions for Dynamics Report Manager and Crystal reports, continue with the step 4.
- Have all users exit the system.
- Make a complete restorable backup of the databases and a backup of the GP application folders for the workstations that have DRM installed on them.
- Then on each workstation that has DRM installed on it, do the following:a. Part 1:
- Download the Dynamics Report Manager Launcher for Crystal Reports 9, 10, and 11 (part 1 of 2) – ONLY for GP 9.0 and Great Plains 8.0! from our Product Downloads page.
- Copy the DRMLauncherCR11SetupC.exe file into the GP application folder.
- Right click on DRMLauncherCR11SetupC.exe file and click Run as Administrator, and then run through the Dynamics Report Manager Launcher.
b. Part 2:
- Download the latest build of DRM for the version of GP you are on. Or, contact Rockton Software Support for the Product Downloads for the specific build of DRM that you are currently on.
- Extract the contents of the build into the GP application folder.
- Right-click on the GP shortcut, select Run as Administrator.
- Choose Yes to include new code.
- Log into the company as sa.
If the above steps do not fix the error message, the message may be caused by an old MSVBVM60.dll file. In this case, you will need to do a complete search on the workstation to find all of the MSVBVM60.dll files. Right click on each file to find the most recent file and then override the older MSVBVM60.dll files with the most recent version of the file.