Dynamics RMS HQ Client keeps crashing

Hi everyone,

We have an issue at the moment with Dynamics RMS HQ Client crashing while attempting to process a 401 Upload Data worksheet. I tried manually creating one and moving the from date back 30min with each one, but it gets to a point where it just crashes. As the day continues this time keeps advancing so it seems as if its something to do with the amount of data it is trying to upload. It does normally upload a lot more and thus I don't really understand why it is crashing now.

Debugging has been switched on and it is crashing at the "Sending Worksheet Message to HQ" message straight after "Uploading store data to HQ"

We have RMS SP 2 & 3 installed, and we're using SQL Server 2008 with the Store using XP and the server using Windows Server 2003.

Oh yes, and all the other Worksheets seem to be working fine.

Any ideas?

Hi Hendre

We seem to be having the exact same problem, any idea what is causing this?

Thanks, Matt

"Hendre Janse van Rensburg" wrote:

attempting to process a 401 Upload Data worksheet. I tried manually creating one and moving the from date back 30min with each one, but it gets to a point where it just crashes. As the day continues this time keeps advancing so it seems as if its something to do with the amount of data it is trying to upload. It does normally upload a lot more and thus I don't really understand why it is crashing now.

Message to HQ" message straight after "Uploading store data to HQ"

using XP and the server using Windows Server 2003.

I have seen this happen when the client has too much data to upload. For example, a store has their system date accidentally set back to 1/1/2000 and makes a sale under that date, then the HQ client tries to syncronize everything since that time and start uploading the entire store database to HQ. It's harder to find this problem than fix it, because you have to look for activity from a date that doesn't fit, like

select t.storeid,time,transactionnumber, t.batchnumber, openingtime,closingtime from [transaction] t join batch b on t.storeid=b.storeid and t.batchnumber=b.batchnumber where timeclosingtime

I suppose any table with a date field could do this, but the ones I see the most are Transaction, DailySales, Journal, InventoryTransferLog, PurchaseOrder, PurchaseOrderEntry

Hi Matt this doesnt seem to be it, all the dates on all our computers seem fine.

Here is the exact problem, and it is happening with all 3 store locations:

HQ client Error, HQ server shutting down

We are having a problem with the data upload (worksheet style 401). All other worksheets process correctly, but when client gets to worksheet style

Connection is aborted due to timeout or other failure Error 3704: Operation is not allowed when the object is closed (unhandled Error, State = '9')

This is happening in client at all 3 of our locations.

I can also see that HQ server appears to shut down once I get this message.

It does not appear to be a timeout problem as it only takes 5-10 seconds for hq server to freeze and hq client to get the error message.

"Matt Hurst" wrote:

If it only takes 10 seconds, then it's probably not a timeout, more likely some other database problem. I think the best chance would be to reindex both the store and the HQ databases then try again. You should only have one 401 worksheet waiting to process and the effective date should be from the time of the last successful upload.

If there is corruption in the store database that would prevent this connection, the only recourse will be to export a new copy of the store database from HQ, but this would replace any work done at the store since the last upload.