Issue

This issue arises from a bug in previous versions of IMan. The design interface would allow duplicate mappings to exist in a connector, this causes an error in the latest version.

In some occasions it may not be possible to delete the field, in that case you will need to remove the field from the job configuration.

Solution

Follow these steps to resolve the mapping issue, these steps must be completed prior to the upgrade.

• Prior to deleting the field any logic should be noted as it may need to be reinstated after the upgrade process. Open the designer and record each field and its contents in all transforms.
• Open the integration file in a text editor, which can be found in the C:\IMan\JobConf folder. Ensure you take a backup of this file.
• In the text editor, navigate to the transform noted in the error. Shown as red in the screenshot.
• Go to the record id noted in the error. Shown in green in the screenshot.
• Delete one of the fields reporting the error. These are shown as orange in the screenshot. In the example here we would remove REFERENCE_1 as this has resulted from a duplicate mapping.
• The upgrade error log may have a number of entries for duplicate fields, repeat steps 3-5 for each transform noted in the log.
• Upgrade the integration and then re-create/re-map the field and reinstate/check any logic for the field in the subsequent transforms.

Symptoms

You may be experiencing issues when working within IMan:

• Pressing the Refresh button to refresh the Preview grid does not display any results or errors.
• When an integration is scheduled immediately i.e. frequency ‘Now’, the integration runs, the audit report email is received but no results are displayed in the right hand pain.
• Pressing the Check button for the VBScript syntax check does not display success or error.
• Other UI functions are not working, and neither are they generating an error.

Probable Cause – Multiple Http Bindings to the Same Site

An issue exists with .net 3.5 where multiple http hosts are bound to a single website preventing webservices hosted in IIS from running correctly. Where there are multiple hosts each webservice request fails logging an error to the server’s Application Event Log.

Viewing the IIS setup shows the two Http bindings.

Resolution

IMan must be running in a site that has a single binding for the http protocol. Where a website has two http bindings either:

• Remove one of the http bindings from the website and restart the website or;
• Create a new website with a single http binding and install IMan to that site.

Unlikely Cause – WCF Http Activation Not Installed

WCF Http Activation allows the webservice providing the audit report data to function.

Clicking on the Javascript error icon at the bottom of browser may display an error similar to:

Resolution

Install WCF Http Activation through Server Manager/Features.

Symptom

Integrations can be run, data is processed, but the audit report is not received via email.

Debug

To ascertain the problem, run an integration from the scheduler tab. This will allow you to view the audit report and any errors in the right hand half of the screen.

At the bottom of the audit report, following completion entry in the detail section of the audit report (green square), there will be an error indicating an issue with the sending of the audit report.

The error can be a little difficult to understand but the key is to find the section which records the actual error message (red square), where the example below has an authentication problem.

The same error is also logged to IManDebugerrors.txt.

WSAEWOULDBLOCK Error

This error occurs whenever IMan cannot make a connection with the SMTP server, and may occur in the following circumstances:

• A firewall at either the client or server side is blocking the connection.
• There is no server listening at the remote host:port to accept the connection.
• Some other software, such as an anti-virus or anti-spyware program is blocking the connection (see below).
• The server was too slow in accepting the connection. IMan has a 10 second connection timeout which cannot be changed, if the connection cannot be made within this time, an error will be raised.

SMTP Server/Exchange Server Requirements & Tips

This section will not discuss the step-by-step setup required for any particular email server/relay, but provide you with a list of tips and generic setup.

• IMan sends all mail via an SMTP host; the server defined in the SetupEmail Servers must accept inbound SMTP connections from the server/workstation on which IMan is installed.
• SMTP Authentication – We recommend that IMan authenticates with the SMTP server using a username and password. I.e. The Email Server specifies a username and password. Anonymous authentication is not just unsecure, but can be difficult to debug due to the sometimes confusing error messages.
• For simplicity the send-from address (as defined in the Email Group) should match the authenticating user id (as defined in the Email Servers). Attempting to send an email with a different from address to the authenticated user can be disallowed on some setups.
• Proxies – Unless the proxy is transparent IMan does not support connections to SMTP servers via a proxy.
  Antivirus

Some antivirus software actively blocks outgoing SMTP connections where you may receive a WSAEWOULDBLOCK error (see above).

Allow the SMTP Mail to be sent from the IMan processing engine (inetpubwwwrootIManbinIntEngine.exe).

Sage 300 Date Formatting

When setting an Date type optional field in Sage300 you may receive the following error:

Accpac API Error 1000 – Invalid input. Failed to convert string ‘<datevalue>’ to an internal Date representation.

To work around this issue you need to have the date formatted in yyyyMMdd format, achieved using the Format function:

Format(%DateField, “yyyyMMdd”)

An update will be made to IMan in a coming version to resolve this issue.

Symptom

When using Internet Explorer 11 it is not possible to drag transforms onto the design area from the palette, neither is it possible to select or open existing transforms.

Resolution

1. Either download and install the latest version of IMan or;

2. Patch your current version of IMan with the following steps:

• Download, save and extract the patch to your local computer.
• Ensure the extracted file is not blocked by right clicking the file, properties and checking there is no Unblock button at the bottom of the properties page.
• On the server with IMan installed, stop all the Realisable Services and reset the IMan IIS application pool.
• Move from the c:\inetpub\wwwroot\IMan\bin\Syncfusion.Shared.Web.dll to a backup folder not anywhere in the %systemdrive%\inetpub\wwwroot
• Move the extracted file from the first step to c:\inetpub\wwwroot\IMan\bin
• Restart the services, login to IMan & test.