Problem: Since the release of GIS Portal Toolkit 9.3, the Harvesting Tool or Harvesting Service is not working as expected
Since the release of GIS Portal Toolkit (GPT) 9.3, there have been various cases of the Harvesting Service and/or Harvesting Tool not working as expected.
The problems may vary and this article does not provide a definite solution for all problems. Instead, it describes the first thing a user should try when there is an issue with a Harvesting Service and/or Harvesting Tool that has been recently deployed.
During installation of the Harvesting Tool, some .dll and .ocx files may not have registered correctly.
Solution or Workaround
Although it may not always solve the problem, a common solution is to unregister and re-register the Harvesting .dll and .ocx files.
Navigate to the bin folder of the Harvesting Tool installation directory. The default location is C:\Program Files\ESRI\Portal\Harvesting_Tool\bin.
Double-click the UnRegister.cmd to run a command that unregisters all the Harvesting Tool .dlls.
Delete all the Tomcat log files. These are usually located in the <Tomcat Installation Directory>\logs folder, by default. Deleting the log files clears out files that are created when the GIS Portal Toolkit is being used and can be referenced later if further debugging is needed.
Navigate to the same bin folder that was used in step 2, and double-click on the Register.cmd to run it.
Attempt the Harvesting Service/Harvesting Tool action again.
If the initial problem persists, examine the newly created Tomcat log files (in the folder from step 4) for further clues.