Sage Estimating Error: “You are not currently set up as a user of the selected Estimating server.  See your Estimating administrator for more information”

Are you trying to install Sage Estimating, get through the install without error, but when you go to open the program get: “You are not currently set up as a user of the selected Estimating server.  See your Estimating administrator for more information.” ? This might be because Sage will not recognize Microsoft/email accounts as users.  Help & instruction on how to fix the error are below.

Problem: While upgrading or installing a new version of Sage Estimating user encounters the error message: “You are not currently set up as a user of the selected Estimating server.  See your Estimating administrator for more information.” The error message prevents you from opening Estimating and will prompt in Estimating Configuration Wizard.

Applicable Hardware/Software observed: Windows 10 & Windows 11, Sage Estimating 21.1

Fix: Create a local account on your computer and re-install a new SQL instance.

Where this works: The user is trying to upgrade Sage Estimating & install a new SQL instance

Error Message:

Instructions:

1. Go to the start menu and type “Manage your Account”
2. View the info page and if your account is an email address (Microsoft Account, outlook, etc), then select “Sign in with a local account instead”

3. Create the local account/password, and complete the mandatory restart

The Estimating program should carry over to the local user, but you will need to install a new SQL instance

4. Execute Sage’s setmeu.exe file again

5. Uncheck the box “Install Sage Estimating”, Check the box “Create a new local SQL Server Instance”

6. Name the instance something different than your first attempt

7. Complete install and try to open Estimating again, making sure to specify the SQL instance you created in the new attempt.

Other possible fixes: If you are upgrading Sage Estimating and trying to access an existing SQL instance and you are on a local account or domain, it could be a security issue.  See this article from Sage’s support:

https://support.na.sage.com/selfservice/viewContent.do?externalId=29690&sliceId=1

Remember, every machine and setup is unique and there are multiple variables that could be the issue.  Still need help?  Contact us for prompt responses.  Same-day emergency service is available in some cases. 360-891-5811