DB Walker - Object does not have Directory ID

[rvenzor]

I get the following message when running DB Walker:

1394:(error) the location object with the object ID={F5B635BD-95B5-4872-AA14-99617BE6062D} does not have a directory ID associated with it.

This means there is no object in the directory representing this object which can cause problems with networking features. Please contact TAC.

Any clues on what this means? My unity is working fine. The only thing i see is that it gives me a:

"Unable to resolve failorver partner name to FQDN."

when i look up a user, and click on the account ID.

[lindborg]

Well, the error means what it says - if there's no DirectoryID value on a location object then that object didn't get created in the directory properly (i.e. it's not in AD under the \Unity folder) - this will only cause you a problem in this case if you have multiple Unity servers on the same network and you want to address messages between the systems - the location objects (the guy that's missing in the directory here) are what transmit information about Unity servers around the network.

So the location object is in SQL but for whatever reason it didn't get created in AD like it should have. this could be a sign of problems with your DC or a permissions issue or the like.

[rvenzor]

Is there a tool where I can locate the SQL orphaned object?

What permissions need to be on the Unity Container/folder? I ran permissions wizard, and no issues came up. I am having trouble with trying to import one user to unity from AD.

Your help is greatly appreciated.

[lindborg]

The location table in the UnityDB database contains all the locations (very likely only a single entry for you) - the ObjectId kicked out by dbWalker is the unqiue identifier for the row in that table if there are more than one entry.

You can view the database using CUDLE (you'll find this as "Database Explorer" in the Tools Depot on your desktop) or using SQL Query Builder or Enterprise manager.

That said, not sure what you want to do with it (please, please, please don't edit or delete this row - you will swiftly destroy your Unity install if you're not careful) - there's not much you will see here that's useful. If the object doesn't synch into the directory it has nothing to do with the SQL entry in the table, it will have to do with rights on the container the object is being created in against the directory facing account.