Interpreting WGM errors

Question

Level 1

95 points

Interpreting WGM errors

I have to do manual search mappings to get WGM to play with my LDAP server.

Now and then I get an error like

"Error of type eDSInvalidAttributeType (-14131) on line 592 of /SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/Plugins/UserAccounts/Use rVolumesPluginView.mm"

Which, in my experience, means SOMETHING isn't mapped properly. Often it's pretty easy to figure out what mapping is missing but at the moment I'm stumped. I'd like to find out more about this error but I can't find the file (is it a file?) to which the error refers.

Can somebody please clear me up on this? When WGM refers to "/SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/Plugins/UserAccounts/Us erVolumesPluginView.mm" what is it talking about?

Thanks,

Posted on Jun 15, 2009 12:02 PM

Reply

Answer 1

Best reply

harry-pmsi

Level 3

535 points

Jun 15, 2009 4:42 PM in response to Sean Murphy3

Take a look at http://www.manpagez.com/man/8/DirectoryService/

Many times I find google is your friend on these types of errors. Put the error as given in the google search box and take a look at what the history is.

HTH,
Harry

Reply

Answer 2

Sean Murphy3 Author

Level 1

95 points

Jun 16, 2009 5:46 AM in response to harry-pmsi

thanks... in my experience Google has not been my friend. I always seem to get the rare ones! Hence why I'm looking to dig a bit deeper.

also, thanks for the man page... maybe I'm missing it but it doesn't seem to explain what "/SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/Plugins/UserAccounts/Us erVolumesPluginView.mm" refers to?

Reply

Answer 3

Jun 16, 2009 8:27 AM in response to Sean Murphy3

Hi Sean,
Based on your needing to set the search policy, additionally receiving this error msg it appears you have an directory field entry that isn't conforming to the expected type. For instance bad character in a data field or wrong character such as a negative sign or dollar sign, or even a reference that is no longer valid.

In the diagnostics section of the link I referred to, setup debug for the OD and look at the logs produced when OD gives you the error. You will get a lot of entries so don't leave it on too long. In terminal:
$ sudo killall -USR1 DirectoryService
the option: USR2 will result inlogging automatically turned off after 5
minutes.

The logs might indicate what value was being looked at to cause the error.

If you don't have "a lot" of users (a relative term) export out the users and groups and see what values the OD is keeping for them.

HTH,
Harry

Reply

Answer 4

Jun 16, 2009 8:44 AM in response to harry-pmsi

Can somebody please clear me up on this? When WGM refers to "/SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/Plugins/UserAccounts/Us erVolumesPluginView.mm" what is it talking about?

This is simply a message indicating that file (and line) of the WGM code which reported the problem. Obviously it would have been better if it told you what the invalid bit of data was... I'd follow Harry's advice and try the logging.

Reply

Answer 5

Sean Murphy3 Author

Level 1

95 points

Jun 16, 2009 11:05 AM in response to Brian Nesse

hmmm. Seems I've reached my quota of 'mark as helpfuls.' Thank you as well, Brian!

I'll check out the debugging stuff... now I don't want to appear hung up on this mystery path thing, but if it really is a file, would it not turn up using the find command line utility? Even if it was inside a package or whatever?

Or does it not exist as a file on the filesystem? If not, where? I'm just curious at this point. Generally if someone goes to the trouble of saying what line of code went wrong in an error message, it means you can go look at it. Who knows?

Thanks again for the suggestions! I'll follow up if there is anything interesting to follow up on.

Reply

Answer 6

Sean Murphy3 Author

Level 1

95 points

Jun 16, 2009 11:39 AM in response to Sean Murphy3

Here is the output. Started the sample just before triggering the error in WGM. Stopped sampling before clicking the OK button on the error.

