Problem Note 41498: Generic Critical Error or unresponsive SAS session following PROC CIMPORT of a SAS/AF® Frame catalog
When using PROC CIMPORT to read in a SAS transport file containing a SAS/AF frame catalog, you might receive the following error in the SAS log:
NOTE: Proc CIMPORT begins to create/update catalog WORK.MO_DISC_CAPA
NOTE: Entry DATAIMPORT.FRAME has been imported.
ERROR: Write Access Violation In Task [ SASCIMPO )
Exception occurred at (01335EDF)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
01335EDF 048DEB78 sashost:Main+0xCF24F
012EF307 048DEB90 sashost:Main+0x88677
66AC74A0 048DEBCC sasccafe:mcn_main+0x164A0
66AC6EE1 048DED30 sasccafe:mcn_main+0x15EE1
66AC1E86 048DFE8C sasccafe:mcn_main+0x10E86
66881254 048DFF88 sascim:mcn_main+0x254
01272B72 048DFFA0 sashost:Main+0xBEE2
01276C90 048DFFB4 sashost:Main+0x10000
7C80B713 048DFFEC kernel32:GetModuleFileNameA+0x1B4
ERROR: Generic critical error.
ERROR: Error converting FORECAST.FRAME. Entry will be deleted.
Another symptom of this problem was found when importing the transport file into SAS 9.2 on a 64-bit machine. In this case, instead of the error, the SAS session stopped responding.
To circumvent this problem, follow the steps below:
-
In the originating SAS session, rename the original SCL entry for the problem Frame. For example if your Frame is named MYFRAME.FRAME, rename the Frame to MYFRAME_BACK.FRAME.
-
Edit your Frame entry for the SCL entry you renamed, and open the SCL source window and then close. This will create a new, empty SCL entry for that Frame.
-
Exit the Frame, but do not compile.
-
Use PROC CPORT to create the transport file of the catalog.
-
On the destination operating system, use PROC CIMPORT to read in the catalog from the transport file in step 4.
-
In the destination SAS session, do the following to associate the backup SCL entry with the Frame:
-
Delete the blank SCL entry created in step 2 that has the same name as the problem Frame.
-
Rename the backup SCL entry back to its original name, like from MYFRAME_BACK.FRAME to MYFRAME.FRAME.
-
Compile the Frame to once again associate the SCL code with its Frame.
Operating System and Release Information
| SAS System | SAS/AF | z/OS | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M0 | |
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M0 | |
| Microsoft Windows 2000 Server | 9.1 TS1M0 | |
| Microsoft Windows 2000 Professional | 9.1 TS1M0 | |
| Microsoft Windows NT Workstation | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | 9.3 TS1M0 |
| Microsoft Windows XP Professional | 9.1 TS1M0 | 9.3 TS1M0 |
| 64-bit Enabled AIX | 9.1 TS1M0 | 9.3 TS1M0 |
| 64-bit Enabled HP-UX | 9.1 TS1M0 | 9.3 TS1M0 |
| 64-bit Enabled Solaris | 9.1 TS1M0 | 9.3 TS1M0 |
| HP-UX IPF | 9.1 TS1M0 | 9.3 TS1M0 |
| Linux | 9.1 TS1M0 | 9.3 TS1M0 |
| OpenVMS Alpha | 9.1 TS1M0 | 9.3 TS1M0 |
| Tru64 UNIX | 9.1 TS1M0 | 9.3 TS1M0 |
*
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.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2010-11-04 13:46:35 |
| Date Created: | 2010-11-03 16:49:14 |
