Why my Sage 50 Freeze every time ?

Hello,

I installed Sage 50 pro edition on my server (Four CPU AMD opteron 16 core with 16 G of RAM with RAID 10 mode and 225 MB of download on my internet)

I already try every thing you guys said about the buffer in MySQLi put this one from 1m to 128M to 500m and the connection manager  I also put this one 56mb to 5000mb!!! and no change!!!

My files are not that large. The larger one is about 60mb of data

I know for sure the problem don't come from my server because when I run sage 50 even with the buffer set to 5000M the % of use for the cpu is about 2% and memory about 20% so there a lot and a lot of space for performance here and I don't see it with sage 50

My gues is.. is it an issue in the program itself?

Parents
  • 0

    Hi Antoine,

    May I ask you to share a little bit more information with us.

    What is the server where your Sage 50 is installed?  Server 2008 R2 or higher?

    What were you actually working on when the Freezing occurred?

    Does the freezing happens randomly?

    During freezing, when you open the task manager, is Sage 50 showing not responding?

    Did you go to check the eventviewer?

    The more information you provide, the better not only us but other experienced users can understand your questions?

    Please post back. 

    Thanks

Reply
  • 0

    Hi Antoine,

    May I ask you to share a little bit more information with us.

    What is the server where your Sage 50 is installed?  Server 2008 R2 or higher?

    What were you actually working on when the Freezing occurred?

    Does the freezing happens randomly?

    During freezing, when you open the task manager, is Sage 50 showing not responding?

    Did you go to check the eventviewer?

    The more information you provide, the better not only us but other experienced users can understand your questions?

    Please post back. 

    Thanks