6/16/09 2:31:37 PM DirectoryService[28] Client: servermgrd, PID: 50, API: dsCloseDirService(), Server Used : Result: 0, Duration: 219.42 usec
6/16/09 2:31:46 PM DirectoryService[28] Client: Workgroup Manage, PID: 8134, API: dsGetRecordList(), LDAPv3 Used : Result: 0, Duration: 4373.69 usec
6/16/09 2:31:46 PM DirectoryService[28] Client PID: 8134, has 12 open references.
6/16/09 2:31:46 PM DirectoryService[28] Client: Workgroup Manage, PID: 8134, API: dsOpenRecord(), LDAPv3 Used : Result: 0, Duration: 4325.30 usec
6/16/09 2:31:46 PM DirectoryService[28] Client: Workgroup Manage, PID: 8134, API: dsGetRecordAttributeInfo(), LDAPv3 Used : Result: -14131, Duration: 85.17 usec
6/16/09 2:31:46 PM DirectoryService[28] Client PID: 8134, has 11 open references.
6/16/09 2:31:46 PM DirectoryService[28] Ref table dealloc callback, API Call: dsCloseRecord(), PlugIn Used: LDAPv3, Result: 0, Duration: 14.49 usec
6/16/09 2:31:46 PM DirectoryService[28] Client: Workgroup Manage, PID: 8134, API: dsCloseRecord(), LDAPv3 Used : Result: 0, Duration: 4.68 usec

Aside from these things about "12 open references" and "11 open references" (not sure what that means) I don't think it's telling me anything new. The -14131 status is the same.

Guess I'll try to spot the bad values in dscl unless someone has a better way of finding mis-mapped attributes?

Thanks, both!

Reply

Answer 7

Jun 16, 2009 2:51 PM in response to Sean Murphy3

I have to do manual search mappings to get WGM to play with my LDAP server.

It hasn't been asked yet. Are you using AD and OD or just OD? What version of Server are you running?

This:

"/SourceCache/WorkgroupManager/WorkgroupManager-319.2.2/Plugins/UserAccounts/Use rVolumesPluginView.mm"

is a string from inside the WGM binary that refers to the Apple build -probably from their svn- of the application and the internal plugins that are used when the app is compiled. I'd ask if you had the latest version of Admin Tools installed, but the error message already confirms that you are. The error, eDSInvalidAttributeType, indicates that you have an entry in your database that WGM doesn't understand, is corrupt, or that you don't have permission to modify.

Reply

Answer 8

Jun 16, 2009 3:05 PM in response to Sean Murphy3

Sean,
The code your OD call is using is here:
http://developer.apple.com/documentation/Networking/Conceptual/OpenDirectory/workingWithRecords/workingWithRecords.html#//appleref/doc/uid/TP40000917-CH6-51654

Note the sequence involved. It appears your log snippet was a little short on the call that preceded GetRecInfo. What is happening before this call?

The part I keyed on was:

If dsOpenRecord returns successfully, the GetRecInfo routine calls >dsDataNodeAllocateString to allocate a data node (attrType) containing the >constant kDS1AttrPrimaryGroupID. It then calls dsGetRecordAttributeInfo using >attrType to specify which attribute to get information for.

HTH,
Harry

Reply

Answer 9

Jun 16, 2009 4:03 PM in response to Sean Murphy3

The specific reference to the error code, -14131, is on page 173 of this manual:

http://developer.apple.com/documentation/networking/Reference/OpenDirectory_Ref/Open_DirectoryRef.pdf

You have an attribute type that OD doesn't understand -therefore invalid.

Reply

Answer 10

Sean Murphy3 Author

Level 1

95 points

Jun 17, 2009 10:53 AM in response to Mabel O'Farrell

"It hasn't been asked yet. Are you using AD and OD or just OD? What version of Server are you running?"

OD on updated 10.5 and eDirectory 8.7 (i think)

"...is a string from inside the WGM binary that refers to the Apple build -probably from their svn- of the application and the internal plugins that are used when the app is compiled"

Mabel, thank you! That makes sense, now. And "Open Directory Reference" pdf? Bless you! That's going in my back pocket...

Reply

Answer 11

Sean Murphy3 Author

Level 1

95 points

Jun 17, 2009 11:06 AM in response to harry-pmsi

Harry, you've been a great help.

I've made some changes on the eDirectory side. While I'm still getting errors, they are different now (for instance dsOpenRecord no longer returns 0.)

In any case, it's not a blocking issue (as in, clients behave as expected) and school just let out so I can take my time, work through the dev documentation you and Mabel provided and suss this out.

Thanks again!

Reply