report file name error with Chinese Date format

[Mike_Millhaem]

Hello,

I am seeing an error at step Write UUT report in the standard model files.  This step is calling the API method save on the object Runstate.Report.

The issue occurs on computers using chinese localization with the date in the report file name.

Is this a known issue?  Is there a way to modify the filename before calling the above method to eliminate the problem?

[Snowman 6008]

Mike,

Can you provide us with a screenshot of the error you are getting?

[Mike_Millhaem]

An Error Message is attached. 

WE have seen this on both Vista and XP.  We are using TestStand version 4.1.1.  I am not sure about the localization, but I have seen this on computers from Taiwan, Korea and Japan.  

If I put a breakpoint in the Model file at the Write UUT Report Step, you can see Chinese Characters in the time portion of the file name.

If you change the report name to not include the time and date, the error does not occur.

We have seen this with ASCII and xml.  With XML, the error also occurs at the step "Add Root Tags to XML Report"

[Snowman 6008]

Mike,

Have you seen this article? Why do I Receive Errors -17306 and Error -17322 in TestStand?  In that picture you're using a custom process model, does the same thing happen when you use the sequentialmodel.seq ? Does this error occur every single time you run except for when you change the report name to not include time and date? If modifying any expressions doesn't help your situation, would you mind zipping up your language folder, and sending me a very small sequence that demonstrates the problem? 

[Mike_Millhaem]

Hello Richard,

I have looked into the article, but I can do that.

The model file is only slighlty modified from the sequential model, and not in the area that caused the error.

In the TestStand Language file, I only have a file for English, as we have not tried to loacalize the TestStand messages.  

I think I understand the problem.  If you look at the report file name, there are two Chinese characters before the numerals for the time.  I think these are probably symbols for AM or PM.  When you pass that string to the save report method, the error message is generated.

I can send you a screen shot that shows the contents of the file name variable next week.

Mike

[Manooch_H]

Hi Mike,

I've tried to reproduce this error on a Chinese Simplified Windows XP OS with TestStand 4.1.1. I do notice that the AM and PM characters don't seem to be correct in some cases in the generated report however I am unable to reproduce the error you showed in your previously attached screenshot.

Could you please give more details on the Operating System that you are running on?

Thanks!

[Mike_Millhaem]

Here is a screen shot that shows the file name directly before the call to Write Report.  That step will fail with this file name.

This was on a Korean computer, but I see the same error on computers from Japan and Taiwan.

Mike

[Manooch_H]

Hi Mike,

Unfortunately I have still not been able to reproduce this error. I have tried reproducing this on a Windows XP Chinese Simplified Operating System with every form of Chinese Regional Setting as well as on a Windows Vista Japanese Operating System.

Could you create a Measurement and Automation Explorer report on one of the Japanese machines where you see this error? In Measurement and Automation Explorer navigate to File»Create Report and select Technical Support from the report types. This should hopefully give me the exact Japanese operating system you are using so that I may continue trying to reproduce the issue.

Thanks Mike!

[Manooch_H · Accepted solution]

Mike,

Do you have the Recognize Multi-byte Characters option enabled? Please navigate to Configure»Station Options and select the Localization tab. There should be a checkbox for Recognize Multi-byte Characters. Is this box checked? If not, try checking the box and running your sequence file again.

Please let me know the outcome of this test. Thanks!

[Mike_Millhaem]

Hello Manooch,

Enabling Multi-Byte characters did the trick!

Thanks,

Mike