Quantcast
Channel: All Business PCs, Workstations and Point of Sale Systems posts
Viewing all articles
Browse latest Browse all 36020

Re: hpdm 4.7 ftps error upload of test package to repository failed

$
0
0

Chen or HP,

 

Did this issue ever get resolved? We are experiencing the same issue except our case is with our Child Repositories.

 

When we run the test from the Master Repository it eventually errors out with the "Insufficient privilege on repository {repository name} with protocol FTPS". In IIS we see the service account connect to the FTP site and on the Child Repository the /Repository/Files/ToDeploy/test-{random numbers} directory gets created but the text.txt file does not copy or image over.

 

The Console log on the HPDM server notes these messages:

2016-04-29 16:01:39 [Thread-47] DEBUG toryPanel$TestRepositoryThread - testUpload: Failure capturing test-1461963496702 from C:\ProgramData\Application Data\HPDM_Temp\Repository\Files\ToDeploy to /Repository/Files/ToDeploy.

 

2016-04-29 16:01:39 [Thread-47] INFO  FileOpt              - Cannot delete file: C:\ProgramData\Application Data\HPDM_Temp\Repository\Files\ToDeploy\test-1461963496702\test.txt

2016-04-29 16:01:39 [Thread-47] INFO  FileOpt              - Cannot delete file: C:\ProgramData\Application Data\HPDM_Temp\Repository\Files\ToDeploy\test-1461963496702

2016-04-29 16:01:40 [Thread-47] DEBUG toryPanel$TestRepositoryThread - testUpload: Successfully captured test-1461963700109 from C:\ProgramData\Application Data\HPDM_Temp\Repository\Files\ToDeploy to /Repository/Files/ToDeploy.

 

Even when we added "All Users" to the FTP Authorization Rules we still ended up in the same situation. This issue does not happen for our Master Repository test. We followed all the same steps when setting up the Child Repositories minus the need to install the Master Repository install on the child respository servers.

 


Viewing all articles
Browse latest Browse all 36020

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>