Double click the client.wyc file. Look at all the URLs. Try those URLs in a browser and see which ones go slowly. It's likely a local proxy or firewall that's blocking the downloads.
Long delay when checking for updates; one-time Internet access needed
Dear support team and wyBuild community,
our update package is located on a network drive. Besides, I have set the self update path to "%updatepath%/wyupdate.wys". I did this in order to avoid the need for an Internet connection.
The problem now is that on some of our test computers the update check lasts about 20-40 seconds, while on others it takes only 3. The needed time on the slow computers seems to be additionally dependent on the logged-in Windows user.
Note that all Windows users have access to the update path. Besides, on other computers the delay was less than 10 seconds for admin users as well as for restricted users.
Do you have any idea which Windows and/or network configuration is relevant for the time duration needed for the update check? Or do you have any other idea how we can solve the problem?
Thanks a lot for any hint and best regards,Markus
Hi Sam,
thanks for your answer!
The client file shows the following URLs:- Server sites: %updatepath%/wyserver.wys- Self-update sites: %updatepath%/wyupdate.wys
I entered these URLs for the following reasons:1. The updates of our application are always located in the customer's intranet.2. Regarding the self-update: I don't want wyUpdate to connect to the Internet, because the customer's computers usually don't have Internet access.
Now I found out the following:1. Start of the batch file which calls wyUpdate and then our application, without having Internet access -> delay of 30-60 seconds, depending on computer2. Connection to Internet established via entering a required proxy server3. Start of the batch file -> no delay at all (max 1 sec.)4. Connection to Internet disabled by removing the proxy server from the configuration5. Start of the batch file -> still no delay
This test shows that wyUpdate needs to connect to the Internet once. After this, no subsequent Internet access seems to be needed.
Now my question: How can I avoid completely that wyUpdate tries to connect to the Internet? As I said, everything shall be done purely within the costumer's Intranet.
Thanks and best regards,Markus
I forgot to mention:This is the call of wyupdate.exe inside the batch file:wyUpdate.exe -updatepath=file:///d:\ExampleDir(Usually this would of course be a network path, but for testing purposes and to exclude the possibility of access restrictions, I entered a local path.)
Only the application's update package including wyserver.wys is in this directory. I don't have any self-update related stuff there. Hope this isn't needed.
Besides, even in the case that the given path "d:\ExampleDir" does not exist, I would not expect wyUpdate to connect to the Internet.
Best regards,Markus
Now my question: How can I avoid completely that wyUpdate tries to connect to the Internet? As I said, everything shall be done purely within the costumer's Intranet.
It only connects to the internet if it needs to. Run wyUpdate from a debugger or setup WireShark and see what's happening. My guess is something funky is going on at these customer's intranet. Probably a misconfiguration of some kind.
Only the application's update package including wyserver.wys is in this directory. I don't have any self-update related stuff there. Hope this isn't needed.
Yes, it is needed. That might be the cause of the slowdown.
So I need to put the file "wyupdate.wys" into my %updatepath% directory, in order stop the self-update process to browse the Internet for it?
Then can you tell me where I can get the current "wyupdate.wys"?
So I need to put the file "wyupdate.wys" into my %updatepath% directory, in order stop the self-update process to browse the Internet for it?
wyUpdate doesn't "browse the internet for it". wyUpdate only looks where you tell it to look. If you tell it to look at a locally hosted intranet file, then it will only look at that locally hosted intranet file. It sounds like your intranet is doing something funky. But this is outside the scope of wyUpdate. There are a variety of tools to help you debug your networking problems.
Then can you tell me where I can get the current "wyupdate.wys"?
Hi Sam,
you may want to know that the reason for the delay had nothing to do with funky intranet configurations. Also your hints did not really solve our problem.
Here's the link to the solution:http://blogs.technet.com/b/markrussinovich/archive/2009/05/26/3244913.aspx?Redirected=true
After adding the mentioned config file to our installation directory, the delay was gone completely.
Maybe you want to add this information to your trouble-shooting database for future user questions. 😉
Best regards,Markus