Category: System Administration

I have hit this issue on my last couple of installations where the Core components fail to install when accessing Sage 200 2015 System Administrator. Sage have identified this as being an issue which relates to virtual environments (which both of my examples were).

When you access System Administration for the first time after install, various messages appear throughout the initialisation, including those referring to the core components and the building of models. You may notice the system freeze during this.

The issue relates to the available resource on the machine. Clearly the virtual environment must meet the minimum System Requirements for Sage 200 2015. For standard single-server environments, this requires at least a dual-core processor and 4GB of RAM.

Interestingly for my examples the servers should have been fine, however the memory was set to be Dynamically allocated and for some reason was remaining below 4GB. Once this was changed to a Static amount, well above the minimum, the core components installed correctly.

Licencing for Sage 200 has changed for 2013.

There are now two licencing options for Sage 200. A subscription option allows you to pay monthly for your use. This is available to both Online and On Premise deployment options. For On-premise there is also the perpetual licensing that there has been for previous versions.

As well as the way you can can pay, there are also more types of user available. There is the option of a Full Sage 200 user or Web user licences (NB. Full users also get access to the Web/Self Service user). For CRM users there is also the CRM User and Suite user options still available.

The way we enter Licences has also changed. Gone are the days of typing out 24 blocks of 5 letters. Licences will now be activated using your account and serial number. These numbers are entered within the System Administration, which launches an automated system (online) that links to Sage’s internal systems. The details are authenticated in order to allow you to licence the system by selecting a licencing button.

Licences are stored in an  XML certificate.

If for some reason you do not have an Internet connection, there is a manual option available.

If you Right Click on ‘Licence’, in System Administration and select ‘Generate Licence Request’. A licencerequest.xml file is generated. This can be manually emailed to Sage, who will send the XML file back, to be imported into System Administration.

I have written various blogs about Sage 200 Report Designer functions but realise I have never advised how to add a report to a users menu. Until NOW!!!

The following document explains the steps required.

  • Including User and Role permissions
  • Adding features
  • Menu Design Mode

Talking Sage 200 – How to Add Reports to the Sage 200 Menu



When logging in to Sage 200 you could receive the following error:

Login failed for user ‘MMSUser’

This would occur if an invalid SQL Server name has been used, the SQL Server can not be accessed from the Sage Server or the Sage 200 user accounts have not been created in the SQL Server instance that Sage 200 is using.

The most likely cause is after an installation. Within the SQL Server instance the user account ‘MMSUser’ must exist. It must also be set up as an SQL Login and not just a database user.

Within System Administration, Select Companies on the left hand side.

Right Click a Company, and select Properties.

Click ‘TEST’. This will create the Sage database users and grant access to the Company database.

When this is done on the first company, a login screen will appear and you need to login to the SQL instance. NB. This is a SQL login, and needs to be a member to the database administration group.

When creating a new Configuration database within System Administration, the following error could appear:

If you view the details it will show this error: 

System Administration is reading the web.config file, that is normally located here:

C:\Inetpub\Sage 200 App Services\Sage200Administration\web.config

If you open the web.config in Notepad, look at the lines: 

<add key=”ConfigurationSQLServerName” value=”[Server Instance Name]” />

<add key=”Sage200ConfigurationSecured” value=”true” />

Make sure that the “ConfigurationSQLServerName” key is looking at the correct SQL Server Name / Instance.

If the “Sage200ConfigurationSecured” key is set as True, it thinks that the System Administration login details for SQL have already been set and secured. This wouldn’t happen until the Configuration database has been created.  Therefore, you need to change the value to False then Save and Close web.config.

Web.config file

Similar to the above, if you are trying to create a configuration database in Sage 200 v2010 System Administration you may get this message:

“Log in failed, cannot open database, mms admin failed.”

The web.config file for 2010 is normally found here:


Open in notepad and find <add key=”Sage200ConfigurationSecured” value=”true”/>

Change the value to be “false”:

<add key=”Sage200ConfigurationSecured” value=”false”/>

I came across this problem having upgraded a site from 2009 to 2010. It is however a common problem that can occur with 2003 Servers.

Having installed 2010 I went to login into System administration, to update the databases etc.

However as soon as I clicked the icon I got the following error:

Error when trying to access Syatem Administration

Having clicked ok (Twice!!), the console form opens but without any System Administration options.


Click ok (Twice)

Select File>Options>Disk Clean Up

Select Delete Files

If you attempt to log in to System Administration at this point the MMC console form displays with the following message:

System Administration MMC error

N.B. This is an error that can occur as a separate issue.

Run the following command prompt:

Cd c:\windows\\framework\v2.0.50727


Installutil “c:\Program Files\Sage\Sage200\Sage.MMSAdmin.MMCSnapIn.dll”

You should now be able to access System Administration.