Again Network Communication Error : 5060

[Azz101]

Hello, trying to configure application deployment using SetupBuilder development edition. I can successfully install application using local IIS folder (http://computer_name:80/dep). Application correctly downloads all required files and installs. When trying to update using wupdate.exe, Network Communication Error : 5060 occurs. I know that is common error, but I read all related information from this forum and still cannot find a workaround:
1) IIS MIME-type settings for this folder allow "." extensions (treat as octet-stream) and I checked "IIS Server Image" checkbox, so install files are without extension. I also use "manifest" (without file extension) for manifest file.
2) I can successfully install application from this folder remotely, just cannot update.
3) I can download manifest file using Internet Explorer.
4) I tried to switch off firewall (both third-party and windows native). I also ensured, that wupdate.exe is allowed in firewall settings.
5) I checked registry settings after install and it seems its correct.

What else can I check to solve this problem?

[linder]

Hello,

I don't think that it is a firewall problem nor is it a registry problem. IMO, you still have a MIME problem or your configuration settings in the "iDeploy Web Update" properties are incorrect.

Check the following first (but as I understand it, you already did)
http://www.lindersoft.com/forums/showthread.php?t=1286
http://www.lindersoft.com/forums/showthread.php?p=7790
http://www.lindersoft.com/forums/showthread.php?t=13687

You said that the web install worked fine. Both web update and web install make use of the same download technology. Can you download the first cluster file with Internet Explorer?

Friedrich

[Unregistered]

Hello,

I don't think that it is a firewall problem nor is it a registry problem. IMO, you still have a MIME problem or your configuration settings in the "iDeploy Web Update" properties are incorrect.

Check the following first (but as I understand it, you already did)
http://www.lindersoft.com/forums/showthread.php?t=1286
http://www.lindersoft.com/forums/showthread.php?p=7790
http://www.lindersoft.com/forums/showthread.php?t=13687

You said that the web install worked fine. Both web update and web install make use of the same download technology. Can you download the first cluster file with Internet Explorer?

Friedrich
Yes, I checked this topics but now did it once again. I configured all MIME-types correctly, I also can download both manifest and cluster files using Internet Explorer. I also changed manifest file extension to INI like in first topic and added mime-type for .ini files but error still the same.

[linder]

Hello,

If you are interested, you can send your project file to support (at) lindersoft (dot) com and we'll review it for you. If you can download it via Internet Explorer and it's not caused by your firewall then the only thing left is an incorrect configuration setting.

Could you also post a screenshot of the error message?

Thanks,
Friedrich

[BLewis]

Hello,

If you are interested, you can send your project file to support (at) lindersoft (dot) com and we'll review it for you. If you can download it via Internet Explorer and it's not caused by your firewall then the only thing left is an incorrect configuration setting.

Could you also post a screenshot of the error message?

Thanks,
Friedrich

I've send a project file (.sb7) to aforementioned mail (hope it will pass through your spam system). Also, here is the screen capture of an error.

[linder]

Hello,

Received. I think it's caused by your Host Address specification. What you have there now seems not to be a valid host name (can't be resolved). I would suggest to use an IP address instead.

Does this help?

Friedrich

[BLewis]

But I'm using local IIS, so this host name cannot be resolved from outside. I tried to use 127.0.0.1 IP instead, web install completed fine, but the same error for web update.

[linder]

I mean WinSock can't resolve the Host Name you entered. I know that we can't access it from here.

If Web Install works fine with the very same configuration settings then I don't know why. Both web install and web update make use of the very same HTTP component.

Because we can't access your files from here, we can't test your scarario :(

In the wupdate.sb7 file (located in the Redist folder), Line 225 (which downloads the manifest file) returns error 5060 which is caused by a failed WinSock action.

Friedrich

[linder]

What you can try is the event logging option:
http://www.lindersoft.com/forums/showthread.php?p=47255&highlight=wupdate.exe#post47255

Perhaps this gives more information. You can send the file (same support address) and we'll see if it provides more information.

Friedrich

[BLewis]

Launched wupdate with /E /C /S options and sent result file to you.

[linder]

Unfortunately, sbevents does not give us more information. Your manifest.ini can't be downloaded because the WinSock recv() function does not return a valid HTTP stream.

Error 5060 is returned if the HTTP stream does not include a "Content-Length:" header.

Friedrich

[linder]

Quick question: what happens if you create a simply empty script and use the "Download File (HTTP)..." script function to download this manifest file. What does %_SB_ERRORCODE% return?

Friedrich

[BLewis]

Quick question: what happens if you create a simply empty script and use the "Download File (HTTP)..." script function to download this manifest file. What does %_SB_ERRORCODE% return?

Friedrich

I don't know exactly how to see %_SB_ERRORCODE% value (I didn't find it in sbevents.txt), but empty script with single "Download File (HTTP)..." downloads my manifest.ini to C:/ folder correctly.

[linder]

Hello,

Just display %_SB_ERRORCODE% with "Display Message Box...". It should be 0 if the functions succeeds.

Web install, Web update and "Download HTTP..." make use of the same download functionality. So I have no idea why Web install and Download HTTP works, but wupdate.exe does not (and wupdate.exe also uses "Download HTTP..."). It does not make any sense.

So "something" on your machine seems to block wupdate.exe execution in this case. I have not seen a similar issue in all the years (and wupdate.exe powers quite a few millions updates).

Friedrich

[BLewis]

I was able to solve this problem by using anonymous authentication for IIS folder where application files are hosted. So, one more solution for 5060 problem is found :)
However, it's strange that I can install application from IIS by using correct login and password, but can not update it.

[linder]

Thanks so much for the update! :)

Perhaps the password in your web update process is incorrect (or not set).

Friedrich

[BLewis]

Thanks so much for the update! :)

Perhaps the password in your web update process is incorrect (or not set).

Friedrich
"Use Web Update Login" was checked, so login data for web install and update should be the same as I understand.

[linder]

Yes, absolutely.

But I think about 99% of all web update users make use of password protected logins (and it works fine for years <g>). So there must be "something" in your configuration that causes this.

Friedrich

[linder]

BTW, there is no difference (from the technical point-of-view) between a web update method powered by IIS or, say, Apache HTTP servers. Our own web install and web updates are also login (password) protected -- it works fine without any problem.

But again, thanks for the update!

Friedrich