Hello,

I am using Sync preview.  It has been syncing successfully for several months but recently the logs have a severity of Warning and have a message similar to the one below

Sync completed with warnings in 21.08 seconds. Upload:   0 changes applied/172 failed Download: 0 changes applied/0 failedData Sync will stop synchronizing changes for this sync group member in 44 days if the failures are not resolved.    For more information, provide tracing ID c8fb9cee-8047-49d1-a390-b94d008fe105 to customer support.

I contacted support but they don't support Sync as it is in preview. How can I using the tracing Id to find out what the specific error is?  I've looked in the event log of the on-premise box and there is nothing to indicate the source of the error there.  SQL Data Sync Agent Preview on the on-premise box reports the local database as reachable and I am able to ping the Data Sync service.

Also in my Sync group the on-premise database has a Status of error.  Is there a way to find out what that error is?

Any help would be gratefully received as I am unsure as how to proceed in resolving these errors.

Thanks in advance.

Hi Richie,

Sorry for the late reply. Checking the status of your sync group, we found that it's now proceeding normally and many changes have been applied now, so I guess you have already resolve the problem by your own?

Per the issue you encounter specifically, there are some error happens when sync trying to delete rows in database -- "Invalid column name 'MultiDesign'", may I know do you delete some columns that are defined in sync rule after the sync group is set up? 

Thanks,

Eva

Hi Eva,

Thanks for your reply.  I may have inadvertently fixed something when I was trying to manually upload data.  Is it possible to find out what the initial issue was the first Warning message was 

Sync completed with warnings in 21.86 seconds. Upload:   0 changes applied/79 failed Download: 0 changes applied/0 failedData Sync will stop synchronizing changes for this sync group member in 44 days if the failures are not resolved.    For more information, provide tracing ID 3619e942-b8b4-4756-9bf4-5c22bb02789b to customer support.

Also the on-premise database in my Sync group still has an error icon beside it.  Is it possible to find out what the reason for this is?

Hi Richie,

As I mentioned in the previous thread, sync is complaining about "Invalid column name 'MultiDesign'". Can you check whether this column still exists in your database? Or is it a computed column? 

Eva

Hi Eva,

Apologies I misread your previous message.  Yes the column MultiDesign exists in both databases and in the Sync Rules.  And I am sure that it always has.  This is why I though that you were referring to an error that occurred while I was adding tables to the database.  

The SyncRules look to the schema of the SQL Azure database so I would be unable to select if it didn't exist in Azure.  And it definitely exists and always has in the on-premise database.

Thanks for you assistance.

Hi Richie,

As I look into the history of your sync group, there are 2 kinds of warnings, except the one you mentioned (which is caused by "Invalid column name 'MultiDesign'"), another warning is:

Error #1: SqlException Error Code: -2146232060 - SqlError Number:515, Message: Cannot insert the value NULL into column 'rowguid', table 'Extranet001.dbo.PPRPanel'; column does not allow nulls. INSERT fails. SqlError Number:3621, Message: The statement has been terminated. 

This kind of error usually happens when you update primary key of a row (SQL Data Sync use PK for change tracking and if you update a primary key value, there will be some warnings, in other words, PK value update is not supported in SQL Data Sync).  

Both of these warnings do not happen after 07/23, so may I ask dose the issue still exist? Were you performing changes on the table schema during 07/21 ~ 07/23, say, delete some columns or update some primary keys?

Hope we can make the issue clear and get it resolved :)

Thanks,

Eva

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 18 hours 31 minutes ago

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 18 hours 21 minutes ago

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM

Hi Eva,

Thanks for your reply.  The issue seems to be resolved.  I think that i inadvertently fixed while making other changes.  The second error mentioned above was definitely caused and resolved by me while working on the database.

I have no idea how the MulitDesign issue happened initially but as it is no longer happening I guess we can not find out now.

I think we can mark this issue as resolved.

Thanks again for all you help.

• Marked as answer by Richie001 Monday, July 27, 2015 12:48 PM