Tryingn to setup content replication between our core server and file servers at remote locations. When we start replication it starts to run and then fails with an ID of 1716 'the system cannot find the file specified'. The preffered server is already setup and both the read and write tests succeed. The share and the permissions are correct on the preferred server to allow content to be replicated. I'm not sure what we are missing at this point. Core is running 9.0 SP3. I did some searches on the site and found this same error message but nothing relating to content replication.
Does the system setup as the replicator have the LANDesk agent installed? Also, make sure the replicator is NOT the core. More info on setting up the replicator is here: http://community.landesk.com/support/docs/DOC-20779
1 of 1 people found this helpful
I didn't realize that the core server couldn't be the replicator. It would be nice if the core wasn't even a choice as a replicator if it won't work but now that I know that is the case I will work around it. I have setup another server to be the replicator and the package is replicating out fine now. Thanks for the help.
I've used robocopy in the past but with over 100 file servers to replicate to and 3 different package sources and30 GB worth of data, Robocopy gets to be too much to manage! It will be nice to have a single point of administration for package replication.
Hmmm, we replicate to over 30 package servers with >350 GBs with a single robocopy script from one server and it works much easier than the current LDMS replicator. However, if it works for you....use it. There are also numerous ERs for replicator. If they fix a couple of items I may take another look.
We use content replication too (9.0 SP2), but it fail so much so we have to use robocopy...
(unknow error OR path too long for landesk, but ok for robocopy OR replicator stopped reporting... etc.), crazy things
LANDesk should work on that tool, it must be reliable
I too had the same problem with Content Replication failing all the time on SP2. The main issue was that it kept thinking the path was too long. I ended up replacing the lddwnld.dll file with the one from SP3 and that took care of the problem. Since then, I have upgraded to SP3 and have ~420 Preferred Servers that I am replicating too with pretty good success.
Ok I will try replacing the dll !
I found it at 3 paths on core :
I replace all three ?
And I have to replace the one on each preferred server ?
I have to rebuild advanced agent too ?
[edit : I have changed the dll on core server + preferred server and launch content replication : failed too]