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. This behavior started already last year, and even now that everything works again. Does anyone have ideas or similar experiences? Martin Scholl 18910 New Hampshire Ave Brinklow, MD 20862 Phone: 301-924-5537 Cell: 301-613-9572 [email protected] www.HIPAAsuite.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
