April 18, 201312 yr I am migrating some script steps that I used to do with TROI url to 360WebAssistant and I am experiencing some inconsistent results. My scripts integrate with many different 3rd part web services, mostly shopping cart APIs to retrieve order information. Sometimes the migration is seamless, I just change the TURL_Get function for a WAGetURL function submitting whatever url string is required and I get my xml response that I can parse. In this particular instance where I am getting my normal xml response when using TURL_Get, using the exact same URL all I am getting is this: "WebService.aspx" as a response when going through WAGetURL I have tried several configuration settings with different connection timeouts, character sets,etc but nothing seems to work. I cannot post publicly the actual url, but I could send it privately to a 360Works tech support member for trouble shooting. I would really appreciate your help, the main reason I am migrating from Troi to 360 is because I have a portfolio license that will allow me to run all these scripts with an auto-timer from the server and It would be very frustrating o have to shell extra money for a server upgrade with Troi when I already have the 360 server license. It must be something simple that I need to do differently or some step I am missing and that will be the key to fix other similar issues I am having with other API migrations. Thanks
Create an account or sign in to comment