RE: [U2] problem with UniVerse SQL Users on windows
David - The UniVerse Administrative and SQL users must have a password in order to be valid. Users who do not have a password cannot administer UniVerse. This applies to both the administrator on Windows and the root user on unix/linux. Add a password to the user you are having trouble with and see if that fixes the problem. Ken At 06:53 PM 4/3/2008, you wrote: UniVerse has made NT AUTHORITY\System the default DBA, but as this has no password as an internal user, I cannot login as NT AUTHORITY\system to create a new SQL User. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] problem with UniVerse SQL Users on windows
Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] problem with UniVerse SQL Users on windows
David - Install instructions for UV on Unix states that you need a uvsql user for this purpose which needs to be setup prior to the installation. Have you checked the Windows installation instructions in the UV docs. You might not have setup the default user prior to the installation. Ken At 01:00 PM 4/4/2008, you wrote: Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- 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] problem with UniVerse SQL Users on windows
Hi Ken With windows the installer was the default SQL Account, which is usually the administrator. It is in updating to the new release that has changed the way things have been done. My actual issue is that UniVerse no longer recognises current SQL users, the only thing I can see is that the domain name is in a different case to that which is stored on UV_USERS in the SQL Catalog. The second issue, is that it does recognise current SQL users, I have no SQL DBA access to UniVerse to resolve issues. Hence locked out. Regards David Jordan Managing Consultant David - Install instructions for UV on Unix states that you need a uvsql user for this purpose which needs to be setup prior to the installation. Have you checked the Windows installation instructions in the UV docs. You might not have setup the default user prior to the installation. Ken At 01:00 PM 4/4/2008, you wrote: Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- 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-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] problem with UniVerse SQL Users on windows
Hi David - Did you do the upgrade with a different user that the original install? If so, uninstall UniVerse and re-install it. It should leave all your user stuff alone, and after the new install, instead of an upgrade, things should be fine. You should however, logon to each account as the administrator who did the install to auto run UPDATE.ACCOUNT. Also, the domain name is case insensitive in Windows authorization. Also, it may be a permissions issue after the update. I have had this type of problem with a Unix update. Check all the permissions on the UniVerse files, especially in the .uvhome/uv/bin directory. Hope this helps. Ken At 03:28 PM 4/4/2008, you wrote: Hi Ken With windows the installer was the default SQL Account, which is usually the administrator. It is in updating to the new release that has changed the way things have been done. My actual issue is that UniVerse no longer recognises current SQL users, the only thing I can see is that the domain name is in a different case to that which is stored on UV_USERS in the SQL Catalog. The second issue, is that it does recognise current SQL users, I have no SQL DBA access to UniVerse to resolve issues. Hence locked out. Regards David Jordan Managing Consultant David - Install instructions for UV on Unix states that you need a uvsql user for this purpose which needs to be setup prior to the installation. Have you checked the Windows installation instructions in the UV docs. You might not have setup the default user prior to the installation. Ken At 01:00 PM 4/4/2008, you wrote: Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- 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-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] problem with UniVerse SQL Users on windows (Domain name is now case sensitive)
Hi Ken 1. I did install as the same user 2. You are right that the domain name is case insensitive in windows, however it appears UniVerse is case sensitive when check against UV_USERS for valid SQL Users. 3. Security of the directories are OK. I eventually uninstalled UniVerse and reinstalled. Now in UV_USERS all domain names are in uppercase and it recognises SQL users. Problem: IBM is making domain name case sensitive and this will effect anyone upgrading where domain names are in lowercase in SQL_USERS. Regards David Jordan Managing Consultant [EMAIL PROTECTED] Mobile: 0428 669 730 Phone: 61 2 9418 8329 Fax: 61 2 9427 2371 PO Box 909 Lane Cove NSW 2066 Australia www.dacono.com.au CAUTION: This email and any attachments are confidential, may be privileged, and are intended for use solely by the addressee. The confidentiality and/or privilege in this email is not waived, lost or destroyed if it has been transmitted to you in error. If you receive this email in error, please notify Dacono by reply email immediately, delete the email and destroy any printed copies. You must not disclose, disseminate, distribute, reproduce or use the information contained in this email which may contain intellectual property or copyright irrespective whether you are or are not the intended recipient. The content and opinions contained in this email are those of the individual sender and may not necessarily reflect the views and opinions of Dacono. Dacono does not guarantee that this email is free from viruses, errors, interception or interference. Use of this email and any attachments is at the sole risk of the user. Dacono does not accept any liability for any loss or damage to your computer system or network (including any consequential damage) which may occur directly or indirectly from the use of this email. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-u2- [EMAIL PROTECTED] On Behalf Of Ken Hall Sent: Saturday, 5 April 2008 10:49 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] problem with UniVerse SQL Users on windows Hi David - Did you do the upgrade with a different user that the original install? If so, uninstall UniVerse and re-install it. It should leave all your user stuff alone, and after the new install, instead of an upgrade, things should be fine. You should however, logon to each account as the administrator who did the install to auto run UPDATE.ACCOUNT. Also, the domain name is case insensitive in Windows authorization. Also, it may be a permissions issue after the update. I have had this type of problem with a Unix update. Check all the permissions on the UniVerse files, especially in the .uvhome/uv/bin directory. Hope this helps. Ken At 03:28 PM 4/4/2008, you wrote: Hi Ken With windows the installer was the default SQL Account, which is usually the administrator. It is in updating to the new release that has changed the way things have been done. My actual issue is that UniVerse no longer recognises current SQL users, the only thing I can see is that the domain name is in a different case to that which is stored on UV_USERS in the SQL Catalog. The second issue, is that it does recognise current SQL users, I have no SQL DBA access to UniVerse to resolve issues. Hence locked out. Regards David Jordan Managing Consultant David - Install instructions for UV on Unix states that you need a uvsql user for this purpose which needs to be setup prior to the installation. Have you checked the Windows installation instructions in the UV docs. You might not have setup the default user prior to the installation. Ken At 01:00 PM 4/4/2008, you wrote: Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- 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-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-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] problem with UniVerse SQL Users on windows (Domain name is now case sensitive)
It's a problem with other applications too. We had the exact same problem with another third-party packaged application. The problem is Windows allows you to define David and david to mean the same thing. But to application software, these are two different users - unless the third-party application bothers to force/translate the user-ID always to uppercase -- it's going to be an on-going issue. I guess to multiplatform applications, they need to make an exception for UNIX, as it allows mixed case user-IDs (I've yet to ever see one though!). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Jordan Sent: Saturday, 5 April 2008 12:19 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] problem with UniVerse SQL Users on windows (Domain name is now case sensitive) Hi Ken 1. I did install as the same user 2. You are right that the domain name is case insensitive in windows, however it appears UniVerse is case sensitive when check against UV_USERS for valid SQL Users. 3. Security of the directories are OK. I eventually uninstalled UniVerse and reinstalled. Now in UV_USERS all domain names are in uppercase and it recognises SQL users. Problem: IBM is making domain name case sensitive and this will effect anyone upgrading where domain names are in lowercase in SQL_USERS. Regards David Jordan Managing Consultant [EMAIL PROTECTED] Mobile: 0428 669 730 Phone: 61 2 9418 8329 Fax: 61 2 9427 2371 PO Box 909 Lane Cove NSW 2066 Australia www.dacono.com.au CAUTION: This email and any attachments are confidential, may be privileged, and are intended for use solely by the addressee. The confidentiality and/or privilege in this email is not waived, lost or destroyed if it has been transmitted to you in error. If you receive this email in error, please notify Dacono by reply email immediately, delete the email and destroy any printed copies. You must not disclose, disseminate, distribute, reproduce or use the information contained in this email which may contain intellectual property or copyright irrespective whether you are or are not the intended recipient. The content and opinions contained in this email are those of the individual sender and may not necessarily reflect the views and opinions of Dacono. Dacono does not guarantee that this email is free from viruses, errors, interception or interference. Use of this email and any attachments is at the sole risk of the user. Dacono does not accept any liability for any loss or damage to your computer system or network (including any consequential damage) which may occur directly or indirectly from the use of this email. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-u2- [EMAIL PROTECTED] On Behalf Of Ken Hall Sent: Saturday, 5 April 2008 10:49 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] problem with UniVerse SQL Users on windows Hi David - Did you do the upgrade with a different user that the original install? If so, uninstall UniVerse and re-install it. It should leave all your user stuff alone, and after the new install, instead of an upgrade, things should be fine. You should however, logon to each account as the administrator who did the install to auto run UPDATE.ACCOUNT. Also, the domain name is case insensitive in Windows authorization. Also, it may be a permissions issue after the update. I have had this type of problem with a Unix update. Check all the permissions on the UniVerse files, especially in the .uvhome/uv/bin directory. Hope this helps. Ken At 03:28 PM 4/4/2008, you wrote: Hi Ken With windows the installer was the default SQL Account, which is usually the administrator. It is in updating to the new release that has changed the way things have been done. My actual issue is that UniVerse no longer recognises current SQL users, the only thing I can see is that the domain name is in a different case to that which is stored on UV_USERS in the SQL Catalog. The second issue, is that it does recognise current SQL users, I have no SQL DBA access to UniVerse to resolve issues. Hence locked out. Regards David Jordan Managing Consultant David - Install instructions for UV on Unix states that you need a uvsql user for this purpose which needs to be setup prior to the installation. Have you checked the Windows installation instructions in the UV docs. You might not have setup the default user prior to the installation. Ken At 01:00 PM 4/4/2008, you wrote: Hi Ken The user NT AUTHORITY\System is an internal windows user name. It is part of the internals of windows and adding a password to it could cause all sorts of things to stop working. It is not a login name, hence I am not sure why it is now being used as the default SQL DBA in universe on windows. Regards David Jordan --- u2-users mailing
RE: [U2] problem with UniVerse SQL Users on windows
Hi Ray Mapping in UV.LOGINS does not help. UV_USERS has domain\user, and if you type WHO, you get DOMAIN\user, the difference being casing. There is no way to force the login to be in lower case and no way to change UV_USERS as I am not a valid SQL User. UniVerse has made NT AUTHORITY\System the default DBA, but as this has no password as an internal user, I cannot login as NT AUTHORITY\system to create a new SQL User. When you hit this type of issue, there appears to be no tools for an administrator to get in to resolve problems, it becomes a lockout situation. Regards David Jordan Managing Consultant --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
