Tag Archive: 2013

Sage have advised Business Partners that Microsoft have announced that as of 9th December 2015, they’ll be removing some of their earlier versions of their REST API, some of which Sage are using to access storage accounts (i.e. blob storage).

Sage have updated Sage 200 2015 to use the latest version and have also included the change within Sage 200 2013 R2 Service Pack 2.

They will not be applying this fix to any other versions of Sage 200 Extra Online, so customers operating any of the versions of Sage 200 Extra Online shown below must be upgraded to Sage 200 2013 R2 SP2 or Sage 200 2015.

  • Sage 200 2013
  • Sage 200 2013 SP1
  • Sage 200 2013 R2

The change is currently planned by Microsoft on 9th December and Sage 200 Online sites must be upgraded no later than 4th December.

There is a Known issue (5924) which is fixed in Service Pack 1 for Sage 200 2013 R2 where the details of held journals, which were created from Journal Templates, are lost if more than one journal has been held.

NB. there was a hotfix for this originally but this is now rolled up into SP1.

Following on from my Early Settlement Discount post, Sage have now released the Service Packs for Sage 200 2011 and 2013 (NOT 2013 R2).

As suggested previously these only serve to be a temporary solution to the legislation change for Early Settlement Discounts and will still require you to process manual transactions in order to correct your VAT postings.

Here are the Sage documents released with the Service packs for more information about the required work around:

Sage 200 2011 Issues Fixed – Service Pack 7

Sage 200 2013 Issues Fixed (On Premise) – Service Pack 2

You will note the service packs can be installed straight away and there is a new parameter to enable the changes.


I think you will agree the work around isn’t the simplest and, particularly if you process a lot of Early Settlement Discounts, you really need to arrange an upgrade to the New 2015 version once it is released, as this will have full functional ability to deal with the legislation change.

The Service Pack for 2013 R2 is due to be released on Friday 06th March 2015. Functionally this will be the same as the changes to 2011 and 2013.

Remember, if you are on any version below 2011, you have no option but to upgrade as NO service packs are to be released.

On 01 April 2015, the legislation when raising or receiving a VAT invoice including early settlement discount will change. The change affects you as a supplier who offers early settlement, and/or as a customer who receives early settlement discount, where an invoice is issued.

For the current legislation, up to 31 March 2015, suppliers who offer early settlement discounts are permitted to account for and include the VAT due on the discounted price on their invoice, even if the full price (i.e. the undiscounted amount) is what is eventually paid. Customers who are offered an early settlement discount are only able to recover the VAT stated on the invoice even if they do not pay within the settlement days permitted.

From the 01 April 2015, suppliers must account for VAT on the amount they actually receive and customers may recover the amount of VAT that is actually paid to the supplier. Because of these changes Sage are releasing updates for Sage 200 however you must be aware how this impacts your version of Sage 200.

Sage 200 2015 will be fully compliant with the new legislation when it is released (end of February). It will also make it easier to process in accordance with the new guidelines. It includes two elements – compliance and usability. Sage therefore recommend that all Sage 200 sites which are affected by this legislation change upgrade their software to Sage 200 2015 as soon as possible.

Some older versions of Sage 200 will have a Service Pack released to assist with the changes however this relates strictly to the point of compliance only. Sites which have installed the relevant update will be able to continue printing compliant invoices.

Sage and indeed my recommendation for Sage 200 2011, 2013 and 2013 R2 sites is to upgrade to Sage 200 2015 as these versions will be less efficient and more prone to human error. That is unless the site has a very limited number of accounts where Early Settlement Discount is effective.

There will be no updates made available for Sage 200 2009 or Sage 200 2010. All sites on one of these versions, that are affected by Early Settlement Discount, should upgrade their software to reduce the amount of manual changes.

When the first Sales order line of a Sales Order has a zero value and no Nominal analysis but further order lines do have Nominal analysis, the  nominal drill down within the SL Transaction enquiry shows the Narrative ‘Intended For -//’

  1. Create a Sales Order with a Free text line with a zero value and no nominal analysis.
  2. Add a second and third order line with Nominal analysis
  3. Save the order and process through to completion (post the invoice).
  4. Within the Sales Ledger open the transaction enquiry for the selected customer and highlight the Invoice
  5. Select the Nominal Drill Down and see the narrative. All lines show ‘Intended for -//’

My occurrence was due to the user using the Free Text line for a comment/note. This is what the Comment line is intended for. The alternative is to enter the Free Text Line at the end.

When logging in to Sage 200 the following error will occur due to certain Authentication settings being configured incorrectly. The error will only be on the clients machines. Logging in to Sage 200 on the server will not cause this error.

Communication Error

IIS Windows authentication settings

  1. Within IIS, expand Sites > select Sage 200 App Services > double-click the Authentication icon in the Features area.
  2. Select Windows Authentication. Ensure this is set to Enabled. If not, select Enable in the Actions panel on the right.
  3. Also in the Actions panel, select Advanced Settings…
  4. Ensure the checkbox for ‘Enable Kernel-mode authentication’ is ticked > OK.
  5. Reset IIS

IIS Anonymous Authentication settings

  1. Within IIS, expand Sites > select Sage 200 App Services > double-click the Authentication icon in the Features area.
  2. Select Anonymous Authentication.. Ensure this is set to Enabled. If not, select Enable in the Actions panel on the right.
  3. Also in the Actions panel, select Edit…
  4. Ensure ‘Specific user’ is selected > Set…
  5. Enter the fully qualified Sage 200 Services username and password. This is the username and password you specified during the installation of Sage 200. For example, <domain>\Sage200Services.
  6. Press OK and reset IIS.

