Discussion Sync stopped AGAIN!!!

  • Wednesday, September 05, 2012 11:09 AM
     
     

    Hi all, Excuse my total anger but I have now had another sync stop for no reason. This is my second forum question. This http://social.msdn.microsoft.com/Forums/en-US/ssdsgetstarted/thread/32cde3ef-447a-4daa-8bfb-ff488e0cb6e1 also has had the same problem.

    I have re entered my credentials and away it goes.

    I feel totally out of the loop with this. There seems no control as all. Office 365 constantly emails you if you are moving subscriptions and makes you feel you are in control. Sync agent shows nothing.

    My client is running a live system and I am getting further emails of missing information between the On premise and cloud system.

    This is totally unacceptable.

    Scott

    • Changed Type scottsanpedro2 Wednesday, September 05, 2012 11:10 AM
    •  

All Replies

  • Wednesday, September 05, 2012 2:59 PM
     
     

    HI Scott,

    Sorry to lead such inconvenience to you.

    We are currently working on a fix for similar issue. For now, you still have to reenter your credential to workaround.

    Can you also share your information so that we can make sure the root cause for your issue was the same?

    Server id: Your server id

    Sync group id: You sync group id

    Region: Where your Data Sync Server is located/created

    Time / Date: Date and time when you encountered the issue

    Tracing Id: The tracing id you see in the message in UI

    For your requirement about in-time notification, sorry to say that currently we have no such feature yet.

    In the future, we shall be able to provide monitoring API which can help you to achieve that.

    You can also add your votes for your needed feature at

    http://www.mygreatwindowsazureidea.com/forums/169922-data-management-sql-data-sync

    Thanks,

    Jarod Zhu

  • Thursday, September 06, 2012 6:17 AM
     
     
    Hi Jarod. Thanks again for your response. Very frustrating for me.
    Here are the details you require.

    Server id: c6q9qbue65

    Sync group id: 7d10678b-0418-4eab-b20f-576d675c43e9

    Region: North Eurpoe

    Time / Date: 05/09/2012 08:02:02

    Sync failed with the exception "BeginSession failed with exception:
    Invalid Database credentials for database 'ComfortEngineer', id: ffc4f9c3-eff3-4c4f-a439-e86e52c77a09"

    For more information, provide tracing id ‘becac049-fe20-4386-bc83-76a18352b0b2’ to customer support.

    Let me know if you need more information.
    I have checked this morning and all seems well.
    It would be very handy to know when the issue is resolved as in the meantime I have to manually check the sync!

    Thanks Scott
  • Thursday, September 06, 2012 3:31 PM
     
     

    HI Scott,

    I checked the service log that your problem was known issue to us.

    Currently our plan is to resolve this issue in next service update release (coming soon in Oct).

    Thanks,

    Jarod Zhu

  • Friday, September 07, 2012 8:43 AM
     
     

    This has happened to me again this morning. I have only just noticed it.

    It stopped last night at UK time 23:29:35 and I just restarted it 09:43

    My client is getting really upset. It's causing all sorts of problems. I go away on holiday soon, what shall I do then???

    Sync failed with the exception "BeginSession failed with exception:
    Invalid Database credentials for database 'ComfortEngineer', id: ffc4f9c3-eff3-4c4f-a439-e86e52c77a09

    "

    For more information, provide tracing id ‘fbcbe36d-40b1-42f1-90bc-870fadd4bfa7’ to customer support.

    Sync failed with the exception "GetStatus failed with exception:
    Sync worker failed, checked by GetStatus method. Failure details:
    Invalid Database state for synchronization. Database id: ffc4f9c3-eff3-4c4f-a439-e86e52c77a09"

    For more information, provide tracing id ‘012c1185-cbe4-41b3-b005-65ef955a8190’ to customer support.

    You are providing a service here which is completely different from general bugs in software.

    This needs to be escalated

    Scott

    PS just readin another forum and he reminds me that this is CTP Release. Do I have no complaint then?


  • Friday, September 07, 2012 10:18 AM
     
     

    HI Scott,

    Sorry for getting you into this trouble.

    I will raise the issue to product team and see if we can solve your problem earlier.

    Regards,

    Jarod Zhu

  • Friday, September 07, 2012 10:41 AM
     
     
    really appreciate you helping. I will help out if you need anything looked into at my end. Scott
  • Monday, September 10, 2012 1:30 PM
     
     

    further error today after running no problem.

    Sync failed with the exception "GetStatus failed with exception:
    Message id has not been set yet."

    For more information, provide tracing id ‘40a06878-f867-43f0-8c5f-2f908f9cf98f’ to customer support.

    Shall I report on these all the time? Seems I need to check to see if its running each day.

    New credentials solved the problem.

    Scott

  • Tuesday, September 11, 2012 1:13 PM
     
     

    HI Scott,

    For the original issue you hit, root cause is that SQL Data Sync service depends on an internal Windows Azure service to valid database credential which might be unavailable sometimes. SQL Data Sync need to handle this failure to avoid user database enter "Invalid credential" status.

    Product team has planned to roll out a hot-fix for this issue as soon as possible.

    For the last sync error "GetStatus failed" error you hit, it is not caused by this issue. Have you tried sync again without re-enter the credential?

    Thanks,

    Jarod Zhu

  • Tuesday, September 11, 2012 4:20 PM
     
     

    Hi Jarod. Thanks for the update. I solved it by re entering credentials. If it comes up again I will try as you have suggested.

    Thanks Scott

  • Sunday, September 16, 2012 3:50 PM
     
     

    Hi Jarod. Stopped again. Just checking on my day off.

    Sync failed with the exception "BeginSession failed with exception:
    Invalid Database credentials for database 'ComfortEngineer', id: ffc4f9c3-eff3-4c4f-a439-e86e52c77a09
    "For more information, provide tracing id ‘1e169d23-792b-4ef8-ba19-a7118f05be1c’ to customer support.

    I go on holiday next week.  Getting pretty worries.

    Thanks Scott

  • Monday, September 17, 2012 1:39 AM
     
     

    HI Scott,

    Sorry that you hit this issue again.

    Currently the hox-fix is on the way to the deployment and shall be ready in 2~3 days.

    Regards,

    Jarod Zhu