18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
Rules for sahi.properties to check failure to open Sahi Controler
W.Simacek
Members
Sorry I did search through many pages of existing posts, but couldn't find my exact problem and the correct troubleshooting steps.
Basically, I can't use {ctrl}+{alt}+{dblclick} to open up the controller window, even after I pressed the {F5} key.
I've been able to start sahi successfully, although I installed it under c:\ruby192\bin\sahi on WindozXP.
? I can start sahi OK on the command line, but do I have to change any other configurations to reflect the new location?
My organization that has autoproxy script that uses port 8080, but our dev server is on port 9080.
When I go into FoxPro and check on Other, I see it is configured to use the autoproxy for our organization, and then it prompts me for UserID and Password the first time I go in.
I've been changing the sahi.properties, but I'm not sure if they need to tie to the proxy server in my browser or the port on the dev server?
? I changed the proxy.port to 8080
I changed all the external proxy server for http settings to first match the proxy port, but I've also tried setting it to the Dev port. The other variables I've moved between my main login and test logins.
?I'd really like to know some general rules of what needs to match to what and some troubleshooting steps to check?
Basically, I can't use {ctrl}+{alt}+{dblclick} to open up the controller window, even after I pressed the {F5} key.
I've been able to start sahi successfully, although I installed it under c:\ruby192\bin\sahi on WindozXP.
? I can start sahi OK on the command line, but do I have to change any other configurations to reflect the new location?
My organization that has autoproxy script that uses port 8080, but our dev server is on port 9080.
When I go into FoxPro and check on Other, I see it is configured to use the autoproxy for our organization, and then it prompts me for UserID and Password the first time I go in.
I've been changing the sahi.properties, but I'm not sure if they need to tie to the proxy server in my browser or the port on the dev server?
? I changed the proxy.port to 8080
I changed all the external proxy server for http settings to first match the proxy port, but I've also tried setting it to the Dev port. The other variables I've moved between my main login and test logins.
?I'd really like to know some general rules of what needs to match to what and some troubleshooting steps to check?