![]() | ![]() | ![]() | ![]() | ![]() |
When SAS Enterprise Guide is connected to a remote UTF-8 SAS server, importing a UTF-16 file fails. The same problem occurs when opening UTF-16 files from within the Server list. The same file is successfully imported when SAS Enterprise Guide is connected to a local server.
Instead of the server reading files in a binary mode, the server is examines the binary file, looking for byte-order marks (BOMs) as indications that the file is an encoded file. If BOMs are found and the implied encoding is not compatible with the server's encoding, then the binary reading of the file fails with an incompatible encoding message.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Enterprise Guide | Microsoft® Windows® for x64 | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Enterprise Edition | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 Standard Edition | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2003 for x64 | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Microsoft Windows Server 2008 for x64 | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Microsoft Windows XP Professional | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Windows Vista | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 | ||
Windows Vista for x64 | 4.2 | 5.1 | 9.2 TS2M0 | 9.3 TS1M0 |