Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
open deploy
z6634
Hi,
I have been trying to deploy the files (with in the same server) in to the Teamsite using file-list. Quite often we are getting a error message:"Remote-ERROR: remote-dir-not-ok".
Our environment is: 5.0.1, Windows 2000. Open Deploy is working for only one directory and for other directories we are getting this error message
Could any one throw light on this issue to resolve.
Thx,
Find more posts tagged with
Comments
Adam Stoller
Let's start with the simple questions first and see where to go from there.
Is that TeamSite 5.0.1 or OpenDeploy 5.0.1 or both?
Is the problem consistent? I.e. does it always happen with specific directories and not to others? or does it vary a lot from time to time which directories (if any) display this behavior?
Is this Windows->Windows or Windows->Unix or Unix->Windows? (You said Windows 2000 - so I know at least one side of the deployment is Windows based, just want to solidify the understanding of the environment)
--fish
(Interwoven Senior Technical Consultant)
script.JPG
z6634
Hi,
Information is given below:
It is Teamsite 5.0.1 & Open Deploy 5.0.1.
Problem is consistent. It happens with some directories only.
It allows me to deploy only to:"Y:\default\main\Bestfoods\UBF\UBF-Dev\WORKAREA\development\templatedata\UBF\articles\data"
It doesn't allow any other work area. I am invoking this deployment thro' command line tool from a perl script.
It is WIndows to windows(with in the same server from Drive E to Drive Y -Teamsite )
Thx,
Adam Stoller
First, I would strongly encourage you to upgrade to OpenDeploy 5.5.1 SP2 - it is (IMO) a vastly superior version of the product.
Secondly, I would verify that the allowedDirectory settings on your Receiver permit you to deploy to those directories and that the allowedDirectory already exist on the receiving side.
Thirdly, if secondly didn't help resolve the problem - I'd suggest zip'ing up the Receciver's odrcvr.xml, the specific deployment configuration file, and the log files from both the sender and receiver, and then posting them as an attachment to a responding forum post.
--fish
(Interwoven Senior Technical Consultant)