Xml Parsing Issue in sql job

Question

I am getting an error while executing the query in a SQL Server job. But if I execute it directly, it works fine.

Executed as user: NT AUTHORITY\SYSTEM.

XML parsing: line 10, character 33
Unexpected end of input [SQLSTATE 42000] (Error 9400). The step failed.
SQL Severity 16, SQL Message ID 9400

Code:

    declare  @URL VARCHAR(max) 

    set @url = 'http://www.spa.gov.sa/english/rss.xml'

    declare  @xmlT TABLE (yourXML XML)
    DECLARE @Response nvarchar(max)
    DECLARE @XML xml
    DECLARE @Obj int 
    DECLARE @Result int 
    DECLARE @HTTPStatus int 
    DECLARE @ErrorMsg nvarchar(MAX)

    EXEC @Result = sp_OACreate 'MSXML2.XMLHttp', @Obj OUT 

    EXEC @Result = sp_OAMethod @Obj, 'open', NULL, 'GET', @URL, false
    EXEC @Result = sp_OAMethod @Obj, 'setRequestHeader', NULL, 'Content-Type', 'application/x-www-form-urlencoded'
    EXEC @Result = sp_OAMethod @Obj, send, NULL, ''
    EXEC @Result = sp_OAGetProperty @Obj, 'status', @HTTPStatus OUT 

    INSERT @xmlT ( yourXML )
    EXEC @Result = sp_OAGetProperty @Obj, 'responseXML.xml'--, @Response OUT 


    INSERT into Tlb(discp, tit, datee, linkk)

--below statement creates problem when i remove this statement it works fine everywhere

        SELECT   
            N.C.value('description[1]', 'nvarchar(max)') discp,   
            N.C.value('title[1]', 'varchar(999)') tit,
            N.C.value('pubDate[1]', 'varchar(99)') datee,
            N.C.value('link[1]', 'varchar(999)') linkk
        FROM
            @xmlT 
        CROSS APPLY 
            yourXML.nodes('//channel/item') N(C)

Answer 1

Your code how to get a flat file via URL works fine...

After this

INSERT @xmlT ( yourXML )
EXEC @Result = sp_OAGetProperty @Obj, 'responseXML.xml'

... your declared table variable contains one row with a valid XML.

"line 10 character 33" might point to

1. totally cut due to a to small varchar variable somewhere in between
   • in my test the line 10 doesn't even have so many characters...
   • Might be, that the content of the file varies, but the first 10 lines seem to carry quite steady data...
   • Try to change your @xmlT to store a VARCHAR(MAX) and do a pure SELECT. The file comes as pre-formatted, "pretty" xml... So: the reported line and character numbers should be OK...
2. invalid XML (e.g. missing closing tag)
   • If the XML is invalid from the source it should not make a difference how you call it...
3. invalid character
   • Might be, that there is some problem with the encoding

My favorite is 1): As the reflected error speaks about "XML Parsing - Unexpected end of input" I'd suppose, that the XML you read is cut somewhere...

Find out

• if you get the same error independing of the XML's content.
• if you get it always and always with the same line and character number

Answer 2

Do you know about the Sql Agent TEXTSIZE?

Specify directly in the procedure TEXTSIZE 512 and exec, you'll get the same error in this case

SET TEXTSIZE -1

OR other value, i use -1 for unlimited size by default sql server textsize on the SQL Agent is 512