Have you tried looking at the way your username is stored in windows. The easiest way I know to do this is run the "net user" command from windows, or "net user /domain" if it's a domain login. All of our network logins are in lower case, as is the same for most of our customers. We did have one customer that entered their logins in mixed case. Apparently, windows is case-insensitive when checking to see if the login is valid, but when it returns the login to Universe, it returns it in the original case that was entered, which for that customer was mixed. UV.LOGINS would not work as we had expected. Ultimately, checking "net user" showed that they were in mixed case. The way that I knew of to clean this up was to delete and recreate the login in windows, or possibly rename the user. Once the user is fixed in windows, give Universe a reboot to clear it's user cache and it should be fixed.
Good luck. -Mike -----Original Message----- From: ATLAS SA [mailto:[EMAIL PROTECTED] Sent: Sunday, August 26, 2007 9:59 PM To: [email protected] Subject: RE: [U2][UV] Up casing Login IDs {unclassified} Thanks Dave, I tried it out but, unfortunately, the problem is occurring before the UV LOGIN voc is invoked. And, to add insult to injury, it is only happening to my login ID, not to the login ID of anyone else who has access to the server. If their UV.LOGINS record is AUSER10, they can enter any case combination they like (AuSEr10) and UV passes AUSER10 to the UV.LOGINS file. I use any case combination of my user ID and UV passes asuer14 to the UV.LOGINS file. Somehow UV knows to upcase all telnet login IDs except mine. I suspect it may be because I installed something whilst logged onto the server as myself, rather than as administrator. However, I did install UV itself as administrator so it's not that. Possibly UVDK? However, I have installed UV & UVDK on dozens of servers (Unix and Windows) and have never had this occur before. Also, I would rather not maintain separately formatted records for myself throughout the DB. It would have further consequences in the management of my records on what is the main payroll database. Has anyone else encountered this problem before? Cheers, Andy ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
