Re: HSSFR4 utiities

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

The error message seems to be saying that the file isn't a valid Excel 
workbook.  (It references OLE2 stream, which would be a .XLS file, or 
OOXML which would be .XLSX... it says it is neither of these things.)

Could that be what is happening?  A bad file?


On 7/23/2019 10:56 AM, Mohammad Tanveer wrote:
> Scott/RPG team,
>
> We have been using HSSFR4 utiities for a long time without any problem and
> all of  a sudden we see following  errors intermittently meaning sometime
> it works sometimes it doesn't
>   ...
> Message ID . . . . . . : RNX0301
> Date sent . . . . . . : 07/23/19 Time sent . . . . . . : 10:21:37
>
> Message . . . . : Java exception received when calling Java method.
>
> Cause . . . . . : RPG procedure SS_OPEN in program USERUL/HSSFR4 received
> Java exception "java.lang.IllegalArgumentException: Your InputStream was
> neither an OLE2 stream, nor an OOXML stream" when calling method "create"
> with signature
> "(Ljava.io.InputStream;)Lorg.apache.poi.ss.usermodel.Workbook;" in class
> "org.apache.poi.ss.usermodel.WorkbookFactory".
> Recovery . . . : Contact the person responsible for program maintenance t
> determine the cause of the problem.
> Technical description . . . . . . . . : If the exception indicates that th
> Java class was not found, ensure the class for the method is in the class
> path. If the exception indicates that the Java method was not found, check
> 10:24:04 AM
>
> Message ID . . . . . . : RNX0301
> Date sent . . . . . . : 07/23/19 Time sent . . . . . . : 10:32:37
>
> Message . . . . : Java exception received when calling Java method.
>
> Cause . . . . . : RPG procedure SS_OPEN in program USERUL/HSSFR4 received
> Java exception "java.io.IOException: System call error number 3004.■" when
> calling method "create" with signature
> "(Ljava.io.InputStream;)Lorg.apache.poi.ss.usermodel.Workbook;" in class
> "org.apache.poi.ss.usermodel.WorkbookFactory".
> Recovery . . . : Contact the person responsible for program maintenance to
> determine the cause of the problem.
> Technical description . . . . . . . . : If the exception indicates that the
> Java class was not found, ensure the class for the method is in the class
> path. If the exception indicates that the Java method was not found, check
> the method name and signature. If the signature is not correct, change the
>
> Regards