Digital Customer Service

Get Involved. Join the Conversation.

Topic

    Ashley Pink
    Chat Error - Chat not created, check business unit id.
    Topic posted October 19, 2019 by Ashley Pink 
    105 Views, 4 Comments
    Title:
    Chat Error - Chat not created, check business unit id.
    Summary:
    Chat Error - Chat not created, check business unit id.
    Content:

    Hi,

    We are setting up the DCS application and have completed the Mandatory Tasks as suggested in the documentation

    But when we click on the Chat window, enter the relevant details and click 'Start Chat' we get the below error

    Chat not created, check business unit id.

    Please note: We have set the Business Unit Id application variable in the DCS application in VBCS with the appropriate value

     

    Appreciate your help

    Thanks in advance

    -- Ashley

    Version:
    19C

    Comment

     

    • Paul Encarnacion

      Ashley, please enable Chrome Developer Tools and see what shows up in the Console and the Network log when you get this error and let us know. That should help us narrow down what the issue is.

    • Paul Encarnacion

      Ashley, the errors indicate that authorization has failed on the chatAuthenticate call.

      This may be due to a misconfiguration of your crmRest connection. The guidance in the Mandatory Setup Tasks in Chapter 3 of the DCS documentation describe the need to create an APPID and use that APPID in the crmRest connection.

      Having said this, don't limit your setup verification to the two points above. Make sure that you step through each of the steps specified in Chapter 3, and do it end to end. All of it needs to be set up properly for a successful configuration. If you follow those documented steps, the reference implementation will work out of the box.

    • Sombit Chakraborty

      Ashley,

       

      We are facing this same problem now. The chat functionality was working fine about couple of hours back.

      And we have the same BU Id application variable in the DCS application in VBCS with the appropriate value.

      Were you able to fix the issue.

       

      @Paul - This was working couple of hours back. 

       

      Thank You,

      Sombit