Tag Info

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

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


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

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

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

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

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


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

I'd take a look at the following: Sharepoint 2010 Custom Error Pages I don't think there's a need to do anything, but leave the pages alone in IIS. Place your custom error pages in the custerr directory Edit the web.config file for your webapp(s) Update the customErrors node to include your custom pages Update the httpError node to turn on custom errors ...


3

Event ID 7076 - Office SharePoint Server "Attempted to read or write protected memory. This is often an indication that other memory is corrupt. " "System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ... Event ID 6398 - Windows SharePoint Services 3 NERA-WPWFE1 ...


3

Have you verified there are no other memory issues? You can run something like Memtest to validate it's not the modules. Are there any other related items in the logs, like excessive AppPool Recycles, etc? EDIT MS has a few KB articles: http://support.microsoft.com/default.aspx?scid=kb;EN-US;946517 http://support.microsoft.com/kb/923028 Additionally ...


3

I found that the problem I had that resulted in a 503 was due to the App Pool being set to support 32-bit applications. I went to IIS manager, app pool, advanced settings, and set "Enable 32-bit applications" to "False". This was on a Content App pool, though, not Central Admin.


3

Are you using Visual Studio's Deploy function? If you did, this could be why, as it does a full retract/deploy with reset and the works. if you want a more granular approach just use the Package function and deploy/retract manually using PowerShell (or stsadm if you are totally retro;-)


3

You cannot unless you are using some sort of proxy server such as ISA in between. http://appdev means port 80, while your site is running on port 7777. You can however, create a Url such as http://appdev:7777 to access your site by defining host header.


3

In IIS 6.0, the anonymous user is actually *IUSR_computername*, which is a valid Windows user that is a member of the Guests group.If that user account has appropriate rights, then the action (typically to read the file) is performed. Your concern of hacking the anonymous account is baseless as the anonymous user is already using that account. With ...


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


3

Try to disable the firewalls for both the database server and the sharepoint front end temporarily and try again. Make sure the account you are logged onto and running the SharePoint Config Wizard has proper database access. Also, Are you bindings in IIS Manager linked to the old IP or hostname? Change that and try again. Also view my blog about this: ...


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

I think you have to re-enable the incoming mail service within the CentralAdmin. At least on initial setup it asks you where you have your drop folder or if SharePoint should automatically detect the local SMTP service.


3

Depends on what you mean by sharing, they will be sharing the same website in IIS, the same web.config, the same content database by default, the same web application settings in Central Admin etc etc. You can configure site collections to be under different host headers if you wish. What are your requirements? Would you prefer each customer to be accessing ...


3

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


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

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



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