• dweil - Friday, April 13, 2018 12:16 PM

    I'm still waiting on our email administrator.
    However, I did find the problem and the fix.
    Not that the error messages gave any indication as to what the problem was.
    I tried subscribing to the report with  different parameters and time periods.
    Mostly it worked but not always.

    The issue was with the data.
    One of the varchar fields that was coming from sqlserver has a "line feed period linefeed" in it. ( hex 0A 2E  OA).
    The abnormal code only caused our exchange server grief but was not visible when manually bringing up the report.
    I wrote some code in the stored procedure to strip out carriage returns and line feeds from those fields.
    I'm guessing one of our users copied some text from a web screen to the application that uses that database.

    Thanks for all your help

    Can you post the "stipping out" code that you settled on?

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)