Post a reply to the thread: Again Network Communication Error : 5060
Click here to log in
What's the name of our main installation product (in uppercase letters), directly followed by the current year?
You may choose an icon for your message from this list
Will turn www.example.com into [URL]http://www.example.com[/URL].
Re: Again Network Communication Error : 5060 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
Re: Again Network Communication Error : 5060
Re: Again Network Communication Error : 5060 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
Re: Again Network Communication Error : 5060 Originally Posted by linder 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.
Re: Again Network Communication Error : 5060 Thanks so much for the update! Perhaps the password in your web update process is incorrect (or not set). Friedrich
Re: Again Network Communication Error : 5060 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.
Re: Again Network Communication Error : 5060 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
Re: Again Network Communication Error : 5060 Originally Posted by 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 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.
Re: Again Network Communication Error : 5060 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
Re: Again Network Communication Error : 5060 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
Re: Again Network Communication Error : 5060 Launched wupdate with /E /C /S options and sent result file to you.
Forum Rules