Article ID: 3579, created on Jan 24, 2008, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation 5.4
  • Operations Automation 5.3
  • Operations Automation 5.2
  • Operations Automation 5.1
  • Operations Automation 5.0
  • Operations Automation 2.6

Symptoms


If there is no Exchange installed in the AD then all Windows File Manager tasks fail in POA 2.6.5 with the error message 'The specified directory service attribute or value does not exist'. Additionally, existing customers cannot login to their Windows File Manager.

Cause


Since POA 2.6.5 the WinFileManager service uses AD attributes 'extensionAttribute7' and 'extensionAttribute8'. Actually, these attributes are created by Exchange during installation. So, if the Exchange is not installed in the AD domain then required attributes are absent and Windows File Manager provisioning tasks fail in POA.
 

Resolution


1. Login on AD Domain Controller as Domain Administrator.

2. The following sub-steps are needed in case when there are more than one Domain Controller in AD:

  2.1 Run adsiedit.msc.

  2.2 Expand the 'Schema' folder.

  2.3 Open properties of the 'CN=Schema,CN=Configuration,DC=...' folder.

  2.4 Find the attribute with name 'fSMORoleOwner'. The value of this property contains name of AD Schema Master. For example, in the value 'CN=NTDS Settings,CN=AD01,CN=Servers,CN=...' the AD01 Domain Controller is the Shema Master.

3. Login to Schema Master server (in case of single Domain Controller it is the Schema Master.)

4. Upload the attached 'extensionAttributes7-8.ldf' file to Schema Master (unzip the archive).

5. Run the following command (replace in the command the string 'DC=hosting,DC=local' to the distinguished name of Windows Domain): ldifde -i -f extensionAttributes7-8.ldf -v -c "<SchemaContainerDN>" "CN=Schema,CN=Configuration,DC=hosting,DC=local"

6. Restart MPS engine using instruction in the KB article #1851.

It may happen that Windows File Manager tasks still fail after applying the instruction above, in this case reboot MPS host, and restart the tasks again.

Attachments

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 0c262e25de71ebe1ac525040493d11d0 80fcf07a72a3fc2739554dff85ce8fe7 c2898cda1192c88ccc616ade5f670bd6 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 a8cdca46e4357a6e38fded820770e272 25ba5a02b9d70d4212e34c355e881968 c27596ac4fff6cb4c8ec8891dae57001 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF