Vulcan Troubleshooting

Ensure nVidia Optimus / AMD PowerXpress doesn't disable the dedicated graphic device

nVidia Optimus and AMD PowerXpress can disable the dedicated driver and revert to the "battery-saving" Intel driver. While going forward we are actively looking for ways to prevent 3rd party software from disabling these graphics cards, in the meantime please follow the steps in the attached technical note.

Tcsh failing with MS short path disabled: "No such file or directory" or "Command not found" error

The file system is not configured to generate 8dot3 names which Vulcan tcsh requires.

Running the command (as Admin) 'fsutil 8dot3name query C:' can tell us the state on volume C: if that's where Vulcan is installed. It is likely to be 1 if this problem is encountered.

Running the command (as Admin) 'fsutil 8dot3name set C: 0' sets it correctly on volume C:.

Running the command (as Admin) 'fsutil 8dot3name set 0' sets it correctly on all volumes.

Design databases reporting errors

Design databases were reporting errors for multiple users, across multiple sites of the one company, when they attempted to access them. Typical error messages eg.

**IDBINX, Error opening database L:\Vulcan\PLANNING\cn_go-line.wrk.isis

**IDBINX, Invalid logical database number

**IDBINX, Erro opening database L:\Vulcan\PLANNING\cn_go-line.wrk.isis

**IDBINX, Invalid logical database number

Troubleshooting revealed that the users experienced no issues with the same databases if these were placed in a C:\drive folder, repaired and then used in this location. Issue exclusively affected design databases that were located in a server folder.

The issue was with Windows Defender version (mostly in relation to Defender ATP). Updated to latest solved the issue.

Was this page helpful?