This is not done by users and is usually done by System Administrators or the users IT support. With companies being increasingly security conscious, users machine are being increasingly locked down, we can advise but do very little when there are installation issues in these cases.
Access Supply Chain support do not generally install Client software but will assist when the following install guide and troubleshooting notes have been followed and the issues still exist.
This document describes how to install the Supply Chain client software and is valid for version ASC7.2.2 onwards.
As a starting point whoever is doing the install has to have a minimum of Local Administrative Rights on the device
CRITICAL NOTE: that this procedure must only be run from the server for installation on a client machine. Do not install on the application server itself.
1. Ensure that the machine is logged in as an administrative user.
2. Navigate to the Server where Supply Chain is installed using Windows Explorer.
3. Navigate from here to ASC7.2.2\CLSetup. (The default installation path on the Server is C:\Program Files (x86)\Access Applications\ASC7.2.2).
Within the CLSetup folder on the server run setup.exe as administrator. If there are any pre-requisite items, the install will prompt for these to be installed.
1. Click Install to continue with the installation and work through the screens as prompted.
2. When prompted, Enter the CD key for this install is: '001-7220-VETTEL-0212'.
3. At the next screen enter the database server (this is the SQL server) and enter the ‘sa’ password.
4. If a connection cannot be made to the SQL server at this point, then please refer to the troubleshooting section at the end of this article.
5. When prompted, enter the server name. This is not the name of a physical server but is the name of the ‘service’ that Supply Chain will run. The ASC Server Name is usually ASC72.
6. For most users select a Typical install (although some users will have a complete install to give them access to utilities like the Form Designer and Supply Chain Administrator for example):
7. When prompted enter the IP address or server name in the CCI Configuration Utility. This will be the server that Supply Chain is installed on (this is not always the same as the SQL server).
8. Click OK to continue once entered.
This part of the install process is now complete.
At this point navigate within Windows Explorer to C:\Program Files (x86)\Access Applications\ASC7.2.2 on the local client machine and check that this folder has at least permission set for user 'Everyone'. This is necessary so that files can be updated correctly for full Supply Chain functionality.
1. Navigate to C:\Program Files (x86)\Access Applications\ASC7.2.2\Client Application on the local client machine and run CLUPDATE.EXE.
2. Select both ‘Form Definition Files’ and ‘Application Files’ when prompted within the Client Update screen. This will confirm when completed.
3. From the same location as previously run UpgradeClient.exe as administrator (from the right-click ‘Run As Administrator’ option). Follow the onscreen instructions, and click Finish when prompted.
4. From the same location again run RegisterSCFNET.bat as administrator.
5. Log in to Supply Chain using SupplyChain.exe (within the Client Application folder) or Supply Chain Client from the Programs menu. The Login Form will display; populate this as follows
• This is the name of the connection, eg. ABCLive. This will default to ‘Connection1’ but make sure to rename this to a more meaningful name.
• User Name: Use the sa login this time.
• Password: Enter the password for the sa login.
• Database: This is the name of the database being connected to, eg. ABC
• Make sure the ‘Change Connection Details’ box is ticked, so users have the extra parameters to populate:
• TCP Server: This is the name of the server that Supply Chain is installed on.
• TCP Port: This is 65112.
• Form Server: Users can normally set this to ‘localhost’.
• Form Server Port: This is 4444.
• Click Login to continue once all the details are populated.
6. Once logged in, click on the File menu at the top left-hand side of the screen:
7. Select Restore Window Layout from the Window Layout menu; then select Layout Manager – click on the Save icon to continue through the Layout Manager screen:
Users may see different modules listed in this screen depending on what needs to be updated on the client machine. If this box does not display, there are no layouts to update.
The next steps are to check that options and reports will run successfully on this machine.
1. Run a Manufacturing option. For example, click on the Stock option on the ribbon and then select the Item Master Definition.
2. This should display the Stock - Item Maintenance screen.
3. Confirm that stock items can be browsed by selecting Open from the ribbon on the new window, and then clicking on the magnifying glass next to the Part field.
4. Run a Ledger option. For example, click on the Debtors option on the ribbon and then select Customers.
5. This should display the Customer List.
6. Run a Crystal report. For example, click on the Stock option on the ribbon and then select Stock Reports.
7. From the menu presented select a report – the Part Master Audit is a good example – and click the Save icon (if a parameter screen is presented). This should display the report to the screen.
8. Finally, log the machine in as the user themselves (as opposed to the admin user) and log in to Supply Chain again, repeating steps 9 – 13.
Trouble-shooting
Problem: When installing an ASC client I’m unable to get past the Database Server screen in the installation program. I get an error message indicating a connection cannot be made to the SQL server or it is not found, despite entering the correct SQL server name and password. (Error 27502 – Could not connect to SQL Server….SQL Server does not exist or access denied.)
Cause: The network configuration on some sites can prevent validation of the SQL server, which is required for the installation to continue successfully.
Solution:
Navigate to the folder on the ASC Server where the client installation program is located (CLSETUP folder) and right click on Setup.exe and send to desktop.
Locate the Shortcut on the Computer that you are installing ASC, right click and select Properties
In the Target box add /VIS_SQLSERVER_CONNECTIONS_TO_VALIDATE=None to the end of setup.exe after a space and ok
Run the shortcut as Administrator and just skip the SQL Settings
After installation of the client check the “MadiSunSQL” Create the 32 ODBC data source, see section directly below
Problem: How to check/manually create the MadisunSQL ODBC data source.
Solution:
1. In Windows Explorer navigate to C:\Windows\SysWOW64\ODBCAD32.exe. Double click this to run the ODBC Data Source Administrator (32-bit).
2. Select the System DSN tab.
3. Within here there should be a MadisunSQL data source configured.
4. If this does not exist click the Add option on the right-hand side.
5. Select SQL Server (check which driver we recommend) and click Finish.
Users will now see the Create a New Data Source to the xxx screen.
1. Enter the name ‘MadisunSQL’ – it is essential that this is spelt correctly.
2. The description is free text, so enter a description here if required.
3. Select the SQL Server to connect to from the drop-down list.
4. Click Next to continue.
5. Select the second option on the next screen to use SQL Server authentication, and enter the sa username and password.
6. Click Next to continue.
7. Accept the defaults on this screen, making sure that there isn’t a default database defined.
8. Click Next to continue.
9. Accept the defaults on the screen, and then click Finish.
10. At this point, users can test the data source to make sure it connects successfully.
11. Click OK to complete setup.
Note: MadisunSQL MUST be 32 bit.
Problem: When I login to ASC, I get a warning message - Microsoft.NET framework. An unhandled exception occurred in your application, object reference not set to an instance of an object.
If I do a restore windows layout I get the same error message as previously.
Solution:
Navigate to the ASC7.2.2 folder (Installation Directory, usual path C:\Program Files (x86)\Access Applications)
Right click on the folder and select Properties
Go to the Security tab and make sure the user Everyone has Full control
Problem: The install has stopped after the install type has been selected.
Solution: Check the toolbar at the bottom of the screen – the next prompt sometimes does not flag to the front of the screen users are working on but will appear in the taskbar. Select this prompt in the toolbar to display it on screen and allow the user to continue.
Trying to run an ASC option on a Newly Installed Client machine I get the error message
The license database for Micro Focus Server has been moved from
its original location or removed and recreated. Delete the database, which is
mfasdb, and reinstall the license keys.
In this instance there is an environment variable that is set incorrectly. On a machine that works:
Click on Windows Key (Ctrl+Esc)
Type Environment until you can see Edit the System Environment Variable, open it
You will then see a system properties screen, select Environment Variables
You should then see a variable for mfasdb
You then need to copy this value into the same place for the machine that is having the issue
Problem: Error 1919 – Error configuring data source MadisunSQL.
Solution: Accept the error during the client install and then manually configure the MadisunSQL ODBC data source as described above.
Problem: Crystal reports will not run on a new client install.
Solution: Make sure the MadisunSQL ODBC data source is configured correctly; Crystal reports will not run on the client machine until this is set up.
Problem: Client install fails on the Crystal install pre-requisite
There are some C++redistributable components which Crystal requires to complete the install. To complete this the vcredist_x86.exe and setup.exe for Crystal runtime are required.
Please contact support to request these files.
Tabbing through a Sales order and the currency code is displaying the incorrect symbol.
There is a setting in the regional settings of windows 10 called administrative language setting and this needs to be set to ENG UK, change to this and reboot the machine.
If all of the above does not work please uninstall and reinstall paying particular attention to the installation guidance in this article.