You say "The only difference between 3 locations are the proxy pac URL asocciated to each server."
I think that a lot of people make their PAC handle this. They make the PAC smart enough to handle three locations instead of having three PACs. I realize this will make the PAC more complex.
The PAC stuff is not included in transaction definition/profiles, what other elements can make a transaction fail in a server and in the same server works ok if re-record the same transaction with no differences with the previous one?
How is your PAC setting different between the working and non-working script?
While TM ART Workbench uses Internet Explorer or a browser of your choice for recording, IE is not used during playback of at least some types of scripts.
For Web scripts (non BDM), proxy settings are in the project profile. In the Workbench
- Click on Settings, Active Profile...
- Be sure Replay is selected in the icon strip on the left, click on Web
- Click on the Proxy tab
The proxy setting in the Profile can also be overridden using the WebSetProxy() function but I'm not sure if there is a function to set a PAC from the script.
What you are reporting is very, very unusual.