Installation-related FAQs

Each installation file has a corresponding XML file which provides a security checksum that is validated against the install.

If the checksum doesn’t match, the install will not continue until it has been resolved.

In addition, every installation has been digitally signed by SYSPRO from EXEs to MSIs. Therefore, the digital signature is broken as soon as a file is edited and re-saved in any way.

If you want to enable output logging to the debug viewer you need to add a registry entry TraceOn, with a value of true.

You can then retrieve debug logs of what the SYSPRO Installer application is doing, as well as the service, provided they are on the same machine.

If SYSPRO Deployment Server errors are generated, the log file is created in the %temp% folder.

SYSPRO Software is published to the Azure Content Delivery Network (CDN). Downloading software is optimized to obtain software based on point-of-presence (POP).

Benefits include:

• Software is always current.

• Local downloads result in faster speed and higher performance.

• Large file support.

• Available 24/7.

  If one region should fail for any reason, the software is then sourced from another POP.

• No more DVD installs.

Upgrading is when you move from one version of SYSPRO software to another (e.g. from SYSPRO 7 Update 1 to SYSPRO 8).

Updating is when you move from one release of the current software to a later release (e.g. from SYSPRO 8 2018 R2 to SYSPRO 8 2019 R1)

When you upgrade from SYSPRO 7 Update 1 to SYSPRO 8 (using the SYSPRO Installer app) the process is as follows:

1. SYSPRO 7 Update 1 installation files are removed.

   There may be some files left behind after this process because of new files added through ports, or third party developer files.

2. The SYSPRO 8 installation process checks whether there are any remaining legacy files.

   If any are found, they are moved to a newly-created archived folder (Archived_SYSPRO7Files).

3. The following folders are added to the archived folder in the SYSPRO 8 install location:

   • \Programs
   • \Screens
   • \Base\Bin
   • \Base\UI

The following SQL Server users must exist prior to using the SYSPRO Installer application, with the appropriate permissions enabled:

Possible scenarios for requiring a reset of your SQL Server credentials include:

• You can't log into SYSPRO because of a SQL Server credential error (e.g. password expired).
• You are in a support environment and have been supplied with a database that you cannot access, possibly due to not having the SQL password.

From SYSPRO 8, you can reset your SQL Server credentials:

1. Open IMPACT.INI (located in the WORK folder) using an editor application such as Notepad.

2. Change the SQLADM entry to SQLADM=[reset] or change the SQLSTD entry to SQLSTD=[reset]

   Changing either entry enables you to reset the password for both accounts. The word 'reset' is not case sensitive.

3. Save the file and log into SYSPRO.

   You will be prompted to enter a new SQL Server user name and password for both the administrative and standard logins.

Yes, you can.

The only difference is during your SQL Configuration when running the SYSPRO Installer app for the first time.

At the SQL Server Name field, ensure that you enter the full instance name (e.g. INSTANCENAME\SQLEXPRESS).

You can check this entry if you run SQL Server Management Studio and view the instance to which you are logging in.

You can speed up the installation process by copying previously downloaded installation files to a folder that the SYSPRO Installer app can use.

Copy the latest files C:\SYSPRO Deployment\SYSPRO Release\* from a computer which has already downloaded the installs, to the target computer folder with the same name.

SYSPRO ERP needs access to the SYSPRO Deployment Service and the SYSPRO Deployment Service needs access to the internet 24/7 and Microsoft SQL Server.

You don't have to install the deployment service on the SYSPRO application server, but it must be on a machine that is visible to all the SYSPRO machines involved.

Ideally, the machine should have permanent internet access to communicate with Azure.

The SYSPRO 8 runtime uses Micro Focus installation software and is therefore listed as Micro Focus COBOL Server within the Program and Features function of your Windows Control Panel application.

SYSPRO 8 was developed to be installed exclusively on 64-bit client and server operating systems. In addition, the SYSPRO 8 installation application is also only available to run on a 64-bit operating system.

However, there is limited support for SYSPRO 8 Clients running 32-bit operating systems. The 32-bit client can only be installed using the export function in the SYSPRO 8 installation application.

The SYSPRO 8 and 32-bit Client Operating Systems guide covers the steps to be taken to install the SYSPRO 8 Client component on a 32-bit operating system (available from the Install Guides page of the Resources section).

When you request a SYSPRO 8 license, you will receive an email containing the XML license file attachment.

Both of these codes are contained in the license file.

If the SYSPRO Installer app detects that the machine on which it is setup is renamed, it will attempt to self-heal with an automatic reconfiguration process, in order to update the deployment details.

SYSPRO 8 must be installed on a 64-bit server (all the SYSPRO services are now 64-bit).

Ensure that you add or set the COBSW variable to -F on your client and server machine where the SYSPRO runtime is deployed.

A maximum of 127 hotfixes can be installed per release (Microsoft limitation). Therefore, ensure that you only install hotfixes that you require. Alternatively, install a consolidated hotfix.

A hotfix KB article contains information about the software included in the hotfix, as well as a summary of the problems addressed.

You can access these by selecting the More button against the hotfix on the Hotfix selection screen of the SYSPRO Installer application.

Within the Hotfix Selection screen of the SYSPRO Installer, you can search for a specific hotfix by any of the following:

• Enter the full KB number (e.g. KB8000006)
• Enter the last digits (e.g. 06) into the search box
• Enter any full text related to the hotfix (e.g. Ledger Query)

This will show Mandatory Hotfixes and Optional Hotfixes.

If there is no Mandatory Hotfix/Optional/Customer-specific Hotfix available for your customer code, but the HOTFIXES button is still displayed on the deployment group home page, then the application has detected that there are additional Optional Hotfixes available for you to view and optionally select.

Yes, in the unlikely event that a deployed hotfix contains a flaw that may result in more damage than it was trying to repair, you can uninstall the hotfix.

The system is able to revert affected programs to a state prior to the deployment of the faulty hotfix.

Although the hotfix notification button is visible to all users, it is only enabled for operators belonging to a group with system administrator privileges.

This button shows the Mandatory or Optional Hotfixes recorded against your customer code, which have not yet been installed.

If you have multiple application servers for the same site, you have to run the SYSPRO Installer on each machine that has the Application Server installed. This is because hotfixes must be applied directly to the Application Server.

When using the SYSPRO Installer application, a consolidated hotfix is clearly indicated with the following phrase appended to its name: ** Consolidated **.

The synopsis will explain the hotfixes that have been included and summarizes how this roll-up and install works.

One of the best things about the hotfix technology in SYSPRO 8 is that if, for any reason, you wish to uninstall a hotfix, the software is restored back to what it was prior to the hotfix being installed.

The same happens if you were to uninstall a consolidated hotfix. The software will revert to just the previously installed hotfixes.

When the SYSPRO Deployment Service is installed, ports 30250 (Endpoint port) and 3702 (Endpoint discovery) are enabled on the Windows firewall.

If you have additional firewall software, you need to open these ports within the software to enable the SYSPRO Installer app to function.

For sites with proxy servers, the following URLs must be open for the SYSPRO Deployment Service to retrieve software and communicate with the SYSPRO Azure service:

• SYSPRO 8 downloads (from Microsoft Azure CDN): https://syspro8install.azureedge.net/*
• Azure service calls: https://sysprodeploymentazlive.azurewebsites.net/*
• InfoZone : https://izauthservicedev.syspro.com/*

The SYSPRO Deployment Service provides support to be discoverable at runtime. Therefore, for WCF Discovery to work correctly, all NICs (Network Interface Controller) should only have one IP address.

Ports that must be open:

• UDP discovery: Port 3702

• Default listening endpoint: Port 30250

  This is the port to which the service responds.

  You can always manually enter the endpoint if discovery is not enabled.

You have one of two options:

• Run the SYSPRO Installer app on each client machine to install the SYSPRO client.

• Use the Export function of the app.

  Once you have completed your export, all items exported are downloaded from Azure to the SYSPRO Deployment Shared folder and a text file is created which you can then use for rolling out to your clients.

When you select to install a language pack, the language file is deployed to the same folder where the SYSPRO.EXE resides (\Base).

You can install as many of the available language packs as you require.