JR25500: WINDOWS INSTALLER TRIES TO REINSTALL DB2 WHEN A NON-ADMIN USER WHO DOES NOT BELONG TO ANY DB2 USER GROUPS LOGON TO THE SYSTEM.

DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• This problem only happens if:
  (1) The DB2 extended-security was enabled when db2 was
  installed, and
  (2) The user who logs on the system after the db2 was installed
  is not a member of the local administrator user group, and also
  not a member of any db2 user groups. Thus, this user does not
  have the authorities required to access any db2
  files/applications.
  .
  In this scenario, the non-admin user logged on the system might
  see a message box like "Please wait while Windows configures DB2
  Workgroup Server Edition".
  In addition, the attempt to reinstall DB2 fails either because
  db2 install image is no longer available to the system, or (even
  the image is still available) the non-admin user does not have
  the authorities required.
  .
  The causes of this 'tries to reinstall' problem are:
  -- The user who logs on the server does not have read
  permissions for DB2 files.
  If the DB2 extended-security is enabled, the SQLLIB directory is
  protected. Only the users in the local administrator group, or
  the DB2 user groups can access the DB2 files installed on the
  system.
  .
  -- InstallShield update service is enabled, which is default
  after installing DB2 9
  The update service tries to validate the products that are
  registered for Update Service after the logon. If the logon user
  does not have the authority to access DB2's SQLLIB, the update
  service process can not too. It will "think" that the product
  (DB2 in this example) is corrupted or damaged, then tries to
  reinstall that.
  

Local fix

• This is a limitation of DB2 9 products on Windows for the time
  being. One of the following ways can be used for the workaround
  if you allow non-admin users, who do not belong to any db2 user
  groups, to access the system where DB2 is installed.
  .
  a) Turn off extended-security
    To uncheck the "Enable db2 extended security" during the
  install .
  b) Add users to the "DB2USERS" users group on the system
    Members of the DB2USERS group have the read access permission
    the db2 files.
    You can add the users who are allowed to access the system
    where DB2 was install to that user group. If you want to let
    everyone have the read access, you can add the build-in
    "Everyone" to the DB2USERS group.
    For example, the command below add all users to the DB2USERS
    group:
        net localgroup DB2USERS Everyone /add
  

Problem summary

• Users affected
  DB2 9 on Windows platforms with extended security enabled.
  Problem Description
  non-admin user logged on the system might see a message box like
  "Please wait while Windows configures DB2 Workgroup Server
  Edition". And msiexec tries to reinstall DB2 9.
  

Problem conclusion

• First fixed in DB2 Version 9.1, FixPak 3 (s070719)
  

Temporary fix

• One of the followings:
  a) Turn off extended-security
  b) Add users to the "DB2USERS" users group on the system
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• INSTALL
  

Fix information

• Fixed component name

  DB2 UDB ESE WIN

• Fixed component ID

  5765F4101

Applicable component levels

• R910 PSN

     UP