Sage 100

 View Only
  • 1.  Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 12:27
    Customer is on v2014 Standard, system has always been a bit slow but they won't move to Advanced. They have 17 licenses. New server at time of upgrade over a year ago. They added SageCRM in December and things were working fine, but they had not yet gone live. At some point between March & April, Sage 100/CRM started hiccuping and giving 'not responding' when trying to promote customers, etc. It has gotten progressively worse and now Sage 100 freezes in all modules on a regular basis. It appears to have happened about 2 weeks after the last Windows Updates and possibly around the same time Sage Support rebuilt key files (customer initiated support call to Sage). IT did adjust the memory on the VM, but customer also indicated the last time it froze, CPU was at 76% for Apache. They rebooted and everything went back to normal at the time. Customer also indicates many open Sage files at the same time. I've been told their server has only 1 core processor, 32-48 gb of Ram (on physical box I believe), not sure what the VM has allocated. The server also has terminal services on it. To me it screams resources but it was working fine till 6-8 weeks ago and nobody is fessing up to making changes so hard to make the argument. Trying to get connected to see if Sage Activity Log shows anything. Any ideas as to what to go looking for?


  • 2.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 12:37
    Nancy, one think I would check is Opportunistic Locking, there is an article on Sage regarding this. Just a thought.


  • 3.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 12:38
    New server a year ago and only one core? I don't even think that is possible...


  • 4.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 13:04
    Nancy, At one point it was recommended in similar situation to have the apache process restarted automatically, nightly or weekly. Sorry, I can't speak to the details on how to create that task restart, yet I'm certain others can @PeterWolf


  • 5.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 15:31
    Maybe diskspace on server.


  • 6.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-18-2016 16:24
    Agree with @ChrisStAmand - it sounds like a file is getting too big to process and then crashes. i had a similar issue with SQL program last week that would seem to run for ever then end in an out of resource error. In that case it was a bug in the SQL code but you could also look in CRM for overly large files, including logs.


  • 7.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-19-2016 09:17
    I have been using Office 365 2016 since December. I have created many SI reports for versions 2014 and 2015 without any issues.


  • 8.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-19-2016 09:50
    There was a post - [here](https://90minds-com.socialcast.com/messages/16414756?ref=stream) - about adding more cores to VM. In the post I believe the symptoms were somewhat similar and that expanding the cores and possibly available memory resolved it. I would ask IT to humor you and try expanding the cores and seeing how that works.


  • 9.  RE: Customer is on v2014 Standard, system has always b

    Posted 05-19-2016 15:14
    Update: Looked at current open files. All Sage related and 885 of them. Most have 0 as # Locks but a few as many as 4 (sy_console) and 10 have 1 (various files). Is this a cause for concern to have this many open? There currently is 8 active users with 20 programs/tasks open. Looked at Sage ticket - Daily Sales Journal appeared to be hanging, they reinitialized the so_invoicerestart and rebuilt key files for SO & AR. 1 invoice was posted 3 x so they fixed it through DFDM. Nothing major in my opinion to cause these add'l problems. Working up a plan to have user document but also maybe turn off Integration Engine/CRM for a few days since they are not yet live anyway. Will look at advising them on adding more cores.