Tag Archive: Deployment


It’s been a while! Lots to start posting about. We have had Sage 200c and there are lots of updates for add ons with changes to Credit Hound, the new Spindle Self Service Portal, Sicon Barcoding and Warehousing to name a few.

It’s busy, busy, busy at Smith Cooper System Partners but I am going to do my best to start posting again.

How are people getting on with Sage 200c?

My personal experience to date has been great and I love the installation as it is much quicker. The Send To Excel feature is a great addition too, saving the reformatting requirements of Export as CSV or Excel.

Advertisements

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.

Yesterday finally saw the release of the much-anticipated Service Pack 2 for Sage 200 Extra 2015.

One of the key items as part of this is the support of Windows 10 operating system.

There are lots of fixes and some additions as detailed in this document released with the update –

Reports

There are some New Reports to be aware of which are not installed automatically as well as Layout updates too. Check these out with your BP. The introduction of the SOP Profitability reports which include Returns and Credit Notes will be music to some people’s ears, although if you needed this previously you have probably had the report written already.

There also some nice Stock reports, offering different views of Sales by Customer, Product Group and Monthly Sales etc.

Summary Screens

My particular favourite addition in this service pack is the added drill down functionality to the Summary screens. Previously a great visual aid (and Sage Sales Persons dream!) they were not altogether complete from a ‘day to day’ point of view. However we are now able to drill all the way down to the transactional items which makes them much more beneficial as an analysis tool.

Sales Summary Outstanding Debt (Totals)

Sales Summary Outstanding Debt (Totals)

 

Sales Summary Outstanding Debt (Drill down to Customers)

Sales Summary Outstanding Debt (Drill down to Customers)

 

Sales Summary Outstanding Debt (Drill down to Transactions)

Sales Summary Outstanding Debt (Drill down to Transactions)

Installation

Service Pack 2 can be applied to sites running either the Base version of Sage 200 Extra 2015 (all SP1 updates are included) or sites with Sage 200 Extra 2015 Service Pack 1.

As with Service Pack 1 there are two installation files:

  • Sage200v2015SP2ClientPrerequisites.exe
  • Sage200v2015SP2.msp

On client machines, both files must be run in the order listed above.

Sage200v2015SP2ClientPrerequisites.exe checks the client files to ensure the correct registry keys are present on the machine.

Sage 200v2015SP2.msp updates Sage 200 Extra.

NB. On a server, you only need to install the Sage 200v2015SP2.msp file.

As ever this Sage 200 Extra 2015 SP2 Installation and Release Notes document gives all the information needed to install the service pack.

 

Short, important post!

Microsoft have now released Windows 10. Please be aware that this is NOT supported for any current versions of the Sage 200 suite.

All being well Service Pack 2 for Sage 200 Extra 2015 will include Windows 10 compatibility. This is currently scheduled for 30th September 2015.

 

After upgrading a Sage 200 site to Sage 200 2015, an error message may be displayed when accessing System Administration for the first time. The message advises of an error in XML document (9, 3).

 

This is caused by not removing any Add-Ons before commencing the upgrade to Sage 200 2015.

Previously, the Add-Ons could be uninstalled in System Administration but when you try to remove the Add-Ons , the below error is displayed.

Exception has been thrown by target of an invocation

This is because in Sage 200 2015, the schema version number has changed so the Add-On trying to be removed does not have the expected schema number assigned to it and so can’t be removed.

In order to complete the upgrade:

Note: You must take a backup of the Sage 200 Configuration Database before proceeding.

  1. Close any errors and select the Add-Ons option in the left pane.
  2. Make a note of the name of each Add-On installed on the site.
  1. Backup the Sage 200 Configuration Database before proceeding.
  1. Open the configuration database in Microsoft SQL Management Studio and open the tblAddon table.
  2. Look for the Add-Ons that were noted in Step 2 in this table. For each add-on, make a note of the AddOnID in the first column.
  3. Remove the entries from the table for each of these add-ons. This should leave only the standard Sage 200 entries in the table, for example, Sage 200 Accounts, Sage 200 Bill of Materials, Sage 200 Accounts Compiled Model.
  4. Close Microsoft SQL Management Studio and re-open Sage 200 System Administrator.
  5. The core components should now install successfully. You will then need to reinstall any applicable Add-Ons, ensuring first that they have been re-compiled for use with Sage 200 2015.

Sage 200 2015 Service Pack 1 is now available.

Business Partners should note the different method of installation on Clients.

This service pack contains two files:

  • Sage200v2015SP1ClientPrerequisites.exe
  • Sage200v2015SP1.msp

On a client PC both files must be run, in that order, to ensure the service pack installs correctly.

Sage200v2015SP1ClientPrerequisites.exe checks the client files and ensures that the correct registry keys are present on the client machines. Sage 200v2015SP1.msp updates Sage 200 Extra. Failure to run the files in this order will cause errors when you try to run Sage 200 Extra 2015.

On a server, you only need to install the Sage 200v2015SP1.msp file.

Sage 200 Extra 2015 SP1 Installation and Release Notes

The following Known Issues have been resolved in Service Pack 1.

Module Issue Tracking System Reference
(where applicable)
Description
Nominal Ledger 5970 Users were unable to import a CSV file with negative budget values.
6318 When importing nominal ledger budgets, a ‘success’ message was displayed but the details were not imported.
6429 The Default Cost Centre drop-down list was not displayed on the Consolidation tab of the Nominal Ledger settings.
Desktop 6389 An ‘Unhandled Exception’ error message appears when trying to add a new feature in Menu Design mode.
6390 Updated the Workspace quick filters to display part searches. Previously, the filter would only search on the entire word (for example, typing AB would only find a customer with the name AB, it wouldn’t find Abbey etc).
6400 User preferences not retained when a user logs out of Sage 200.
6424 Adding reports to the Home Page Favourites now makes the report appear in the Summary screen.
6425 Creating a new folder in Home Page Favourites and adding the report generates an error.
6443 Error in Workspaces where the ‘OR’ filter did not work correctly. In previous versions the OR filter was working like an AND. As a result, no details were being returned by the filter.
6444 Unable to run reports or layouts from favourites.
6487 Non Taxable Receipt launches Taxable Receipt Form.
Purchase Orders 5753 Could copy an order without saving any supplier details.
6480 Multiple Delivery Dates button missing if Project Account Integration not enabled.
Sales Ledger 6451 Save and Allocate button on the Sales Ledger reverse transaction form is now read-only when reversing receipt or payment. This was active in the release version of 2015.
Stock 6455 MRP Replenishment Options missing from the Manufacturing tab on the Stock Item screen when using low screen resolution on some low-spec laptops and PCs.
Timesheets 6469 Enter Timesheet Week – Incorrect Cost rate saved.
Analysis Codes 6470 Issue when editing a newly created analysis code in Sales Order Processing or Purchase Order Processing.
Sage 200 CRM 6432 Ergonomic UI not working as expected after upgrade from 7.1.
Developers 6401 Addon fails to install when contains 2 content parts.

Sage 200 Extra 2015 SP1 Feature Updates and Issues Fixed gives some further details of items included in this update.

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.

THIS NEW PARAMETER CANNOT BE DISABLED ONCE SELECTED, SO DO NOT ENABLE UNTIL REQUIRED.

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.

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