We have an old server (Windows server 2003) which was running a DA server for us for roughly a year. To make a long story short, we have built a new 2003 server since the original had a virus infection. Almost everything is running fine, except for some errors we are getting from a DA client app trying to work with the DA service running on this server.
yes, we will be migrating to a new up-to-date windows server, but we must get this step working first.
Here is a sample error we’re encountering, which does NOT Happen on the old infected server:
Inner Exception #2 Create rule
RemObjects.DataAbstract.DAUpdatesFailedException
One or more updates failed to apply on the server. R9260053, 2017, 1, 847089:
at RemObjects.DataAbstract.Linq.LinqDataAdapter.ThrowFailures(List`1 changes, String failureMessage) in c:\CI\b\rofx\932\Data Abstract for .NET\Source\RemObjects.DataAbstract\Linq\LinqDataAdapter.pas:line 945
at RemObjects.DataAbstract.Linq.LinqDataAdapter.ThrowExceptionForFailedChangeDeltas(Delta[] deltas) in c:\CI\b\rofx\932\Data Abstract for .NET\Source\RemObjects.DataAbstract\Linq\LinqDataAdapter.pas:line 485
at RemObjects.DataAbstract.Linq.LinqDataAdapter.ProcessPendingChangeDeltas(Delta[] serverDeltas, IDictionary`2 originalDeltaChangeIds) in c:\CI\b\rofx\932\Data Abstract for .NET\Source\RemObjects.DataAbstract\Linq\LinqDataAdapter.pas:line 304
at RemObjects.DataAbstract.Linq.LinqDataAdapter.ApplyChanges() in c:\CI\b\rofx\932\Data Abstract for .NET\Source\RemObjects.DataAbstract\Linq\LinqDataAdapter.pas:line 528
at admng2.APReconMain.FinishReconcile(Object sender, ItemClickEventArgs e) in D:\dev\miller\quickbooks\admng2\APReconMain.xaml.pas:line 1778
This error means that some of requested data update operations are being rejected by the SQL server.
The RemObjects.DataAbstract.DAUpdatesFailedException exception raised has a property named Changes.
Investigate this property - it will contain rejected Delta Changes. These Delta Changes have a property named Message that should explain why this particular change has been rejected by the server.
Or alternatively if you’re running MS SQL server start the SQL Server Profiler and run the crashing operation. You’ll see the failing command. THen investigate why this command fails. This can be caused by a very different reasons: from a data format issue in the data being sent from the new server (f.e. due to different locale settings) up to damaged database file or failing HDD on the server.
My question then is why. Same os. Same configuration. Same firewall settings. One server works. One doesn’t when it comes to updates. I have to do some real error logging but at one point today I saw some message about possible memory corruption
Which database drivers do you use?
‘Corrupted memory’ message is a quite serious thing. Usually for DA server it means that something is wrong with the DB drivers it uses.