I cant get the folder sync to work at all.

Everything is set up correctly but when I go to add a sync folder it says:
This path is invalid. Please use a path that starts with 'C:\Inetpub\vhosts\Intranet\Portals\0\'

Okay so that is not going to work as I need to sync with other folders on the server. On another installation I dont get the above error but the sync folder remains empty. I see in the schedule that no files have been indexed (even though there are 5 in there). I placed in the sync folder path C:\docs\generaldocs and gave NETWORK SERVICE full permissions to the folder.

How can I get this to work? The documentation is poor at best.

Thanks,

First: you need host access to specify a path which lies outside the portal root. Or (as host) you need to allow administrators to do this (Main Options).

Second the failed sync: DMX will look at what changes took place since the last time it ran. If it somehow oevrlooked them or failed at the beginning then it will keep overlooking them. There is a script under Admin > Run Scripts that allows you to jumpstart the sync folders ("Synchronize all SyncFolders in Portal"). Try running that.

Peter

Great, I see now that in using host it works when I use the kickstart script.
I have mapped network drives. Can i reference these also? I have had no issues now, so long as I use C:\... I need to get to I:\... I have assigned NETWORk SERVICE access but get the error:

Failed folder sync. Message: Could not find a part of the path 'I:\Templates on Caseview\Old Templates - Copy\'., Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileSystemEnumerableIterator`1.CommonInit() at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler) at System.IO.DirectoryInfo.InternalGetDirectories(String searchPattern, SearchOption searchOption) at System.IO.DirectoryInfo.GetDirectories() at Bring2mind.DNN.Modules.DMX.Services.SyncFolders.SyncFolderSynchronizer.?(String A_0, Int32 A_1) at Bring2mind.DNN.Modules.DMX.Services.SyncFolders.SyncFolderSynchronizer.Run(String SourceFolder, Int32 CollectionId, Boolean Recurse) at Bring2mind.DNN.Modules.DMX.Services.SyncFolders.SyncFolders.RunCode(PortalSettings& PortalSettings, HttpResponse& output, NameValueCollection parameters)

AFAIK it works with anything the .net framework has access to. The most important thing is that the worker process identity (usually NETWORK SERVICE) has access. The problem is most likely related to the fact that the server's NETWORK SERVICE is a local machine account and not recognized on the remote server.

PS Note that Sync Folders *dont' scale*. I.e. you can do this kind of thing but don't expect to be able to sync many Gbs of data. The caveat is that the process kicks in every X minutes and if the sync lasts for longer than that, the process is less and less useful. Obviously syncing over a network takes longer than local so it also influences this.

Peter