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

Question

Question

Web Access not working in SharePoint 2013 server

Web Client Integrations
Updated June 30, 2017
asked on June 3, 2014

Hello,

 

I have lfs, web access, and sharepoint 2013 installed in the same box. I am able to use the sharepoint admin portal but Web access pages are not loading. I can see the virtual directory installed in IIS, changed the port to 81 , still it didnt work. Security looks good and it has access to application files.

 

I just wanted to know if someone experienced this sort of issue.

 

 

 

0 0

Answer

APPROVED ANSWER
replied on June 3, 2014

If http://localhost:81 doesn't work, then the issue is with the Default Web Site itself or how it's configured. If the web site itself isn't functional, then the Laserfiche web application (Web Access in this case) won't be accessible.

 

Please address any issues with the web site first and make sure that is functional before proceeding with trying to use Web Access.

1 0

Replies

replied on June 3, 2014

Are you just using the Default Web Site in IIS with http binding to port 81? If you go to http://localhost:81 in a web browser, do you see the default page for the default web site?

0 0
replied on June 3, 2014

Alex,

Yes, under the default site the site bindings are set to port 81, restarted IIS, and tested the following URLs, did not work.

 

1. http://localhost:81

2. http://localhost:81/laserfiche/configuration/configuration.aspx

3. http://192.168.1.70:81/laserfiche/configuration/configuration.aspx

4. http://sp_dev:81/laserfiche/configuration/configuration.aspx

0 0
View 6 previous replies
APPROVED ANSWER
replied on June 3, 2014

If http://localhost:81 doesn't work, then the issue is with the Default Web Site itself or how it's configured. If the web site itself isn't functional, then the Laserfiche web application (Web Access in this case) won't be accessible.

 

Please address any issues with the web site first and make sure that is functional before proceeding with trying to use Web Access.

1 0
replied on June 3, 2014

Because of the port conflict with SharePoint, the default site isn't running initially.  After you change the port you have to explicitly start the site, which people often forget to do.

1 0
replied on June 30, 2017

hi, we're running into a very similar issue. we're installing WA on the default website on port 80, not knowing that the customer also has their own website on port 80. we then changed WA to port 81, but WA doesn't startup or load.

the reason for this is because the service for the default website is still stopped. we tried to manually restart it, but there's no option. restarted the WWW service and no luck. even restarting the server yields no solution. having the customer changing their website to port 81 is not an option. 

any bright ideas on how to get WA to work in this situation?

0 0
replied on June 30, 2017

Are you saying that the "Start" button under "Manage Web Site" is disabled or missing?

0 0
replied on June 30, 2017

yes, it's grayed out

0 0
replied on June 30, 2017

Are "stop" and "restart" enabled then? If so, then it means the site is actually running/started.

In the web browser, what happens when you try going to http://localhost:81 ?

0 0
replied on June 30, 2017 • Show version history

i may be confused. but this is what we got when we try to manually start it now. we tried deleted and re-created the default the conflicting website, but that still didn't work. rebooted machine still didn't work. it looks like the server still thinks port80 is still being used by another application.

0 0
replied on June 30, 2017

Can you check the http port binding for the default web site? You had mentioned using port 81 in your initial post but I'd just like to confirm that. If the default web site has http bound to port 81, then can you confirm that no other site is using a protocol bound to that same port and already running? Once confirmed, try starting the web site again.

If further assistance is needed, can you get a screenshot showing the bindings for the default web site as well as the other web site that's already running?

0 0
replied on June 30, 2017

i got it resolved. looks like the website service didn't like it when there are 2 port bindings. to get the service to start again, i had to remove port 443. then start the service. then had to add port 443 to the Site Binding.

 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...