Comments on: Why is Sage Line 50 so slow? http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/ Technology. Where's it all heading? Wed, 25 Jan 2012 20:18:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: BW http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1959 BW Wed, 25 Jan 2012 20:18:01 +0000 http://blog.frankleonhardt.com/?p=189#comment-1959 about six years ago we got updated from sage line 100 to mms and have had nothing but problems since. We pay about £1000 per year for a new licence but in the six years have never go a update. Were do we go from here about six years ago we got updated from sage line 100 to mms and have had nothing but problems since. We pay about £1000 per year for a new licence but in the six years have never go a update. Were do we go from here

]]> By: Ian http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1576 Ian Thu, 03 Nov 2011 18:48:51 +0000 http://blog.frankleonhardt.com/?p=189#comment-1576 If anyone is in any doubt, it appears that Sage have done some serious work on Sage Line 50 2012. We have customers reporting very positive performance improvements after install and data conversion. [Ed: Personally I'd like something more than hear-say, but interesting] If anyone is in any doubt, it appears that Sage have done some serious work on Sage Line 50 2012. We have customers reporting very positive performance improvements after install and data conversion.

[Ed: Personally I'd like something more than hear-say, but interesting]

]]> By: j-g http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1308 j-g Mon, 19 Sep 2011 15:56:46 +0000 http://blog.frankleonhardt.com/?p=189#comment-1308 Hi, I think your solution was to run on XP - which may well work but isn't really a long term supported solution. Apart from RDPing did you suggest anything else? I did get Sage to fix some issues many years ago as they were reading (check for / open / read / close) same file for each line of a ledger entry) - but they have just reverted and is now worse than ever :( J Hi, I think your solution was to run on XP – which may well work but isn’t really a long term supported solution. Apart from RDPing did you suggest anything else? I did get Sage to fix some issues many years ago as they were reading (check for / open / read / close) same file for each line of a ledger entry) – but they have just reverted and is now worse than ever :( J

]]> By: Gav Richards http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1307 Gav Richards Mon, 19 Sep 2011 15:21:39 +0000 http://blog.frankleonhardt.com/?p=189#comment-1307 Hi Mark, Not checked on here for a while but saw your reply and though I'd respond. We did have exactly the same problem as other people were experiencing and I overcame them to a reasonable extent. If you read my entry a little further up the blog you'll see what I did to help speed up Sage. I found this blog by searching "Sage" & "slow" nearly a year ago and I hoped my entries would be some help to people with the same issues. Perhaps I was mistaken, judging by the responses I've receive so far. Hi Mark,
Not checked on here for a while but saw your reply and though I’d respond.
We did have exactly the same problem as other people were experiencing and I overcame them to a reasonable extent. If you read my entry a little further up the blog you’ll see what I did to help speed up Sage.
I found this blog by searching “Sage” & “slow” nearly a year ago and I hoped my entries would be some help to people with the same issues.
Perhaps I was mistaken, judging by the responses I’ve receive so far.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1066 Mark Wed, 10 Aug 2011 14:49:58 +0000 http://blog.frankleonhardt.com/?p=189#comment-1066 Hi Jon, Below is the response form our IT guy: We have done this. There are a couple of metrics on the other page you sent that might lead in the right direction, though. http://www.sbslimited.co.uk/AV.htm That page would seem to indicate that Avast Home (which is related to the AV we use) has a pretty substantial impact on file access times, regardless of whether files are excluded, or even if the AV engine itself is disabled completely. The only way to confirm or refute this is to uninstall the AV from all the workstations and do some testing. If this is the case, I will be looking to the manufacturers for a refund, and we will have to go with another AV solution. - I'll let you know if this is the solution to our problems. Regards Mark Hi Jon,

Below is the response form our IT guy:

We have done this.
There are a couple of metrics on the other page you sent that might
lead in the right direction, though.
http://www.sbslimited.co.uk/AV.htm
That page would seem to indicate that Avast Home (which is related to
the AV we use) has a pretty substantial impact on file access times,
regardless of whether files are excluded, or even if the AV engine
itself is disabled completely.
The only way to confirm or refute this is to uninstall the AV from all
the workstations and do some testing.
If this is the case, I will be looking to the manufacturers for a
refund, and we will have to go with another AV solution.

- I’ll let you know if this is the solution to our problems.

Regards

Mark

]]> By: Ian http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1065 Ian Wed, 10 Aug 2011 14:42:32 +0000 http://blog.frankleonhardt.com/?p=189#comment-1065 Mark Take a look at the SMB2 problem I mentioned somewhere in this comments section. If your servers are 2008 or 2008 R2 and your clients are Vista or Windows 7, then you should consider disabling SMB2 on your network. + adding DTA to your exclusions + the other helpful stuff in this comments list. Mark

Take a look at the SMB2 problem I mentioned somewhere in this comments section. If your servers are 2008 or 2008 R2 and your clients are Vista or Windows 7, then you should consider disabling SMB2 on your network.

+ adding DTA to your exclusions + the other helpful stuff in this comments list.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1064 Mark Wed, 10 Aug 2011 14:35:25 +0000 http://blog.frankleonhardt.com/?p=189#comment-1064 Thanks Jon, I'll check it out + let you know if your suggestion helps. Thanks Jon, I’ll check it out + let you know if your suggestion helps.

]]> By: jon http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1063 jon Wed, 10 Aug 2011 14:19:27 +0000 http://blog.frankleonhardt.com/?p=189#comment-1063 Mark, A lot smaller company we had exactly the same problems, excluded every sage folder we could find on server and client from virus scan, all sorts of tweaks and tricks but the thing that we hadn't done which solved most of our problems was to disable real time virus scanning on .dta file types. as soon as these file types were excluded from checking our problems vanished. We were using eset antivirus, win 7 clients and win 2003 server. Mark,
A lot smaller company we had exactly the same problems, excluded every sage folder we could find on server and client from virus scan, all sorts of tweaks and tricks but the thing that we hadn’t done which solved most of our problems was to disable real time virus scanning on .dta file types. as soon as these file types were excluded from checking our problems vanished.

We were using eset antivirus, win 7 clients and win 2003 server.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1062 Mark Wed, 10 Aug 2011 13:28:23 +0000 http://blog.frankleonhardt.com/?p=189#comment-1062 Gav, you are not suffering from the problems that other sage users experience every day. How you found this blog is a mystery to me. Rest assured, the less software, staff and accountants you have that are unwilling to move from sage when the need arises, the better off you will be. Gav, you are not suffering from the problems that other sage users experience every day. How you found this blog is a mystery to me. Rest assured, the less software, staff and accountants you have that are unwilling to move from sage when the need arises, the better off you will be.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1061 Mark Wed, 10 Aug 2011 13:20:26 +0000 http://blog.frankleonhardt.com/?p=189#comment-1061 Mr S, Sage has been happy to take our money for all the "wrong" versions we bought. Please don't pretend they have suddenly developed a conscience. If I worked for sage, I too would with-hold my name from public viewing. Mr S,

Sage has been happy to take our money for all the “wrong” versions we bought. Please don’t pretend they have suddenly developed a conscience. If I worked for sage, I too would with-hold my name from public viewing.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1060 Mark Wed, 10 Aug 2011 13:12:30 +0000 http://blog.frankleonhardt.com/?p=189#comment-1060 Stick with version 11. An upgrade will cripple you. Stick with version 11. An upgrade will cripple you.

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-1059 Mark Wed, 10 Aug 2011 13:09:10 +0000 http://blog.frankleonhardt.com/?p=189#comment-1059 Hi Claire, Hope i'm not too late with this advise. Our company has spent well in excess of 25grand on upgrading our hardware + server. We also moved into a new building and had a new data-cable wiring job done. Things with sage have only gotten worse. Twice we have been tricked into upgrading teh sage program which has only worsened things further. Sage is the problem and nothing else. Mark Hi Claire,

Hope i’m not too late with this advise. Our company has spent well in excess of 25grand on upgrading our hardware + server. We also moved into a new building and had a new data-cable wiring job done. Things with sage have only gotten worse. Twice we have been tricked into upgrading teh sage program which has only worsened things further.

Sage is the problem and nothing else.

