Tag Archive: timeout errors


Service Pack 3 has now been released for Sage 200 2011. The main focus is on CRM fixes but there are also a few Manufacturing and Core module fixes/updates.

This service pack rolls up service packs 1 and 2 as well as any hot fixes that proceeded them. SP3 also includes documentation updates for Deployment and Integration Guide, System Requirements, CRM Implementation Guide and Upgrading Sage 200 CRM.

A full list of included fixes is available in the attached document: –

Issues fixed in Service Pack 3 for Sage 200 2011

Fixes/Updates of note include the following:

Core Modules

  • There is a now a setting to stop the ability to enter NL Payments/Receipts with different dates for each side of the posting i.e. current functionality allows the bank side to have one date and the transaction side to have another date.
  • Validation option for second reference on Invoices and Credit Notes.
  • The ‘Posting order line’ message does not clear when the POP order entry form is closed without saving. This has now been fixed.
  • The nominal accounts assigned to project items are not retained when a project is amended. This has now been fixed.

Manufacturing

  • New workspaces have been created for the Manufacturing modules.
  • Graphical Planner 11.2 is included.

BOM

  • Where BOM allocations include multiple BOMs, the ‘Undo Allocation’ option incorrectly removes the whole allocation. This has now been fixed

CRM

  • Cannot print a prospect quote entered via form launching for a prospect company in CRM.
  • The ‘Company Type’ must be re-selected when changes are made to the company summary screen if the ‘Company Type’ has been made a mandatory field.
  •  A ‘Progress’ tab has been added to the integration: ‘Administration > Integration > Integration Name | Progress’. The progress tab displays the number of records remaining to be synchronised.
Advertisements

I have received a number of queries recently relating to Time Out errors being experienced during the running of a year end. There have been a couple of known issues with regards to these errors which were actually fixed in Sage 200 2011 SP1.

Below are details with regards to the issues now fixed in Sage 200 2011 SP1:

Known issue 3226 related to SQL timeout errors when running year end. The routine reached about 4% of Stage 2.

Known issue 4179 related to running year end on large data sets. Data sets with a high volume of transactions for a particular period or companies with a large number of accounts, timeout errors could occur when calculating period values.