Quantcast
Channel: Mitel MiContact Center Knowledge Base
Viewing all articles
Browse latest Browse all 959

Workforce Scheduling (WFS) clients cannot connect

$
0
0
Article ID: 50623 - Last Review: November 17, 2016

Problem

Workforce Scheduling clients cannot connect to the server



Symptoms

When opening the WFS client you will see the error:
“A network-related or instance-specific error occurred while establishing a connection to the SQL server. The server was not found or not accessible.”



Cause

The Server and clients may not be on the same domain or for whatever reason the clients cannot resolve the computer name of the server, possibly because of a DNS issue.



Resolution

The WFS clients pull down SQL information from the connection string on the server inside the registry.  If the clients cannot resolve this computer name, we need to do one of the following workarounds:

NOTE:  Do not perform step 2 on the MiContact Center server.  This is for client machines only, and can cause serious issues with real-time and softphone control if performed on the server itself.

  1. Edit the connection string on the server to use the IP instead of the computer name.
  • On the server, type regedit in the Run box then press Enter
  • Expand the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\prairieFyre Software Inc\CCM\Client
  • Double click the ConnectionString key on the right and modify the DataSource
    • You should see something in the string like 'Data Source=CCM\SQLEXPRESS'
    • Replace the computer name with the IP address of the server
    • In this example, after the change it would look like 'Data Source=192.168.1.100\SQLEXPRESS'
  • Create a connection string on the client in the registry. There is logic in the system that if a connection string exists on the client, it will use that instead of looking to the server. (This will need to be done on each client)
    • Type regedit in the RUN box to open the registry editor.
    • expand the key HKEY_LOCAL_MACHINE\SOFTWARE\prairieFyre Software Inc\CCM\Common
    • Create a new String Value called CCSConnectionString and set the value to the same as in step #1
  • Edit the hosts file on the local system to resolve the IP address to a computer name. (This will need to be done on each client)
    • With notepad, edit the hosts file located in "c:\WINDOWS\system32\drivers\etc\hosts"
    • Add the server IP address and server computer name on a new line below the loopback (127.0.0.1   localhost)
      • Example: 192.168.1.100     CCM
  • Edit the DNS servers to point the server computer name to the correct IP address.


  • Applies To

    CCM version 5.6 and newer




    Viewing all articles
    Browse latest Browse all 959

    Trending Articles