You’re offline. This is a read only version of the page.
We just finished our year-end upgrade and user is reporting MEM_BAD_POINTER error when trying to print. The GP install is on a Windows Server 2003. I found the below solution on a previous post, but that didn't appear to be after an upgrade. Does the year-end make any changes to the Reports.dic file that need to stay in place, or can I restore back to the Reports.dic from before the year-end upgrade?
"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!"
*This post is locked for comments
I have the same question (0)
I followed these instructions from another post here, which cleared the error and reports are now working.
"Tools->Customize->Customization Maintenance. Use this screen to export all of your modified reports to a package file. Mark all of the reports to be exported. Then exit GP and rename REPORTS.DIC. If you use a shared REPORTS.DIC make sure everyone is out of GP. Then Tools->Customize->Customization Maintenance and import the package file. This will rebuld the REPORTS.DIC."
Share
Report
All responses (
Answers (
1