PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
OSP-INTSRVSUP-MSGNTA0274 AFTER APPLYING THE LATEST GROUP SF9
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM REL NUMBER MIN/MAX OPTION
---- -------- --- ------- ------- ------
NONE
NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
foregoing.
This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF. You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
CL command.
APAR Error Description / Circumvention
-----------------------------------------------
Customer had been using the user enrollment function to enroll
users in the windows domain and synchronize passwords. After the
group was applied and the server synchronized with the new
qvnadaem.exe enrolling new users would fail with msgnta0274
although apparently successful. Qvnadaem also crashed at least
once. Removing SI44683 and copying the older version of qvnadaem
from the ifs to the server resolved the issue.
CORRECTION FOR APAR SE51446 :
-----------------------------
1. The qvnadaem.exe will crash when enrolling a user with a
template into a domain and he template string length is shorter
than that of enrolled profile description. This is because the
code forgets to recalculate the template string length before
allocating its memory. In stead, it duly uses profile
description's string length mistakenly. So when freeing
template's memory, the illegal memory is mistakenly freed, thus
causing code crash.
2.When enrolling a user with a template into a domain and the
user already being one of the template's enrolled group's
members, the enrollment will not succeed. This is because
Microsoft has adopted three sets of error code for ADSI. When
comparing and judge if an error is hit, the wrong error code is
used, thus causing an enrollment failure.
This fix has solved both problems.
CIRCUMVENTION FOR APAR SE51446 :
--------------------------------
None.
Activation Instructions
None.
Special Instructions
None.
Default Instructions
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
Supersedes
PTF/FIX NO(S). APAR TITLE LINE
-------------- ------------------------------------------------------------
SI44683 QVNADAEM Enhancements using Active Directory APIs
SI36461 OSP-QVNADAEM SERVICE CONTINUALLY RESTARTS ON WINDOWS 2008 R2
Summary Information
System.............................. | i |
Models.............................. | |
Release............................. | V7R1M0 |
Licensed Program............... | 5770SS1 |
APAR Fixed.......................... | View details for APAR SE51446 |
Superseded by:...................... | View fix details for PTF SI58320 |
Recompile........................... | N |
Library............................. | QNTAP |
MRI Feature ........................ | NONE |
Cum Level........................... | C3037710 |
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.
Was this topic helpful?
Document Information
Modified date:
13 April 2012