Colin: Thanks for the logging info. By the way, I created a basic Windows user with "users" privileges. I created a "UniData" group. Groups don't have, I think, any inherent privileges. They're a category that users can be associated with that can be given privileges for directories and files.
Thus, a user named "DesignBais" would be created with Windows "users" privileges and I would then make them a member of the "UniData" group. In the file system, I'd change the security to allow only "administrators" and "UniData" users access to the UniData directories. This works fine in telnet, but not in UniObjects. I'm validating all users, associations, and permissions. I'll try this whole thing again. :-( Thanks, Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Monday, February 05, 2007 6:35 AM > To: u2-users@listserver.u2ug.org > Subject: RE: [U2] UD: UniObjects permissions > > Sorry, I meant to say that the 80011 wasn't always very helpful. > > Unfortunately, Bill didn't say which permissions he gave the UniData > group; however, since he can telnet in I'm assuming they are enough. > This is why I brought up the "privilege" file (it should exist in the > account you are logging into). I've seen VSG hammer the OS level > permissions on the file, I'd check it first. > > Another thing to look at is if a UOLOGIN program is globally > catalogued. > It can prevent login which returns this error. > > There are a couple of log files that may also be helpful. > Check the *log > files in the unidata\bin directory. > > A debug log can also be created: > 1. Create a text file called "serverdebug" in the U2 home directory > using any text editor. > 2. Add a line with up to 3 parameters. server and debug are mandatory. > > Parameter Description > 1. Server - U2 server process: > udcs = UniData > uvcs = UniVerse > 2. Debug - Debug level. > 0 = no debug > 1 = log connection information > 9 = log all messages > 3. [Log] - Path and name of log file. > (Optional) If this value does not exist, U2 uses > /tmp/XXapiserver_####.log on UNIX systems, or > C:\temp\XXapiserver_####.log on Windows NT or Windows 2000 systems, > where "####" is the U2 api_server process ID, "XX" is uv or ud, > depending on whether the server is running UniVerse or UniData. > If used, _<pid> will be appended to the file name. > > eg. udcs 1 > > Hth > Colin Alfke > Calgary Canada > > >-----Original Message----- > >From: Tony G > > > >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. > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
