In the IP address edit box, leave everything All Unassigned.ġ0. From the Type drop down menu select https.Ĩ. In the Site Bindings window select the Add button.ħ. From the menu list select Edit Bindings.Ħ. Open the Internet Information Service (IIS) Manager.ĥ. To use SSL with a self signed certificate a binding for the port most be added using IIS Manager.
Edit the DNS servers to point the server computer name to the correct IP address.Īrticle ID: 52330 - Last Review: September 25, 2015. Add the server IP address and server computer name on a new line below the loopback (127.0.0.1 localhost). With notepad, edit the hosts file located in "c:\WINDOWS\system32\drivers\etc\hosts". (This will need to be done on each client) Edit the hosts file on the local system to resolve the IP address to a computer name. Create a new String Value called CCSConnectionString and set the value to the same as in step #1. Remote desktop manager enterprise 8.0.1.0 software#
expand the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\prairieFyre Software Inc\CCM\Common. Type regedit in the RUN box to open the registry editor. 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). In this example, after the change it would look like 'Data Source=192.168.1.100\SQLEXPRESS'. Replace the computer name with the IP address of the server. You should see something in the string like 'Data Source=CCM\SQLEXPRESS'. Double click the ConnectionString key on the right and modify the DataSource. Expand the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\prairieFyre Software Inc\CCM\Client. On the server, type regedit in the Run box then press Enter. Edit the connection string on the server to use the IP instead of the computer name. This is for client machines only, and can cause serious issues with real-time and softphone control if performed on the server itself. NOTE: Do not perform step 2 on the MiContact Center server. If the clients cannot resolve this computer name, we need to do one of the following workarounds: The WFS clients pull down SQL information from the connection string on the server inside the registry. 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. The server was not found or not accessible.” “A network-related or instance-specific error occurred while establishing a connection to the SQL server. 
When opening the WFS client you will see the error:
Workforce Scheduling clients cannot connect to the server Article ID: 50623 - Last Review: November 17, 2016
0 kommentar(er)
