• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

Valence 6.3 vvOut_execSQltoSS 500 HTTP error on XLSX download

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Valence 6.3 vvOut_execSQltoSS 500 HTTP error on XLSX download

    Hi all,
    my customer switched in portal admin to xlsx template and get a 500 HTTP response upon download the Excel Report from self written native app. I just check the backend source code. They use vvOut_execSQLtoSS with vvOut.downlod='1'. If i switch back to old XLS the download works. Can someone help to solve this issue?
    Thanks in advance
    Boris?

  • #2
    Hi Boris,

    Do you see anything related to the .xlsx generation/download attempt being logged in the Errors app? Or any Valence jobs stuck in a MSGW state?

    If not, do you see the not-yet-downloaded .xlsx file sitting in the IFS temporary files path? The temporary file path is likely /temp/ in the Valence instance IFS directory, unless it has been overridden in Portal Admin > Settings > Hidden Settings > Temporary Files Path (or Portal-Administration > einstellungen > Verborgene Einstellungen > Pfad für temporäre Dateien).

    If you don't see the file in the temp directory, perhaps you could confirm the xlsx generation functionality itself is working by logging into a 5250 session and trying this:
    • ADDLIBLE VALENCE6 (or whichever libary you're using)
    • CALL EXSS01 PARM('1')
    EXSS01 will call the vvOut_execSQLtoSS service program procedure to generate a simple Excel spreadsheet file called "exSS01 Sample 4.xlsx" located in that Valence instance's temp directory.

    If that works, perhaps you could try adjusting the routine to mimic the download your customer is attempting. Perhaps the problem lies within the data.

    If you do see the file, then I suspect there's something interfering with the .xlsx download from the back end, perhaps a unique network restriction or something like that.

    Let us know what you find out.

    Comment

    Working...
    X