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

Question

Question

WebLink/ASP.NET Error

asked on August 14, 2014

I've got an in-house web application that generates a PDF and uses RA to create a document and attach the PDF as an electronic document. Then it takes the EntryID from that document and builds a WebLink URL and opens that in a new tab. The problem is that many times WebLink will show the following error:

 

 

If I manually browse to the document in WebLink it works just fine. In fact, if I take a browser window that's currently looking like the above screenshot and refresh it after I've manually touched the document, it starts working as well.

 

The error is actually an ASP.NET error that occurs when an application tries to specify a relative path that is above the root of the application.

 

This instance of WebLink is 8.2.1.

1 0

Answer

SELECTED ANSWER
replied on August 14, 2014 Show version history

Have a look at this answer to see if it doesn't resolve your issue 

 

https://answers.laserfiche.com/questions/59028/Weblink8-Browsingaspx-Error--CANNOT-OPEN-ELECTRONIC-DOCUMENTS

 

you may need to change the link to the following in order for this to work if the above answer does not:

 

https://xxxxxxxx/weblink8/ElectronicFile.aspx?docid=483610&dbid=0

 

0 0
replied on August 18, 2014

Ok, I finally got a chance to test this properly. It appears to work. Can anyone explain why this works?

0 0
replied on August 19, 2014

I have a suspicion that it's due to the Intelligencia URL Rewriter that Laserfiche WebLink uses along with coding issues in WebLink. Classic Mode  works directly with ISAPI extensions while Integrated Mode works directly and is tightly integrated with the ASP.NET request pipeline.

 

For example this URL will not be processed by the URL rewriter:

 

"https://xxxxxxxx/weblink8/ElectronicFile.aspx?docid=483610&dbid=0"

 

but the one you were having troubles with is processed by it.

 

By the way, is this WebLink installation running on IIS 7 or above?

2 0
replied on August 19, 2014

It's on 7.5. Any other issues with running Classic mode? I'm not inclined to move my primary WebLink instance over when it's working just fine as it is. It's probably safer just to use the URL sample you've posted.

 

Thanks!

0 0
replied on August 19, 2014

I personally have not seen any performance issues when switching to classic mode.

0 0

Replies

replied on December 18, 2015

If anyone else comes across the "Cannot use a leading .. to exit above the top directory" error when using the REST-style URL, the problem was identified in SCR:77939 and fixed in Hotfix 1013039.

It has been rolled into 8.2.2 and 9.x releases.

1 0
replied on August 15, 2014

Hi Devin, 

 

If your question has been answered, please let us know by clicking the "This answered my question" button on the response.

 

If you still need assistance with this matter, just update this thread. Thanks!

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

Sign in to reply to this post.