Troubleshooting

Common troubleshooting scenarios and performance guidelines.

Multiple HTTPS bindings on an IIS website with Integration Server

For the Integration Server installed and running with IIS, the WCF services hosted in IIS are configured by default to have only one base address. If your project requires multiple HTTPS bindings, the following error message from the Integration Server indicates the limitation:

"This collection already contains an address with scheme http. There can be at most one address per scheme in this collection".

To enable multiple site bindings and avoid the error, enter the following configuration in the Integration Server configuration file:

<system.serviceModel>

  <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />

</system.serviceModel>

Emails with large attachments fail to send

When an agent sends an email with large attachments, the Agent Portal may display one of the following errors:

• Email size (<size> KB) exceeds the allowed limit (<limit> KB). The email, including the attachments, exceeds the Max. outbound email size configured in the email settings of the agent applications of the service, in the Management Portal. Increase the limit of the service, or reduce the size of the attachments.
• Unexpected value: ModelState The request exceeds the value of maxRequestLength in the Web.config file of the Integration Server. The Integration Server trace shows the message ModelState is invalid! ContentLength=<size in bytes>. Increase the value of maxRequestLength in the node httpRuntime of the Web.config file of the Integration Server, taking into account that the attachments are encoded in Base64, which increases their size by about 40%.

RabbitMQ issues

If you have issues with events in the Agent Portal or issues with the default port 5600, reinstall the RabbitMQ component of Integration Server and uAgent Web as follows:

1. Open a Windows command prompt as administrator.
2. Uninstall the RabbitMQ Windows service as follows:

set ERLANG_HOME=C:\Program Files\Altitude\Altitude uCI 8\Altitude Integration Server\ESFService\RabbitMQ\ERLang

set RABBITMQ_SERVICENAME="Altitude uAgent Web RabbitMQ 8"

cd "C:\Program Files\Altitude\Altitude uCI 8\Altitude Integration Server\ESFService\RabbitMQ\sbin"

rabbitmq-service remove

3. Install the RabbitMQ Windows service with a port different than 5600 as follows:

set ERLANG_HOME=C:\Program Files\Altitude\Altitude uCI 8\Altitude Integration Server\ESFService\RabbitMQ\ERLang

set RABBITMQ_BASE=C:\ProgramData\Altitude\Altitude uCI 8\Altitude uAgent Web\RabbitMQ

set RABBITMQ_SERVICENAME="Altitude uAgent Web RabbitMQ 8"

{{REM obtain short path below running cmd "for %I in (.) do echo %~sI" in the rabbitmq.conf file folder}}

set RABBITMQ_CONFIG_FILE=C:\PROGRA~3\Altitude\ALTITU~1\ALTITU~1\RabbitMQ\rabbitmq.conf

REM obtain node name below with "<service name>@<COMPUTERNAME env var>"; remove all spaces; replace any existing '#' chars with '-'

set RABBITMQ_NODENAME=AltitudeuAgentWebRabbitMQ8@mymachine.domain.com

set RABBITMQ_DIST_PORT=25600 //20000 + rabbitmq port (=5600 for first installation)

REM obtain file path below, like in RABBITMQ_CONFIG_FILE

set RABBITMQ_ENABLED_PLUGINS_FILE=C:\PROGRA~3\Altitude\ALTITU~1\ALTITU~1\RabbitMQ\enabled_plugins

cd C:\Program Files\Altitude\Altitude uCI 8\Altitude Integration Server\ESFService\RabbitMQ\sbin

rabbitmq-service install

4. Locate the RabbitMQ configuration file rabbitmq.conf.

5. Ensure the configuration file only has the following lines:

listeners.tcp.1 = 127.0.0.1:5600

auth_mechanisms.1 = EXTERNAL

6. Start the uAgent Web RabbitMQ Windows service.
7. Test the Agent Portal, and check if it runs as expected.