Test Data Manager

Expand all | Collapse all

Anyone have issues after upgrading to Windows 10 in accessing TDoD?

  • 1.  Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-28-2016 02:56 PM
      |   view attached

    I have a user who was able to access Grid-Tools using the TDoD url without any issue.  Now that she has been upgrade to Windows 10 she keeps getting the error window of "Error getting repo.." and then after clicking OK getting, "Error getting build information"....Application tried to connect to web service but web service cannot be reached.  Please contact administrator.

     

    User was on an older Silver Light version so she upgraded Silver light and rebooted and still got same issue.

     

    I was able to log in with user credentials without any issue...I have Windows 10.

     

    User was able to log in from a different machine having Windows 7 with no issue.

     

    Any suggestions would be greatly appreciated.

    Attachment(s)



  • 2.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-28-2016 03:54 PM

    Hi Jennifer,

     

    Please try the following solutions and let us know if it helps.

     

    - The Service URL needs to have the IP address instead of localhost.

    1. Go to C:\Grid-Tools\TDoD\TDoD_ConfigEditor

    2. Configure Portal tab

    3. Settings tab

    4. Service URL http://localhost:8090/GTService

    5. Change URL to the server IP address.

     

    - Delete the ALM Service URL (if not in use) from the TDoD Configuration Editor.

    1. Go to C:\Grid-Tools\TDoD\TDoD_ConfigEditor

    2. Configure Portal tab

    3. Settings tab

    4. ALM Service URL http://<<machinename>>:8095/ALMService

    5. Delete URL (or make sure it is the correct URL)

     

    If those solutions did not resolve the issue, please be sure to check the following:

     

    - 'Verify’ all settings and ‘Start Service’ for TDoD:

    1. Go to C:\Grid-Tools\TDoD\TDoD_ConfigEditor

    2. Configure Portal tab

    3. Settings tab

    4. Click the ‘Verify’ button. Take note of any success or error messages.

    5. Configure Service tab

    6. Click the ‘Verify’ button. Take note of any success or error messages.

    7. If successful, please click the ‘Start Service’ button. Take note of any success or error messages.

    8. Send support the log file in C:\Grid-Tools\TDoD\TDoD_Service\logs if you are still experiencing issues

     

    TDoD configuration references in documentation:

    - https://docops.ca.com/ca-test-data-manager/3-5/en/installing/install-test-data-on-demand/install-and-configure-test-data-on-demand

    - https://docops.ca.com/ca-test-data-manager/3-5/en/provisioning-test-data/data-reservation/test-matching-rally-integration/configure-test-data-management

    - https://docops.ca.com/ca-test-data-manager/3-5/en/installing/install-test-data-on-demand/pre-installation-tasks

     

    If none of these things resolved the issue, please open a support case so that we can investigate further and we will post the final resolution on here once the case is closed.

     

    Best regards,

    Taylor



  • 3.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-28-2016 05:23 PM
      |   view attached

    Thank you.  Will try and let you know



  • 4.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-29-2016 11:16 AM

    User with the issue does not have TDod on their computer.  I re-checked the server and all is configured correctly.



  • 5.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-29-2016 11:25 AM

    Hi Jennifer,

     

    The user does not have TDoD installed? How are they accessing TDoD and Datamaker?

    You can always open a support ticket if you are uncomfortable sharing environment details.

     

    Best regards,

    Taylor



  • 6.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 07-29-2016 08:20 PM

    Try these steps

    1. Ping the TDoD host by IP and Name – if fails – contact Network Admin
    2. Ping the workstation from the server by name and IP – if fails – contact Network Admin.
    3. Open the ports in the firewall Inbound and Outbound rules for 8090 similar to how the Server is setup.
    4. In the IE, verify that the TDoD Server is not a restricted site in the Internet Options > Security > Restricted Sites.
    5. 5. Check Ports 80 and 443 and see what is using them.

     

    If the User checkable items all show connectivity, then the next level of investigation would be to involve Level 2 people on both sides.  From the CA’s side, Development will be brought in to look the Application side. On the Client side, Network Administrators will need to be brought in to do communications via a network sniffer like Wireshark to see what packets and their contents are being sent back and forth.



  • 7.  Re: Anyone have issues after upgrading to Windows 10 in accessing TDoD?

    Posted 08-02-2016 12:09 PM

    The ultimate solution to this issue was to add in the fully qualified server name to the Hosts file in C:\Windows\System32\drivers\etc.  This allowed the workstation to pickup the TDoD Application Server name and communicate with it.

     

    To diagnose it was a Hosts file entry that was needed, pinging from the Client's workstation to the TDoD Server host iwith a none fully qualified name worked.  It failed when using a fully qualified name.  This lead to following:

     

    Steps to Diagnose:

     

    First, ping the fully qualified host name forcing IPv6 communication)

    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] [[-j host-list] | [-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 to the Hosts file located in this folder

     

    C:\Windows\System32\drivers\etc

     

    The entry looks like this in the Hosts file

     

    ####:ab#:#####:ab#:####    fully.qualified.hostname     hostname

     

    After entering the above entry into the Client Machine's Hosts file, all communication with regards to the TDoD Server started working.