ArchiveOne For Files, all versions
If the ArchiveOne For Files services are unable to communicate on the required ports you may see a number of different symptoms. For instance, an unarchive policy fails to unarchive any files although the policy finds files matching the specified criteria or, when you attempt to open an archived file, the retrieval fails.
When examining the log_AOneBrokerService.txt file, in the ArchiveOne Broker Service startup tracing, you will see the line:
Initialising DataTransferImpl host...
Host initialisation failed. Exception : HTTP could not register URL http://+:7777/. Another application has already registered this URL with HTTP.SYS.
Another process is already using the port required by the ArchiveOne Broker Service for communication with the File Agent services.
The log file will identify the process name (in the above case HTTP.SYS) which is using the required port. If it is not clear from the log file which process has seized the port:
- Open a command prompt and run the command: netstat -ano
- Find the port number which the log file has identified as unavailable and the corresponding PID number using this port.
- Open Task Manager and select the 'Processes' tab.
- Under the 'View' menu, click 'Select Columns'.
- Tick 'PID (Process Identifier)' and click 'OK'.
- The PID column will now be visible and you can look up the name against the PID number provided by the netstat command.
Once you have identified the process responsible:
- Stop or disable the process/service which is using the required port.
- Open the Microsoft Services console (services.msc) and restart the 'ArchiveOne Broker Service'. The required port should now be available for the ArchiveOne Broker service to seize.
- Start the other process again.
Depending on the process which has seized the required port, you may be able to configure the software to use another specified port. This will avoid the chance of the port being unavailable to the ArchiveOne Broker service in the future.
Link To This Page: