Problem Note 39925: An error occurs when the LDAPS_SEARCH CALL routine returns the exact entries 40, 80, 160, and so on, from an LDAP or Microsoft Active Directory server
 |  |  |  |
A Read access violation occurs when a query that passes to an LDAP or Active Directory server via the LDAPS_SEARCH CALL routine returns these exact entries: 40, 80, 160, 320, and so on. Message such as the following are written to the SAS log:
ERROR: Read Access Violation In Task [ DATASTEP ] Exception occurred at (055C4A58) Task Traceback Address Frame (DBGHELP API Version 4.0 rev 5) 00000000055C4A58 000000000536FCC0 uwuldaps:mcn_main+0x3A58 0000000004113249 000000000536FCD8 sasxkern:mcn_main+0x32249
Segmentation Violation In Task [ DATASTEP ] /opt/sas/SASFoundation/9.2/sasexe/sas [0x4f82f0] /opt/sas/SASFoundation/9.2/sasexe/sas [0x4f8494] /opt/sas/SASFoundation/9.2/sasexe/sas [0x41adbc] /opt/sas/SASFoundation/9.2/sasexe/sas [0x41aac3] /opt/sas/SASFoundation/9.2/sasexe/tkmk.so(bkt_signal_handler+0xec) [0x2b810c074aa8] /lib64/libc.so.6 [0x36706302f0] /opt/sas/SASFoundation/9.2/sasexe/uwuldaps(lentry+0x132) [0x2aaab91d31e6][0x2aaab94b2d3b]
This error commonly occurs when user import and synchronization programs such as importAD.sas read the results returned to the LDAPS_SEARCH CALL routine.
The filter argument in the LDAPS_SEARCH CALL routine specifies the search criteria that pass to the LDAP server. The LDAP server then returns a list of matching entries. For example, the following sample of code passes a query to an LDAP server:
filter="(&(displayName>=A)(displayName<=C))"; call ldaps_search( handle, shandle, filter, attrs, num, rc );
To work around this error, modify the filter value to query a narrower or wider range so that the number of entries returned is not one of the values listed above. For example, this sample of code widens the range of the query:
filter="(&(displayName>=A)(displayName<=F))"; call ldaps_search( handle, shandle, filter, attrs, num, rc );
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Integration Technologies | HP-UX IPF | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 |
| 64-bit Enabled Solaris | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| 64-bit Enabled HP-UX | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| 64-bit Enabled AIX | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Windows Vista for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Windows Vista | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP Professional | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2008 for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft® Windows® for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows XP 64-bit Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| z/OS | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Linux | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Linux for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| OpenVMS on HP Integrity | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Solaris for x64 | 9.21 | 9.21 | 9.2 TS2M0 | 9.2 TS2M3 | ||
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2010-12-06 11:02:49 |
| Date Created: | 2010-06-08 10:11:06 |