Latest Entries »

I will be striving for more posts about the 2016 version, released last week, but for now here is a video to give you a taster.

It’s not as big or as exciting as 2015, but there are some pleasing additions.

Advertisements

Sage 200 Consultants wanted

At Smith Cooper System Partners we are expanding our brilliant and dedicated team.

Reporting to our implementation manager, we require an experienced Sage 200 consultant to join our busy delivery team. This is NOT a trainee position so the successful candidate should have a proven track record of Sage 200 implementations along with a working knowledge of the add-on market (Draycir, Eureka, Sicon etc.). Customer service is very important to our company, so a customer first attitude and a strong desire to produce quality projects is also essential. Would suit an experienced Sage 200 consultant looking for a new challenge, who wants to work in a positive, forward thinking environment and can “hit the ground running”.

We also have roles for a Support consultant and Account Manager

Smith Cooper Are Hiring For Sage Software Professionals

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’.

 

2015 in review

The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 27,000 times in 2015. If it were a concert at Sydney Opera House, it would take about 10 sold-out performances for that many people to see it.

Click here to see the complete report.

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.

 

I’m delighted, excited and proud to have been part of the great achievements at Smith Cooper System Partners.

Read more here:

http://goo.gl/lwqs4U

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.