Sal Skillern

Multi user mode within Sage appears simple on paper. Multiple users working at the same time, same company file No interruptions. In fact, this is where the majority of Sage users begin to lose patience. A few minutes later everything is working fine. Then sage 100 support suspends users, freezes or completely shuts down. Sometimes, it will throw an error. Sometimes, it disappears. There is no warning. No explanation. If you've ever had to deal with this, you already know the pain. Let's find out why this happens and what you can realistically do before this becomes a problem for your workplace. The real reason Sage has a hard time in multi user mode Sage relies heavily on stable communication between the server's network and the other systems connected to it. If even the slightest connection is lost, Sage reacts badly. It's rarely due to one large mistake. Usually it is a combination of little things that build up. Network instability is among the major causes. Even if your connection appears good, the internal network's drops or loss of data packets can interrupt Sage sessions. Multi user mode is highly sensitive to this. Another reason that is often cited is poor configuration of the system during installation. A lot of businesses speed through Sage setup. The default settings remain the same. Permissions may be partially configured. All appears fine as long as more users is logged in. Then Sage begins to crash. Conflicts regarding access to company files When multiple users attempt access the same the file Sage should manage locks and permissions in real time. If the document is stored in the wrong location or accessible via mapped drives that are not secure, conflicts may arise. An individual saves a report. Another user attempts to open reports. Sage can't sync as fast as it should. Crash. This can be exacerbated if employees are viewing large reports or and inventory modules simultaneously. User permissions that appear okay but aren't Permissions issues can be quite sneaky. In the beginning, everything looks perfect. Users are able to login. Open files. Data is displayed. However, behind the scenes, Windows permissions or Sage user roles could be missing. A user might not have complete read and write access. Another might be missing modify rights on the share folder. Sage does not always provide an explicit warning for this. Instead, it crashes. Problems with servers and hosting In the event that Sage was hosted using a locally-hosted server, this server requires proper resources. Too little RAM, an overloaded CPU or insufficient operating system updates could cause instability to Sage sessions. Virtual servers can create problems too. Hosting shared environments often restrict resources without prior warning. During times of high traffic, Sage becomes the victim. It is for this reason that many crashes are experienced during busy times like the month's end or payroll days. Background programs interfering with Sage A silent antivirus program is a unintentional troublemaker. Certain antivirus programs systematically examine Sage file when they're being used. This causes file access to be interrupted and can cause Sage for to be shut off. Backup tools that run during the office hours also can lock files without warning. The user may experience a crash. The system detects that there is a conflict. The firewall rules restricting Sage ports may cause occasional disconnects that look like software issues. Incorrect data and an increasing file size Over time, Sage company files grow. More transactions. More reports. More users. If maintenance routines are not followed then data corruption will slowly build up. Sage might still open. Single user mode is likely to work flawlessly. But multi user mode exposes the weaknesses. The frequency of crashes increases. Especially those with more than two accounts are signed in. How can you minimize Sage crashes in multi user mode? Let's look at what actually aids. Start with the network. A stable and reliable wired connection always more secure than wireless connections for Sage users. Avoid working over unstable VPNs unless they are properly configured to work with accounting software. Review the company file address. It should be located on a trusted server with identical access paths for all users. Avoid desktop sharing and temporary folders. You should check the permissions meticulously. Not just Sage user roles However, check Windows folder permissions also. Each Sage user should have full read and write access to the shared folder of the company. Schedule antivirus-related exclusions for Sage folders. This alone can solve a shocking number of complaints about crashes. Make sure backups don't being used during hours of work. Make sure they are scheduled for late at night or early morning. Run Sage data verification and maintenance frequently. Don't be waiting for errors to be discovered. When fixes fail after that, you can't fix it Sometimes you're doing everything correctly and Sage will not work. This usually happens when the problem is much deeper. The cause could be file corruption that requires expert intervention. It could also be server issues with configuration. The issue could be related to conflicting versions within Sage Updates on different computers. This is where a lot of people are able to stop speculating and seek answers directly. Making a call to the support number now saves precious time and will prevent any further destruction. A trained technician can find which issue is at the root instead of attempts to solve the problem. Supporting the cause of delay makes things worse Many businesses are constantly restarting Sage and hoping the problem will go away. The problem is that it rarely happens. The risk of repeated crashes increases with each of corruption of data. Invoices can not be saved in a timely manner. Payroll entries might duplicate. Reports could show incorrect numbers. In the end, when the help request is made, the issue is much more complex in scope than it actually needed to be. Contacting early via the sage 50 support phone number generally results in better resolution and shorter downtime. Last thoughts from real-world use Sage multi user mode is powerful but so tolerant. It is a system that expects everything to function correctly. Network. Permissions. Server. Security software. Every single one of them. The majority of crashes are not random. They're signals that something underneath needs attention. If your Sage software has a few times of crashes the software is an indication. If it is constantly crashing It is the right time to be proactive. Get the basics right first. The stability of your network. File access. Permissions. Maintenance. And when things stop making sense, don't spend hours speculating. Finding expert help early will help save your data, time, and your sanity.