GeinDock Suite
Home › Troubleshooting

Troubleshooting

Problems grouped by where they show up, with the cause that explains most of them first.

Problems grouped by where they show up, with the cause that explains most of them first.

A message appears at start-up

Message What it means What to do
3D Viewer Unavailable, with Quit and Continue Without 3D View.The graphics driver on this computer does not provide OpenGL 3.3, which the viewer needs. The message states the version it found.The message lists three fixes. Install the current graphics driver from Intel, AMD or NVIDIA, because the one Windows installs by itself often falls short. On a laptop with two graphics chips, set GeinDockSuite.exe to "High performance" in Settings › System › Display › Graphics. Run the application on the computer itself, not over Remote Desktop. If you continue instead, no structure is drawn and any step that needs the 3D view will not work.
Licence Check Failed: "The licence could not be checked."The check itself could not be carried out. It is not a problem with your licence.Press Retry. Do not activate again. If it persists, send the text of the message to support.
Licence Not Readable: "Your licence could not be read just now."Windows would not let the application read its settings at that moment, usually because security software or another program was holding them. The licence is intact.Close any installer or antivirus scan that is running, then press Retry. You do not need to activate again. If it keeps happening, contact support.
Licence Error: "The system clock appears to have been set backwards, so the licence cannot be verified."The computer's date or time is earlier than it was when the application last ran.Set the correct date and time in Windows, then start GeinDock Suite again. Activating again does not help while the clock is wrong.

The run will not start

Symptom Likely cause What to do
Run Docking is greyed out.One of the steps it depends on is incomplete.Hover over the button. Its tooltip names the exact thing that is missing.
Step 1 shows loaded rather than prepared.The structure was read but preparation was never run.Reopen the receptor dialog and press Prepare Protein.
Step 2 shows added.At least one ligand did not prepare.Reopen the ligand dialog and read the Status column to find which.
A specialised mode reports its step 4 as not set.The mode's picker has not been filled in.Open it and make a selection. Those modes cannot run without one.

The run fails or produces nothing

Symptom Likely cause What to do
A job fails immediately, before any progress.Endpoint protection is blocking the backend processes.Read the Log panel for the actual error, and add the install folder to your protection product's exclusions. Folder names with accented or non-Latin characters are handled from version 3.2 and are no longer a reason to move anything.
One ligand fails and the rest of the batch continues.That structure could not be prepared.Look at it in the ligand dialog. A zero atom count or an invalid status means the file did not parse.
The run completes but reports no poses.Nothing fitted inside the box.Check the box in the viewer with Analyze › Show Grid Box. A box that is in the wrong place, or smaller than the compound, produces exactly this.
Every score is close to zero or positive.The ligand is not in the site, or the receptor has no charges.Confirm the box position, and confirm that preparation actually ran rather than being skipped.

The results look wrong

Symptom Likely cause What to do
The top poses are several Ångström apart with almost identical scores.The search did not converge.Raise exhaustiveness, tighten the box, and check the ligand conformer. Clustering confirms the diagnosis.
The pose sits outside the pocket, on the surface.The box is in the wrong place, or it is a blind docking box.Redefine the box from the co-crystallised ligand and run validation.
Validation fails at every configuration.Something upstream is wrong rather than the box.Check that the right chain was kept, that a needed cofactor or metal was not stripped, and that the box is centred on the right ligand rather than a buffer molecule.
Validation reports a low best RMSD but a high top pose RMSD.The search found the crystal pose and the scoring function did not rank it first.Look further down the pose list, try another scoring function, or express what you know as a constraint.
A flexible run is worse than the rigid one.The enlarged search space was not matched by more search effort.Reduce the flexible selection to the residues you can justify, or raise exhaustiveness.
Every pose satisfies the constraint.The constraint is too loose to restrain anything.Tighten the radius, switch a sphere to the ligand centre, or use a named atom instead.

The display looks wrong

Symptom Likely cause What to do
The viewport is black and nothing is drawn.Nothing is loaded, or everything is hidden.Check the Project panel, and check the checkboxes in the Structure panel.
The ligand is drawn far away from the protein.A ligand loaded on its own keeps its own coordinates and has not been docked.This is expected. The status bar says so. Run the docking to get a pose in the site.
The structure looks like beads rather than a smooth cartoon.The cartoon needs secondary structure, which a model without it cannot supply.Use ribbon or tube instead.
A surface takes a long time or does not appear.Surfaces are expensive on large structures.Use the Gaussian surface, or restrict the surface to the pocket from the Interactions panel.
Labels are unreadable over the structure.They are the same colour as what is behind them.Open Analyze › Label Settings and turn on the plate behind each label.
The panel layout is a mess.Panels have been dragged around.View › Panels › Reset Panel Layout.

Performance

Symptom Likely cause What to do
A run takes far longer than expected.The box is too large. This is the most common cause by a wide margin.Check the volume in the grid dialog. A site sized box is a few thousand cubic Ångström; a whole protein box is many times that.
The whole machine becomes unusable during a run.The search is using every core.Reduce CPU Cores in the settings dialog.
The viewer is sluggish.A surface or a spacefill representation on a large structure.Switch to cartoon, hide the chains you are not using, or restrict the surface to the pocket.

The Co-Scientist

The status in the header of the Co-Scientist panel names the problem in a word or two. The table of connection states in Meet the Co-Scientist covers every one of them; the rows below are the cases that are not a connection state.

Symptom Likely cause What to do
The message box is greyed out.The terms of use have not been accepted, or the assistant has been switched off for a time.Press Read the terms on the start screen and accept them. If the footer carries a message instead, wait and press the reconnect button in the header later.
The header shows a status other than Ready and nothing can be sent.The assistant cannot reach the GeinDock AI service, or the licence or the allowance does not permit it.Hover over the status for the full message, then follow the connection states table. The rest of the application is unaffected.
The assistant seems to have stopped partway through a task.It is waiting for you. The status reads Needs approval or Needs your answer.Scroll to the end of the conversation and answer the card, or type what you want instead.
A docking run it started carries on after you pressed stop.Stopping the assistant stops the conversation, not the job.Press Stop in step 5 of the Docking Panel.
An answer states something that does not match the screen.The assistant works from a summary of the session and can misread or misremember it.Tell it what you see, and check the result in the panel that holds it. See the limits listed in Working with the Co-Scientist.
The allowance meter is amber or red.The allowance for the period is running low, or is used up.See Conversations, allowance and privacy for the reset date and for ways to use less.
"The Co-Scientist service is busy. Please wait a moment and try again."Too many requests reached the service at once. Nothing is wrong with your session.Wait a little and send the message again.
"The conversation is too long for the model."The conversation has grown beyond what the assistant can read in one go.Start a new conversation and restate what you need. The old one stays saved.
"The connection to the Co-Scientist service was interrupted", followed by a reason.The link to the service dropped while an answer was arriving.Check your internet connection and send the message again.

Reading the log

The Log tab beside Analysis carries the full commentary from the application and from the backend. When something goes wrong, read it from the point where the job started rather than from the end, because the cause is usually a decision made early rather than the error reported last.

What to include when you report a problem. The version and build from Help › About GeinDock Suite, the docking mode you were in, the relevant part of the Log panel, and the saved project file if you can share it. The About window shows the build and its date under the version, and its Copy details button puts all of it on the clipboard ready to paste into an email. Between them those four almost always identify the cause.

Getting help