The error 80011 is misleading and seems to come up for a lot of cases where it shouldn't. The userID that Bill is using is valid, and as he indicates, he can telnet in with this user. The problem is that UniObjects returns the 80011 error if the user does not have admin privileges. Add the user to the administrator group and the UO login succeeds, proving that the 80011 error is incorrect.
So the fundamental question is, what is the minimum set of permissions required for a UniObjects connection to succeed? One would hope it's not full admin privs but some subset, or ideally the required permissions should be tunable via some config settings. Bill mentioned mv.NET and DesignBais. The different errors from these products arise because there is different client code wrapped around UO. mv.NET reports the error that was generated, hence the 80011. DesignBais connects to the server and expects a response from UO wrapped in XML. Since this isn't coming back, it's reported as an XML error and not a comms error. An enhancement request has been filed for better reporting in such cases. Thanks and Regards, Tony Gravagno Nebula R&D (Providing support for Bill on both his mv.NET and DesignBais products, but we are at a loss on this UO matter.) Colin wrote: >This is what I have for the error code: >80011 UVE_BAD_LOGINNAME The login name provided is incorrect >I've had some weird things happen with the permissions on the "privilege" file >in the account when using OLEDB and ODBC. From: Bill Haskett >I can telnet into the server using any user name who's a member of the >"UniData" group. However, using UniObjects, I cannot access a UniData >account unless the user supplied is an administrator. ____________________________________________________________________________________ Never Miss an Email Stay connected with Yahoo! Mail on your mobile. Get started! http://mobile.yahoo.com/services?promote=mail ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
