In this installation of the mailbag, we will answer questions on how to help us help you when writing an email for technical support and what to do with missing files which are not actually missing. |
Question
When I sent in an email for technical support, I was asked to provide more information which I gladly did. In general, what type of information should I include in my email requesting technical support?
- What Should I Say
Answer
Dear What Should I Say,
Recently, a number of people have expressed interest in knowing what information should be included in an email requesting support. Because of this, the Mailbag writer requested that some information be provided on this topic by the Technical Support Team. In response to this request, the Technical Support team has developed its "Tips for Requesting Technical Support: How to Put Your Issue on the Fast Track to being Resolved".
Missing Files on Import
Question
On import, I am getting a message that some type of XML file cannot be found. Is there a problem with installation or the update?
- Missing Something
Answer
Dear Missing,
A number of people have reported a similar problem. The error in the File Import Validation Report probably looks similar to the following screen shot.
If this is the type of message you received, there is nothing wrong with your installation of the Client Tool.
Instead, the problem is that the Version tag in the file you are attempting to import is incorrect. The picture below shows the Version tag circled in a detail of an XML file.

The Version tag is near the top, and it is used to identify which version of the XML schema should be used to validate the XML file. The value in that tag must match an accepted version number. Currently, the production version of the Client Tool and the CTP will accept a value of "1.0" for all three XML file types: monitoring plan, QA, and emissions. As of release 2 of the production Client Tool and CTP2, the Version value for an emissions XML file can also be "1.1".
Any other value than the accepted values will result in this file import error message. The message should really read, that the value in the Version tag is not a valid value. However, like many of the XML validation messages, this message is produced by the proprietary Microsoft software which validates the XML, and the message cannot be changed. What the message is trying to say is that an XML schema for the version indicated by the value in the Version tag could not be found.
To fix the problem, you should go back to your DAHS vendor and ask them to modify what value is put in the Version tag.
If you have a question for the ECMPS Mailbag, simply send an email to ecmps-testing@pqa.com.
Labels: Mailbag
In this installation of the mailbag, we will answer questions on how to help us help you when writing an email for technical support and what to do with missing files which are not actually missing.
0 Comments:
Post a Comment
<< Home