Skip to content

A freshly built test/training environment installs without any errors, but logging in as the application owner afterward returns an 'Operation timed out' error. What's a good first thing to check?

Answer

Check the Machine and Address configuration for the Middle Web Server (MWS) instance — the Machine name field is often pre-populated correctly by the installer, but the Address field commonly comes up blank and needs to be manually set to match the actual hostname of the VM/server used for the installation. A blank or mismatched Address value is a common cause of an operation-timeout error on a first login attempt against a freshly installed environment.

← Browse Developer Studio, deployment, and upgrades questions