LAN Manager Authentication level

  1. Select Start > Control Panel > Administrative Tools > Local Security Policy.
  2. Double-click the Local Policies folder and select Security Options.
  3. From the list of policies, double-click ‘Network security: LAN Manager authentication level’.
  4. From the drop-down list, select ‘Send LM & NTLM – use NTLMv2 session security if negotiated’ and select OK.

If the error persists…

  • If you are using a Workgroup, password protected sharing will cause the above message to appear. This should be turned off within the Control Panel > Network and Sharing Centre > Change Advanced Sharing Settings.
  • Ensure the server that hosts the Sage 200 Web Services has been added as trusted site within Internet Explorer Options. You can access this within Internet Explorer > Tools > Internet Options > Security tab > Trusted Sites > Sites.

Where an IIS reset is required above, all users must be logged out of Sage 200 and indeed any other system which use’s IIS.

In a recent installation of Sage 200 2013 (RELEASE VERSION) I found that the server already had a shared directory called ‘Sage’. This was being used for Line 100 data purposes.

In an attempt to avoid issues with Line 100 (which is their current Live system) and current ODBC reports, I decided the best approach was to install Sage 200 2013 to a Share named something else. I went for ‘Sage200‘.

For various reasons this is something I have needed to do with previous version of Sage 200/MMS; and without issue apart from the occasional requirement to amend the SVNMOSW file on the server for 2011.

For 2013 however, I found that this wasn’t the most simple of decisions.

It appears there are numerous config files that are coded to look for the Share name ‘Sage’. It isn’t as simple as telling the installation wizard that the logon directory would be in *Sage200\Logon and it then know to install relevant files as such.

Firstly, although I had gone down this route, after installing Sage 200 onto the server Line 100 still stopped working. Users were no longer able to access the ‘Sage’ share..!!! Having checked the share on the Sage folder, it seems Sage 200 recognises a share named ‘Sage’ exists on the server so attempts to hook on to this (noticeable by the Share comment being ‘Sage 200 File Server’). On looking at the permissions they had all been disabled by the Sage 200 install.

Next step was to create the Configuration database in System Administration. Here I got an error, the XML details telling me ‘Cannot find file: //SERVER/Sage/Logon/Credentials.xml

Correct! This file did not exist, but it wouldn’t have been created yet as this is done during the configuration database creation. However the message did allow me to identify it was looking for the wrong Share.

My instant thought was SVNMOSW, but this does not exist in 2013, however there are the following files that needed to be manually amended:

C:\Program Files (x86)\Sage\Sage200\Sage200CommonAppSettings.config






IMPORTANT NOTE – Service Packs overwrite these files, so amendments are required again after installing updates.

Finally having gotten things to work on the server I went to a client machine to install, using the Installers directory (in my ‘Sage200’ share!). Upon running the setup and selecting to install the Sage 200 Client I received the error ‘This folder does not contain S200ASServerRootCA.Cer certificate’

Within the Installers directory is an InstallSetting.xml file. This includes a Certificate path, which needed amending to \\SERVER\Sage200\Logon\SSLCertificate

There are also some other lines in this file which should be amended to include the correct share name.


I was finally able to install, and successfully logon to Sage 200.

So my opinion is……..unless absolutely necessary stick to a Shared directory called ‘Sage




‘Login failed for user ‘.’ Please run System Administration to check company settings.’ error

2013 - Login failed for user

Check the following points:

  • Ensure the Windows user has been linked to the relevant Sage user in System Administration.
  • The Windows user, e.g. ‘JohnBull’, has been included as a user in the ‘Sage Users’ group which is set up as part of the installation process.
  • Check that the ‘Sage Users’ and ‘Sage Administrators’ groups have sufficient permission to access the Sage shared folder (by default, C:\Sage).
  • The ‘Sage Services’ user set up as part of the installation process must have sufficient security permissions on the Sage shared folder.
  •  IIS v8 only – Ensure ‘HTTP Activation’ has been enabled within .NET 4.5 as per the below:

2013 - Login failed for user_IISv8HTTPactivation

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.

One of the key elements of Sage 200 2013 is the choice of deployment that it offers. Companies can now choose between an On-Premise and an Online (Cloud) deployment.

Cloud ERP solutions are becoming a serious option for companies. This is increasingly due to the savings they can make on infrastructure requirements such as the latest Hardware, Security and Backup systems. In the past, companies have been wary about how secure Cloud solutions are, as their key business data is involved. But Cloud solutions (generally) have much more sophisticated security and data recovery systems than what business can implement internally.

Sage 200 2013 Online has no upfront expenses for hardware just a single monthly subscription fee. You pay for what you use and there is more flexibility than before to add and remove users or modules.

With Line 100 becoming end of life in April 2014; Sage 200 online offers more companies an affordable upgrade option without the loss of key functionality, as now there is an upgrade option for Sage 200 without the added costs of new servers and other required components such as Microsoft SQL server.

For certain businesses it can still make sense to invest upfront, They may wish to keep data in-house and have the resources required to invest in technology/infrastructure as well as continue ongoing maintenance.

On-Premise has all the same functionality as Online, but the addition of modules which are not currently available to the online option. Therefore the requirements ofa company may dictate which option they can go for. For example if a Manufacturing solution is required, the On-Premise deployment would need to be implemented.














Project Accounting











This document from Sage gives further details about the differences between Sage 200 2013 On-premise and Online.