Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Error when printing PO
- Thread starter rsymonds
- Start date
Can you give us more details to work with?
What is the menu path you use to run this report?
Is this really a shortcut, or is this from the menu option?
Is this a standard Macola (Cobol) report (ugly single font like from DOS days) or is this an integrated Crystal report?
If this is a Crystal report of some sort, I suspect your problem will lie somewhere in reinstalling crystal reports. If you have crystal developer, you can open the problem report and under the help menu, you can see what dll's are being used in that report.
We have had similar problems with Macola ES 9.5. When we have a new computer with a first time install, we sometimes have to copy and reregister dll's.
What is the menu path you use to run this report?
Is this really a shortcut, or is this from the menu option?
Is this a standard Macola (Cobol) report (ugly single font like from DOS days) or is this an integrated Crystal report?
If this is a Crystal report of some sort, I suspect your problem will lie somewhere in reinstalling crystal reports. If you have crystal developer, you can open the problem report and under the help menu, you can see what dll's are being used in that report.
We have had similar problems with Macola ES 9.5. When we have a new computer with a first time install, we sometimes have to copy and reregister dll's.
RunMR2kReport indicates this is an ICR - integrated crystal report.
Are you running SQLor Pervasive?
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
Are you running SQLor Pervasive?
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
- Thread starter
- #4
Go to a command prompt and go to C:\program files\common files\macola shared, and enter this command:
for %1 in (*.dll, *.ocx) do regsvr32 /s %1
This will register all the .dlls and .ocxs in the directory. You may see error messages that certain dlls did not register. This is OK because not all dlls can be registered.
Then try your report again. Let me know if that works.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
for %1 in (*.dll, *.ocx) do regsvr32 /s %1
This will register all the .dlls and .ocxs in the directory. You may see error messages that certain dlls did not register. This is OK because not all dlls can be registered.
Then try your report again. Let me know if that works.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
- Thread starter
- #6
- Thread starter
- #7
crystalreporting
Instructor
Actually - it might.
Most of the folks I deal with don't use the integrated reports, but I have seen memory problems switching printers with XP SP3. I've seen the problem occur with ES and Progression installs and eventually discovered the problem was external to Macola.
We could replicate the problem by rebooting the workstation in question, opening a blank document in MSWord and trying to switch to a printer on the network. This would result in an 'out of memory' error. Removing SP3 fixed the problem.
Peter Shirley
Macola Consultant, PA and surrounding states.
Most of the folks I deal with don't use the integrated reports, but I have seen memory problems switching printers with XP SP3. I've seen the problem occur with ES and Progression installs and eventually discovered the problem was external to Macola.
We could replicate the problem by rebooting the workstation in question, opening a blank document in MSWord and trying to switch to a printer on the network. This would result in an 'out of memory' error. Removing SP3 fixed the problem.
Peter Shirley
Macola Consultant, PA and surrounding states.
- Thread starter
- #9
I think this is the same problem I had, try this:
Fresh client installs of 7.6.400b forget to install the C:\windows\crystal or C:\winnt\crystal directory depending on your windows version. Copy the "Crystal directory under c:\windows or c:\winnt from a pre 7.6.400b workstation to the new workstation. Existing clients upgraded to 7.6.400b work because they already had the Crystal directory installed.
Fresh client installs of 7.6.400b forget to install the C:\windows\crystal or C:\winnt\crystal directory depending on your windows version. Copy the "Crystal directory under c:\windows or c:\winnt from a pre 7.6.400b workstation to the new workstation. Existing clients upgraded to 7.6.400b work because they already had the Crystal directory installed.
- Thread starter
- #11
rsymonds,
Did you try registering the files as I suggested?
Also try logging om to the workstation as the domain administrator and see if you still get the error.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
Did you try registering the files as I suggested?
Also try logging om to the workstation as the domain administrator and see if you still get the error.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
"What version of URGENT!!! are you using?
- Thread starter
- #13
I would suggest exporting the "HKLM\Software\Macola" registry key from another computer on the network where the report currently works. Take this exported .reg file to one of the new computers, launch the reg file, confirm your action, and then try to open Macola and run the report again.
Ever since 7.6.400 I have seen this come up from time to time due to problems with the new installer. The keys that don't get updated and will sometimes be the cause of these errors are the keys that maintain the mapped drive letter to Macola.
Scott Travis
Ever since 7.6.400 I have seen this come up from time to time due to problems with the new installer. The keys that don't get updated and will sometimes be the cause of these errors are the keys that maintain the mapped drive letter to Macola.
Scott Travis
- Status
Similar threads