RE: [U2][UV] Up casing Login IDs {unclassified}
Yea, I can make a connection just fine. But I would like to create a
connection pool so my web app always has a couple open connections to
work with.
Jonathan Lienhoop
Marvin Johnson & Associates, Inc.
1.800.457.5255
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hester
Sent: Monday, August 27, 2007 6:28 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2][UV] Up casing Login IDs {unclassified}
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mike
> Pflugfelder
> Sent: Monday, August 27, 2007 6:30 AM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2][UV] Up casing Login IDs {unclassified}
>
snip
> 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
That's been our experience as well. We authenticate our linux UV logins
against Active Directory, and our UV user names have always been all
uppercase. Users can log in using either case (or mixed case), but the
user name in UV as returned by @WHO is exactly how the user name was
entered when it was created in AD.
When new users are inadvertently created with the wrong case, we delete
them from AD and re-create them correctly.
-John
---
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/
RE: [U2][UV] Up casing Login IDs {unclassified}
Problem solved! Thanks to all who replied.
I had installed UV as the administrator, but edited the odbc.config file
as myself. A uvregen at the command prompt and then stopping and
starting UV services sorted out UV and it is now passing my login ID to
the UV.lOGINS file in upper case.
I had stopped and started UV as part of my trouble shooting of this
problem but not with a uvregen, which seems to be the key here.
Cheers,
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hester
Sent: Tuesday, 28 August 2007 10:28 a.m.
To: u2-users@listserver.u2ug.org
Subject: RE: [U2][UV] Up casing Login IDs {unclassified}
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mike
> Pflugfelder
> Sent: Monday, August 27, 2007 6:30 AM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2][UV] Up casing Login IDs {unclassified}
>
snip
> 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
That's been our experience as well. We authenticate our linux UV logins
against Active Directory, and our UV user names have always been all
uppercase. Users can log in using either case (or mixed case), but the
user name in UV as returned by @WHO is exactly how the user name was
entered when it was created in AD.
When new users are inadvertently created with the wrong case, we delete
them from AD and re-create them correctly.
-John
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
If you are not the intended recipient you must not use, disclose, copy or
distribute this message or the information in it.
If you have received this message in error, please Email or telephone
the sender immediately.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2][UV] Up casing Login IDs {unclassified}
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Mike
> Pflugfelder
> Sent: Monday, August 27, 2007 6:30 AM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [U2][UV] Up casing Login IDs {unclassified}
>
snip
> 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
That's been our experience as well. We authenticate our linux UV logins
against Active Directory, and our UV user names have always been all
uppercase. Users can log in using either case (or mixed case), but the
user name in UV as returned by @WHO is exactly how the user name was
entered when it was created in AD.
When new users are inadvertently created with the wrong case, we delete
them from AD and re-create them correctly.
-John
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2][UV] Up casing Login IDs {unclassified}
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: u2-users@listserver.u2ug.org
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
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
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
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Taylor
Sent: Saturday, 25 August 2007 6:52 a.m.
To: u2-users@listserver.u2ug.org; MACK ANDREW, MR
Subject: Re: [U2][UV] Up casing Login IDs {unclassified}
Andrew,
Add PTERM CASE NOINVERT to your UV.LOGIN in the UV account:
LOGTO UV
ED VOC UV.LOGIN
4 lines long.
: P
0001: Paragraph
0002: IF @TTY = 'phantom' THEN GO END.OF.LOGIN
0003: PTERM CASE NOINVERT
0004: END.OF.LOGIN:
Bottom at line 4.
hth,
Dave Taylor
CEO
Sysmark Information Systems, Inc.
49 Aspen Way
Rolling Hills Estates, CA 90274
800-SYSMARK (800-797-6275)
(O) 310-544-1974
(C) 310-561-5200
(F) 310-377-3550
www.sysmarkinfo.com
Your Source for Integrated EDI Translation, DataSync Integration and
Software Migration Authorized IBM Business Partner
- Original Message -
From: "Moderator" <[EMAIL PROTECTED]>
To: ; "MACK ANDREW, MR"
<[EMAIL PROTECTED]>
Sent: Friday, August 24, 2007 6:45 AM
Subject: [SPAM] [U2][UV] Up casing Login IDs {unclassified}
> Bounce notice: If you read this list through Indexfocus, Nabble, or
any
> other
> replicator - and you would like to be able to participate - sign up
> directly with us. Here's all you need to know: To subscribe or
> resubscribe please visit http://listserver.u2ug.org/.
>
> REPOSTED FOR NON-MEMBER ADDRESS: "MACK ANDREW, MR"
<[EMAIL PROTECTED]>
>
> Hi all
>
> I am setting up a new UV production server. UV 10.1.18 on Windows
Server
> 2003, INFORMATION flavour. Access is via QVTTerm. On the existing prod
> server, when you enter your enterprise login ID at the server login,
UV
> up cases the login ID and presents it to the UV.LOGINS file. However,
on
> the new server it is changing the login ID to lower case. Since all
our
> apps expect upper case, this is very frustrating.
>
> For example, on the existing server I login as auser14 and a Who at
TCL
> shows KIWI\AUSER14. UV.LOGINS is:
>
> Record Key:AUSER14
> 001 DOMAIN:KIWI
> 002 LOCAL :
> 003 DOMAIN.ACCOUNT :D:\DATA\USERS
> 004 LOCAL.ACCOUNT :
> 005 DESC :Andrew Mack
> End of record
>
> On the new server. I login as auser14 and a Who at TCL shows
> KIWI\auser14. If I login as AUSER14, a Who at TCL shows KIWI\auser14.
I
> have to have UV.LOGINS records in both AUSER14 and auser14 otherwise
it
> falls over with the error "Unable to find user account information in
> the UV.LOGINS file".
>
> Could someone please advise what setting determines the case that UV
> works with?
>
> Thank you
>
> Andrew Mack
> Senior Database Manager (UV/SQL)
> Joint Applications Engineering Group
>
> 342 5914 (Dtln)
> (04) 2371 914 (DDI)
>
>
> The information contained in this Internet Email message is intended
> for the addressee only and may contain privileged information, but not
> necessarily the official views or opinions of the New Zealand Defence
Force.
> If you are not the intended recipient you must not use, disclose, copy
or
> distribute this message or the information in it.
>
> If you have received this message in error, please Email or telephone
> the sender immediately.
> ---
> 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/
The information contained in this Internet Email message is intended
for the addressee only and may contain privileged information, but not
necessarily the official views or opinions of the New Zealand Defence Force.
Re: [U2][UV] Up casing Login IDs {unclassified}
Given that the purpose of UV.LOGINS is to map all possible login IDs (user, machine\user, domain\user) to one user ID, why not copy the upper case ones to lower cased equivalents in UV.LOGINS? --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2][UV] Up casing Login IDs {unclassified}
Andrew,
Add PTERM CASE NOINVERT to your UV.LOGIN in the UV account:
LOGTO UV
ED VOC UV.LOGIN
4 lines long.
: P
0001: Paragraph
0002: IF @TTY = 'phantom' THEN GO END.OF.LOGIN
0003: PTERM CASE NOINVERT
0004: END.OF.LOGIN:
Bottom at line 4.
hth,
Dave Taylor
CEO
Sysmark Information Systems, Inc.
49 Aspen Way
Rolling Hills Estates, CA 90274
800-SYSMARK (800-797-6275)
(O) 310-544-1974
(C) 310-561-5200
(F) 310-377-3550
www.sysmarkinfo.com
Your Source for Integrated EDI Translation, DataSync Integration and
Software Migration
Authorized IBM Business Partner
- Original Message -
From: "Moderator" <[EMAIL PROTECTED]>
To: ; "MACK ANDREW, MR"
<[EMAIL PROTECTED]>
Sent: Friday, August 24, 2007 6:45 AM
Subject: [SPAM] [U2][UV] Up casing Login IDs {unclassified}
> Bounce notice: If you read this list through Indexfocus, Nabble, or any
> other
> replicator - and you would like to be able to participate - sign up
> directly with us. Here's all you need to know: To subscribe or
> resubscribe please visit http://listserver.u2ug.org/.
>
> REPOSTED FOR NON-MEMBER ADDRESS: "MACK ANDREW, MR"
<[EMAIL PROTECTED]>
>
> Hi all
>
> I am setting up a new UV production server. UV 10.1.18 on Windows Server
> 2003, INFORMATION flavour. Access is via QVTTerm. On the existing prod
> server, when you enter your enterprise login ID at the server login, UV
> up cases the login ID and presents it to the UV.LOGINS file. However, on
> the new server it is changing the login ID to lower case. Since all our
> apps expect upper case, this is very frustrating.
>
> For example, on the existing server I login as auser14 and a Who at TCL
> shows KIWI\AUSER14. UV.LOGINS is:
>
> Record Key:AUSER14
> 001 DOMAIN:KIWI
> 002 LOCAL :
> 003 DOMAIN.ACCOUNT :D:\DATA\USERS
> 004 LOCAL.ACCOUNT :
> 005 DESC :Andrew Mack
> End of record
>
> On the new server. I login as auser14 and a Who at TCL shows
> KIWI\auser14. If I login as AUSER14, a Who at TCL shows KIWI\auser14. I
> have to have UV.LOGINS records in both AUSER14 and auser14 otherwise it
> falls over with the error "Unable to find user account information in
> the UV.LOGINS file".
>
> Could someone please advise what setting determines the case that UV
> works with?
>
> Thank you
>
> Andrew Mack
> Senior Database Manager (UV/SQL)
> Joint Applications Engineering Group
>
> 342 5914 (Dtln)
> (04) 2371 914 (DDI)
>
>
> The information contained in this Internet Email message is intended
> for the addressee only and may contain privileged information, but not
> necessarily the official views or opinions of the New Zealand Defence
Force.
> If you are not the intended recipient you must not use, disclose, copy or
> distribute this message or the information in it.
>
> If you have received this message in error, please Email or telephone
> the sender immediately.
> ---
> 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/
[U2][UV] Up casing Login IDs {unclassified}
Bounce notice: If you read this list through Indexfocus, Nabble, or any other replicator - and you would like to be able to participate - sign up directly with us. Here's all you need to know: To subscribe or resubscribe please visit http://listserver.u2ug.org/. REPOSTED FOR NON-MEMBER ADDRESS: "MACK ANDREW, MR" <[EMAIL PROTECTED]> Hi all I am setting up a new UV production server. UV 10.1.18 on Windows Server 2003, INFORMATION flavour. Access is via QVTTerm. On the existing prod server, when you enter your enterprise login ID at the server login, UV up cases the login ID and presents it to the UV.LOGINS file. However, on the new server it is changing the login ID to lower case. Since all our apps expect upper case, this is very frustrating. For example, on the existing server I login as auser14 and a Who at TCL shows KIWI\AUSER14. UV.LOGINS is: Record Key :AUSER14 001 DOMAIN:KIWI 002 LOCAL : 003 DOMAIN.ACCOUNT :D:\DATA\USERS 004 LOCAL.ACCOUNT : 005 DESC :Andrew Mack End of record On the new server. I login as auser14 and a Who at TCL shows KIWI\auser14. If I login as AUSER14, a Who at TCL shows KIWI\auser14. I have to have UV.LOGINS records in both AUSER14 and auser14 otherwise it falls over with the error "Unable to find user account information in the UV.LOGINS file". Could someone please advise what setting determines the case that UV works with? Thank you Andrew Mack Senior Database Manager (UV/SQL) Joint Applications Engineering Group 342 5914 (Dtln) (04) 2371 914 (DDI) The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
