Troubleshooting Startup on Windows

 

 

 

Have error messages printed to the window on startup

1. Open the Schrodinger Command Prompt

START → Schrodinger release → Schrodinger Command Prompt

 

2. Run the following command:

maestro_console

 

3. Request support and upload the console errors printed to the window.

 

 

 

Conflicting Python installations

If there are conflicting installations, Maestro can fail to start with import errors:

Import Error: No module named…

There are a few different approaches to avoid this situation listed in this article.

 

 

 

Profiles

Each profile activates a different set of menus or tasks. Different profiles can be affected by different licenses. For example, the Materials Science profile has special mouse action bindings. The Maestro BioLuminate profile opens with a panel on the right side. Please try to change the profile you are using to see if that makes a difference. If not, please follow the instructions in Conflicting settings / preferences from earlier Maestro installations to clear out the user profile.

 

 

 

Conflicting settings / preferences from earlier Maestro installations

Start with an empty local Schrodinger folder as it contains settings and preferences and feature flags. On Windows there are two folders containing settings, preferences and feature flags:

C:\Users\<user_name>\AppData\Local\Schrodinger
C:\Users\<user_name>\AppData\Roaming\Schrodinger

Make sure no jobs are currently running and then try to remove or rename these folders and then start Maestro again and say “No” if there is a prompt asking to copy settings from earlier releases. If the above locations do not appear to exist, try navigating to the locations %LOCALAPPDATA%\Schrodinger and %APPDATA%\Schrodinger instead.

 

 

 

Graphics card driver

If Maestro fails to start showing graphics related errors, please try to start Maestro using:

START → Schrodinger release → Low Graphics Versions → Maestro

If this allows Maestro to start, then you will most likely have to update the graphics card driver on your machine.

 

 

 

Qt related errors

To get more information on errors related to Qt, please open: 

START → Schrodinger release → Schrodinger Command Prompt

run:

set SCHRODINGER_SHOW_QT_MESSAGES=1

followed by:

maestro
NOTE: The output can be quite long.

 

 

 

License issues

If Maestro is not starting due to license issues, please see Schrödinger License Manager Instructions.

 

 

 

Need for Visual C++ libraries

If Maestro fails to start and the DOS startup window shows the following error:

The system cannot execute the specified program.

This indicates that the Visual C++ libraries are probably not installed. These libraries need to be installed by a user with administrator privileges, and they are available in the software distribution, in the “thirdparty” folder seen in the extracted installation bundle folder. Run the vcredist_x64.exe executable to install the libraries.

 

 

 

Unicode / locale

If the system Locale is not set to English US by default, please try switching the Locale to English US to see if that helps. You can set the Locale in the Clock, Language and Region section of the Windows Control Panel.

Unicode characters in the user name are not supported. If possible, please create a user name without special characters.

 

 

 

Antivirus program

Some antivirus programs can quarantine files from the installation (exe and/or dll files), preventing Maestro from starting. Other antivirus programs can cause long startup times as the program is scanning the files in the installation upon startup. Please try to temporarily disable the antivirus program to see if that makes a difference.

 

 

 

Permission issues

If the installation was done by someone other than yourself, please make sure that you have permission to access the installed files.

 

 

 

Submit support request

Request support and and provide any error messages that you see when trying to start any of Maestro, Maestro BioLuminate, or Materials Science Maestro. Please also include the diagnostic archive of the affected machine, following the instructions in this article.