It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

PST Processor is unable to connect to the AOnePolFileAccess webservice

  • Type: Knowledgebase
  • Date changed: 3 years ago
Solution #00007636

Scope:ArchiveOne Enterprise, all versions



You are running the PST Processor but it is not processing any policies. If you view the PST Processor on the client machine from the system tray icon, its current status reports it is awaiting a valid connection. Looking the PST Processor logging, you see:

16 13:31:38 CheckExchangeServer got server name 'FailedToReadFeeServer'
16 13:31:38 BestConnection called with BaseUNC='\\FailedToReadFeeServer\Add-ins\' FileAccessURL='' UserAndDomain='PSTProc'
16 13:31:38 ChooseBestConnection picking the best connection available
16 13:31:38 ChooseBestConnection skipping as no authentication required for 'Direct file access'
16 13:31:38 ChooseBestConnection about to try 'Web service using security token'
16 13:31:38 TestConnectionWeb using URL:
16 13:31:38 SyncConnectionAlternative:Configured to use URL:
16 13:31:38 SyncConnectionAlternative:Call to GetVersion
16 13:31:38 SyncConnectionAlternative:Call to GetVersion FAILED, Response 'FailedServiceCallForDirectories' from call
16 13:31:38 TestConnectionWeb call to GetVersion FAILED, call returned response 9:'FailedServiceCallForDirectories' status 0, exception:Response 'FailedServiceCallForDirectories' from call
16 13:31:38 ChooseBestConnection found failure when trying 'Web service using security token'
16 13:31:38 ChooseBestConnection FAILED to find any usable connection for sync (not a security problem)
16 13:31:38 WebOnlyEstablishConnection ABORTING as can't find best connection


The PST Processor is unable to connect to the AOnePolFileAccess webservice successfully. This is required for PST processing functionality.


To diagnose why the AOnePolFileAccess website is unavailable:

1. Check the URL is correct.

2. The URL for the AOnePolFileAccess website may be an internal or external hostname, but must be resolvable internally on the network.If the URL is correct, copy the URL into a web browser and you will be able to see any authentication prompts, page not found, or SSL certificate errors. The URL must be accessible without user intervention.

3. If you have a proxy server, you should confirm that you are bypassing any proxy authentication requests.
4. HTTP 403: Forbidden errors imply you are trying to access a website that requires SSL without using HTTPS. If SSL is configured in IIS Manager for this website and you have a valid SSL certificate, then you should specify HTTPS on the URL. If you do not have a valid SSL certificate for this address, then you should remove the requirement for SSL from the website in IIS Manager and ensure the System Configuration Wizard Search URL setting is not set to use SSL.


Link to This Page: