You’re offline. This is a read only version of the page.
285
Hi,
We have a client that has Seagate Crystal report - VBA customization . The customization was develop when the client was still under GP 6.0. The customization was then upgrade together with GP 9.0 and it worked on all existing machines. When we tried to install the customization on a newly bought Windows XP SP2 machine with GP 9.0 SP2 install, the crystal report customization does not work. Everytime we import the package, we do get error message "Object not Found 414" the missing object tends to be Crystal32.ocx. Due to this, the customization did not work. We already tried to copy Cystal32.ocx and Crystal32.oca to the System32 folder and manually register it. However, the same error message received when we re-import the file.
Eventually, we tested the customization package on a test machine with Windows XP SP3 installed. We imported the customization package and it worked without any errors. The seagate crystal report generate ran very smooth and we did not encounter error thereafter.
And so we had the new workstations to have Windows XP SP3 installed ( since all of them are in SP2). When we import the customization package, it work successfully as expected. The client never tested the standard reports or even other modified reports in after SP3.
Apparently, after a couple of weeks, the client reported that they are getting the "SmartHeap Library" "MEM_BAD_Pointer". They are getting this error while trying to print Standard as well as Modified Report. We can't figure out what went wrong.
It is so strange since we never get this error our test machine and on my machine. All the standard and customized reports worked under Windows XP SP3.
Now we can't seem to determine why this is happening.
Really appreciate any inputs.
Thanks in advance!
~abc~
*This post is locked for comments
Hi ~abc~,
I assume that you've disabled all automatic Windows Updates on this Windows XP machine, as well as any other side products that might get updates.. XP isn't supported anymore, so chances are that there aren't any updates pushed to the system.
VBA can be very tricky to troubleshoot, as it's having ties in many libraries in the system, not just GP. Not so long ago Microsoft had pushed some office updates to windows, and suddenly some GP clients using VBA code stopped worked or were crashing randomly.
You're client is well aware that they are running their system on a completely un-supported GP & Windows version, and it such cases it's hard get any support from Microsoft anymore, as they are long past due even extended support..
May I ask what those VBA Customizations are doing in conjunction with the GP built-in reports ? what was the purpose of the VBA code ?
Could those Crystal reports be re-written ? what about the GP version ? is the client still under active maintenance contract? could they upgrade their GP to the latest build ?
I could only recommend to contact Victoria Yudin as she sells an add-on product for GP called "GP Report Viewer" on her site : http://www.flex-solutions.com/
The product allows for Crystal Reports integration into GP forms to replace existing built-in reports seamlessly, so the users don't have to deal with external tools. She might be able to help you with troubleshooting the issue.
Great responses from the Community. Let us know how it goes.
[quote user="Jimmyg2k"]
I am glad to hear this. could you please post the steps to restore the file? I think, it would be helpful for others.
Thank you.
[/quote]
OK, so simply restoring the file was not enough. It did clear up the MEM_BAD_POINTER error, but upon running a different report, we had another error accessing SQL data. So... To fix this what I did was remove the report.dic file. Then I went into GP, and went to tools, report writer. There were no custom reports, which was good this means the report.dic file is blank. Then I Imported the previous/existing report.dic file from another location, this re-created the report.dic file, and this allowed us to run all of our reports, and all worked great!
[quote user="Jimmyg2k"]
I am glad to hear this. could you please post the steps to restore the file? I think, it would be helpful for others.
Thank you.
[/quote]
I would assume that each instance would be different. It all depends on how each performs their backup, and how each would restore from this backup. I located the reports.dic file on my server (The one on the workstation/client was unchanged) I found that it was on drive x, folder y...
I made a copy of the existing reports.dic file, named the copy reports_old.dic, then I used my backup software to restore the file from a time when all was working, I specified to overwrite the existing file in the backup software, and after the file was restored from tape, I verified the modified time was from a time previous to the problem, that was it, all worked as expected. Once I verified that all was working I deleted the reports_old.dic file that I created prior to restoring the file from tape, as it is no longer needed.
My problem may not have been specifically SP3 related, we did an update to GP for year end stuff, and that is what created our issue, but here are the steps I followed, and the error message I had was almost identical to the begining of this post, which is what drew me here in the first place. This post helped me to solve my issue, so if anybody is running GP 10, and doing year end updates, and you get an error like the one here, replacing the reports.dic file with a pre-update version will work.
I heard the error occurs due to a corrupted 'Reports.dic' file. Does anybody know how to repair or recreate Reports.dic?
Also, search in
https://mbs.microsoft.com/knowledgebase
https://support.microsoft.com/search
Have a question- if you are already on SP3, and still having the error- what would be suggested to do?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (