Forum Discussion

aa1's avatar
aa1
Contributor
5 years ago
Solved

Run a bat file from network does not work

Hi,   I am trying to use wshshell to run a bat file from cmd but somehow I cannot get it right. All I am doing is do a cd\ on the cmd to get back to local and then browse the network path. Do I n...
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    Rather than use "CD", set the CurrentDirectory property on the WshShell object.

     

    For that matter... you don't need to instantiate the shell object... TestComplete provides a wrapper.  I don't think, either, that you need to use the CMD /K anywhere in this... you just need to indicate the batch file to run... which is, I assum, the contents of the "path" variable.

     

    var path = "\\\abc.local\\def\\Clickonce\\AB\\stg\\xyz.temp.Desktop.application";
  WshShell.CurrentDirectory = "C:\\" //Or whatever you want your root to be
  WshShell.Run(path);
  Delay(10000);
aa1's avatar
aa1
Contributor

Hi tristaanogre ,

 

Thank you for the reply. I tried doing that but I couldnt make it to work. If I split it into two lines:

 

1. WshShell.Run("cmd /K cd\\") ----- Opens cmd and resets the path due to cd\

2. WshShell.Run("cmd /K" + path); -- Opens cmd and searches for the path and gives error that it cannot find the path specified. The path is not accessible from this location.

 

I need to reach the path after doing cd\ so how do I do it in two steps?

 

Please advise.

 

 

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

Rather than use "CD", set the CurrentDirectory property on the WshShell object.

 

For that matter... you don't need to instantiate the shell object... TestComplete provides a wrapper.  I don't think, either, that you need to use the CMD /K anywhere in this... you just need to indicate the batch file to run... which is, I assum, the contents of the "path" variable.

 

var path = "\\\abc.local\\def\\Clickonce\\AB\\stg\\xyz.temp.Desktop.application";
  WshShell.CurrentDirectory = "C:\\" //Or whatever you want your root to be
  WshShell.Run(path);
  Delay(10000);
  • aa1's avatar
    aa1
    Contributor
    5 years ago

    Hi tristaanogre Thank you. That works. It was able to instantiate the application. It now gives me a pop up to choose Run or Cancel. I scripted to choose the Run button and click it. It clicks but does not launch the application. If I manually click on the Run button, it launches the application however during automation it just stays in the background and does not launch the application. Any idea why?

     

     var path = "\\\\abc\Desktop.application";
  WshShell.CurrentDirectory = "C:\\";  
  WshShell.Run(path);    

  var dlgOpenFileSecurityWarning = Aliases.dfsvc.dlgOpenFileSecurityWarning;
  Sys.Desktop.Keys("[Tab]");
  Sys.Desktop.Keys("[Tab]");
  Sys.Desktop.Keys("[Tab]");
  dlgOpenFileSecurityWarning.btnRun.ClickButton(); 
  aqUtils.Delay(ProjectSuite.Variables.ExistsTimeout); 

 var p = Sys.WaitProcess("dfsvc");
  if (p.Exists)
  {
    //if (p.WinFormsObject("TrustManagerPromptUI").Exists)
    if (p.WaitWinFormsObject("TrustManagerPromptUI",10).Exists)
    {
      Sys.Desktop.Keys("[Tab]");  
      Sys.Desktop.Keys("[Tab]");  
      Sys.Desktop.Keys("[Enter]");
    }
   }
   AgentApp = Sys.WaitProcess("abc.Desktop",ProjectSuite.Variables.Timeout);

  aqUtils.Delay(ProjectSuite.Variables.ExistsTimeout);

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      5 years ago

      Probably should be asked as a different thread as it is, technically, a different problem.

       

      So... from what I see, this is a "ClickOnce" application that sort of does the install on click, right?  

      I'm guessing that what MIGHT need to happen is that you may need to run TestComplete as an administrator to ensure that proper elevated permissions are applied.

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      5 years ago

      As a sidenote... I tend to avoid hard-coded delays for waiting for processes and windows.

       

      Try the following... replace

       

        aqUtils.Delay(ProjectSuite.Variables.ExistsTimeout); 

 var p = Sys.WaitProcess("dfsvc");
  if (p.Exists)

      with simply

       

       var p = Sys.WaitProcess("dfsvc",ProjectSuite.Variables.ExistsTimeout);
  if (p.Exists)

      This will wait up to the timeout value and, if it returns sooner, will continue sooner.  That way if you have your timeout set to 60000 and the process is available in 30000, you will only wait 30000.

      • aa1's avatar
        aa1
        Contributor
        5 years ago

        Thanks tristaanogre . I will create a separate thread for this issue in that case. I tried running as an admin but that did not make any difference. Will also take note of the hardcoded delay improvement. Thank you!