none
Problems with registering DCS services RRS feed

  • Question

  •  

    I’m trying to run the RegisterCCFServices.bat after an development installation (everything selected) of DCS but this is the error I get:

    [CCF Server] = WINDOWS200301

    Registering CCF Service : Addressbook

    http://WINDOWS200301/Microsoft.Ccf.Csr.WebServices.ContactCenter/AddressBook.svc

     -Contract:http://microsoft.com/ccf/ContactCenter/AddressBook#AddressBook

    Microsoft Distributed Connectivity Services

                             ServiceModelReg Tool

    Error:There are no 'live' service instance for the specified ServiceType and Sco

    pes.

    Stack trace:   at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactor

    y.InternalCreateChannelFromDiscovery[TChannel](String contractName, String contr

    actNamespace, String action, InstanceContext callbackInstance)

       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCr

    eateChannel[TChannel](String contractName, String contractNamespace, String acti

    on, InstanceContext callbackInstance)

       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.CreateChan

    nel[TChannel]()

       at Microsoft.ConnectedIndustry.ProcessExecution.Tools.CFFServiceModelReg.Main

    (String[] args)

     

    In het event viewer i see 4 messages appearing:

    1-      A warning with following content:
    {ModuleName} : ScopeProvider

    {MESSAGE} : GetCurrentScopes called without an active context

    2-      A warning with following content:
    ExtendedChannelFactory::GetBinding - Error getting metadata from mex address: http://windows200301/ManagementServices/DiscoveryAdminService.svc/mex - The error is: Metadata contains a reference that cannot be resolved: 'http://windows200301/ManagementServices/DiscoveryAdminService.svc/mex'.

    3-      A warning with following content
    ExtendedChannelFactory::InternalCreateChannelFromMex<TChannel> - Error: Error getting metadata from mex address: http://windows200301/ManagementServices/DiscoveryAdminService.svc/mex.

    4-      A warning with following content:
    ExtendedChannelFactory::InternalCreateChannelFromMex<TChannel> - StackTrace:    at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.GetBinding(EndpointAddress mexAddress, String contractName, String contractNamespace)

       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCreateChannelFromMex[TChannel](EndpointAddress mexEndpointAddress, String contractName, String contractNamespace, String action, InstanceContext callbackInstance)

    5-      An Error with following content:
    {ModuleName} : ServiceModelReg

    {MESSAGE} : Error:There are no 'live' service instance for the specified ServiceType and Scope

    6-      An Error with following content:
    ModuleName} : ServiceModelReg

    {MESSAGE} : Stack trace:   at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCreateChannelFromDiscovery[TChannel](String contractName, String contractNamespace, String action, InstanceContext callbackInstance)

      at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCreateChannel[TChannel](String contractName, String contractNamespace, String action, InstanceContext callbackInstance)

       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.CreateChannel[TChannel]()

       at Microsoft.ConnectedIndustry.ProcessExecution.Tools.CFFServiceModelReg.Main(String[] args)

     

     

    The problem seems to be something with the mex endpoint, but I didn’t succeed in pinpointing it. Any suggestions?

    Wednesday, January 14, 2009 2:03 PM

Answers

  • Hello,

    Can you check if you DCS is up and running.

    The issue on my machine (which was solved last week) was a security problem.

    It is important that the servie users of DCS have to correct rights on the db.


    So first check is the MMC console of DCS works and if you can see the default operations is their.


    Kind regards,
    gert
    • Marked as answer by Beloega Thursday, April 9, 2009 12:01 PM
    Monday, February 16, 2009 8:10 AM

All replies

  • Hello,

     

    I am just building my new dev environment from scratch, and everything seems fine (without DCS). As I am running the script "RegisterCCFServices" I am getting the same errors.

     

    Did you get any help, or fix your problem meanwhile ?

     

    Thanks,

    Erich

     

     

     

    Saturday, January 24, 2009 3:21 PM
  • Hi,

    Ensure that you can browse to the following urls and that the server name "windows200301" is correct.- 

    http://windows200301/ManagementServices/DiscoveryAdminService.svc
    http://WINDOWS200301/Microsoft.Ccf.Csr.WebServices.ContactCenter/AddressBook.svc

    from the machine where you are running the registerCCFServices.bat file. The url for the discovery service is picked up from the ServiceModelReg.exe.config. If its not correct it can be edited in the config file.

    Mudit


    Saturday, January 31, 2009 9:05 AM
  • Mudit,

    I had variation of the same problem. DiscoveryAdminService.svc and AddressBook.svc both work fine with the URL as you suggested and the URL in ServiceModelReg.exe.config is also correct. However I still can't register the services.

    I also attempted to register a single service (rather than running off the batch file) but same problem. This is how it looks

    COMMAND AT THE COMMAND PROMPT:
    ===========================
    ServiceModelReg -Url:http://ANAN-J6P0J3K/Microsoft.Ccf.Csr.WebServices.ContactCenter/AddressBook.svc -Contract:http://microsoft.com/ccf/ContactCenter/AddressBook#AddressBook

    RESULTING ERROR:
    =============
    C:\Program Files\Microsoft CIS\DCS Business Logic Visual Studio Extensions VS200
    8\ServiceModelReg>ServiceModelReg -Url:http://ANAN-J6P0J3K/Microsoft.Ccf.Csr.
    WebServices.ContactCenter/AddressBook.svc -Contract:http://microsoft.com/ccf/Con
    tactCenter/AddressBook#AddressBook
    Microsoft Distributed Connectivity Services
                             ServiceModelReg Tool
    Error:The server was unable to process the request due to an internal error.  Fo
    r more information about the error, either turn on IncludeExceptionDetailInFault
    s (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration
     behavior) on the server in order to send the exception information back to the
    client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documenta
    tion and inspect the server trace logs.
    Stack trace:
    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message
     reply, MessageFault fault, String action, MessageVersion version, FaultConverte
    r faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRunt
    ime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on
    eway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan tim
    eout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean on
    eway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCall
    Message methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
       at Microsoft.ConnectedIndustry.ServiceModel.Discovery.DiscoveryResolver.GetEn
    dpoints(String serviceType, Scopes scopes)
       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCr
    eateChannelFromDiscovery[TChannel](String contractName, String contractNamespace
    , String action, InstanceContext callbackInstance)
       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.InternalCr
    eateChannel[TChannel](String contractName, String contractNamespace, String acti
    on, InstanceContext callbackInstance)
       at Microsoft.ConnectedIndustry.ServiceModel.ExtendedChannelFactory.CreateChan
    nel[TChannel]()
       at Microsoft.ConnectedIndustry.ProcessExecution.Tools.CFFServiceModelReg.Main
    (String[] args)
    ===================================================

    I've looked at the ServiceBehaviorAttribute and it's already set.

    Any idea? I would be grateful for any help.

    Kind regards

    Friday, February 6, 2009 6:58 PM
  • Hello,

    Can you check if you DCS is up and running.

    The issue on my machine (which was solved last week) was a security problem.

    It is important that the servie users of DCS have to correct rights on the db.


    So first check is the MMC console of DCS works and if you can see the default operations is their.


    Kind regards,
    gert
    • Marked as answer by Beloega Thursday, April 9, 2009 12:01 PM
    Monday, February 16, 2009 8:10 AM