User cannot connect to the IMAP service if the PortChange tool was used to change ports

Versions / Builds Affected

20141117 (and potentially any other version)

Status

Resolved

TT / JIRAID

2942

How to Identify

A user tries to connect to GFI Archiver via IMAP, but the connection fails. ..\IMAP\DebugLogs\Adapter.log reads: 2015-01-22,13:55:13,047,1,"#000005FC","#00000028","info ","Adapter",">> Logon JohnDoe" 2015-01-22,13:55:13,047,1,"#000005FC","#00000028","info ","Adapter","--Logon using Username: JohnDoe" 2015-01-22,13:55:17,134,1,"#000005FC","#00000028","error ","Adapter","error:Failed to Login: No connection could be made because the target machine actively refused it 127.0.0.1:8017" It indicates that the IMAP service tries to connect to the Core service via the default port of 8017. The Core service is up and running. The .NET remoting ports were changed using the PortChange tool and Core is NOT running on 8017, but another port. Therefore IMAP cannot connect to it. The issue is, that the PortChange tool does not change all necessary files as it should when changing ports.

Workaround / Fix Details

20141117 1. Use the PortChange tool to change ports back to the default ones. 2. Apply patch: http://ftp.gfisoftware.com/patches/ARC2015/20141117/ARC2015_PATCH_20150219_2942.zip 2. Use PortChange tool again to change ports as desired if needed ----- Fixed in GFI Archiver 2015 SR1 build 20150218

Required Actions

1. Use the PortChange tool to change ports back to the default ones 2. Upgrade to GFI Archiver 2015 SR1 build 20150218 or newer 3. Use the PortChange tool to change ports as desired