Forum Discussion

h_jansen's avatar
h_jansen
Occasional Contributor
9 years ago
Solved

TC11.30 TestedApps do not run when having an UNC path of network path

 

I have installed the latest TestComplete 11.30 yesterday.

Now all my tests fail because the application will nog start anymore.

The error is "The system cannot find the file specified."

 

In the TestedApps we start an application on N:\path\start_data.bat

When I browse in TestedApps the batch file can be found, and it worked on TC 11.20.

When I start WinWord on the C-drive it starts.

 

So it appears to be the network/UNC-patch that makes it inpossible to start.

 

Keyword Tests
Network
testedapps
UNC
  • TanyaYatskovska's avatar
    TanyaYatskovska
    9 years ago

    Hi Guys,

     

    I see that our R&D Team has confirmed this issue in TestComplete 11.3, and they are preparing a patch that should fix it. The patch should be ready very soon. So, if you haven’t contacted our Support Team yet, please get in touch with them and request the patch. Here is the patch ID that you can specify in the message: CC-6032

    We are sorry for the inconvenience.

17 Replies

Sort By
  • m_essaid's avatar
    m_essaid
    Valued Contributor
    9 years ago

    Hi,

    I had this problem with the new version 11.30

    All my .bat files where invisible for TestComplete

    It's not related to UNC locations

    I separated the call to cmd.exe and the command line

     

    For example :

     

    TestTedApps.Clear;

    TestedApps.Add('cmd.exe', '/c \\ (enter your unc here)\batchfile.bat', 1, true, '');
    TestedApps.cmd.Run;

    • qtrolazyg's avatar
      qtrolazyg
      Contributor
      8 years ago

      Do you know the patch for UNC was included in version 11.31?

      • TanyaYatskovska's avatar
        TanyaYatskovska
        SmartBear Alumni (Retired)
        8 years ago

        Hi Qtrolazyg,

         

        Sure. Update to the latest product version.

         

  • h_jansen's avatar
    h_jansen
    Occasional Contributor
    9 years ago

    Issues has already been reported with the Custer Care Team: Case #00165579

    • TanyaYatskovska's avatar
      TanyaYatskovska
      SmartBear Alumni (Retired)
      9 years ago

      Great. Thanks.

      Please let us know the solution when you and the Team find it.

  • JNeedles's avatar
    JNeedles
    Contributor
    9 years ago

    I'm also having this problem using:

     

    \\HQLIFSP02\Magic\Magicxpa2.4\MgxpaRuntime.exe

     

    Worked fine before the upgrade.  Saying it can't find the file now.  Should I open an additional ticket?

    • JNeedles's avatar
      JNeedles
      Contributor
      9 years ago

      Difference seems to be this:

       

      Command Line in 11.20:

       

      "\\hqliapd05\Magicxpa2.5\MgxpaRuntime.exe" /ini=xpaPREPUser.ini /StartApplication=%APPLIC%al.ecf

       

      Command line in 11.30:

       

      UNC\hqliapd05\Magicxpa2.5\MgxpaRuntime.exe" /ini=xpaPREPUser.ini /StartApplication=%APPLIC%al.ecf

  • h_jansen's avatar
    h_jansen
    Occasional Contributor
    9 years ago

    Issue is not related to batch files only.

    When changing my testedapp to an executable on the UNC-path it also does not start with the message file not found.

     

    When I chamge the testedapp to a batch file on the local drive it will start from TestComplete.

     

    Fact is, it worked in 11.20 and does not work in 11.30.

    • m_essaid's avatar
      m_essaid
      Valued Contributor
      9 years ago

      it's related to the new 11.30 version.

      unc paths where already working before and are still working

      • TanyaYatskovska's avatar
        TanyaYatskovska
        SmartBear Alumni (Retired)
        9 years ago

        Hi Guys,

         

        I see that our R&D Team has confirmed this issue in TestComplete 11.3, and they are preparing a patch that should fix it. The patch should be ready very soon. So, if you haven’t contacted our Support Team yet, please get in touch with them and request the patch. Here is the patch ID that you can specify in the message: CC-6032

        We are sorry for the inconvenience.