Copy the file from the server to your workstation and try it. Alternatively move to another workstation with QB and try to open the file on the server. Its a program problem from what I've read on QB message boards and not one I've seen Intuit address.
- I can access the sample data file using my workstation whether or not the data file is located on the workstation or server.
- I /can't/ access the live data file using my workstation whether or not the data file is on my workstation or on the server
- I can access the data file on the server from QB installed on another workstation.
The thing is the QB software has been stable for months so something recent has upset it - and all I know is it is just one pc and one data file
So I'm still struggling to find a solution.
=========================== You can try pulling & re-inserting the memory module(s). It could be a hardware issue for you. If you aren't familiar with playing inside the box get someone who is to help you.
If that doesn't fix the problem then swap memory modules with another workstation (using the same type of memory) to see if that works. If it does then trash your old memory & buy new.
If you uninstall & reinstall again, make sure you reboot after the uninstall. Manually delete any residual program files/folders under Program Files then reboot again before reinstalling QB.
There is a free memory test utility called memtest86 available here:
formatting link
The QB sample files are very small, so it is quite possible that your actual QB data file has grown to a size that is causing your system to attempt to access a rarely used portion of RAM that is bad.
I doubt jiggling the modules will help, but one may need replacing.
Note that OP is using QB2005, which doesn't have the more efficient memory usage of an SQL DB engine like QB2006 and up. His workstation is going to be pulling that whole data file from the file server, and it will get cached locally.
I understand you're being your occasional cynical self, but in this instance it is perfectly possible that bad memory is the case, especially if it is a large data file. System caching of a large data file can cause normally unused upper reaches of RAM to be utilized, which can expose a bad memory sector.
For instance, about a year ago I had a situation where a server would crash everytime a large file was copied from it to any other system. But it ran for months on end as long as this wasn't done. All the errors seemed to indicate a failure somewhere in the disk system. But it turned out to be a bad RAM module which was found by memtest86.
It could be some other hardware or OS problem as well, but a good memory test is a place to start in this case.
Because you forgot the most important thing when asking for free advice on a newsgroup. You forgot that its a newgroup and anyone that walks crawls or slithers on their belly will give you bullshit answers. There is nothing wrong with your physical memory. The QB data file is currupt and must be fixed.
I stand corrected. If the OP jiggles his memory module the problem will go away. I guarantee it.. The bad memory is probably memory that only QB uses and not other applications etc.
I wouldn't go buy new memory until you verify that's the problem. Swapping memory from another machine would be a good test if you can do it.
It should. IME memory problems start as hiccups and quickly snowball into bigger things.
If you can use the memory hog known as Photoshop successfully then you may not have a hardware failure. We've all (except Allan) been trying to give you avenues to research in solving your problem. Hardware is a logical issue to address when you've already reinstalled the program and verified the file wasn't corrupted.
You might try uninstalling & reinstalling QB (again) and Quicken, doing a reboot after each task, and taking care to delete residual files left behind. You could also call Intuit but they'd probably have you doing these troubleshooting steps themselves so get them out of the way first.
Why do I receive the following error when using QuickBooks? The instruction at "0x004b0022" referenced memory at "#x########." The memory could not be "read."
Possible Cause: This error may be preceded by another error message and is typically caused by some form of data or list damage.
Answer: The amount of time to complete the following steps is unpredictable as it depends on the file size, transaction type, system resources, etc. It is best to perform these steps when you have time to allow them to complete.
Re-sort your lists:
Note: Re-sorting a list will return it to alphabetical order.
1.. From the QuickBooks Lists menu, select Chart of Accounts.
2.. If the Show All checkbox at the bottom of the Chart of Accounts window is active, ensure that it is selected. After re-sorting all lists, return the checkbox to its original state.
3.. Click Account (at the bottom of the Chart of Accounts window), and then select Re-sort List. Click OK to the Resort Lists message to proceed.
4.. Repeat steps 1 through 3 for each of the following lists:
a.. Item list b.. Class list (if you use classes) c.. Memorized Transactions list Note: Steps 5 through 8 will allow you to re-sort all lists that contain names. 5.. From the Banking menu, select Write Checks.
6.. Click the drop-down arrow in the Pay to the Order of field, and then press CTRL+L to open the Name list.
7.. Click Name (at the bottom of the Name List window) and select Re-sort List. Click OK to the Resort List message to proceed.
8.. From the File menu, choose Open Company, and then click OK. This will reopen your data file and load the re-sorted lists. Verify your data:
1.. From the File menu, choose Utilities, and then choose Verify Data.
2.. When the verify is complete, you will receive a message about the results:
a.. If you receive the message, "QuickBooks detected no problems with your data," your data is clear and you may resume your work with this data file in QuickBooks. If you continue to receive the error noted above, you can read and post messages relating to your issue on the Help & Support Message Boards. If you are still having difficulty after referencing all of our free support resources, please contact our Technical Support staff for one-on-one telephone support.
Please note that Intuit charges for some telephone support calls and services. The support engineer will inform you if there is a charge for the call after discussing your issue.
b.. If you receive the message, "Data has lost integrity," continue to the steps below. Rebuild your data file:
Important: Do not perform these steps on a data file that is on a network.
1.. If your company data file is located on a network drive, copy the data file to a local drive before rebuilding it.
2.. From the File menu, choose Utilities, and then choose Rebuild Data.
3.. Before running the rebuild utility, you are required to make a backup. Do not overwrite existing backups. Rename this backup to avoid overwriting an existing backup. Click OK to the backup message and then OK in the QuickBooks Backup window after you have renamed the backup.
4.. You will be notified when the rebuild is complete with the message, "Rebuild has completed."
5.. Verify your data again by choosing Utilities, and then Verify Data from the File menu.
6.. When the verify is complete, you will receive a message about the results:
a.. If you receive the message, "QuickBooks has detected no problems with your data," your data is clear and you may resume work with this data file in QuickBooks. Remember to copy the repaired file back to the original location if you are running QuickBooks on a network.
b.. If you receive the message, "Data has lost integrity," do not attempt to rebuild the data file again. Please contact our Technical Support staff for one-on-one telephone support. Please note that Intuit charges for some telephone support calls and services. The support engineer will inform you if there is a charge for the call after discussing your issue.
BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.