You’re offline. This is a read only version of the page.
1,491
Hi All,
Anytime the hq client tries to synchronise with HQ I get this error message" not enough storage available to complete this operation (Unhandled error, state=9)
Please help
*This post is locked for comments
Hi Michael
Thanks for the response. I have tried setting the FromTime back to where they last uploaded and I've also tried running it for the current time. For some weird reason it wants to upload all the Journals again as well as a few other tables like the Item table. I have sorted through the dates for the Journal table and found nothing out of the ordinary. So far each of the stores have uploaded all of their Journals after changing the collation and clearing the DatabaseMetaData table, but only the two biggest stores that have been running the longest as well have gotten this error.
There is more than enough space and the databases are set to growing dynamically. I have also tried to reindex both the store and HQ databases.
I haven't tried restarting the HQ SQL server though and will try that tonight.
Another quick question though, do you think it will help if I send 101 (Synchronise Store DB) worksheet? Would that allow store to see what it has sent and what not?
Thanks again
Hendré
Henndre,
What is the FromTime date set to on the 401 worksheet, check, it’s possible its set to an earlier date eg 01/01/1900, so it will pull data from that date making the data very huge
Secondly, it’s possible there is a bad date in one of the transaction which is possible if the PC went off resetting the BIOS system time, identify and correct the date and try synchronizing again
Thirdly check the database size both the .mdf and the log file to see if there is enough space (You can check this from Administrator, go to Database -> Properties-> % Usage)
You can also restart both the store and the HQ SQl servers to clear the Temp tables
Finally you can try Reindexing the HQ database from the HQ Administrator
All the best
Hi
We have a similar problem to you. HQ was down for about two weeks and now that its up and running again, we keep getting that "not enough storage available to complete this operation (Unhandled error, state=9)" error when we try to run a 401 worksheet. I must add that we changed the collation of both the HQ and Store database and had to clear the DatabaseMetaData table to get POS to work again.
So my question is, how can we get around that error and upload that data? I have thought about attaching the store database to a VPC and trying to upload it from the same server but that is quite a distance to drive so any other options would be welcome
Thanks in advance
Hendré
*Edit* It would appear that certain tables, like the Journals are being uploaded from the beginning while others like the Transaction table is just uploading what has been missed. Not sure if that makes a difference or not
Thanks, it worked, but currently I have about 7289331 records to upload from the PurchaseOrderEntryDetail table, and is there no way to break them into separate uploads because I think the number of records is too many for the single upload.
Thanks for your answers, am grateful
Michael,
1) Clean out the machine's temp files in;
C:\Windows\Temp and C:\Documents and Settings\<username>\Local Settings\Temp for XP
or C:\Users\<username>\AppData\Local\Temp for Vista/Win7
OR
Just use CCleaner www.ccleaner.com
Also search for any QS_*.tmp files and delete them. Also look for any old Windows Updates files in the Windows folders, ccleaner should delete those too.
2) Next check you timeout settings here:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Retail Management System\Headquarters\Client\Timeout\Message
Or for 64 bit OS
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Retail Management System\Headquarters\Client\Timeout\Message
Set it to 3600 for a 60 minute timeout if you are sending big worksheets
It certainly would not hurt to do so. You can see big performance gains by doing so. We like our customers to do it about once a month or so. There should be no downside other than it may slightly degrade database performance while the reindex in happening. You will still be able to run transactions, just may be a tick slower.
For HQ Server I have E:\ for mdf file and free space=72gb, F:\ for log file free space=45gb
For Store server I have E:\ for mdf file and free space=95gb,F:\ for log file free space=73gb
Do I reindex both databases?
Thanks
Michael,
If those are the sizes, then the database should not be trying to expand. Sounds like theres plenty of free room in both database. How about the physical storage space on the hard drive?
As far are reindexing, the error message you provided is pretty vague, as are most in RMS. This could mean there is a problem inserting an index in to the system. Rebuilding the index will ensure that some of the free space will be available for index updates, plus it generally always helps overall database performance.
Thanks,
For HQ the size is 89gb and usage is 92%
For Store the database size is 4gb and the usage is 80%
What is the effect of reindexing
Thanks
Make sure your timeout are all set to around 60 seconds or more, especially for HQ Client and Server as operations can take a while. This is likely a larger issue, but for troubleshooting sake, is there enough storage on the hard drive fro the database to grow? Also if you go into RMS Administrator (either one) and connect to the database, then go to Database -> Properties, what is the usage %? Have you tried re-indexing the HQ database?
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,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (