Tag Info

New answers tagged

0

Try to recycle the app pool/reset IIS after you have made that setting. Here is another possible solution. The last time I had observed this issue was when the RAM on my dev server was filled up to the brim and the server was consuming a lot of CPU. I would suggest to try and stop unwanted heavy services and processes and check if you can open the site.


0

It works for me. I would like to notice that you should restart the configuration at the begining. if you did just a refresh (by clicking on a refresh button provided), it doesn't work.


1

It sound's like the web applications get a timeout and does not get created correctly. I've had this problem in both production and staging environment, and changing the time-out has worked perfect both times. This is usually because you either have too many Web Applications in your SharePoint Server, or because your SharePoint Server is slow! As part ...


0

for a reason the authentication provider for my web application was changed from NTLM to kerberos. so i modify the Authntication provider to NTLM and now evertthing is working well.


2

Looks like you change the AppPool from IIS. It is highly recommended to update / Change the app Pool Account from SharePoint(central Admin / powershell). central admin > Security > Configure Service Accounts After Changing please perform IIS on all servers. One Most important thing, before changing the account you should make sure new Account should have ...


1

1st thing, sharepoint is not capturing the port 80( their is no hard requirement for it). When you create the SharePoint Web Application, you can select the port number other than 80 and also provide the host header. For Non-SharePoint sites, you can simple create another web site in IIS on a port which is not being used. If you want same host header for ...


1

There should no problem doing this. You can even make SharePoint not use port 80 if you want. When you create a new Web Application in SharePoint you provide the host header and port.


0

As per your description looks like you still have reference old domain's service account... Check the Managed Services account(from Central Admin) and make no old domain account showed here. run the below powershell to remove it.[Remove-SPManagedAccount][1] -Identity DOMAIN\ServiceAcct And Also try to add your service account using this powershell. ...



Top 50 recent answers are included