Altair RISE

A program to recognize and reward our most engaged community members

Nominate Yourself Now!

Unable to connect to the Monarch internal database

Hello all

Long time user of v10.5, just made the jump to v14. We've only got it installed on a couple of machines so far but one (mine) is having a problem when trying to switch to Classic Mode. I'm getting an error that says "Unable to connect to the Monarch internal database." The other PC doesn't have this problem. Can anyone suggest what might be wrong? In theory the two PCs are identical - we're a large public sector organisation and our PCs are tightly controlled by IT so we can't make any unauthorised changes.

Thanks

Andy

Find more posts tagged with

English

Monarch

Accepted answers

All comments

Altair Forum User

I have seen this a couple of times. Usually the fix for me was to reinstall Monarch. If you your machine is locked down with User Access Controls, try running the installer as administrator.

Altair Forum User

I have seen this a couple of times. Usually the fix for me was to reinstall Monarch. If you your machine is locked down with User Access Controls, try running the installer as administrator.

Thanks - I'll give that a try.

Altair Forum User

Andy,

In addition to Chris's reply if running the install again (after a machine reboot perhaps?) does not deliver a solution you may need to consider whether there is some form of system protection deployed that is preventing a complete install of sub-component programs like specific .NET routines to offer one example.

Also anything related to the current status of Windows and any related Office applications on your machine compared to the one that works.

If, somehow, you have managed to get hold of Windows 10 Fall Creators Release then all bets are off! (Yes, I know that is extremely unlikely in your locked down corporate environment ...)

There should be a log file for the installation somewhere. It might offer some clues.

HTH.

Grant

Mike Reed

The resolution to the below error is to delete the authorization token for your machine, which deletes your machine from the Authorized Machines list on your profile, then generate a new Auth token for the same machine. This resolved the below error we were getting:

Daniel Cloutier

Hi,

I'm having the same error message.

Uninstalled and reinstalled Monarch, the Visual C++ components and the SQL server 2017 LocalDB.

deleted the Auth Token and recreated it. and activated it successfully.

Still get the error.

Anything else I should look for?

Thanks!

Community-Pasted-Attachment-1679327059207.png