Reply to Thread

Post a reply to the thread: another cause for 5060 error?

Your Message

Click here to log in

What's the name of our main installation product (in lowercase letters)?


You may choose an icon for your message from this list

Additional Options

  • Will turn into [URL][/URL].

Topic Review (Newest First)

  • 09-25-2017, 11:06 AM

    Re: another cause for 5060 error?

    Hi Chris,

    email sent

  • 09-25-2017, 10:18 AM

    Re: another cause for 5060 error?

    Here you go -
    This one is for a web install includes 9 segments.
    This one is on the secure site with no segments
    This one is on unsecured site with segments.

    send me a message to ccordes hat trva dot com and Ill send you the login info

    Thanks for the help,
    Chris C

    I hope this can help you in return.
  • 09-25-2017, 03:27 AM

    Re: another cause for 5060 error?


    it would be great if you could send me the link to a smaller "cluster" file and to the setup.exe for a web install / web update.

    Thank you for your help.

  • 09-23-2017, 10:49 AM

    Re: another cause for 5060 error?

    I'd be glad to put up an install up there for you to test.
    Do you want one that is segmented or whole?
    Send me an email and I'll give you the real URLs etc.

    Chris C
  • 09-23-2017, 05:25 AM

    Re: another cause for 5060 error?

    Thank you for your kind words, Chris

    BTW, did you remove the pgs_setup.exe from your secure site (https download link you posted)? I can't download it with IE or Edge, etc. Would it be possible to put it back so I can test the SSL functionality?

  • 09-22-2017, 05:59 PM

    Re: another cause for 5060 error?

    Many thanks, Friedrich for the quick reply at least now I know I'm not going crazy.
    With the size of this data, this will be better to download all of it from the secure site and do the non-data upgrades from the regular site.

    Thanks for the great product. I'm sure you'll have SSL working before too long.
    Chris C.
  • 09-22-2017, 11:07 AM

    Re: another cause for 5060 error?


    The core Windows Winsock component only supports HTTP communication. HTTPS communication is not supported. Many sites offer both a secure and a non-secure version. If you only have a secure version, then HTTP calls in SetupBuilder will always fail (e.g. with Error 5060 or 505010054 = WinSock Error Code 10054).

    We are working on "WUPDATE2.EXE" and "WUCHECK2.EXE" SSL web update clients which are powered by our new (soon coming) HTTPs support in SetupBuilder. This is not a trivial change and requires changes to be made to many of the internal compiler functions. Our SSL support will be backward compatible down to Windows 2000. It supports Windows 2000 - Server 2016.!

  • 09-22-2017, 09:20 AM

    another cause for 5060 error?

    Please excuse the length of the explanation.
    I've changed my setup to include a large data file. (Client request) To distribute, I'm adding Web Install. Web update has always worked well.
    Website has the usual structure where the public directory is where the root of the website exists and the download directories are below that.
    So will download the setup exe
    This also requires a login - user: password
    That all works fine. And when I set up Web Installation, these settings work perfectly.
    Host:, Port: 80, Host Directory: software/client, Host User: user, Host Password: password
    As a test this is just right. WebInstall works and the software gets installed.

    BUT Client requires a secure connection so I want to use the generic SSL that is included in my hosting package. Very easy. I enable the certificate and a directory is added to my site named secure.
    This directory is accessible through a different address -
    From there, the /secure directory is the root. I then create software/client directories under /secure and place the all the installation files in there.
    I can now download the installer from secure URL - Hooray!
    BUT, The installing crashes when it tries to get the file segments from the web. Error 5060.
    I've dealt with this before and I searched through the forum for other hints; I even contacted my host to see if they had something set oddly.

    Here is how I have it setup -
    Host:, Port: 443, Host Directory:, Host User: user, Host Password: password
    I've tried IIS Server Image checkbox both on and off
    and .bin File Extension on and off. - because I've had that issue before.
    Still Error 5060.

    Is there something that I should ask my host?
    Do you see ANYTHING I've got wrong?
    Is there a scripting change needed to handle the new secure URL?

    Thanks for any suggestions,
    Chris C

Posting Permissions

  • You may post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts