In the crtdds_write.sas macro, there is a macro parameter _cstOutputEncoding that is set to UTF-8 as a default value.

This results in this tag being added to the define.xml file:

<?xml version="1.0" encoding="UTF-8"?>

As a result, this error might be encountered if the encoding of the SAS Session does not match:

ERROR: Invalid byte 1 of 1-byte UTF-8 sequence

 

To fix this issue if it is encountered, change this macro parameter value to the SAS® session encoding.

The encoding of the SAS session can be found by opening SAS and running the following code:

proc sql;

select setting into: encoding from sashelp.voption where optname = 'ENCODING';

quit;

%put NOTE: the ENCODING option is set to &encoding;

Below are the steps to change the value:

1. Open the folder C:\Program Files\SASHome\SASClinicalStandardsToolkitCRTDDS10\1.4\standards\cdisc-crtdds-1.0\macros\
2. Open the file crtdds_write.sas
3. Change UTF-8 to the value of the ENCODING macro variable.

Note: if your encoding is missing, then follow the instructions below to change the encoding to the preferred language encoding:

Setting the Encoding of a SAS Session

For additional information about the encoding option: open this link

For listing of encoding values: open this link

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Clinical Standards Toolkit	Microsoft® Windows® for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2003 Datacenter Edition	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2003 Enterprise Edition	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2003 Standard Edition	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2003 for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2008	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows Server 2008 for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Microsoft Windows XP Professional	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Enterprise 32 bit	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Enterprise x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Home Premium 32 bit	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Home Premium x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Professional 32 bit	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Professional x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Ultimate 32 bit	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows 7 Ultimate x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows Vista	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Windows Vista for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		64-bit Enabled Solaris	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		HP-UX IPF	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Linux for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1
		Solaris for x64	1.4	1.5	9.3 TS1M1	9.3 TS1M1

* 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.

---

Error when generating a define.xml file is caused by unrecognized characters in UTF-8 encoding.

Type:	Usage Note
Priority:	medium

Date Modified:	2014-03-27 17:24:37
Date Created:	2012-11-21 10:19:14