Redwood JGETFILE error on file transfer

[former_member641025]

• Hi,

  We have recently decided to try and output spool files from Redwood to one of our selected process servers, This is so our customers can access the spool files as due to their larger size we are unable to email them out.

  We are using the jgetfile tool as advised by Redwood, for some spool files it works but for others we get error (255) or on a different process server we get error (2147483647). The file appears partially copied but doesn't finish leaving the file as a .PROGRESS file type. The same spool always failsin the same place but this is different for every spool (i.e. file sizes, characters in files are all different)

  looking at the Windows event log on the process server it states that the agent is crashing, please see below:

  Faulting application name: jgetfile.exe, version: 9.1.3.0, time stamp: 0x5ba4040b
  Faulting module name: jgetfile.exe, version: 9.1.3.0, time stamp: 0x5ba4040b
  Exception code: 0xc0000005
  Fault offset: 0x0000b711
  Faulting process ID: 0x31bc
  Faulting application start time: 0x01d4ce75999f7caa
  Faulting application path: C:\Program Files (x86)\Redwood\agent\9_1_3_20180920_17\bin\jgetfile.exe
  Faulting module path: C:\Program Files (x86)\Redwood\agent\9_1_3_20180920_17\bin\jgetfile.exe
  Report ID: 94dd7281-6862-4eed-b500-5a63df2ed2ac
  Faulting package full name:
  Faulting package-relative application ID:

  I have already tried:

  Different process server

  trying to remove spool and log file limits on the process servers

  removing and reinstalling the agent

  Redwood is currently on version 9.1.3.1

[gmblom · Accepted solution]

Hello,

As this looks like a binary core dump I can unfortunately not more then suggest to raise an incident. Ideally you can also supply the spool file(s) that are causing the issue.

Regards Gerben

[former_member641025 · Accepted solution]

Hi Gerben,

Thanks for your quick response.

I was worried it might be something like that, You wouldn't possibly know any alternative methods I might be able to use until SAP can take a closer look at this?

Regards Luke