BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
Rupasree
Obsidian | Level 7

Hi All,

 

I am getting an error,when I am publishing/executing a campaign with traditional Chinese text in the description.

When I remove the Chinese text from the description ,the campaigns executes successfully.

I have a requirement where in SAS MA must support traditional Chinese text.

Attached is the screenshot of the error.

 

Your help is highly appreciated.

Thanks in advance.

 

Regards,

Rupa

1 ACCEPTED SOLUTION

Accepted Solutions
Dmitry_Alergant
Pyrite | Level 9

You need to switch your SAS server environment to Unicode (UTF8) encoding.   It may not be using it currently.

 

Try connecting with Enterprise Guide and running "proc options option=encoding; run;". If it says anything other than UTF8, you can use Chinese until you switch to UTF8. 

 

If it is confirmed that you need to switch the encoding, this is quite a major change in the way SAS works, so do not attempt this switch on a live production environment if it is already operational and in use by the users - unless you have first tested it extensively in your non-prod environment (if you have one)  have plenty of downtime window and you have properly backed up everything, e.t.c.  It's easier if it is a brand new environment only being configured.

Normally the UTF8 encoding is selected at the time SAS is installed ("Use SAS as Unicode server" checkbox") but it can be switched after the fact: http://support.sas.com/kb/51/586.html

 

After the switch, you will certainly need to recreate the MAMisc.Sequence dataset - SAS MA won't work until you do it. Use Enterprise Guide:

proc sql;

  create table MAMisc.Sequence_copy as select * from MAMisc.Sequence;

  drop table MAMisc.Sequene;

  create table MAMisc.Sequence as select * from MAMisc.Sequence_copy;

run;

 

Depending on your environment, if your or custom stored processes store and update datasets in Base SAS libraries, you may have other base SAS datasets that need to be migrated / recreated with the new encoding. MATables library should be fine though (you can leave it as is).

 

Your users will also need to use "K functions" in calculated variables instead of traditional text manipulation functions (length, cat, find, substr etc).

 

-------
Dmitriy Alergant, Tier One Analytics

View solution in original post

4 REPLIES 4
pcapazzi
Pyrite | Level 9
You would need to look at the MA Core Log from around that time and post more detail. Try to find the connection statement and the errors around it.

Do you have a SAS Tech Support Ticket created?
Rupasree
Obsidian | Level 7
Hi, Below is the error that i found in the Core log file: ERROR [CIAsyncExec-8] [dc57890466b9aaa4:-3a141d8f:15f5bf92e28:-5a94] com.sas.analytics.crm.util.SystemCheck - executeCampaign(flowStateID) com.sas.analytics.crm.error.client.ApplicationException: Macro[MAPUBWP]. PROC Copy failed - while attempting to create dataset out of XML stream. Check the log for details.: MA error code 722: Vendor code 1008 Regards, Rupasree
Dmitry_Alergant
Pyrite | Level 9

You need to switch your SAS server environment to Unicode (UTF8) encoding.   It may not be using it currently.

 

Try connecting with Enterprise Guide and running "proc options option=encoding; run;". If it says anything other than UTF8, you can use Chinese until you switch to UTF8. 

 

If it is confirmed that you need to switch the encoding, this is quite a major change in the way SAS works, so do not attempt this switch on a live production environment if it is already operational and in use by the users - unless you have first tested it extensively in your non-prod environment (if you have one)  have plenty of downtime window and you have properly backed up everything, e.t.c.  It's easier if it is a brand new environment only being configured.

Normally the UTF8 encoding is selected at the time SAS is installed ("Use SAS as Unicode server" checkbox") but it can be switched after the fact: http://support.sas.com/kb/51/586.html

 

After the switch, you will certainly need to recreate the MAMisc.Sequence dataset - SAS MA won't work until you do it. Use Enterprise Guide:

proc sql;

  create table MAMisc.Sequence_copy as select * from MAMisc.Sequence;

  drop table MAMisc.Sequene;

  create table MAMisc.Sequence as select * from MAMisc.Sequence_copy;

run;

 

Depending on your environment, if your or custom stored processes store and update datasets in Base SAS libraries, you may have other base SAS datasets that need to be migrated / recreated with the new encoding. MATables library should be fine though (you can leave it as is).

 

Your users will also need to use "K functions" in calculated variables instead of traditional text manipulation functions (length, cat, find, substr etc).

 

-------
Dmitriy Alergant, Tier One Analytics
suksma
SAS Employee

Hi there,

 

Please raise a track with SAS Technical Support, so that we may help you with issue.

Many thanks.

How to improve email deliverability

SAS' Peter Ansbacher shows you how to use the dashboard in SAS Customer Intelligence 360 for better results.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 4 replies
  • 2290 views
  • 0 likes
  • 4 in conversation