ERROR SolarWinds.Orion.Core.Actions.Utility.WebPageFetcher - FAIL: This session is no longer valid

Question

Hi

Some of my monthly scheduled report failed this month.

Report had to be send with xls and pdf by mail.

User used to run the scheduled report is the admin of solarwinds.

I received the mail with this message : Unable to retrieve url: XXXXX/.../Report.aspx using PDF type.
And no pdf file was attached.
The xls file attached contain a login page with also "The session times out", "Enable cookies to login", "Enable Javascript to login".

My core.businesslayer.log file contain this :

2020-12-01 03:14:23,674 [123] ERROR SolarWinds.Orion.Core.Actions.Utility.WebPageFetcher - FAIL: This session is no longer valid. If you wish to reuse the session later, please consider calling GetCookies to retain the session cookies, then reuse these cookies through HtmlToPdfOptions.Cookies with another session. (4)
EO.Pdf.Internal.k4: This session is no longer valid. If you wish to reuse the session later, please consider calling GetCookies to retain the session cookies, then reuse these cookies through HtmlToPdfOptions.Cookies with another session. (4)
at EO.Pdf.Internal.lr.l()
at EO.Pdf.Internal.lr.a(a A_0)
at EO.Pdf.Internal.lr.a(cj A_0)
at EO.Pdf.HtmlToPdfSession.Dispose()
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, Stream stream, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, Stream stream)
at SolarWinds.Orion.Core.Actions.Utility.WebPageFetcher.GetPdf(String accountId, String url)
2020-12-01 03:14:23,674 [123] ERROR ReportingLogger - Error during fetching pdf document
2020-12-01 03:14:23,674 [123] ERROR ReportingLogger - Error during fetching url: SAVIP-SONDE:8787/.../Report.aspx using PDF type
System.ArgumentNullException: Value cannot be null.
Parameter name: PDF document
at SolarWinds.Orion.Core.Actions.Impl.Email.EmailUrlExecutor.BuildReportingMailMessage(ISmtpClient smtpClient, EmailConfiguration config, ReportingActionContext reportingContext)

So, I supposed my session timed out and pdf cannot be created and so attached to email of course.

But the questions are :

- Why session are sometimes timed out? (because sometimes it works fine)

- How to fix this?

Thanks for your help.

vinay.by · Answer

I am not sure where this session timeout parameter can be set, its always good to raise a vendor support case for such changes.

But then just another query with respect to what we can check, you mentioned this report is scheduled to run at a particular time isnt it? Are lot of reports scheduled at the same time ? I mean you have any other report schedules running at the same time as this schedule of this report.

Alternative Solution: Rather than 2300+ rows can you reduce or break this report into two so that it doesnt cross 1200 rows or so ? This isnt an ideally approach but i am assuming its because of the number of pages that PDF is creating. And yes this error does occur occasionally when there is a load on your Orion - maybe due to long running queries on your DB, we might need to check why so.

mdeneumostier · Answer

It is a monthly report and in xls there is 2730 rows.
Running it manually is OK.

Even there is session timeout in the pdf I'm not sure that is the problem.

Log indicates This session is no longer valid.

I thought that admin user don't log on solarwinds for certains days and so its connection is no longer valid.

But where is the parameter to increase the time?

I can't reproduce this error.

Thanks

vinay.by · Answer

What is there on that report ? Is it report pretty big ? I mean some kind of an inventory report or so which is huge ?

Session timeout generally happens when your Web GUI cannot load that report data completely during conversation into a PDF (Ideally happens when the report has too many rows or if its massive with lot of information on it).

Can you open that Report URL on your Primary Poller ? Login into your Primary Poller, Open IE and paste that link. Just make sure the Report URL loads well on your Primary Poller which is where this action is called from.