How to configure and troubleshoot the Form Launcher for use with Sage 200 and Sage 200 CRM.

Configuration

NOTE: If you are using Sage 200 Professional 2011 or below, you will be prompted to authenticate with a user name and password when attempting to launch a form for the first time.

The Task Launcher should run on the port specified in CRM Administration> System> ERP Form Launch Settings. If the Task Launcher won’t start on this port on any client, it would be advisable to amend the port in CRM to a port which is available for use on all Sage 200 client PCs.

Using Task Launcher on Terminal Services

NOTE: Please Note: As of the 2017 R2 release of Sage 200 CRM, Form Launching on RDS/TS environments are no longer supported.

When using Terminal Services, the Task Launcher needs to be configured to run in multi-mode. To enable Task Launcher to run in multi-mode you must add '/mode:m' to the end of the target in the properties for the listener.

This must be amended for the Task Launcher program and for each of the user startup shortcuts. These can be located in:

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Sage Task Launcher

C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Once amended the full target path should show "C:\Sage200Client\Bin\Sage.TaskLauncher.Listener.exe" /mode:M.

Once these changes have been made, end all instances of the listener via task manager and stop the task launcher service on the Terminal server.

Start the service, via services.msc and then start each instance of the listener on the client sessions, either by launching the Sage.TaskLauncher.Listener.exe or restarting the client session.

NOTE: To use the Task Launcher in multi-mode on a Terminal Server, IIS must be present on the server. In particular, the ASP feature in IIS must be installed. If this isn’t the case you may see the error “Please check the despatcher is running” when trying to run the Task Launcher. If any changes are made, the Task Launcher should be exited from the task bar and restarted.

Troubleshooting

If you are unable to launch forms from Sage 200 CRM, you should check the following:

• Does your user login have access to the relevant area in Sage 200?
• Is there an ‘error on page’ at the bottom left of the screen in Internet Explorer? If so, review the error within here for further information.
• Does the issue affect all machines? If not, it could be permission related. You should troubleshoot further with other CRM users, Sage 200 users and Windows users.
• In Internet Explorer settings, ensure the CRM server has been added as a trusted site.  If using Remote Desktop Services, you may also need to the RDS server that people use CRM from as well. Refer to the video at the top of this article for further guidance if necessary.
• Within Internet Explorer Tools > Options > Security tab > select Custom Level and scroll down to the ‘Misc’ area. Set ‘access data sources across domains’ to be enabled.
• Is the Task Launcher Listener running? If so, right-click on the icon in the system tray and select Exit, then restart it from the Start menu.
• Hover over the Task Launcher icon in the system tray – does the port number it is currently running on match the port in CRM Administration> System> ERP Form Launch Settings? If not, update this within Sage 200 CRM as necessary.
  
  

  NOTE: If the port numbers are not the same, this may be due to another application is running on the same port. Please take this into consideration before making any changes. It should also be noted that the setting in Sage 200 CRM is global, so should only be changed to a port which is available on all client machines using Task Launcher.

• If the Task Launcher keeps starting on the wrong port, you can check it has inherited the correct setting via the Registry. Open the Registry and select HKEY_CURRENT_USER >SOFTWARE > Sage > TaskLauncher. If this is showing the correct port, it would indicate the port is in use by another application and this should be investigated further.
• Unless using Terminal Services, the Windows service Sage Task Launcher Service should be disabled.
• Does the CRM Company name contain an ampersand, e.g Smith & Co, try a company which does not contain an ampersand in the name or try removing the ampersand, restart the Task Launcher and try launching the form again.
  
  

  NOTE: This is a Known Issue that is fixed in Sage 200 CRM 7.2.

• Does the Sage 200 Company (the Company name as shown in Sage 200 System Administration> Companies) contain an ampersand? If so, try removing this, restarting the Task Launcher and try launching the form again.

[BCB:19:UK - Sales message :ECB]