Hot answers tagged

9

"Keyset does not exist" means you need to give your web application pool identity account access to your certificate. Do this in the Certificates Snap In.


8

An application pool is a collection of websites running as a single process, with a single identity. You can have multiple websites running under a single application pool, but you can not have a single website running in multiple application pools. Splitting websites over application pools allows more rigid security between the sites, as well as preventing ...


6

1) Because the Microsoft SharePoint Foundation Web Application service is running on your App Layer. Go to Central Admin -> Manage services on server, select your App server, then stop this service. 2) DNS entries are the way to target a WFE for end user access. End users will only go to the WFE DNS is pointed at (or if DNS is pointed at a VIP, to the ...


6

According to Microsoft: You cannot use the period character at the end of a site name, a subsite name, or a site group name. You cannot use the period character at the end of a folder name. You cannot use the period character at the end of a file name http://support.microsoft.com/kb/905231/en-us Are you looking for a way to by-pass this directive?


5

There is a fine line of difference between IIS Reset and Web Application Pool recycle when it comes to SharePoint Deployments. IIS Reset does 2 important things concerning SharePoint - It recycles all your application pools at one go and clears the memory objects. It reloads all dlls from the GAC(global assembly cache) in the farm servers. Web ...


5

Problem resolved after I stop those Windows Services! - Service Bus Gateway Service Bus Message Broker Windows Fabric Host Service


5

SharePoint 2010 requires .NET Framework 3.5 SP1 Agreed with holding back from using .NET 4 until WWF supports it.


5

Whatever ID the application pool is running as needs 1) proper permissions to the config database (see this info from Microsoft) 2) inclusion in the proper security groups on the local machine (these usually start with WSS_) and 3) permission to go through the proxy using a windows credential rather than a forms-style login. If you are in a large corporate ...


5

You also need .NET Framework 3.5 installed. Check under features that its available. If not, follow the guide How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2


4

# Load IIS module: Import-Module WebAdministration # Adds registered Microsoft SharePoint PowerShell snap-ins Add-PSSnapin "Microsoft.SharePoint.PowerShell" # Get SharePoint Web Application $app = Get-SPWebApplication http://site/ # Get pool name from web application: $poolName = $app.ApplicationPool.Name # Recycle the application pool: Restart-WebAppPool ...


4

I haven't actually tried this myself in 2010, but I didn't think it was necessary to edit the web.config file manually these days. AFAIK, SharePoint Foundation does not support the custom error pages that are typically used in IIS sites. Check out this post by Todd Carter. You could use a feature receiver to deploy a custom error page into the SharePoint ...


4

Is the JScript running server or client-side? If server-side, SharePoint's safe mode parser will block the request. This is SharePoint's protection mechanism to deal with the fact that end users can add content to SharePoint pages. If client-side, it could be the same issue, I'm not 100% sure. Assuming it is indeed the safe mode parser which is preventing ...


4

The workflows and such are based on the .NET 3.5 framework SP1, so I would be hesitant to try to use .NET 4 until it is supported.


4

Check whether your credentials for your domain has changed and you did not apply it. If this is the issue, change the following: - Open app pool advance setting > Identity > custom account > Set (give user name and passowrd)


4

There should be no problem in moving the logs, but if you want to move the entire inetpub folder including the homedir of the SharePoint Web Application then you should do it before you create the Web Application or you'll have to delete the existing Web Application create them again using the new homedir and attach the databases. YOU SHOULD NOT JUST MOVE ...


4

it should be on the lines of: <add name='MyHttpModule' type=MyAssembly.Global, MyAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=87b3480442bff091' /> name = give it a name; type = namespace.classname , namespace version = is the version found in project -> properties -> application -> assembly information culture = neutral ...


4

this could be faulting at several stages! first place to look even tho you migh of already is look at the app pool, start or recyle "sharepoint webservices root". now go under sites and start "SharePoint Web Services" right click, manage and then click start or recycle. now do an iisreset. if that doesnt work, you could test this one out! Moving one ...


4

No. IIS is only for serving up webpages. It should not be part of SQL Server, which uses tcp/ip, or named pipes to communicate with other servers.


3

As mentioned in the blog post you references, it simply needs to happen after the response has been created (i.e. the page content) and before the UpdateRequestCache event. The blog post shows an idea example of using the PostRequestReleaseState event. This happens almost immediately after the response is generated. public void Init(HttpApplication app) ...


3

In IIS8 (which you are using, if you are using SharePoint 2013) it uses ASP.NET 4.5. The application events are different from 3.5 and are raised in the following order: BeginRequest AuthenticateRequest PostAuthenticateRequest AuthorizeRequest PostAuthorizeRequest ResolveRequestCache PostResolveRequestCache After the PostResolveRequestCache event ...


3

WOW, thats alot of lazy changes to IIS. Stuff that i wouldnt recommend.... if you need to do it than do one thing at a time or atleast test it on a test server first! i understand you might have 100's of web apps and app pools but doing multiple changes for all webapps is crazy --- unless well tested on just one webapp to start with!! as for the issue: ...


3

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 ...


3

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 ...


3

I had faced the similar issue when i was working with STS. The reason you get the error is because there is no trust being established between the Sharepoint and STS . If i am not wrong you might be getting the error at the below lines of code :) This is definitely a certificate issue. SecurityTokenService sts = new ...


3

Max, check the version of .NET you have installed. Sharepoint 2010 requires .NET 3.5 and does not support 4.0. "SharePoint 2010 does not support access from .NET Framework 4 or being run in a .NET Framework 4 app domain. If you must support the .NET Framework 4, we recommend that you develop a web service that uses the .NET Framework 4 and then connect to ...


3

No, this will not work if you only do that. If you make all of the configuration changes in IIS (on all of the WFE servers) to add the new binding to the IIS site, but without telling SharePoint about it then you'll get a SharePoint monster which sometimes will kind of work. Depending on how you navigate to the first page it'll show that using the https ...


3

Sounds like your IIS bindings are screwed. Run the SharePoint Configuration Wizard - it'll reconfigure the IIS web application for your to the SharePoint Web App configuration that it knows about.


3

This seems to be an issue with the powersheel_ise.exe and once I close and reopen it, it seems to be fine. Here's a link I found.


3

A port is a port is a port. SharePoint processes them all the same but any port other than 80 (for http) or 443 (for https) will need to include the port number in the url. That's about the only difference.


3

The short answer is: "No, it does not impact your ability to create other web applications which are NOT targetting SharePoint." Some Facts: You can still create ASP.NET Applications not targetting the SharePoint AS LONG AS you work with a new physical IIS web site which is not used by SharePoint. You can also create ASP.NET MVC application as long as ...



Only top voted, non community-wiki answers of a minimum length are eligible