Forum Discussion
Vivek72
11 years agoContributor
Hi All
I am not using Data-Driven Testing nor my scripts are hooked to any excel files. The problem is not just confined to excel files but Microsoft word too. To be sure I checked Task Manager if any Office related .exe files are running already before trying to open Microsoft files, so I can say no process was running already. But yes, if I close the default dialog that is displayed usually before any office application opens, I can see the .exe process related to that file in the task manager still running. Sys.Process("EXCEL").Terminate() or any such sort of commands are of no use because this issue is not created while script execution or after the script execution, it just happens if I open test complete and access project file from my Network location and then try to open any Office products from the same network location.
Thanks for all suggestions.
I am not using Data-Driven Testing nor my scripts are hooked to any excel files. The problem is not just confined to excel files but Microsoft word too. To be sure I checked Task Manager if any Office related .exe files are running already before trying to open Microsoft files, so I can say no process was running already. But yes, if I close the default dialog that is displayed usually before any office application opens, I can see the .exe process related to that file in the task manager still running. Sys.Process("EXCEL").Terminate() or any such sort of commands are of no use because this issue is not created while script execution or after the script execution, it just happens if I open test complete and access project file from my Network location and then try to open any Office products from the same network location.
Thanks for all suggestions.
Related Content
- 11 years agoMorgan
- 11 years agokpinnisetti
- 5 years agoADHDude
Recent Discussions
- 10 hours agodhundley