On Premise Installations Follow

The process of implementing GlasPacLX on to a customer's on premise system can contain a lot of hurdles. The following document to help cover many of the steps needed to successfully implement GlasPacLX during an on-premise installation.


Setup Processes
Installing SQL Manually
Installing GlasPacLX
ComApp service
Setting up Attachments

Windows Version
User Access Control (UAC)
SQL Version
Full SQL vs. SQL Express
Terminal Server
Active Directory

Setup Processes

Installing SQL Manually

There are a few cases where SQL Server will need to be installed manually. If the customer is using a full version of SQL Server or needs SQL 2012 Express installed, because of a Windows version requirement, then SQL will need to be manually installed. In cases where a full version of SQL Server is needed, the customer should have a local technician assisting them. However, if the customer requires SQL Express 2012, then this can be installed by GTS.

In any case where SQL Server needs to be installed manually, there are couple of options that need to be selected:


During the installation process, you can use the default settings for most screens. However, there are three specific instances where you will need to change the settings listed.

  • Instance Configuration
    On the Instance Configuration screen, you will need to change the instance name to GTS.

  • Server Configuration
    Once you reach the Server Configuration screen of the installer, verify or change the settings for the SQL Server Database Engine and the SQL Server Browser, so that the Startup Type is set to Automatic, and the Account Name is set to NT AUTHORITY\SYSTEM.

  • Database Engine Configuration
    The Authentication Mode needs to be changed to Mixed Mode, and the GTS sa password will need to be entered.

Once SQL Server has finished installing, you will need to enable the TCP/IP and Named Pipes protocols for the SQL Server (GTS) instance of SQL. Click on the START button, and locate SQL Server Configuration Manager. Open SQL Server Network Configuration, and select Protocols for GTS. In the right-hand column, enable Named Pipes and TCP/IP by right-clicking on each and making the change. Restart the SQL Server service to enable your changes.

Installing GlasPacLX


The installation of GlasPacLX on the customer's server can be either straight forward, or a curvey mess depening on the customer's needs. The customer may need to have GlasPacLX installed on a secondary drive (d:, e:, f:, etc.). They may have a separate SQL server, or a mixed environment of a Terminal Server and client workstations, or remote users. Be aware of the following items as they can cause problems if you're unaware of them.

  • Folder and Share permissions
    The entire drive partition where GlasPacLX has been installed must be shared out for GlasPacLX to run correctly on client computers. The share rights will need to be set to at least Read permission. Additionally, the GTS folder on that partition must have full permission set for all users who will be running GlasPacLX.
  • Opening the Firewall for SQL
    You may need to create an Inbound Firewall rule for the SQL Server (GTS) service, and the SQL Browser service. Open Control Panel > Windows Firewall, and click on Advanced Settings.
    Select Inbound Rules > New Rule.

    Select Program, and click Next.

    Locate the file path for the SQL Server (GTS) and SQL Browser services, by opening the specified service, and copying the Path to Executable. Paste this entry in to the "This Program path:" field.

    Leave the Allow the connection option selected and click Next.

    Uncheck Public on the Profile screen, and click Next.

    Enter a name for the Inbound Rule, and complete the creation process. Repeat this process for the second SQL service.

  • Do not try connecting remote locations directly, use a terminal server
    Some customers may have remote shops that are connected by a VPN connection. These customer MUST have a Remote Desktop server for their remote users. Attempting to connect GTS to a shared SQL instance across the internet can cause data loss and data corruption.

ComApp service


The ComApp service handles a multitude of tasks that range from communicating with Mobile users, retrieving GLAXIS dispatches, transmitting EDI, and acting as the database backup scheduler. Because it is so fundamental to a great many processes, it needs to remain up and running at all times. Once GlasPacLX has been installed on the server, open Services.msc. Locate the GTS ComApp service, and open its Properties by double clicking on it. Select the Recovery tab.

Set the First Failure and Second Failure drop down boxes to Restart the Service. Save your settings, and exit out of the Services window.


The ComApp registry settings store the same information that GlasPacLX stores about Database server, Database name, and File location. If these registry keys are not created, then the ComApp will not be able to communicate with the GlasPacLX database. The easies way to identify if the registry entries have not been created is to look at the ComApp version. The ComApp will display an old version number if the registry entries do not exist. To create the registry keys manually,

Setting up Attachments

Not all customers use attachments, but it is best practice to set them up. If they decide to add Mobile at some point, they will definitely need attachments.


Before anything else, create a user account on the server or domain for the Attachment user. This should not be a user account that is used by others, and it should be set so that its password never expires.


Create a folder named LXAttachments on either the root of their GlasPacLX installation drive, or under the GTS folder. Give all users Modify permissions, and give the Attachment user full permissions to that folder. Share the folder, giving the Everyone group full share permissions.

