Windows connector

This section provides some tips and guidelines for getting your Windows connector to work.

Devices do not appear after starting the connector

If the Windows connector starts successfully, but you do not see devices in the OpenText Functional Testing Lab console:

Verify that your machine can detect your devices
Check the connector.log file located in <Windows connector folder>\connector\log folder and make sure that there are no "connection refused" messages or other errors.
If the connector.log does not show any errors, check the service.log file on the OpenText Functional Testing Lab server machine. The file is located here:
- Windows server: <Path to OpenText Functional Testing Lab server installation folder>\server\log
- Linux server:<Path to the OpenText Functional Testing Lab server installation folder>/server/log

iOS 17+ devices are not detected. Failed to create new MIB_UNICASTIPADDRESS error.

For iOS17.4 and later, the Windows machine must be able to allow the creation of a network adapter. This adapter must bind to an IPv6 address. If you cannot connect devices running on iOS 17.4 and later, check the tun_device.log file located in Functional Testing Lab for Mobile and Web Connector\tunDevice\log\. If there is an MIB_UNICASTIPADDRESS error in the file, resolve the issue as follows:

Check that the value of the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents is 0x00. If the value is not 0x00, change the value to 0x00.
In the IPv6 Configuration Policy, select the option to enable all IPv6 components.
Restart the Windows machine.

For more details, see configuring IPv6 in Windows in the Microsoft documentation.

App features are blocked by a firewall

During installation, if Windows issues the warning “Windows Firewall has blocked some features of this app”, click Allow access or contact your system administrator. When this message is issued, the current Connector installation is aborted.

Remote device view is blocked

If you cannot view a remote device in the OpenText Functional Testing Lab device lab, this may be a result of the anti virus software installed on the machine. For example, McAfee Host Intrusion Prevention blocks access. Workaround: Disable the anti virus while running the test.

Remote device access or recording fails

The Windows connector starts successfully and the device displays in the OpenText Functional Testing Lab device lab, but remote access or recording do not work. Sometimes OpenText Functional Testing Lab issues a message with the problematic IP address and port. In other instances, you may receive a "connection refused" message, indicating an IP address problem:

Check the service.log file on the OpenText Functional Testing Lab server machine and look for possible "connection refused" errors:
- Windows server: <Path to OpenText Functional Testing Lab server installation folder>\server\log
- Linux server:<Path to the OpenText Functional Testing Lab server installation folder>/server/log
Check that the IP address (shown in the error message) that OpenText Functional Testing Lab is trying to reach, is the correct one for your connector machine. To show the IP address of your machine, open a command line window and type ipconfig.

If, for example, you were connected to a different network or IP when you installed the connector, you need to run the Modify configuration utility under Start > OpenText Functional Testing Lab Connector and enter the new IP of the connector machine.
Check that the port shown in the error message, is open for incoming traffic on the connector machine.

Proxy and SSL issues

If you indicate SSL during connector setup, proxy machines that require credentials are not supported.
If you have a device connected when you install the connector for an SSL environment using a proxy server, the devices do not appear in OpenText Functional Testing Lab. Workaround: Connect the devices after you install the connector software.

Could not reach the server error message

While trying to connect to a secure SSL lab server: If you receive a message "Could not reach OpenText Functional Testing Lab server", this may be due to a modified CA certificate on the server machine.
Solution: Reconfigure or modify the connector and retrieve the new certificate.

Connection refused or connection timed out message

When trying to run the installation, if the setup program issues a "connection refused" or "connection timed out" warning, it could mean that:

The server is down. Check that you can ping the server.
The IP address of the lab server is wrong.
The port for the connector is wrong.
The version of the connector that you are using is not compatible with the version of the server. Check OpenText Functional Testing Lab on ADM Marketplace to see that you are using the most up-to-date version of the connector.

If the server details (IP address or port) have changed since you last installed the connector, modify the connector and specify the new information.

Port conflicts prevent the connector from starting

If an existing service running on your machine is claiming the port on which the connector runs, there is a conflict, and the connector does not start up.

To change the port, run the Modify configuration utility under the Start > OpenText Functional Testing Lab Connector menu.

Unable to install Agent due to prior installations of Android SDK

If you installed the Android SDK for a specific user (not the SYSTEM user), the Windows connector setup program may be unable to install the Agent, because the manually installed SDK is not accessible from the SYSTEM user.
Workaround: Reinstall the Android SDK as a SYSTEM user, and delete the ANDROID_HOME environment variable.