I didn't run into that exact issue, but ran into something similar in some respects. We run UV on linux, but rely on our Active Directory domain for authentication. Earlier this year we ran into an issue where new users were unable to log in at some point late in the day, but all the currently logged in users were fine. One of the domain controllers had error messages regarding failed authentication for each failed login attempt. Running "dcdiag" on that domain controller revealed an issue with one of the AD databases (sorry, can't remember which one). I was able to immediately resolve the problem by removing the problem DC's IP address from /etc/krb5.conf on the UV server and recycling samba and winbind. Our Windows admin located MS documentation on fixing the DC issue and was able to clear it up.
I recommend you run dcdiag on all the domain controllers and see if any report problems. -John -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Martin Scholl Sent: Tuesday, June 08, 2010 6:41 AM To: 'U2 Users List' Subject: [U2] [Unidata-Windows] Can login, but not execute any command Upfront: The problem was solved by re-installing UniData My client had UniData 7.2.3 on Windows within his domain. He rebooted all servers within his company over the weekend. Yesterday UniData suddenly didn't work anymore. I could log in to the database, but any command, whether Write, Select or catalogued subroutine would stop dead in its track. There was no error message, no indication what could have gone wrong. UniObjects had no time-out, the application hung for hours. I telneted into the database and many users got the unknown user error, I just found one user that allowed me to log in. I ran a few commands and that worked. My hunch is that a Windows update changed NT-Authentication and UniData didn't like it. Poking through the logs, I see in the Windows security log two entries for every UniData login, one success and one failure: The first a success audit: A trusted logon process has registered with the Local Security Authority. This logon process will be trusted to submit logon requests. Logon Process Name: \udapi_server.exe Then a failure audit: The logon to account: HHC-Unidata by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0 from workstation: HORIZONSERV4 failed. The error code was: 3221225572 The error code means: 32212255720 The specified user does not exist. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
