You are viewing limited content. For full access, please sign in.

Question

Question

Download Report error in Forms in DMZ setup

asked on November 21, 2019

Hi Everyone,

 

I have a client that is having issues downloading reports from their external Forms server in their DMZ that is set up with the DMZ configuration. The services on the external forms server are all turned off and the config files point to the internal forms server. 

 

On the internal forms server, users are able to download reports without issues. When they log into the external forms server however, they get an error saying "Laserfiche Forms has encountered a problem. The requested report is no longer available". We log into both as the same user, and this is the only thing that we can see that is having an issue.

 

Has anyone else run into this, or know if this may or may not be a supported use for the DMZ setup? Any info would be greatly appreciated. smiley

 

Thanks!

Cody

0 0

Answer

SELECTED ANSWER
replied on November 25, 2019

Hi Cody (and John-Paul),

I checked internally and found this is a known bug with Forms DMZ setups. Fortunately, we've already fixed it in Forms 10.4.2! It will ship with Laserfiche 10.4.2, currently targeted for mid-December 2019.

Long story short, Forms Routing Engine currently returns a local file path for the report file on the internal server. On the DMZ Forms instance, said local path obviously does not have the report file, so it throws that "Not found/available" error. The fix replaces the "local path" method with simply streaming report files between Forms instances instead.

2 0

Replies

replied on November 21, 2019

amazing timing!  I also just discovered the same issue and we are on a DMZ setup.  I was able to generate the report as long as I logged in to the server side.  The external facing log in (on the website server) produced those same errors you mentioned.  Would love to hear if there is a fix!

0 0
replied on November 21, 2019

Cody and John-Paul,

Are either of you able to find and provide the full error message + stack trace from an Event Log? Those are greatly helpful in any troubleshooting efforts. I'd look in the Forms and Windows>Application logs to start.

0 0
replied on November 25, 2019 Show version history

Hi Samuel,

 

The only thing we could find for errors is below. I've changed a few values for client privacy, being the domain name and the computer name, but everything else is the same. 

 

 

Log Name:      Laserfiche-Forms-App/Operational
Source:        Laserfiche-Forms-App
Date:          11/22/2019 8:37:48 AM
Event ID:      60003
Task Category: GeneralError
Level:         Error
Keywords:      Session0,Session1,Session2,Session3
User:          DOMAIN\laserfiche.sup
Computer:      server.domain.org
Description:
[500]: The requested report is no longer available
Function: Error
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Laserfiche-Forms-App" Guid="{98141CA4-660B-51C6-66B4-EC37F5B2FD87}" />
    <EventID>60003</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>5531</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000f00000000000</Keywords>
    <TimeCreated SystemTime="2019-11-22T16:37:48.882482500Z" />
    <EventRecordID>28028624</EventRecordID>
    <Correlation />
    <Execution ProcessID="5972" ThreadID="4736" />
    <Channel>Laserfiche-Forms-App/Operational</Channel>
    <Computer>server.domain.org</Computer>
    <Security UserID="S-1-5-21-1612364073-692612332-1123090905-16058" />
  </System>
  <EventData>
    <Data Name="message">The requested report is no longer available
Function: Error
</Data>
    <Data Name="internalErrorCode">500</Data>
  </EventData>
</Event>
0 0
SELECTED ANSWER
replied on November 25, 2019

Hi Cody (and John-Paul),

I checked internally and found this is a known bug with Forms DMZ setups. Fortunately, we've already fixed it in Forms 10.4.2! It will ship with Laserfiche 10.4.2, currently targeted for mid-December 2019.

Long story short, Forms Routing Engine currently returns a local file path for the report file on the internal server. On the DMZ Forms instance, said local path obviously does not have the report file, so it throws that "Not found/available" error. The fix replaces the "local path" method with simply streaming report files between Forms instances instead.

2 0
You are not allowed to follow up in this post.

Sign in to reply to this post.