Follow

Error messages associated with incorrect configuration of TEAMserver

The following is a list of specific problems with the configuration or installation of TEAMserver, and the associated effects and error messages. Bear in mind that this is not an exhaustive list of all the error messages or problems that can exist in a TEAMserver installation; it is possible for an issue not documented in this article to produce similar effects or messages.

Issues, effects and error messages

  1. Clocks on server and client not synchronized.
    1. HTTP
      1. Attach TM or TB to project:
        Déjà Vu X3 was unable to connect to http://192.268.1.54/TEAMserver/. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        Microsoft.Web.Services2.AsynchronousOperationException: WSE101: An asynchronous operation raised an exception. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
      3. Request floating license:
        The specified login is not valid
      4. Floating license diagnostic: incorrectly reports that the license was obtained.
    2. TCP
      1. Request floating license: still works.
      2. Attach TM or TB to project: still works.
  2. TEAMserver is not available or not running.
    1. HTTP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to http://192.268.1.54/TEAMserver/. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        Microsoft.Web.Services3.AsynchronousOperationException: WSE101: An asynchronous operation raised an exception. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.268.1.54:80 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketlnternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, lAsyncResult asyncResult, Exception& exception) --- End of inner exception stack trace ---
      3. Request floating license:
        Unable to request floating license from the specified TEAMserver
      4. Floating license diagnostic:
        Unable to obtain a valid license.
        Status: ActivationFailed
        ActivationFailed: A connection with the server could not be established
    2. TCP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to tcp://192.268.1.54. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
      3. Request floating license:
        Unable to request floating license from the specified TEAMserver
  3. Port 8081 blocked:
    1. HTTP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: TEAMserver is responding.
      3. Request floating license:
        The license service for the specified TEAMserver is not responding
      4. Floating license diagnostic:
        Unable to obtain a valid license. Status: ActivationFailed ActivationFailed: A connection with the server could not be established
    2. TCP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: TEAMserver is responding.
      3. Request floating license:
        The license service for the specified TEAMserver is not responding
  4. Port 1846 blocked
    1. HTTP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: works.
      3. Request floating license: works.
      4. Floating license diagnostic: works.
    2. TCP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to tcp://192.268.1.54. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.Net.Sockets.SocketException (0x80004005): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.268.1.54:1846
      3. Request floating license:
        Unable to request floating license from the specified TEAMserver
  5. Port 1845 blocked
      HTTP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: works.
      3. Request floating license: works.
      4. Floating license diagnostic: works.
      TCP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: works.
      3. Request floating license: works.
  6. Port 80
      HTTP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to http://192.268.1.54/TEAMserver/. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.NullReferenceException: Object reference not set to an instance of an object. at Atril.TMServer.Client.SoapProxy.CallService(Object Info, String SoapAction, Type ResultType) at Atril.TMServer.Client.SoapProxy.IsAlive() at Atril.TMServer.Client.TMServerEnabler.IsProxyAlive(String ProxyId) at CheckConnectivity.MainWindow.TestButton_Click(Object sender, EventArgs e)
      3. Request floating license:
        Unable to request floating license from the specified TEAMserver
      4. Floating license diagnostic: works.
      TCP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: works.
      3. Request floating license: works.
  7. Registry key HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled value set to 1.
      HTTP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to http://192.268.1.54/TEAMserver/. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.RijndaelManaged..ctorO at Adduxis.Components.Security.RijndaelEncyption.SetKeyAndlnitVector(Byte0 NewKey) at Atril.TMServer.Client.TokenIssuerProxy.RequestSecurityContectToken(ProxyConfi guration Configuration) at Atril.TMServer.Client.SoapProxy.ConfigureEnvelope(SoapEnvelope Envelope, String SoapAction) at Atril.TMServer.Client.SoapProxy.GetEnvelope(Object BodyObject, String SoapAction) at Atril.TMServer.Client.SoapProxy.CallService(Object Info, String SoapAction, Type ResultType) at Atril.TMServer.Client.SoapProxy.IsAlive0 at Atril.TMServer.Client.TMServerEnabler.IsProxyAlive(String Proxyld) at CheckConnectivity.MainWindow.TestButton_Click(Object sender, EventArgs e)
      3. Request floating license:
        Unable to request floating license from the specified TEAMserver
      4. Floating license diagnostic: works.
      TCP
      1. Attach TM or TB to a project: works.
      2. Connection diagnostic: works.
      3. Request floating license: works.
  8. Using DVX3 v9.0.765+ and TEAMserver v2.0.29+, but the TEAMserver's floating licenses service was not patched.
      HTTP
      1. Floating license diagnostic:
        Unable to obtain a valid license.
        Status: (64) ActivationFailed
        License for CryptoLicensing Generator has invalid signature: ... NwA==
        ActivationFailed: License for CryptoLicensing Generator has invalid signature: ... NwA==
        Able to ping license service: License for CryptoLicensing Generator has invalid signature: ... NwA==
  9. There is an unspecified problem with the storage.psf file used by the LicenseService. It needs to be replaced with a fresh copy.
      HTTP
      1. Floating license diagnostic:
        Unable to obtain a valid license.
        Status: (64) ActivationFailed
        Activation limit reached. Context=''
        ActivationFailed: Activation limit reached. Context=''
        Able to ping license service: true
  10. The configuration file for the WebService (/Web/WebService/web.config) does not have the right value in the <licenseServiceURL> tag.
    1. HTTP
      1. Attach TM or TB to project: works.
      2. Connection diagnostic: TEAMserver is responding.
      3. Request floating license:
        The specified login is not valid
      4. Floating license diagnostic: works.
  11. The following error message appears when the server has 2 or more netowrk adapters, and one of them has a self-assigned IP address (the self IP address will be of the form 169.*.*.*). Disabling IPv4 on that network adapter should solve the problem.
    1. TCP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to tcp://192.268.1.54. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.Net.Sockets.SocketException (Ox80004005): A socket operation was attempted to an unreachable network 169.254.155.239:1846

        Server stack trace:
        at System.Net.Sockets.Socket.DoConnectlEndPoint endPointSnapshot, SocketAddress socketAddress)
        at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)[...]
  12. The folder the log files for the TCP Service and the WebService are stored in has incorrect user permissions. By default, this folder is C:\ProgramData\ATRIL\TEAMserver\MyTMServer\. You mujst assign Full Control to the accounts that IIS uses to run the WebService, and the accounts that runs the TCP Service. By default, the account is Network Service.
    1. HTTP
      1. Attach TM or TB to a project:
        Déjà Vu X3 was unable to connect to tcp://192.268.1.54. Please check the login credentials you specified and make sure they are valid.
      2. Connection diagnostic:
        System.Net.Sockets.SocketException (Ox80004005): A socket operation was attempted to an unreachable network 169.254.155.239:1846

        Server stack trace:
        at System.Net.Sockets.Socket.DoConnectlEndPoint endPointSnapshot, SocketAddress socketAddress)
        at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)[...]
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    semonbright

    A SocketException is thrown by the Socket and Dns classes when an error occurs with the network. Most of the time these are connectivity issues due to different IP protocols (IPV4/IPV6) between the two server/computers trying to communicate or extra authentication rules setup on one of the computers for in/out connectivity. Ways to troubleshoot this SocketException are, check you have proper internet connection is there on your machine or not, and you are able to ping the remote server or not. Possible causes for the error:

    You are using the wrong IP address.
    You are using the wrong port.
    Firewall blocking the connection.

    More Info: http://csharp.net-informations.com/communications/exec.htm

Powered by Zendesk