Two questions: 1. non-dbo schema supported? 2.SyncScope not Supported error?

Proposed Answer Two questions: 1. non-dbo schema supported? 2.SyncScope not Supported error?

  • 1 августа 2012 г. 15:29
     
     

    I have provisioned my database with a non-dbo schema but it seems not to be working. Are non dbo schemas supported in Sync Framework Toolkit??

    Also can anyone assist me with what this error means??

    {"ErrorDescription":"Microsoft.Synchronization.Services.SyncServiceException\u000d\u000aSyncScope not supported.\u000d\u000a   at Microsoft.Synchronization.Services.RequestParser.GetCommandParameters(NameValueCollection queryStringCollection)\u000d\u000a   at Microsoft.Synchronization.Services.RequestParser.ParseIncomingRequest()\u000d\u000a   at Microsoft.Synchronization.Services.SyncService`1.ProcessRequestForMessage(Stream messageBody)\u000d\u000a\u000d\u000a\u000d\u000a"}

Все ответы

  • 2 августа 2012 г. 6:00
    Модератор
     
     

    non-dbo schema is supported. 

    can you share some more info when are you getting the error above?

  • 2 августа 2012 г. 15:01
     
     

    It's kind of hard to explain but when I provision my db with my schema included I get the error above or I get and error saying and it doesn't look like the scope_config and scope_info tables are getting populated properly compared to provisioning (dbo)

    ErrorDescription":"Microsoft.Synchronization.Data.DbSyncException\u000d\u000aCannot find a valid scope with the name 'cbcsync' in table '[scope_info]'.

    When I provision my db without my schema included I'm getting an error that says

    {"ErrorDescription":"Microsoft.Synchronization.Data.DbSyncException\u000d\u000aCannot find a valid scope with the name 'cbcsync_fbbbbc18-81fb-40d5-b686-a7bfc8184e1b' in table '[scope_info]'. Ensure that this scope exists and that it has a corresponding valid configuration in the configuration table '[scope_config]'.\u000d\u000a   at Microsoft.Synchronization.Data.SqlServer.SqlProviderFactory.ReadConfiguration(String scopeName, SyncSchemaInfo syncSchemaInfo)\u000d\u000a   at Microsoft.Synchronization.Data.SqlServer.SqlSyncProvider.Configure()\u000d\u000a   at Microsoft.Synchronization.Data.SqlServer.SqlSyncProvider.BeginSession(SyncProviderPosition position, SyncSessionContext syncSessionContext)\u000d\u000a   at Microsoft.Synchronization.Services.SqlProvider.SqlSyncProviderService.GetChanges(Byte[] clientKnowledgeBlob)\u000d\u000a   at Microsoft.Synchronization.Services.DownloadChangesRequestProcessor.ProcessRequest(Request incomingRequest)\u000d\u000a   at Microsoft.Synchronization.Services.SyncService`1.ProcessRequestForMessage(Stream messageBody)\u000d\u000a\u000d\u000a\u000d\u000a"}

    There error is occuring on my initial sync

    http://server/_dotnet35/hhd/CBCSyncService/CBCSyncService.SVC/CbcSync/DownloadChanges

    Ran the same code again and the error message came back with the same error except the scope name is different {"ErrorDescription":"Microsoft.Synchronization.Data.DbSyncException\u000d\u000aCannot find a valid scope with the name 'cbcsync_049034fb-77a8-4504-8c7b-7d9daa252244'


    • Изменено V.Moss 2 августа 2012 г. 18:27
    •  
  • 3 августа 2012 г. 1:12
    Модератор
     
     
    on the service code, did you set the schema name via SetSyncObjectSchema inside InitializeService ?
  • 3 августа 2012 г. 15:24
     
     
    Yes I did. but it appears to be looking in dbo.
  • 6 августа 2012 г. 10:29
    Модератор
     
     

    can you query what your scope_info table contains?

    if you specify a schema name, do you see the sync created objects prefixed with your schema?

  • 13 августа 2012 г. 12:09
     
     Предложенный ответ
    This a well-known bug

    Senior Jack of all trades


    • Изменено M.Bi 13 августа 2012 г. 12:09
    • Предложено в качестве ответа vmoss 25 октября 2012 г. 17:00
    •