Jump to content
We've recently updated our Privacy Statement, available here ×

BrandonL

Members
  • Posts

    1
  • Joined

  • Last visited

BrandonL's Achievements

Newbie

Newbie (1/14)

  • One Month Later
  • First Post Rare
  • Week One Done

Recent Badges

0

Reputation

  1. After upgrade to 9.0 from 8.1 our larger reports are failing towards the end of processing with only a fairly general error message. Invoke-RestMethod : resource.not.foundResource 6ea06350-e6ee-4671-9725-de03c7983f62 not found.6ea06350-e6ee-4671-9725-de03c7983f62 At D:\Jaspersoft\bin\JasperReports.ps1:76 char:3 + Invoke-RestMethod -Uri $uri -Method GET -Headers $headers -OutFile ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand I'm sort of at a loss for how to troubleshoot the issue - wondering if this resource name "6ea06350-e6ee-4671-9725-de03c7983f62" is something I can identify/investigate/troubleshoot etc? Anyone else seeing similar issues. My assumption at this point is either process is failing at the end of the query when it hits a temp space/sort space limit on the DB or its failing on the Jasper side trying to convert the query results into report image format (pdf). (Is there a config setting that allocates or throttles RAM consumption I may need to increase?) Was considering submitting this as a case and/or searching the Community site or posting this there. Saw this event was planned for tomorrow and decided I'd try that first..... Thanks!
×
×
  • Create New...