Troubleshooting Studio Enterprise connectivity issues

Studio Enterprise is approaching end of life (EOL). Learn more.

Relevant Products

Studio Enterprise

Problem

Users are unable to connect to your Studio Enterprise server with Revu.

Solutions

You can isolate and resolve Studio Enterprise connectivity issues using the following information:

Is the correct Studio server URL being used?

Confirm that the Studio server URL listed in the Server Profiles dialog matches the hostname displayed in the Status section of the Bluebeam Studio Enterprise Administrator, and that it also does not begin with https://.

Has the Server Certificate been installed correctly?

If you're using a self-signed certificate, it must be installed in the Trusted Root Certification Authorities Certificate Store in Windows. You can confirm whether or not this has been done, and install the certificate, if needed, by following these steps:

  1. Run Internet Explorer as an Administrator.
  2. Enter the full URL for your Studio server in the address line. (e.g. https://YourStudioServerName.local).

If the page loads with a security error, then you'll need to install the public certificate (.cer) in the Trusted Root Certification Authorities Store, under Local Computer.

If a self-signed certificate is correctly installed and Revu is still unable to connect, check the machine name of the server, the name on the certificate, and the server URL in Revu for discrepancies. These must match or else Revu will continue displaying a security error and fail to connect.

Can other users connect to your Studio Server?

If some of your users are able to establish a connection to your Studio server, confirm whether or not they're using Studio accounts by logging in with their email address, or their Active Directory accounts. If it turns out that users who are unable to connect are trying to use their AD accounts, get them to try using their Studio accounts. However, if neither authentication method works you'll need to open the Studio Enterprise Administrator and restart the Bluebeam services by selecting Tools > Restart Server.

Are your Bluebeam products compatible with each other?

Please make sure that the version of Revu installed on the end-user machines or devices is compatible with Studio Enterprise 3.2.