I'm attempting to use the KB article to allow Shadow Folders to be created on another machine.
I created the customASPNET id, and can add the shadow folder entry via the Admin Tool (also at version 2.0.1). However, after the new entry is created, the admin tool opens a dialog that states "Please wait while refreshing shadow folder". Another dialog pops up with problems - see attachment.
Any ideas?
Thanks,
Don
Addendum: The same problem now happens if the shadow folder is located on the same computer running vault...
Vault 2.0.1 and shadow folders using UNC names
Moderator: SourceGear
-
- Posts: 114
- Joined: Fri Mar 05, 2004 11:18 am
- Location: Raleigh, NC
Vault 2.0.1 and shadow folders using UNC names
- Attachments
-
- vault_shadowfolder_problem.jpg (82.81 KiB) Viewed 5063 times
-
- Posts: 114
- Joined: Fri Mar 05, 2004 11:18 am
- Location: Raleigh, NC
I got around this problem. I originally followed the instructions in the MS article about creating a CustomASPNET account and then modifying the local policies and permissions to limit the scope of the new ID.
However, changing the identity in web.config to a domain ID that already has substantial authority solved this problem.
Don
However, changing the identity in web.config to a domain ID that already has substantial authority solved this problem.
Don