Description

On a new install of the attunity connect daemon (client), we are
getting the following error (popup) when Attunity Connect Daemon (IRPCD) Windows SERVICE attempts to start:
The attunity connect daemon (IRPCD) service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service



The IRPCD log shows
(1) Attunity Connect Daemon (IRPCD) - Started at 29-Aug-05 15:47:46
(1) [C026] Failed to bind server to port 2551
[C026] Permission denied.
(1) [C007] Server initialization failed
(0) Closing log file at MON AUG 29 15:47:46 2005

What exactly are we failing to have permissions to?

Forgot to mention - we have ensured that the service account (system) has read/write/execute permissions to the Attuntiy directory and specified debug directories..


Solution

Have you checked to see if there is a firewall issue where port 2551 is blocked or if the port is in use by another process. The command netstat -a -b -n from the DOS prompt will give you a list of all port connections active. Look through the list for port 2551 being owner by another process.

You can move the daemon to start on a different port other then the default port 2551. You would use the IRPCD command from the attunity command window on the windows server. The -l option allows you to put in the machine name or ip address followed by a :port number

The example commands to do this are:
C:\Program Files\Attunity\Server\tmp>irpcd -s unregister start
The IRPCD service was deleted successfully

C:\Program Files\Attunity\Server\tmp>irpcd -s register -lspear-xp:2553 start
The IRPCD service was registered successfully

C:\Program Files\Attunity\Server\tmp>irpcd -s start
Daemon was started

C:\Program Files\Attunity\Server\tmp>