Tag Archive: Installation


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.

Advertisements

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

Sage200CommonAppSettings

C:\Inetpub\Sage200AppServices\Sage200SecuredServices\Web.config

Sage200SecuredServicesWebConfig

C:\Inetpub\Sage200AppServices\Sage200Services\Web.config

Sage200ServiceWebConfig

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.

InstallSettings

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

When it comes to installing Sage 200 service packs there are a few ways that it can be done, browse to the share from each client machine, copy and run on each machine, or set it up to deploy and run at the next login.

Deploying the service pack is quick, easy, it insures all services packs are installed on all client machines and makes it easier to install remotely.

  1. Copy the service pack to the Updates directory within the Sage share
  2. Go to Program Files/Sage/Sage 200
  3. Double click SageMMSUpdateAdmin.exe
  4. Enter the full Service Pack file name (including extension) into the File Name field i.e. Sage200v2011SP2.msp not Sage200v2011SP2
  5. Type a Version number 1.00.00.00 etc.
  6. Click Save.
  7. This will Generate a file called DEPLOYMENT.DAT within C:\Program Files\Sage\Sage 200
  8. Put DEPLOYMENT.DAT into the Updates directory within the Sage share.
  9. Now Login to Sage 200 on each machine
  10. Download the update(s), as prompted
  11. Install the update(s), as prompted

NB. If other files have been deployed previously (i.e. there is something already in updates), and these need to continue deploying where required, there will already be a DEPLOYMENT.DAT file in the Updates directory. This should be copied to Program Files > Sage > Sage 200 before step 3 above. This way you will be amending the deployment already set up.

NB. If the SP has already been installed on to a machine before setting up the Deployment, it will still try to download and Install when you login to Sage 200 for the first time after setting up the deployment. In this instance allow the file to download. Then go to Program Files > Sage > Sage 200 > Updates. In here there should be a file called Deployment.xml.

  • Right click and “Open With” ‘Notepad’
  • There will be a line for each Deployment starting: <File Name =”Sage2002011SP2.msp”…..
  • On the line for your File Change the Status to = “2”  (It should be showing as “1”)  (Status 1 = Downloaded, Status 2 = Installed)
  • Close & Save.

This happens for me on the server(s) as I tend to manually install service packs here. I install the server(s) like this because once a service pack is installed to the server(s), you have to login to System Administration and update companies.