web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics RMS (Archived)

HQ Client - Not enough storage is available to complete this operation (after export from HQ Admin)

(0) ShareShare
ReportReport
Posted on by

Hi All,

I lost one of my store databases over the weekend due to windows corruption (the backup was also corrupted). After trying to restore the original db and backup I exported the store database from HQ Admin.

 

All was well until I connected HQ Client, which is now trying to upload ALL records (>10,000) for 3 tables: Journal, Transaction and TransactionEntry. This results in an error once the HQ Client gets to "Sending Worksheet Message to HQ".

I think the issue is down to the Timestamplog table but do not know how to resolve.

I have tried all the usual fixes (registry timeouts etc). I am using SQL Express 2008 on store with db size of 1.1 GB (so SQL storage not an issue). I have also transferred the database to the local network as HQ server/database but same result. I have detached the database and re-created the log file. I have reindexed. All not getting me anywhere.

Any help is gratefully welcome and very much appreciated.

 

Thanks.

John.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    raelhefn Profile Picture
    on at

    Delete any 401 request data upload worksheet for this store from HQ. Synchronize your database and run 401 from current date only.

  • John Finn Profile Picture
    on at

    Hi Ramy,

    Thank you for your reply.

    Can you confirm that ws 101 syncrhonise SHOULD be used in the case of exporting an already existing store database from HQ. I understood that this was only to be used on the first occasion when store database is exported (created) in HQ.

    Thanks.

    John.

  • Suggested answer
    raelhefn Profile Picture
    on at

    101 generated automatically from HQ when you export any database.

    in your case database time out is caused from HQ client tried to upload data to HQ and field may be a lot of uploading worksheets trying to upload data to HQ in same time deadlock may occur in this case.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics RMS (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans