Sage 200 On Premise
Set up Form Launching
If you want to open Accounts forms from within CRM, you must make sure that the Sage Task
Launcher is installed and configured correctly and that your CRM users have access to the
Accounts database and the relevant Accounts forms.
To launch Accounts forms from CRM:
n
The Accounts Client must be installed on the same PC that you are using to access CRM.
n
The Sage Task Launcher must be installed on the client PC.
n
The Task Launcher must be running on the same port that is specified in the
Administration
> System > ERP Form Launch Settings
. This is
8088
by default.
You can check the port number the Task Launcher is using, from the system tray.
For more information about changing the port for the Task Launcher, or about using the Task
Launcher on a Terminal/ Citrix server, see
Changing the port number for the Form Launcher
n
The Task Launcher Listener application must be running:
Start > All Programs > Sage
Task Launcher > Sage Task Launcher Listener
.
n
Users must have access the Accounts Forms in CRM. This is specified in the
Administration > Users > User Details
.
n
Users must have access to the Accounts database and Accounts forms in Sage 200 System
Administration. See
Set up user accounts on page 162 .
Change the port number for the Form Launcher
By default, the Sage 200 CRM Task Launcher Listener listens on port
8088
. If this port is already in use, then you must change the port in the Task Launcher Listener and in Sage 200 CRM.
To change the port in the Sage 200 Task Launcher Listener
To change the port in the Sage 200 Task Launcher, you must edit a value in the registry.
178
10 | Install and set up Sage 200 CRM
1. To open the Registry Editor, choose
Start > Run
.
2. Enter
regedit
in the
Open
box.
3. Click
OK
. The Registry Editor window appears.
4. Select
HKEY_LOCAL_MACHINE > SOFTWARE > Sage > TaskLauncher
.
5. In the right pane, right-click on
Port
.
6. Select
Modify
from the pop- up menu. The
Edit String
window appears.
7. Enter the new port value in the
Value Data
box.
Note:
This port must not be blocked by a firewall.
8. Stop the Task Launcher Listener. Right-click on the system tray icon and select
Stop
Listener
from the pop-up menu.
9. To apply your changes, select
Start Listener
from the pop-up menu.
Next you must change the Sage 200 CRM settings to use the same port number.
To change the port in Sage 200 CRM
To change the port number used in the Task Launcher URL generated by Sage 200 CRM:
1. Open Sage 200 CRM.
2. Select
Administration > System > ERP Form Launch Settings
. The
Sage 200
Accounts Form Launch Settings
page appears.
3. Enter the new
Port Number
.
Note:
This port must not be blocked by a firewall.
4. To confirm the new port number, click
Save
.
Using the Form Launcher with Terminal Services, Remote Desktop
Services and Citrix
Running form launcher for multiple users on Terminal Services/Remote Desktop Services or Citrix requires additional configuration. You must: n
Set the
Task Launcher
service to run automatically.
n
Set the Task Launcher to run in
Multi-user
mode on the client desktop.
If you are deploying Form Launcher with Remote Desktop Services on Windows 2012 or 2012 R2 you must also enable the IIS Features '.NET 3.5' and '.NET Extensibility 3.5'. The Task Launcher service will not start correctly without these features.
For further information on how to configure Sage 200 with Citrix and Terminal Services, see
Installing Sage 200 using Citrix or Terminal Services on page 32
.
179
Sage 200 On Premise
To set the Task Launcher Service to run automatically
1. From the Start menu, select
Control Panel > Administrative Tools > Services
.
2. Right-click the
Sage Task Launcher Service
.
3. Select
Properties
from the pop-up menu.
4. Select
Automatic
from the
Startup type
drop-down list.
5. Click
Start
, to start the service.
6. To confirm the changes, click
OK
.
To set the Task Launcher to multi user mode
In a Terminal Services, Remote Desktop Services and Citrix environment, you must set the Sage
Task Launcher to run in multi user mode. To do this, you must add a startup parameter to the Sage
Task Launcher shortcut.
You can set up the Sage Task Launcher for individual users or for all users.
To set the Sage Task Launcher for individual users
1. On the client machine, open the
Sage Task Launcher Listener
from the user's Startup folder. The location of this folder can differ between operating systems. From the 'run' dialog
(Start > Run) the following command will take you to the current logged in user's startup directory:
shell:startup
An example of this folder might be:
C:\Users\desktop.admin\AppData\Roaming\Microsoft\Windows\Start
Menu\Programs\Startup
.
2. Right-click the Sage Task Launcher Listener shortcut.
3. Select
Properties
from the pop-up menu.
4. Add
/mode:M
to the end of the
Target
string.
5. To confirm the changes, click
OK
.
To set the Sage Task Launcher startup mode for all users
Follow the instructions above using the
Startup
folder in the
All Users
group.
The location of this folder can differ between operating systems. To find it, from the 'run' dialog (Start
> Run), enter the following command:
shell:common startup
This will ensurethat each user has the Task Launcher running in the correct mode within their session.
Note:
This application typically uses about 20MB of memory.
180
10 | Install and set up Sage 200 CRM
Troubleshooting
The first time you launch an Accounts form from CRM, the form may take some time to open.
If you cannot launch Accounts forms from CRM, check the following:
Does the user have access to the relevant Accounts database?
Does the user have access in Accounts to the form you want to launch?
Does the user have access in CRM to the form you want to launch ?
Is there is an error on the webpage?
If so, check the error details in your browser.
Does the port number match the port number specified in the ERP Form Launch settings?
Are there other applications running on the port specified for the Task Launcher? If this port is already in use, change the port for the Task Launcher.
Is the Task Launcher running?
To check this, stop and re-start the Task Launcher, by right-clicking the icon in the system tray.
Do you have pop-up blocker enabled in your web brower?
181
Sage 200 On Premise
Are you using Internet Explorer? Is
Protected Mode
turned on?
If so, add the CRM website to the list of trusted sites for each CRM user.
The CRM website is in the Local Intranet zone. This has the protected mode enabled when
UAC is turned on. When you attempt to launch forms, the CRM website posts a request to the local machine. This is blocked by Internet Explorer. Adding the CRM web server to the list of trusted sites will allow CRM to launch forms on the user's session, as trusted sites do not have protected mode enabled by default.
To do this: a. Open Internet Explorer and select
Tools > Internet Options
.
b. Select the
Security
tab.
c. Select
Trusted Sites
.
d. Click
Sites
.
e. Enter the URL for CRM in to the box.
For example, if your CRM URL is
https://myserver/CRM/eware.dll
, enter the URL as
https://myserver
.
f. Click
Add
and the URL will now appear in the trusted websites list.
Note:
You may be prompted to have a secure URL; clear the
Require server verification (https:) for all sites in this zone
check box, if you are not using https for your CRM site.
g. Click
Close
on the
Trusted Sites
window.
h. Click
OK
to apply these changes.
If you opened the Internet options from within Internet Explorer then you should restart
Internet Explorer to ensure the changes are applied.
If you run Internet Explorer again and navigate to the CRM website, the status at the bottom right of Internet Explorer is
Trusted Sites: Protected Mode Off
. You can now launch Sage
200 forms from CRM.
For more information see Ask Sage Article 28206 .
182
11
Upgrading Sage 200 CRM
Use this chapter if you are upgrading from Sage 200 CRM 7.2 d hotfix 1 integrated with Sage 200 2013 R2.
To upgrade from earlier versions of Sage 200, please see the Upgrading CRM Guide.
IMPORTANT
You
must
upgrade your existing installation of Sage 200 in a test environment before upgrading live data.
This section is designed to be read prior to starting the upgrade process.
Testing an upgrade prior to going live is critical to minimise any impact on your customer. By following the steps in this section you will have clear documented steps and an audit of events should any problems occur either during the test upgrade or at 'go live' with the customer.
Do not dispose of your test environment until the live upgrade has been performed and the end user is satisfied that the upgrade has completed successfully.
Should problems be encountered during the test stage or at go live, technical support will assist in identifying the root cause provided that evidence of the pre-checks are available as outlined in this document. If it is evident that the pre-checks have not been carried out, we would endeavour to assist, however this would be on a chargeable basis.
If you are unsure about anything outlined in this section, or during the upgrade process please contact
Sage Technical Support. It is better to address issues as they arise in the test environment than afterwards when an issue may impact the end user.
Key facts for upgrading Sage 200 CRM:
1. You must upgrades all parts of Sage 200 at the same time. If you upgrade Sage 200, you must also upgrade Sage 200 CRM and vice versa.
183
Sage 200 On Premise
2. Your existing installation of Sage 200 CRM
must
be v7.2d hotfix 1.
You can check the version of Sage 200 CRM that you are using from the CRM log on window.
3. Your existing installation of Sage 200 must be Sage 200 2013 R2.
To upgrade from earlier versions of Sage 200, please see the Upgrading CRM Guide.
184
