TDoD: Error getting build information
Article ID: 4193
Updated On:
Products
Issue/Introduction
After upgrading to Windows 10, we are no longer able to access TDM using the TDoD (Test Data on Demand) URL. A popup window appears stating "Error getting repo…" and then after clicking OK we are getting, "Error getting build information. Application tried to connect to web service but web service cannot be reached. Please contact administrator.”
Our administrator was able to login with the user's credentials without any issue on a Windows 10 machine. We were able to login from a different machine having Windows 7 with no issue.
Environment
Cause
The Windows 10 workstation is unable to resolve the hostname of the Server running the GTService (TDoD). This could be because of a DNS issue, or because the Windows 10 workstation is set up for IPv6 communication.
Resolution
Add in the fully qualified server name to the Hosts file in C:\Windows\System32\drivers\etc. This will allow the workstation to pick up the TDoD Application Server name and communicate with it.
If your system is using IPv6, try the following:
First, ping the fully qualified hostname.
Per the help file below, -6 was used to force IPv6 communication.
C:\>ping
Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [-k host-list
[-w timeout] [-R] [-S srcaddr] [-4] [-6] target_name
Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet (IPv4-only).
-i TTL Time To Live.
-v TOS Type Of Service (IPv4-only. This setting has been deprecated
and has no effect on the type of service field in the IP Header).
-r count Record route for count hops (IPv4-only).
-s count Timestamp for count hops (IPv4-only).
-j host-list Loose source route along host-list (IPv4-only).
-k host-list Strict source route along host-list (IPv4-only).
-w timeout Timeout in milliseconds to wait for each reply.
-R Use routing header to test reverse route also (IPv6-only).
-S srcaddr Source address to use.
-4 Force using IPv4.
-6 Force using IPv6.
ping -6 fully.qualified.hostname
Ping request could not find host fully.qualified.hostname. Please check the name and try again.
Next, ping just the hostname forcing IPv6 communication
ping -6 hostname
Pinging fully.qualified.hostname [####:ab#:#####:ab#:####] with 32 bytes of data:
reply from ####:ab#:#####:ab#:#### : time=20ms
reply from ####:ab#:#####:ab#:#### : time=27ms
reply from ####:ab#:#####:ab#:#### : time=27ms
reply from ####:ab#:#####:ab#:#### : time=27ms
Next, add the fully qualified hostname to the Hosts file located in C:\Windows\System32\drivers\etc
The entry should look like:
####:ab#:#####:ab#:#### fully.qualified.hostname hostname
Additional Information
For more help, see community post https://communities.ca.com/thread/241758373.
Feedback
