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

Question

Question

Installing WebLink with SharePoint 2003

asked on July 28, 2016

A client of ours is attempting to install Weblink on server that already has SharePoint 2013 installed on. We are encountering error messages when attempting to get to the default page.

 

Does this article from 10 years still apply (https://support.laserfiche.com/kb/1011115/enabling-weblink-to-function-when-microsoft-sharepoint-is-installed-on-the-same-computer-)? Any known issues with WebLink & SharePoint sharing the same server?

 

Regards

0 0

Replies

replied on July 28, 2016

There isn't enough information about how the websites are setup in IIS, but assuming this was a default install of IIS that had the Default Web Site with HTTP port 80 bound to it, then when you install SharePoint on that web server, it will create a new site for SharePoint and take over port 80. This then forces the Default Web Site to be stopped.

If you had then installed WebLink and the web application was created under the Default Web Site then you won't be able to get to WebLink since the site would be stopped. Try using a different port for HTTP for the Default Web Site and then make sure the site can be started. Then try going to http://server:port/weblink  and see if the page loads.

1 0
replied on July 29, 2016

The typical WebLink installation was performed which installed WebLink under the Default  Web Site. The Default Web Site is not running as SharePoint has taken over port 80 and no port is assigned to the Default Web Site. Preferably, Client would like to run WebLink under the SharePoint Site.

A virtual directory was created under the SharePoint and the physical path pointed to the WebLink Web Files directory. This gives a 500.19 error message with message indicating that there is duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined in the web.config file.

 

 

0 0
replied on July 29, 2016

Make sure that the Application Pool you manually created for WebLink has the same settings at the one the installation created.

0 0
replied on August 1, 2016

I didn't create any new Application pool. The app pool created by WebLink installation is still there. Did we need to create a new application pool for the Weblink virtual directory (created under the SharePoint site)?

0 0
replied on August 2, 2016

Anyone?

0 0
replied on August 2, 2016

WebLink is probably inheriting unexpected settings from the SharePoint site.  You could try making the changes to the web.config file that are causing the errors, but I don't know if in the end you'll end up with a working WebLink instance.  I can't find any SharePoint documentation that suggests installing a web application on its site is a supported operation.

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

Sign in to reply to this post.