Tag Archive: Service Pack


Sage 200 2016 SP2

Sage 200 2016 SP2 has been out for a while now.

One key issue that impacted users in Sage 200 2016 were the restrictions on Accounts which were placed ‘On Hold’.

There is an issue with entering Memo’s and also it is not possible to allocate transactions.

SP2 fixed the Memo issue. It didn’t fix the allocations but after I did some communicating with Sage support they did a great job and there is actually a Hotfix now available.

It still isn’t possible to import transactions which is something else we have come up against, however my opinion on this is that for Invoices in particular it is probably working by design. I would be interested to know other people’s thoughts on this.

Service pack 3 has now been released for Sage 200 Extra 2015. There are a number fixes included as detailed in Sage 200 Extra 2015 SP3 Issues Fixed .

Sage 200 Manufacturing

Stock Projection Details

Some changes have been made to improve compatibility with Windows 8, Windows 8.1 and Windows Server 2012, these changes also make a consistent look and feel with other areas of Sage 200 Extra.

As a result of these changes, the following graphs are no longer available:

• Graph tab on Stock Projection Item Details

• Graph tab on Monitor Operation Times

• Histogram tab on Monitor Operation Times

The changes also prevents some workspace options (for example, opening, saving, Copy to Clipboard, print and the tools to change the display of the charts).

MRP – Unable to amend the first recommendation on the system

When the user runs MRP within Manufacturing for the first time, the MRP numbering sequence runs from MRP000000, rather than MRP000001.

As a consequence of this, the first recommendation will not be selectable on the MRP Recommendations form.

To renumber the recommendations you must run the MRP twice on a new dataset, before actioning or maintaining any recommendations.

Subsequently, MRP need only be run once.

Sage 200 Suite Tools

Sage 200 2015 SP3 uses a new version of ManufacturingCSVFileConversion.exe

If you attempt to use the previous tool, the following message appears:

Error launching application. Could not load file or assembly ‘Sage. Manufacturing, Version – 17.0.0.1’.

 

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.

 

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.

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.

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.

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.

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

 

 

 

Service pack 5 for Sage 200​ 2011 has today been released.

This is the last “planned” service pack release for Sage 200 2011, although hotfixes will continue to be released as required. The next main release for Sage 200 will be Sage 200 2013, which will be for both Cloud and On Premise versions.

Service Pack 5 rolls up all fixes included in previous service packs.

With the release of Service Pack 5, Sage 200 2011 will now become compatible with Windows 8 operating system (32 & 64 bit Pro and Enterprise editions).

The list of issues fixed in Service Pack 5 is below:

Service Pack 5 Issues Fixed for Sage 200 2011