Symeon: The UniRPC service starts, like most services, under the "local" system account. The checkbox "Allow service to interact with desktop" is checked (the install did this).
Thanks, Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Symeon Breen > Sent: Monday, February 05, 2007 2:22 AM > To: [email protected] > Subject: Re: [U2] UD: UniObjects permissions > > I am not sure how this works on windows, but on *nix the > uniobjects user passed in is not as important as the user > and mask that the unirpcd deamon is running as. I have had > to edit the startud shell script to set the permissions > correctly so that anything created by uniobjects is > accesible by other processes. > > Rgds > Symeon. > > > > On 05/02/07, Tony G <[EMAIL PROTECTED]> wrote: > > > > 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 [email protected] To unsubscribe please visit http://listserver.u2ug.org/
