Problem Note 59941: Your SAS® session might stop responding or terminate abnormally when you use the street geocoding method with PROC GEOCODE
Your SAS session might stop responding or terminate abnormally when you use the street geocoding method with PROC GEOCODE. Error messages like the following might be generated when this occurs:
The SAS task name is [GEOCODE]
ERROR: Read Access Violation GEOCODE
ERROR: Write Access Violation GEOCODE
Exception occurred at (05D3F001)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
This problem might occur when the street name contains three words, the last two words match a two-word street type, and the first word of the street name is a direction. An example is 123 E Orch Rd, Cary, NC, 27513.
If this is the case, you might circumvent the issue by creating a new data set from the Sashelp.Gctype data set where the name of the street is removed from the Name variable. You can then reference the modified data set using the TYPE= option in the PROC GEOCODE statement. The example code below illustrates this:
data sasuser.gctype;
set sashelp.gctype;
if name='ORCHRD' then delete;
run;
proc geocode
method=street
data=addressdata
out=geocoded
lookupstreet=lookup.usm
type=sasuser.gctype;
run;
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS/GRAPH | z/OS | 9.4 TS1M4 | 9.4 TS1M5 |
z/OS 64-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft® Windows® for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Pro 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8 Pro x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro 32-bit | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 8.1 Pro x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows 10 | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2008 | 9.4 TS1M4 | |
Microsoft Windows Server 2008 R2 | 9.4 TS1M4 | |
Microsoft Windows Server 2008 for x64 | 9.4 TS1M4 | |
Microsoft Windows Server 2012 Datacenter | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 R2 Std | 9.4 TS1M4 | 9.4 TS1M5 |
Microsoft Windows Server 2012 Std | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Enterprise 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Enterprise x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Home Premium 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Home Premium x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Professional 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Professional x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Ultimate 32 bit | 9.4 TS1M4 | 9.4 TS1M5 |
Windows 7 Ultimate x64 | 9.4 TS1M4 | 9.4 TS1M5 |
64-bit Enabled AIX | 9.4 TS1M4 | 9.4 TS1M5 |
64-bit Enabled Solaris | 9.4 TS1M4 | 9.4 TS1M5 |
HP-UX IPF | 9.4 TS1M4 | 9.4 TS1M5 |
Linux for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
Solaris for x64 | 9.4 TS1M4 | 9.4 TS1M5 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Using the street geocoding method with PROC GEOCODE might cause your SAS session to become unresponsive or to terminate abnormally.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2017-03-07 10:35:48 |
Date Created: | 2017-02-10 10:18:53 |