Error 2502 - "Could not open request"

[Elleah]

Hi,

I believe that TU2 automatically detects firewall but I am wondering why one of my user encountered an error 2502. They are using fortigate-100A firewall. Before performing the update they have to un-plug first the firewall and plug again after performing the update. Why is this happening? The update file is not blocked by their firewall.

I have attached my script and the log file of my user. Please advise what's the possible cause.

Thanks for the help in advance.

Regards,
Elleah

[Mark]

Hi Elleah,

TrueUpdate automatically detects proxies, not Firewalls. Firewalls are programs/hardware that is designed to control access to the Internet from your computer.

It sounds like your users will have to configure their firewall to grant your client executable access to the Internet. Once they do this they shouldn't have any more problems.

I did notice something else interesting when I was looking at your log file. What I noticed was that in the second stretch of runs with the firewall plugged in that your update ran successfully, yet it always seemed to quit after the: "Success Run client data event: Client Script" line.

[Elleah]

Hi Mark,

According to my user, they have grant the permission already and all the update files I am using while performing the update is not being blocked by their firewall. What else should be the possible cause?

In your last paragraph, what does it mean then? Why it succeed, when it seems that the update doesn't do anything yet. Those lines also puzzles me, when I've tried to investigate the log file, I've also noticed it.

Thanks,
Elleah

[Mark]

Hi Elleah,

If the customer has given access to your client executable properly then I am not sure why it is failing when they have the router plugged in and succeeding when they do not. Perhaps they gave permissions to your old client executable, but because of updates they have not given permission to your current executable?

Maybe ask them which executable they have given permission to, just to be sure that they have given access to your update executable and not your main programs executable.

As far as my last paragraph is concerned I'm not really sure why that is happening either. Do you have any Application.Exit() actions in your client script? Is their any way that any of your screens might not be shown in your client script?