####CONFIGURE GLASPACLX 1. Log on to GlasPacLX 2. Open Company > Settings 3. Select Attachment Configuration 4. Enter the UNC path to the LXAttachments share. Entering a drive letter will cause errors when clients attempt to attach thier files. 5. Type the Active Directory Domain name or if they are not using Active Driectory, enter the Server name on the Domain field 6. Enter the Username that you created for the attachments 7. Type in the user's password, and click Save to apply your changes


If the customer is using an actualy Windows Server version as their server, you will need to install the Windows Desktop Experience feature. This is especailly important for customers with Remote Desktop servers as not all graphics files will open without the feature being installed.

  1. Launch the Server Manager application
  2. Click on Features in the left column
  3. Select Add Features
  4. Browse through the list to Desktop Experience, and put a check in the box next to it
  5. Allow the required prerequisite features to be installed
  6. Once Desktop Experience has finished installing, reboot the server
  7. Log back on to the server to allow Desktop Experience to complete its activation


For an auto glass installation, make sure you verify that the NAGS installed with GlasPacLX is current. You can check the Help > About screen in GlasPacLX for the version date.

The vehicle and parts images for NAGS are't included with the NAGS installer. Make sure to download them separately. Unzip and copy the GMPics.dat file into the GTS/GM8 folder on the installation drive.


Windows Versions

Version of Windows workstation prior to Vista are no longer supported for the installation of GlasPacLX. If the customer wants to use older Windows versions as Terminal Server clients, that is up to them, but they cannot be installed with GlasPacLX. Windows 10 will be supported for the installation of GlasPacLX starting in early November 2015.

All versions of Windows server after Server 2003 are supported for the installation of GlasPacLX.

User Access Control (UAC)

User Access Control can cause installation and execution issues for several parts of GlasPacLX. It can keep the ComApp feature from installing correctly, and block the attachments feature from functioning. Newer version of Windows (ie. Windows Server 2012 & 2012 R2, and Windows 10) keep more UAC functions running even after reducing the setting to its lowest levels.

To fully disable UAC, the following two actions must be completed: 1. Disable UAC through Control Panel.
Open the Control Panel, and select Large icons or Small icons in the View by dropdown menu. Launch the User Accounts applet, and then click on Change Users Account Contol Settings. Move the slider down to Never notify, and click OK. Reboot the computer to enable the changes.

2. Disable LUA through the Registry.
Open a Command Prompt window, type regedit, and hit enter. Expand the following Registry Keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System. Under System, locate EnableLUA. Double click the entry to edit it, and then change the Value data from 1 to 0. Close the Registry, and reboot the computer again to enable your changes.

SQL Versions

Please be aware of the following minimum SQL version requirements for the version of Windows being run:

Windows 7: SQL 2005 (Suggested: 2008 R2 SP2)
Windows 8 & 8.1: SQL 2008 R2 SP2
Windows 10: SQL 2012 SP1
Windows Server 2008 & 2008 R2: SQL 2005 (Suggested: 2008 R2 SP2)
Windows Server 2012 & 2012 R2: SQL 2008 R2 SP2

Full SQL vs SQL Express

SQL Express has restrictions that can impact customer if they are unaware of the limitations. The maximum number of CPU cores, Memory used and Database files sizes are as follows: * All versions of SQL Express will use a maximum of 1 CPU * All versions of SQL Express will use a maximum of 1GB of Memory * SQL Express 2005 has a maximum database file size of 4gb * SQL Express 2008 R2 and later versions have a maximum database file size of 10gb

Customers with more than 9 users, or a high SQL resource need, should conside purchasing a full version of SQL Server.

Terminal Server vs Client/Server installations

There are a couple of differences to note when installing GlasPacLX on a Terminal server versus a Client/Server installation.


When installing GlasPacLX on a terminal server, always make sure to launch a Command Prompt first, and enter the following command:

change user /install

Failure to run this command before installing an application will keep the installer from registering DLLs for all users. Non-Administrative users will get "DLL not registered" errors when attempting to run GlasPacLX when it has not been installed correctly. Once GlasPacLX and all its supporting applications have been completely installed, run the following command to return the server to standard execution mode:

change user /execute


The client and server computers in this configuration must have usernames and passwords that match. The server needs to have user accounts created on it that are the same as those used on the client computers. So, if a user logs on to a client computer as FrontDesk1 with a password of MyGlass01, then the server needs to have a user created on it that matches. Once these users have been created on the server, then the clients will be able to access the GTS share.

Active Directory Domains

Some customers may have had a technician install Windows Active Directory in their network environment. Active directory stores all user and computer acounts and password in a central secured location. If the customer has Active Directory, make sure to create the Attachments user account inside of Active Directory. Do not create the Attachments user as a local user account on the Server.

Have more questions? Submit a request


Powered by Zendesk