Sage 50 error: "Advisor Rule engine cannot start
Sage 50 cannot tell which version your company database is, so the Advisor rule engine refuses to start; usually a version mismatch or damage.
“Advisor Rule engine cannot start because the database version is not recognized.”
When Sage 50 shows this message, it means the Advisor component, the part of the program that runs automated rules against your data, cannot launch because Sage 50 cannot work out which version of the database it has been given. The complaint is about version recognition, not about your bookkeeping. In plain terms, the program and the company file disagree about what the file is, and until that disagreement is settled, the rules engine stays offline.
Why it happens
The usual causes, roughly in the order we see them:
- The company file was created or last updated in a different release of Sage 50 than the release installed now.
- A program update installed partially, or the file was moved to a machine running a different release.
- The file was restored from a backup written by a different edition.
- The internal version information in the database is damaged or unreadable, so nothing can recognize it.
Update the program first
The safest first step is to make sure the copy of Sage 50 on this machine is fully up to date. Install any pending updates, restart the computer, and open the company file again. If the file was written by a slightly newer release, bringing your installation current clears the message without touching your data.
Open the file in the release that last used it
If the message appeared after moving the file, restoring a backup, or reinstalling, open the file in the same release that used it most recently, if that release is still available to you. Take a fresh backup from there before doing anything else. Avoid a setup where two different releases take turns opening the same file; that is a common way this message starts.
Restore a backup taken before the message appeared
If you have a backup from before the message began, restore it and work on the restored copy, keeping the original untouched. Repeated attempts to force a file open when its version information cannot be read add risk without adding information.
When the file itself is the problem
If updates change nothing and the message appears on every machine and every release you try, the version information inside the database is probably damaged. A reinstall will not fix that, because the damage is in the data file, not the program. This is the point where the file needs professional attention: our engineers repair damaged Sage 50 and Simply Accounting databases directly, and we can tell you what state the file is in before anyone commits to anything. Details are on our Sage 50 database repair page.
If it appeared during a downgrade or a conversion
The same message shows up when a file is moved between editions, for example from Quantum down to Pro or Premium, or when the data is on its way to another product. An edition change has to translate the database deliberately; opening the file in the lower edition and hoping for the best does not work. See our Sage 50 Quantum downgrade service. If the real goal is moving the books to QuickBooks, that is a conversion rather than a repair, and the version question gets settled as part of doing it properly: Sage 50 to QuickBooks conversion.
Next step
Send us the file for a free evaluation. We will establish which release the database actually is, whether the version information can be repaired, and the safest route back to a working file, and you get a firm quote before any work starts.