Category: Sage 200


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.

 

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.

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.

On 1 July 2015 Sage 200 products were given new names as below:

  • Sage 200 (on premise version) is now called Sage 200 Extra
  • Sage 200 Online is now called Sage 200 Extra Online

Why Have they done this?

In line with a new addition to Sage’s product portfolio, they are changing the existing product names to ensure products are aligned and customers can better identify the product to suite their business needs.

On  1 July, Sage ‘soft launched’ a new product called Sage 200 Standard Online. This is an online accounting solution that provides “direct support from Sage, simple scalability and a compelling online experience”.

This product is an online subscription solution, designed to bridge the gap between Sage 50 and 200 Extra Online.

Sage 200 Standard Online Benefits include:

 

  • No need for expensive hardware
  • Risk-free implementation service that allows customers to migrate their data without risk
  • Support direct from Sage that helps customers manage complexity with ease
  • Greater control of a customer’s business as it becomes more complex with intuitive financial management and commercial business tools
  • Improved insight with powerful Excel reporting tools that help customers operate more efficiently and improve performance

 

Sage 200 Standard Online availability

 

Sage 200 Standard Online soft launch will be between 1 July – 5 October 2015. Full launch of the product will be from October onwards. It will also launch in Ireland in October.

 

How can I participate?

 

Initially Sage will sell Sage 200 Standard Online directly to customers. From October, there will be opportunity for Business Partners to get involved in the distribution

 

“Sage 200 Standard Online is an addition to our rich product portfolio and does not replace any existing product.”

 

 

 

Here is a great document from Sicon which details the comparisons between their Fixed Asset module and the Sage 200 2015 fixed assets module.

Sicon Fixed Assets v Sage 200 Fixed Assets

 

I haven’t posted much in recent months, and certainly not as much as I would have liked since the 2015 release.

The truth is I have been too busy. I totally intend to gets some posts out in the coming months.

Remember to follow @talkingsage200 on twitter as I often retweet and post on here too. Also follow please @smithcoopersp to find out what work and plans we are doing in Sage/Sage 200 world.

Craig

 

Originally posted on Talking Sage 200:

Its been billed as the most important update in years and I have to say, I do not think users will be disappointed. Here are some details of the new features within Sage 200 2015 which was officially released at the end of February.

Look and Feel
Whilst the basis is familiar to current Sage 200 users, the screens and menus have changed in appearance giving a more modern design. Many of the changes are designed to make it easier for users to navigate Sage 200 and find/access what they want.

Look 1 Homepage

List View List View

Look 3 Redesigned Process Maps

The 2015 design is much more intuitive.  A really nice feature is the frequently accessed page where the system remembers the functions you have used the most, so there is a quick way of getting back to them. What’s even more impressive is it remembers by day. So if you access something on a Friday, the next Friday it will be…

View original 553 more words

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.

In the core Project Accounting module it is possible to create project Statuses and specify whether costs can be entered for a status.

When entering Timesheets in the standard system you are not able to select a project with a status that does not allow costs (as you would expect). However if entering timesheets via WTE, you are able to select a project even if it has a status that does not allow costs.

This was reported in 2011 SP5 originally, and is still not fixed within 2015.