Hello,
We are seeing portions of text missing from our notification emails using NS 2.0 and the built in SMTP delivery protocol.
The notification looks fine in the MS notifications table -- no missing text in the field that becomes the email body, so it may be a bug in the xsl transform code where the text disappears. Our xslt is very simple and it has been tested. The field is plain text. We run perhaps thousands of "short" notifications through the system each day with no problems.
I can work around the problem by reducing the size of the message from it's original size of 2000 characters to 1600. Nothing in the text looks suspect.
Suggestions?
Thanks,
Marcus
We have not seen this - you might try replacing your XSLT with Noop.xslt that comes with some of our samples. This will cause the XSLT not to do anything. This will help you isolate whether the XSLT is actually the problem. The other thing to try is change the delivery protocol to file - this will let you see the full output that is going out to the delivery provider. If you use both these techniques together you'll see where the trunction is occurring. The last possibility is that the event field is too short for the content and truncation is occuring on insert.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks Lukasz,
Unfortunately, we're not seeing a simple truncation, but rather a portion of the text within the message is missing, text that is not at the end of the notification.
The text is not missing in the notifications table, so it's in the XSLT step or after.
Marcus
|||
Can you post sample text and the part of the XSLT that is supposed to be formatting the text?
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
Here is the incoming text (I've added quotes):
"The OFCM, in conjunction with its Committee for Space Weather, is now supporting a decadal review of the NSWP to quantify and document the progress toward meeting program goals. A committee has been formed to carry out the assessment (Chair: Louis J. Lanzerotti, New Jersey Institute of Technology; Daniel N. Baker, University of Colorado; Tammy E. Jernigan, Lawrence Livermore National Laboratory; Delores J. Knipp, U.S. Air Force Academy; Ray A. Williamson, George Washington University; S. Pete Worden, University of Arizona; Robert J. Rizza, Executive Secretary, Office of the Federal Coordinator for Meteorology). The Committee is gathering input from the broad space weather research and applications communities in the
Thank you,"
Here is the generated email message (I've added the quotes again). Note the missing text from the last sentence of the paragraph, before the "thank you":
"The OFCM, in conjunction with its Committee for Space Weather, is now supporting a decadal review of the NSWP to quantify and document the progress toward meeting program goals. A committee has been formed to carry out the assessment (Chair: Louis J. Lanzerotti, New Jersey Institute of Technology; Daniel N. Baker, University of Colorado; Tammy E. Jernigan, Lawrence Livermore National Laboratory; Delores J. Knipp, U.S. Air Force Academy; Ray A. Williamson, George Washington University; S. Pete Worden, University of Arizona; Robert J. Rizza, Executive Secretary, Office of the Federal Coordinator for Meteorology). The Committee is gathering input from the broad space weather research and applications communities in the United States, including operations and users and will perform a comprehensive review of the program. This can best be achieved with very strong community participation. Therefore, all those interested in the NSWP are encouraged to complete the questionnaire (please c Thank you,
Thank you for using the SEC Product Subscription Service. If you would like to remove a product subscription or update the personal information in your account, go to: https://pss.sec.noaa.gov. For problems, contact: mailto:secproducts@.noaa.gov."
Here is the the Application.xslt:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="text"/>
<xsl:template match="notifications">
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="notification">
<xsl:value-of select="message"/>
Thank you for using the SEC Product Subscription Service. If you would like to remove a product subscription or update the personal information in your account, go to: https://pss.sec.noaa.gov. For problems, contact: mailto:secproducts@.noaa.gov.
</xsl:template>
</xsl:stylesheet>
|||
Marcus -
I've never seen the problem you're describing here.
How did you capture this text? Did you copy it out of an email? Or from a file?
Have you tried sending the notifications through noop.xslt as Lukasz suggested?
If 200 notifications go out with 2000 characters each, do all have the same text missing?
--
Joe Webb
SQL Server MVP
http://www.sqlns.com
~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811
I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)
Joe -
This text was copied directly from an email notification.
I have not tried noop.xslt yet, as it would require setting up a test string -- I cannot "play" with the production string. :)
All notifications with this text exhibit the problem. And again, the text is fine in the MS notifications table.
Sounds like I need to set up a test service - ugh.
Thanks,
Marcus
|||CLUES!
I have tried using the noop.xslt and the text is still missing.
But, if I switch to the File protocol it works! No missing text.
So perhaps the bug is in the SMTP delivery protocol.
Thanks,
Marcus
|||Lukasz Pawlowski, are you there? I was hoping for a response to this, as you asked for additional information.
Thanks,
Marcus
No comments:
Post a Comment