For details about how to use the Check for Updates service, see Using Check for Updates.

Error: There is a problem saving the download file to your computer

This error message is displayed if:

You don't have enough disk space

The Check for Updates service downloads the updates to the location defined by the RGTEMP environment variable, or the TMP variable if the RGTEMP variable doesn't exist.
If you don't have enough disk space, you can change the environment variable to a location with more space. 

There's a problem with permissions on your computer

The Check for Updates service downloads the updates to the location defined by the RGTEMP environment variable, or the TMP variable if the RGTEMP variable does not exist. If your user account doesn't have permissions to write to the location specified by these environment variables, contact your system administrator.

There's a problem with the download file on the Redgate web server

Contact Redgate support.

Error: There is a problem with the network connection

This error message is displayed if:

Your internet connection dropped while the Check for Updates service was downloading the updates

Try checking for updates again later.

Proxy authentication failed

Check your user name and password.

Your computer can't connect to the Check for Updates service.

Contact your system administrator. If you're using a proxy server, check it's configured correctly (see Control Panel > Internet Options > Connections).

There's a problem with the download file on the Redgate web server

Contact Redgate support.

The Redgate Check for Updates service, available through the Help menu of most Redgate products, may fail to connect to the Redgate update service if internet access goes through a proxy server that requires authentication.

The Check for Updates service uses SOAP to communicate with a web service hosted at update.red-gate.com on TCP port 80. The service supports connections through an HTTP proxy as long as the proxy server integrates with Internet Explorer and has been properly configured in Internet Options > Connections (available from Internet Explorer or Windows Control Panel). In other words, Check for Updates uses Windows WinInet API to send and receive requests for updates.

If the proxy server doesn't integrate with Windows and doesn't support transparent NTLM authentication, Check for Updates will prompt you for a proxy username and password and try to authenticate using Basic Authentication. Finally, the request will fail with the message "could not connect to the update service".

Even when WinInet is properly configured for your proxy server, there are two known circumstances that may cause Check for Updates to fail:

• An automatic configuration script is used to configure the Internet Explorer proxy connection. In this case, the connection properties can be configured differently for every connection. This can cause Check for Updates to behave erratically, sometimes being able to connect and sometimes not. 
• A bug in some versions of Check for Updates whereby any proxy server that doesn't have "realm" configured will cause Check for Updates to crash. Contact your proxy administrator to make sure a realm is configured in the authentication settings.