Prerequisites

Central Upload Agent can be a huge benefit for many migrations. Setup and operation of the Central Upload Agent is different than the typical Migration Agent and requires specific steps to be functional.
This article can help when troubleshooting the Central Upload Agent (CUA).
For set up of CUA please check KB:

Note

Most usable source for troubleshooting CUA are logs.
Logs for the Central Upload Agent are stored in the temp location of the user that is being used to run it.
E.g.: If the CUA is running under account svc_cua, path to CUA logs would be:
C:\Users\svc_cua\AppData\Local\Temp\QUADROtech\MigrationAgent.log

 
Steps
1) Check if the CUA is running

In Task Manager look for: FlightDeck Migration Agent (32)
CUA is installed by default in C:\Program Files (x86)\QUADROtech\Central Upload Agent.
If CAU Agent is not running you can start it manually running MigrationAgent.exe

2) Check if the CUA service is running

In Services look for: Central Upload Agent and note account under which is running (will be needed for later steps)
CUA is installed by default in C:\Program Files (x86)\QUADROtech\Central Upload Agent.
If CAU Agent is not running you can start it manually running MigrationAgent.exe

2) Check if the CUA service is running

In Services look for: Central Upload Agent and note account under which is running (will be needed for later steps)
If either from above steps is not fulfilled, please check your installation or try start it manually.

3) Check if the account used for the CUA service can see the directories on the specified Central Server(s)

Log in as the CUA service account try to reach \\server\share or try to map the network drive \\server\share with the CUA login.
If the access is denied, adjust the rights for the account or use an account with sufficient rights to run the CUA service.

4) In case Forced Upload/Migration is used, check if the CUA service account has access to “Administrative share” on user workstation
Login under the CUA service account try to reach \\UserWorkstation\c$ or try to map a network drive \\UserWorkstation\c$ with CUA login where PST file is located.
 
5) Check if the CUA service account has Read/Write rights to  Uploads directory on the PST FlightDeck server (network view – UNC path)

Login under the CUA service account try to reach the upload directory via \\FDserver\Uploads$ or try to map a network drive \\FDserver\Uploads$ with CUA login. If connected,  attempt to create, modify, and delete a file in that location. Sharing properties can be changed in Uploads>Properties>Advanced Sharing. The CUA service account should have “Full Control” on this directory.

 
6) Check if the CUA service account has Read/Write rights to the CentralUploadTemp directory on the PST FlightDeck server (network view – UNC path)

Login under the CUA service account try to reach the upload directory via \\FDserver\Uploads$\CentralUploadTemp or try to map a network drive \\FDserver\Uploads$\CentralUploadTemp with the CUA login and try to create file there.
Sharing properties can be changed in CentralUploadTemp>Properties>Advanced Sharing. The CUA service account should have “Full Control” on this directory.

 
7) Check if the CUA service account has Read/Write permissions to the Uploads and CentralUploadTemp locations on the PST Flight Deck server (local path)

Login under the CUA service account and try to create a file in the Uploads and CentralUploadTemp directories.
D:\FlightDeck\Uploads and D:\FlightDeck\Uploads\CentralUploadTemp (D drive is just example, should be replaced with drive used for your FD Uploads directory)
Security properties can be changed with an administrative account in Uploads>Properties>Security by adding access for the CUA service account (“Full Control”) to these directories.
8) Check if CUA is using local configuration
CUA should be configured to use local configuration not to download configuration from PST Flight Deck server as this is intended for Migration Agents on the workstation.
Please change the value in file Config.local.xml (it is located in the installation directory of CUA, e.g.: C:\Program Files (x86)\QUADROtech\PST FlightDeck Shared Scanner\Central Upload Agent). Look for variable ConfigVersion. This value must be higher as retrieved from FD server.
E.g.: In CUA logs D you get 151191566 and you config.local has 100000000.
If you change this value to 300000000 it will be higher configuration retrieved from PST Flight Deck Core server and therefore used by CUA.
 
Print Friendly, PDF & Email