Regarding the Intuit Technical article of the same name, I have found that this issue is occurring if the path name includes an apostrophe. The QuickBooks file however may contain an apostrophe. After much testing I have only to change the folder name to have this work or fail. I get the same results using our server or a client desktop.
Eg: C:\O'Harra\O'Harra.qbw will give an error but C:\OHarra\O'Harra.qbw will not.
For what it's worth we are opening about 20 different QBX files, many of which are larger the 3MB stored on a Windows R2008 R2 server with deep file paths.
I also think that the bullet items in the articles "reasons" section should be more specific.
- What is a remote location (as opposed to bullet 2 network location)?
- Restore refers to QBB. I think this should read "Restore (QBB) or Convert (QBX)"
We are using QB 2019 Release R5P
Hi there, @RangerZ.
Glad to have you back here in the Community. I'm here to share some clarifications with fixing the error that you received.
The "Portable or Accountant's copy is being restored over the network" means that a copy is restored on a different computer where QuickBooks is not installed locally. You'll need to make sure that you have your own copy stored on the computer where QuickBooks is located to prevent this error.
Also, restoring .QBB file refers to the copy that will be deleted automatically once a backup copy is completely stored. For more details about this process, please refer to this article: Resolve error in reload.sql at line #####. Sybase message: the disk sandbox feature is enabled.
However, if the issue persists after trying these steps, I'd suggest reaching out to our Customer Care Team. They have the necessary tools to work with you to find out what exactly may be causing this issue.
To reach them:
Please let me know if I can be of additional assistance. I hope you have a wonderful week ahead.
Please try rereading my post. I am basing the post on the article you refer me to.
I find the article weak in details (we can disagree). This level of content is just not helpful to the less technical user.
We are a bookkeeping and tax company. I get files from clients and my issue was opening a specific file which we store in a folder that has an apostrophe in the path name.
The items cited in the article, and which you try to clarify are NOT my problem. Indeed we routinely store and open files over our network with no issue. If the path has an apostrophe it fails, network or not.
Hey there, RangerZ.
I appreciate sharing your thoughts about the content of the article provided by my colleague. This information will help us improve on how we present the steps to our users.
I’ll be sure to send your feedback directly to our Content Development Team so they'll look into this.
Since the issue only occurs for path with an apostrophe, I recommend getting in touch with our Technical Support Team for more in-depth troubleshooting. One of our phone specialists can use tools like screen sharing and double-check what’s causing the error message to show.
Let me know about how things go after contacting support. I want to make sure this is taken care of for you. Have a good one.
As a former software product manager this bug would probably lie at the bottom of my priority list.
As an IT manager it's easier and faster to just change the path name than deal with support (who generally can address process issues but seems lacking on technical ones).
As a user I would like to share with others a very specific failure scenario as opposed to the vague ones in the tech note. Visibility is my most important goal.
Thanks for getting back to us and sharing your thoughts about this issue. Allow me to help route you to our feedback page to let our Engineers know about your idea regarding the path name.
We always value your thoughts including the helpful ideas you want to share to our Product Developers. That said, you can send a report by going to the Help menu of your QuickBooks account. Then, choose Send Feedback Online and click the Bug Report.
I'll also make sure to send feedback to the appropriate channels for them to look into this further.
Should you have any other concerns, please let me know. I'll be around to help.