Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: 500 Internal Server Error when installing a hotfix (Internet Explorer)

Suggest edit Updated on May 7, 2019

When you install a hotfix using Internet Explorer as your browser, you might encounter the 500 Internal Server Error or "The page cannot be displayed" error. This occurs if the DL file containing the primary hotfix (or hotfixes) also contains a large number of dependent hotfixes (Additional Related Hotfixes), such as for example, over a hundred dependent hotfixes.

Errors

500 Internal Server Error

The page cannot be displayed.

Explanation

When Update Manager installs a large number of hotfixes from a DL file, the browser client is not aware that the PRPC server needs a long time to scan system inventory and install the large number of hotfixes delivered in the DL file. Internet Explorer imposes a time period by which the server must return data. When that period lapses, Internet Explorer times out.

You see the Internet Explorer error because the browser assumes that there is no response from the PRPC server. However, the primary hotfix and all of its dependent hotfixes (Additional Related Hotfixes) are successfully installed.

You can prevent the 500 Internal Server Error from occurring again by adjusting the Windows registry key for the Microsoft Internet setting ReceiveTimeout.

Suggested approach

Read the Microsoft Support article KB181050, Internet Explorer error “connection timed out” when server does not respond - [181050]

Choose one of the options provided in this article:

  • Fix it for me
  • Let me fix it myself

Reference

Internet Explorer error “connection timed out” when server does not respond - [181050]

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us