Error: Your environment isn’t eligible for an SQL server upgrade when using Domain controller

The MYOB SQL Upgrade Utility will check if your system meets the MYOB’s requirements such as required space and Microsoft's published recommendations and requirements.

Microsoft does not recommend installing SQL on a Domain Controller (although does not explicitly prevent it during an SQL install) and our utility will flag the risks and our recommendations if you’re installing on a Domain controller.

Our recommendation is not to install a Domain Controller, but we understand that some practices may choose to do so.

Installing on a Domain Controller

You can still use our utility to complete the upgrade, but you need to complete some steps manually when running the SQL utility to complete MYOB-related tasks that the SQL upgrade utility performs.

Before you run the utility, read the Microsoft recommendations and follow any advise/warnings provided. Make sure you understand how a Domain Controller works and any risks involved when installing on it.

Once you've reviewed the Microsoft recommendation, and are aware of the risks and warnings follow the steps below to run the SQL utility.

1. Run the MYOB Upgrade SQL V2 utility and let it perform the Eligibility check. If you are using the MYOB Upgrade SQL V1. Please adjust the below steps to suit the different V number (e.g. SQLServerUpgrade-V1exe.Config and SQLServerUpgrade-V1.log)

2. If the eligibility check fails, exit the utility.

3. Go to the folder where the SQL Utility is and open SQLServerUpgrade-V2exe.Config file in notepad (or similar).

4. Find the line <add key="StartStage" value="1" /> and change the value from 1 to 2 (do not alter anything else).

5. Save and close the file.

6. Restart the utility and proceed as per the instructions.

Things to remember

• Fix any other errors that show in the SQLServerUpgrade-V2.log file before proceeding (such as disk space, CPU specifications and so on).

• Do not proceed with the above steps, if there are any other failures beyond being on a Domain Controller noted in that log.

• As some MYOB services are using the LocalSystem account to communicate with the SQL server, you will need to set these to Log on as and set up a named user that exists in the domain, and also in the SQL server.  Make sure the user exists and can access the SQL server as the MYOB SQL utility will not do that for you.