Posted: 10 Apr 2017 13:21 EDT Last activity: 16 Oct 2018 12:03 EDT
msiexec.exe failed to start within the given timeframe
I am new to the Robotics Automation course and while going through the Windows adapter exercise, i am encountering the following error " the process msiexec.exe failed to start within the given timeframe"screen shots attached. if anyone else has faced the similar issue, please help in resolving he same. Thanks in Advance.
***Updated by moderator: Lochan to move post from PSC to Pega Academy***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Path property to C:\Program Files (x86)\OpenSpan\CRM Setup\CRM.exe and
Working directory to C:\Program Files (x86)\OpenSpan\CRM Setup.
But didn't help.
Even I tried SRIDHAR17's suggestion to add CRM.exe full path to Target path. Still didn't work. By doing so, it says, "The process CRM.exe failed to start with in the given timeframe". So what ever the exe path we are giving in Target path, the corresponding application's timeout error is getting returned.
Ok. I have changed the StartMethod from StartAndWait to Start and now I'm able to interrogate the login window. I guess for CRM test application there is no target application that needs to be ran upon running CRM.exe. Not sure if my understanding is correct.
If you use a path and target path together, you need to use the 'start and wait' start method. The target path would contain the location of the exe where you want to perform interrogation. The path would contain the exe that launches the process. Please be sure you are using Robotics studio v8.0.1063. Also please check your services and make sure the Openspan services are started.
I am experiencing the same issue. I tried all the above recommendations and none of them worked for me. I am using the Pega Robotic Studio Version 8.0.1089.0 on Window 10 home edition. I am unable to interrogate. Any help to resolve this issue would be greatly appreciated.