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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Application Error: Memory could not be read

Status
Not open for further replies.

TerryH

MIS
Oct 23, 2000
13
US
We have a program (InfoReports)loaded on one Win2000 PC that get's the error message:
PROREPNT.EXE-Application Error
The instructiion at (memory address)referenced memory at (memory address). The memory could not be read.

This happens the second time the application is opened.
The first time you open the app each day it works fine, but the second time you open it, you get the message.

Any advise is appreciated.
Terry Houchins
Fujikoki America
Dallas Texas
 
This application is not release the Memory locations it took when it start ,, So You have to Restart after finishing work with it each time before you can use it again ..
May Be it's a bug in the Software ! Eng.Mohamed Farid
Cisco Certified Network Associated ,,
Building Cisco Remote Access Network Certified ,,
Routing Cisoc Networks Certified ,,
Switching Networks Cisco Cerified ,,
 
We thought at first that might be what was happening but the software company say's that it is a Microsoft issue.

Terry in Texas
 
Send To support@Microsoft.com ,, But you have to send the Error Number and the Exact numbers in the Error dialog ..

But I still saying that the Software has some problem ! Eng.Mohamed Farid
Cisco Certified Network Associated ,,
Building Cisco Remote Access Network Certified ,,
Routing Cisoc Networks Certified ,,
Switching Networks Cisco Cerified ,,
 
Terry,

This will be a tough one to track down to a specific cause. I just spent several hours working on the same issue today with another program. Go to Google and type in "memory could not be read" (include the quotes) and you'll find lots of references, most involving Win2K, with many different solutions. Our problem was resolved by reinstalling the DCOM and MDAC updates from MS. Go through the hits on Google and see which solutions seem to fit your situation. Hopefully you'll find one that does the trick. Good luck, and let us know if you get it fixed. ------------------------
Doug J.
Winchester, VA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top