Issues with ldap_add via LDAP Interface on WS 2008 R2 from WGM for mounts

Question

Important Setup Information:
Active Directory domain on Windows Server 2008 R2
Extended AD Schema to include apple-* attributes
Mac OS X Snow Leopard Server 10.6.2 bound to Active Directory
Connected to Active Directory Forest in Workgroup Manager with Domain Admin / Schema Admin credentials.
The Issue:
When attempting to configure a Home path using an SMB URL using the following attributes:
Mac OS X Server/Share Point URL:
smb://gio-storage-01.giodivine.com/Users
Path to Home Folder:
user 01
Full Path:
/Network/Servers/gio-storage-01.giodivine.com/Users/user01
I receive the following error:
*Not authorized.*
This action failed because you are not authorized to perform the operation.
I checked the console, and found the following (completely useless) error:
Got unexpected error of type eDSPermissionError (-14120) on line 574 of /SourceCache/WorkgroupManager/WorkgroupManager -361.2.1/Plugins/UserAccounts/UserVolumesPluginView.mm
I enabled diagnostic logging of the LDAP Interface on the Active Directory server and acquired the following error attributed to the "permissions" issue that Workgroup Manager emits:
Internal event: Function ldap_add entered
Internal Event: The LDAP server returned an error.
Additional Data
Error value:
00000057: LdapErr: DSID-0C090C30, comment: Error in attribute conversion operation, data 0, v1db0
So; it would appear that there is some issue with the Active Directory schema extensions, or that the UserVolumesPluginView module is not referencing the schema correctly. My expectation would be that an apple-mount object be created to describe the mount point in /Network/Servers and that the unixHomeDirectory attribute on the User object would be set to the newly created map point.
The latter occurs, i.e. the unixHomeDirectory attribute is set to:
/Network/Servers/gio-storage-01.giodivine.com/Users/user01
The map point is never created in Active Directory, however. It did create a new container in AD at the root, i.e. cn=Mac OS X,dc=giodivine,dc=com, but nothing is ever created there.
I have attempted to completely remove all of the extended schema changes, re-compare an OD master against the AD PDC, recreate the schema changes LDF, and re-apply the changes to no avail.
Any information as to how I can find out exactly what call to ldap_add is being made so that I can somehow track down the faulty schema extension attribute would be helpful. Are there ways to enable verbose diagnostic logging of Workgroup Manager and it's accompanying modules?
Thanks in advance!
Deavon M. McCaffery
<Edited by Host>

Answer 1

Hi Scot,
Sometimes a third party backup application will change the default VSS provider adding VSS writers which causes Windows Server Backup using an incorrect component in doing backup, that's why I suggest to delete it for a test. Anyway you can reinstall it
after testing.
And as you said a high-load CPU could also be the cause of the issue so you may need to first rule hardware effective out.
If issue still exists, please try the steps below as well:
1. Please check DCOM Server Process Launcher service is started.
2. If not, try to change RPC service to run as SYSTEM account. To do this please modify the following key:
Note: Backup the key before edit incase it cause any issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\RpcSs\
Find "ObjectName" and change the value to LocalSystem.
Reboot to see if DCOM back to work and if Windows Server Backup starts working. If not, please provide the result if there is any new error occurs.
If DCOM still not work, please compare the content of the following key with a working server:
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE
Edit if there is any difference and make sure you created a backup of the key before editing. 
If you have any feedback on our support, please send to [email protected]