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

Question

Question

Weblink HTTP error 500.19/Object reference error

asked on October 3, 2014

When trying to access the http://<servername>/weblink8/ link I receive an HTTP error 500.19. The error points to a duplicate instance of adding the Welcome.aspx page to the default documents(located in the web.config for Weblink, see screen shot). Upon removing this entry from the web.config I receive an "Object reference not set to an instance of an object" error when trying to load the page(see screen shot). Trying to access http://<servername>/weblink8/login.aspx or http://<servername>/weblink8/welcome.aspx results in the same error.

 

I need to access the configuration pages to update default columns and layout of the Weblink site. The public facing Weblink loads and works correctly.

 

Environment is Windows Server 2008R2 SP1 64bit and IIS7(version 7.5.7600.16385)

http500.19.png
object_reference.png
http500.19.png (45.59 KB)
0 0

Replies

replied on October 10, 2014

The 500.19 issue for Thomas was resolved by going through the Weblink configuration utility for their publicweblink/weblink8 site.

1 0
replied on October 6, 2014 Show version history

Since you have a 64 bit system, you will need to check and apply this kb: https://support.laserfiche.com/KB/1012684 

0 0
replied on October 7, 2014

The original error is 0x800700b7 which the KB does not reference. The second problem after "resolving" the first error does not list any error codes. 

 

In the KB it says to check scenario 6 in order to accomplish the following: See Scenario 6 for details on workarounds to either disable the XPress compression scheme, configure IIS to only load the 64-bit version of the module for 64-bit application pools, or to use a 32-bit version of the compression module.

 

The Xpress compression scheme is not installed. The IIS app pool is set to integrated and 64 bit(32bit apps are not enabled). The compression module file "suscomp.dll"does not exist on the system in either 32bit or 64bit form. It also talks about adding preconditions to module entries which I am not sure which modules to apply them to.

0 0
replied on October 7, 2014

For the 800700b7 issue, please review this MS article: http://support2.microsoft.com/kb/942055

0 0
replied on October 7, 2014

I feel as I might not be explaining the situation correctly.

I tried to access the "http://<servername>/weblink8/" link, I received an HTTP error 500.19 - 0x800700b7 in Internet Explorer.

The error points to a duplicate instance of "<add value="Welcome.aspx" />". This is being set elsewhere in IIS so the entry which is located in the web.config for Weblink is unnecessary. See screen shot in the intial post.

I edited the web.config in the "C:\Program Files\Laserfiche\WebLink 8\Web Files" folder. I commented out the line "<add value="Welcome.aspx" />" which is located under <defaultDocument>.

I saved the changes to the web.config file.

 

After making the changes I tried loading the "http://<servername>/weblink8/" page again. Now I receive "Object reference not set to an instance of an object" error when trying to load the page(see screen shot in initial post). Trying to access "http://<servername>/weblink8/login.aspx" or "http://<servername>/weblink8/welcome.aspx" results in the same error.

I also attached a copy of the Windows Event Viewer entry created when the page tries to load(event_viewer_entry.txt).

 

 

I tried some of the fixes provided by "https://support.laserfiche.com/KB/1012684" with no change in behavior. Those fixes seem to be for a different problem all together.

0 0
replied on October 7, 2014 Show version history

To make sure it is not something as simple as a corrupted Welcome.aspx page, please uninstall Weblink, delete the Weblink installation directory and reinstall it.

0 0
replied on October 7, 2014

I will schedule downtime and try this. I forgot to mention this is Weblink 8.2.2

0 0
replied on October 8, 2014

I was able to re-install Weblink 8.2.2 during a maintenance window last night. I am experiencing the same problems with the new install.

0 0
replied on October 8, 2014 Show version history

Did you modify the config file and remove the <add value=> entry
as suggested by the MS kb http://support2.microsoft.com/kb/942055

0 0
replied on October 8, 2014

Yes, I made the same configuration changes as my prior post as I had received the same errors.

0 0
replied on October 9, 2014

Please open a case with Support.

0 0
replied on October 9, 2014

Case 163206 opened. Thank you for your time.

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

Sign in to reply to this post.