Sage Server

[Sebasten Lizarraga]

Sage100 Advanced and Premium are powered by the Application Server, which allows multiple users to remotely access the server using TCP/IP. Users can be connected on an internal LAN or externally through an intranet or WAN. The Application Server also allows for encryption using SSL to protect your data if operating in an environment that is not secure, such as over the Internet.

Before you can start Sage 100 Advanced or Premium, you must first configure the Application Server. The Application Server can be configured to run as a service; it must be configured using the following steps to access the Sage 100 server.

For security purposes, the first setting you should change is the socket number on which the Application Server listens for requests. By default, this is set to 10000, but can be any valid socket (port) between 9000 and 10000. Make sure the socket you choose is not being used by another service or application on this server.

In this current configuration, a user must remain logged onto the server where the Application Server is running. The user logged on to this server must have access to all resources required by Sage 100 (all rights to all program and data folders in Sage 100).

You can start the Application Server by selecting the Application Server Startup menu item from the Windows Start menu. This starts the Application Server, which will continue to run until the user is logged off or the server is shut down.

You can also turn off the Application Server by closing the Application Server task that appears on the Task Bar of the server. To do this, right-click the task and click Close from the pop-up menu. The Application Server will shut down after a few seconds.

If you already have a Windows domain user account set up to run the Application Server, skip this step; otherwise, create a new domain user on your server that has appropriate access rights to run all the functions and features of Sage 100. This should include the Modify permission to the application folder, any folders where Sage 100 data is located, the Windows folder, and access to the Registry. This account must also be granted the Log On as a Service right.

If you are not running in a domain environment, create and use a local computer account for your workgroup; however, you must ensure this account can execute a UNC path to the MAS90 folder. Test this by entering the UNC path in Windows Explorer. If you are prompted for a user name and password, the account is not set up properly.

Select the path of the Sage 100 installation, if it is different than the default Sage 100 installation path. The Application Server Service installation wizard installs the service components necessary to run the Application Server as a service.

If the service is set to Manual, you will need to launch this window to start up the service each time the server is reset. You may want to set the service to Manual if you plan on performing maintenance on the server and do not want the Application Server service to start up after restarting.

The Application Server has a number of additional features that can be useful for system administrators. You can enable some of these features for added security or logging purposes; however, these are not required to run Sage 100. To enable these features, you must log on to the server and start the Application Server Configuration program.

In the Application Server Configuration window, on the Sessions tab, you can view a list of all the users who are currently in the system and which task they are running. This window also provides you with more detailed information about the machine name, IP address, and connection time for each process. This is useful when trying to find users on the system or people in a particular application. Master Console in Sage 100 can also be used for this purpose.

Individual sessions can be terminated if they appear to be locked up or become unresponsive. Terminating a process in this manner can cause data corruption issues and should be done only as a last resort. To terminate a session, select the session from the list and then click Terminate.

The Application Server can be configured to use SSL to encrypt data being sent to and from the Application Server. This can be extremely useful when using the Internet or any other unsecure medium to connect workstations to the server; however, SSL does add extra overhead in terms of performance. This feature should be enabled only if it is necessary. Using SSL in a secured, intranet environment or over an already protected tunneling protocol (like VPN) is not recommended due to the potential performance impact.

The SSL component of the Application Server uses the OpenSSL protocol and drivers. To use SSL, you must first configure the Sage 100 Application Server to use SSL and then generate an SSL certificate. For more information, Generating an SSL Certificate.

Make sure all users are out of Sage 100. After SSL is enabled, a different connection string is required for each of the workstations connecting to the server. Workstations that do not have this additional information will not be allowed to connect to Sage 100.

Verify which start-up icon the user used when trying to connect to the server, and verify that the -SSL argument is in the target command line. Users may have multiple shortcuts connecting to the server that need to be modified.

Once it finishes, click next to start the configuration process. If you selected ok to any of the updating of the ODBC drivers, you should be prompted with a windows update request when the installer starts the first part of the configuration process. When you see this, click Yes to allow the installer to install the latest ODBC drivers.

The original installer should continue with the print server update after the ODBC update is finished. If everything went well, you would get a completed screen with no errors on it. Click next to continue.

The next screen will be a reminder. The reminder is to remind you that if you updated windows components (in this case, ODBC) that you may want to restart the server machine. Take note and click next. It should take you to the Done screen. Click done to finish.

Next, we are going to restart out machine, just as the reminder asked us to. It does not hurt to restart after installing any component, but when prompted, you should always take advantage of the time and do it.

I am completely new to Sage, and have been tasked with migrating the current install to a new server. We are on a server 2012 domain controller and migrating to a server 2019 domain controller. I have looked at Sage documentation, however cant really what I'm looking for regarding CRE300 accounting.

Hopefully it'll include all prerequisites for install of sage such as SQL and the like, how to install Sage, how to migrate data over, how to point clients to new server and anything else that is pertinent. Unfortunately, having sage do this is quite possibly out of the question. (not for my part)

You really should consider hiring a Sage Consultant to come on sight and help you. With their help, I think we did it in less than a day on one live company data folder and 19 years of archived data folders without using the replicator. I feel like it would be so easy to mess things up without someone's help even using Sage's Server Migration Tool. I think Knowledgebase has some information on server migration that you should search for (along with the documentation under help). I think it becomes more difficult if you use file attachments, macros, My Assistant, etc.

Hi Stan, here ya go. Be sure to do your own homework, make sure the links are for your product. Some of the links are of the same context, however, I've included them as there may be differences in details between them. I'd rather have too much than too little documentation...

We had a physical server that hosted our Sage 100 files and other settings. We recently virtualized it for backup and security purposes, and put it back on the same physical server now as a Hypervisor. We set the VM resource settings as high as we could but now the server is significantly slower. Is there some network setting in Hyper-V that could be causing this? Even accessing files seems slower.

The network settings that may dramatically drop performance in the case of Hyper-V are RSC and VMQ, so you may try playing with them Poor Network Performance on Hyper-V VMs in Windows Server 2019 Windows OS Hub .

I dealt with Sage bare metal installs forever, I was fed and done with sage, at the time they did not have cloud product so we moved to CMiC, however I think sage does now offer a cloud version for sage 100. I would look into moving away from local install all together.

Have you tried changing the hypervisor? The primary alternative, ESXi, is free (with some limitations), and you may also try oVirt on Linux or Proxmox/XCP-NG. To avoid configuring the Sage virtual machine from scratch every time, you may just convert it using a free V2V Converter V2V Converter / P2V Converter - Converting VM Formats . While such an approach is not recommended for production, it is acceptable for testing purposes.

I performed server migration on Sage 100 ERP 2013. Installation and data are fine, but workstations keep looking for old server on launching client, even after completely uninstalling and reinstalling workstations. Not sure how to remove the old server connections. On launching ERP 100 it says it can't connect to the old server and won't go any farther. How do I remove the old server completely from the workstations?

Some additional info.

When you uninstall the workstation, it should ask whether you want to remove all registry entries. Do it.

Additionally, if you have created any shortcuts on your desktop or other places, it likely will have references to the old server in it as well. Delete those shortcuts. (I have noted that in older versions, the shortcuts don't have these references and it would get all the info from the sota.ini file - later versions have them in the shortcut itself).

Then reinstall the workstation. Make your shortcuts from the new icons in your start menus.

3a8082e126