Hi all:
I am running v. 2.0.2014 on SO and HQ and both are at database v. 2.06 using SQL Server 2008 R2 Service Pack 1 Security Update (KB2716440). I created a new template database from a current store. I reindexed both the template DB and the HQ DB and also ran a DBCC CHECKDB against both with no errors reported.
When running the Export Database Wizard (connected through HQ Administrator as "SA" user), I am able to select the template database, create a new database, copy the database structure and begin the export data to new database process when I receive an Error 0. The process hangs at Exporting table HQMessage.
Any help would be greatly appreciated.
Ted Archer
*This post is locked for comments
If the issue is isolated to the STORE database I am somewhat unsure how performing or attempting to perform maintenance on the HQ database, would resolve an issue with STORE? You mentioned one of the stores, which sounds like other store databases previously exported successfully for you. So if that is correct, the issue is not with HQ DB at all. The issue is with the store that fails to connect yes? It sounds like in order to correct the connection error you are attempting to export another database?
1. What is the connection error?
Instead of using the sample perhaps this will work.
Open administrator log in with your SA and before connecting to a database or sample try MASTER. (type the word master into the database names)
Connect to the master database so you see master on the bottom of the screen connected.
Then once master is connected try to restore the stores database that is giving you the issue from a backup and see if it gives you any difficulties. If there is an issue within the tables on this stores database? Causing the ERROR 0. (It would probably not allow you to restore).
If it allows you to restore without error (do not name the database the same as before by the way in this process pick a new name) then the connection issue is perhaps not related to the stores database at all? If the other stores databases exported and connected successfully it likely isn't HQ it is "this store".
Have you also updated your SQL to SP 3 as I suggested as of yet?
Thanks, I hope this helps.
Mabuhay!
Thank you! I think that would be one of the causes why we have an issue on exporting store database also. We added some table due to integration with LS Retail and because we dont export database that much we dont notice until one of our store failed on connection thru our HQ Client and now we are facing an error exporting Store Database.
Weve tried reindexing HQ Database but still no, we tried to export and restore HQ Database to other PC but still no. But the error 0 stop when exporting table AccountReceivable which is included on the original tables of RMS.
Hi Ted,
We've faced this issue due to custom tables in export database. We were able to identify the table which was causing the export error by removing each custom table.
Since we couldn't trace the exact issue, we first export the DB and create the custom table which was causing the Error 0
..
Butch,
Thank you for your response. I have created a support request with Microsoft and they are working on the issue. The HQMessage and Item tables were both checked for NULL values which would cause the error and none were found.
It has been determined that the issue lies within my Template store database (the export runs correctly with a blank store database created from the backup file shipped with RMS).
I have uploaded copies of my Headquarters and Template store databases to Microsoft and will update the community on the resolution in hopes that it may help another in the future.
Ted
Hi Ted,
I believe the current SP level for both SQL 2008 R2 and 2008 R2 Express is SP 3 not 1.
I believe this kb may help you after you've updated the SQL too I hope: support.microsoft.com/.../862876
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156