Usage Note 33710: Corrupted roaming profiles in a Windows environment cause read access violations and a general critical error
If you try to invoke SAS® on a Windows operating system, you might receive an error message similar to the following:
ERROR: Read Access Violation In Task [ RESULTS )
Exception occurred at (67762E4E)
Task Traceback
<traceback info>
ERROR: Read Access Violation In Task [ sasxkern )
Exception occurred at (67762E4E)
Task Traceback
<traceback info>
ERROR: Generic critical error.
ERROR: Explorer failed to initialize.
WARNING: Protected resource may be inconsistent
The problem might be caused by a corrupted Windows roaming profile.
To resolve the situation, remove the existing profile and re-create it.
Operating System and Release Information
| SAS System | Base SAS | Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.1 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 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M0 | |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M0 | |
| Microsoft Windows XP Professional | 9.1 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: | Usage Note |
| Priority: | medium |
| Date Modified: | 2008-10-23 13:52:18 |
| Date Created: | 2008-10-20 10:22:57 |