Mark

]]> By: Mark http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-1058 Mark Wed, 10 Aug 2011 13:00:45 +0000 http://blog.frankleonhardt.com/?p=189#comment-1058 Our Sage "partner" upgraded us to the latest version in April without any authorization from us. It has virtually put our whole company at a standstill for the past few months. Sage stalls with every operation at every workstation with messages such as: (Waiting to open file ACCDTA). A workstation could stall for anything between 5 mins up to an over an hour. Sometimes sage just vanishes from the screen and you have to log-on again, remove the user that was logged on and hope for the best. This regularly causes data corruption which means we are checking data + doing back-ups twice a day - a process which takes an hour each time. We've upgraded our hardware memory + power at the sage "partners" request and at a cost of 1000.00 euro. We've cleared down 10's of thousands of transactions bring it well below the recommended limit. We've tinkered with + adjusted antivirus software as recommended. None of all this has brought about any improvement. Invoices are going out between 10 + 30 days late, same applies to statements. Using the sage program is the single largest cause of stress within our company and has been our largest challenge since it was first installed back in 2001. If sage have such a large customer-base, it comes as no surprise to me that the world is always on the brink of financial meltdown. I am seriously considering returning to manual book-keeping. Our Sage “partner” upgraded us to the latest version in April without any authorization from us. It has virtually put our whole company at a standstill for the past few months. Sage stalls with every operation at every workstation with messages such as: (Waiting to open file ACCDTA). A workstation could stall for anything between 5 mins up to an over an hour. Sometimes sage just vanishes from the screen and you have to log-on again, remove the user that was logged on and hope for the best. This regularly causes data corruption which means we are checking data + doing back-ups twice a day – a process which takes an hour each time. We’ve upgraded our hardware memory + power at the sage “partners” request and at a cost of 1000.00 euro. We’ve cleared down 10′s of thousands of transactions bring it well below the recommended limit. We’ve tinkered with + adjusted antivirus software as recommended. None of all this has brought about any improvement. Invoices are going out between 10 + 30 days late, same applies to statements. Using the sage program is the single largest cause of stress within our company and has been our largest challenge since it was first installed back in 2001. If sage have such a large customer-base, it comes as no surprise to me that the world is always on the brink of financial meltdown. I am seriously considering returning to manual book-keeping.

]]> By: Geoff http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-2/#comment-867 Geoff Mon, 02 May 2011 14:16:24 +0000 http://blog.frankleonhardt.com/?p=189#comment-867 Quote: "People say it’s stupid to suggest Sage actually want these errors and problems to continue just to get more money and I agree." Un-quote. Maybe there is a possibility that they may be right and they do. I have heard that they want people to keep with the support. Looking at it black and white why would anyone keep a product going that is just so bad. Jobs? Face-saving? Corporate psychopathy? If Tesco made a product that everyone complained about it would be removed from the shelves tout-suite! Why not the same with Sage? Quote: “People say it’s stupid to suggest Sage actually want these errors and problems to continue just to get more money and I agree.” Un-quote.

Maybe there is a possibility that they may be right and they do. I have heard that they want people to keep with the support. Looking at it black and white why would anyone keep a product going that is just so bad. Jobs? Face-saving? Corporate psychopathy?

If Tesco made a product that everyone complained about it would be removed from the shelves tout-suite!

Why not the same with Sage?

]]> By: jon http://blog.frankleonhardt.com/2010/why-is-sage-line-50-so-slow/comment-page-1/#comment-820 jon Mon, 04 Apr 2011 10:21:13 +0000 http://blog.frankleonhardt.com/?p=189#comment-820 We finally have resolved our issues With Sage 2009 and "waiting to open account.dta" messages and general slowness. We are also using Eset nod32 and excluded everything as you have. This didn't work but what I did finally do was to go to advanced setup, realtime file system protection / threatsense engine parameter setup click setup, and then got to extensions and add dta files. These are then excluded and Sage has been marvellous since. No problems and runs faster too. We did this on server and clients and so glad that we did. We finally have resolved our issues With Sage 2009 and “waiting to open account.dta” messages and general slowness.

We are also using Eset nod32 and excluded everything as you have. This didn’t work but what I did finally do was to go to advanced setup, realtime file system protection / threatsense engine parameter setup click setup, and then got to extensions and add dta files. These are then excluded and Sage has been marvellous since. No problems and runs faster too.

We did this on server and clients and so glad that we did.

]]>