Children
  • 0 in reply to Keith L

    - Server 2008 R2 Standart Serv pack 1

    - It happen on every windows of sage for example going to a report it freeze then it start to go faster for like 3 or 4 more clic (switching windows and going to sales or purchases and then it freeze again) and so on ..fast and freeze 10 sec.. fast and freeze...

    -yes the freezing happens randomly

    -Yes it show no responding on task manager but like I said only for  only10 sec then it start running fast again (the program did not stop completely)

    - yes I did check the eventviewer but like I said only 10% of my RAM is USE and only 2% of my four CPU are use

    -I run other program like Office (outlook) Exchange server... Quickbook... and Xactimate  in the same time that I run Sage 50 and the other program are extremely fast and don't freeze like sage does

    The server is in my office and I connect to the server Remotely from my home .. and I try running sage on the server (Live) and also on the remote desktop session and both freeze

    I tried to increase the connexion manager I put it to 3500mb instead of 56! and the buffer size of de dbengine from 1 to 128 to,256 to,512M and NO change!

  • 0 in reply to Antoine Rioux

    Hi Antoine, 

    Please follow the steps below:

    1.Open Control Panel then Programs & Features (or Add/Remove Programs).
    2.Verify if you have more than one antivirus software installed.

    1.If you have more than one, uninstall them until you only keep one antivirus.
    2.reboot.

    3.If you have any pending Windows Updates awaiting installation, then please install them then reboot.
    4.Uninstall Sage 50 Accounting.
    5.De-activate your antivirus.
    6.Open an explorer window (Win + E keys).
    7.Go to C:\Sage\
    8.Open the folder containing the latest version of Sage 50.
    9.Go to the \Setup\ folder.
    10.Right-click the setup.exe file.
    11.Windows Vista, 7, or 8: Click Run as administrator.
    12.Windows XP: Click Run As then login as the administrator login.
    13.Please follow the screen and proceed with the installation of Sage 50.
    14.Reboot.
    15.Windows Vista, 7, or 8: Everytime you use Sage 50, please right-click the Sage 50 Accounting shortcut icon on your desktop then select Run as administrator.

    1.Alternatively, you can right-click it once then
    2.Click Properties.
    3.Click Compatibility.
    4.Add a checkmark to Run this program as an administrator.

    Hope this helps.

  • 0 in reply to Keith L

    -I already did that Server 2008 R2 Standart Serv pack 1

    No update

    No antivirus

    Everything run perfect except Sage 50

  • 0 in reply to Antoine Rioux

    Antonine,

    You may need to consider going to MS config, disable all the non-microsoft services, startup item except Sage 50, reboot and test. 

    As per my previous post, reinstall Sage 50 with firewall off also.  You can always put back the necessary Sage 50 processes to be excluded from the firewall later. 

    Hope this helps.

  • 0 in reply to Keith L

    Antonine... try the sample company... see if it exhibits the same behavior. If it does then as Keith suggests uninstall and reinstall. OR change some of the RDP settings

  • 0 in reply to GwG

    Here is the log file!!

    Maybe you can find the problem with it

    InnoDB: Restoring possible half-written data pages from the doublewrite

    InnoDB: buffer...

    120301 22:01:19  InnoDB: Starting log scan based on checkpoint at

    InnoDB: log sequence number 0 50491.

    InnoDB: Doing recovery: scanned up to log sequence number 0 50491

    120301 22:01:19  InnoDB: Started; log sequence number 0 50491

    120301 22:01:19 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: ready for connections.

    Version: '5.0.38-enterprise-nt'  socket: ''  port: 13541  MySQL Enterprise Server (Commercial)

    120301 22:56:48 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Normal shutdown

    120301 22:56:49  InnoDB: Starting shutdown...

    120301 22:56:52  InnoDB: Shutdown completed; log sequence number 0 5928997

    120301 22:56:52 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Shutdown complete

    Error in my_thread_global_end(): 2 threads didn't exit

    120301 22:57:25  InnoDB: Started; log sequence number 0 5928997

    120301 22:57:25 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: ready for connections.

    Version: '5.0.38-enterprise-nt'  socket: ''  port: 13541  MySQL Enterprise Server (Commercial)

    120301 22:57:42 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Normal shutdown

    120301 22:57:43  InnoDB: Starting shutdown...

    120301 22:57:47  InnoDB: Shutdown completed; log sequence number 0 5929375

    120301 22:57:47 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Shutdown complete

    Error in my_thread_global_end(): 2 threads didn't exit

    120301 22:58:27  InnoDB: Started; log sequence number 0 5929375

    120301 22:58:27 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: ready for connections.

    Version: '5.0.38-enterprise-nt'  socket: ''  port: 13540  MySQL Enterprise Server (Commercial)

    120301 23:01:15 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Normal shutdown

    120301 23:01:18 [Warning] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Forcing close of thread 3  user: 'winsim'

    120301 23:01:18  InnoDB: Starting shutdown...

    120301 23:01:20  InnoDB: Shutdown completed; log sequence number 0 5932843

    120301 23:01:20 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Shutdown complete

    Error in my_thread_global_end(): 2 threads didn't exit

    120305  9:02:28  InnoDB: Started; log sequence number 0 5932843

    120305  9:02:28 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: ready for connections.

    Version: '5.0.38-enterprise-nt'  socket: ''  port: 13541  MySQL Enterprise Server (Commercial)

    120305  9:24:01 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Normal shutdown

    120305  9:24:02  InnoDB: Starting shutdown...

    120305  9:24:06  InnoDB: Shutdown completed; log sequence number 0 6065376

    120305  9:24:06 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Shutdown complete

    Error in my_thread_global_end(): 2 threads didn't exit

    120305  9:24:42  InnoDB: Started; log sequence number 0 6065376

    120305  9:24:42 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: ready for connections.

    Version: '5.0.38-enterprise-nt'  socket: ''  port: 13540  MySQL Enterprise Server (Commercial)

    120305  9:25:28 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.0.38\mysql\mysqld-nt.exe: Normal shutdown

  • 0 in reply to Antoine Rioux

    I also have sage 2013 and 2014 install with MySQL 3.51 and 5.2 maybe the problem is because there is two program and 2 sql instead of one

  • 0 in reply to Antoine Rioux

    THE log file looks normal. MySQL 3.5 and 5.2 can co-exist on the same machine.  Try Sample company?

  • 0 in reply to GwG

    Hey thanks for the help but yes I remotely connect to my server an hour ago in administration rdp session and I uninstalled Sage 50 and all component related to Simply accounting ... I installed it again and it work really fast in my administration session BUT. here is the problem... as I was connected in administration RDP session I also connect as an other user (RDP) like my employees does and on that session Sage 50 was really slow so basically every time I have two or more RDP session connect to my server, SAGE 50 run fast but freeze all the time and every time I'm alone on an rdp session and connect as an administrator   there is no freeze and every thing run super fast!

  • 0 in reply to Antoine Rioux

    Sounds like you have not activated and setup Terminal Services. Multiple RDP connections will slow down the server.... setup Terminal Services but there is licencing fees for TS.... check it out

  • 0 in reply to GwG

    Off course I had installed TS!!  right now I'm connected to my server remotely from my office and I write this message on an RDP session !

    If I go on my task manager I also see that there are 10 users right now connect via RDP on my server ! and they are all working on sage 50 ! (those are my employees 6 in the office and 4 at home)

  • 0 in reply to Antoine Rioux

    Ok i'll do my best to explain what i did and what i did not so far

    - Uninstalled sage and reinstalled (NO CHANGE STILL FREEZING)

    - Desactivate the Antivirus (NO CHANGE STILL FREEZING)

    - Connect to my server as an Admin (only one RDP session) GOOD NO FREEZING

    - Connect to my server as and Admin and connect one of my employees to the server (NO CHANGE STILL FREEZING)

    *** WE WORK ON MULTIPLE RDP SESSION AND EACH SESSION OPEN ONE COMPANY ***

    Exemple: user 1 connect RDP to the server and open Company # 1 in sage 50

    user 2 connect RDP to the server and open Company # 2 in sage 50

    My self (ADMIN) connect RDP session to the server and open company # 3

    and so on and so far...

    So here i'm trying to find why Sage 50 is so slow when 2 user or more connect via RDP to the server ? and as i said my server is really fast so it not suppose to be a probleme even if there 100 user connect to it !

  • 0 in reply to Antoine Rioux

    what happens it you have two admin users connected - does it freeze ?

  • 0 in reply to Roger L

    Yes

    If the Administrator user connected and myself Antoine sessions (admin also) it freeze

  • 0 in reply to Antoine Rioux

    I distinguish between RDP and TS Client. To myself they are two different connection types. For yourself RDP is a TS Client..... but any way go to SERVICES and change LOG ON for the SAGE 50 CONNECTION MANAGER to Administrator make sure not to allow interaction with desktop. ALSO check out the  Windows System Resource Manager, use this snap in to change the way the CM runs

  • 0 in reply to GwG

    I did it last night and I'm testing it right now with my employees and it didn't work so.. no change still freezing