Hot answers tagged iis
7
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 ...
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
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
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 ...
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
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
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
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
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
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 ...
2
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.
2
Recycling the application pool can help, but it has a pretty big impact on the end users. I tried doing this in one environment years ago where there just weren't sufficient resources.
It sounds like you have a pretty large server, but what is the general layout of the farm? Would it be possible to isolate a set web front end not behind the load balancer ...
2
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
...
2
Does your app pool account have access to the networked information?
It's worth checking IIS log files to see exactly what's being requested.
A tool such as SysInternals Procmon is very useful for determining what access problems are occurring within an application. I'd recommend firing it up when you make the request and seeing what context the content ...
2
Use an utility like Windows Service Monitor to visually track which of the required services (including SQL Server) are up and running. Your error is frequently due to SQL Server (as mentioned by Deepu above).
Also make sure that the required SharePoint service accounts have the appropriate access to other installed resources. Good post about it here from ...
2
First, to have sharepoint connect to your SQL Server instance again, create a SQL alias by running the following command:
cliconfg
Create a SQL alias (2nd tab) that has the old server name as alias and the new name of the server as the alias's target:
Next, when you rename a server that has sharepoint running on it, you need to tell SharePoint about ...
2
Reattach the upgraded database. Since the default site was already there when you attached it, it didn't properly find your site collections. Now that the default site collection is gone you should be ok if you reattach (assuming nothing else has gone wrong and all other steps have been completed).
2
You can do this with a SQL alias. Create an alias on your SharePoint servers with the exact same name as the existing SQL connection. Then point this alias to the correct instance and port. SharePoint will be unaware of the change.
The procedure to move all databases to another SQL server is more or less the same procedure: ...
2
It could easily explainable by the concept of "Application Extension" in SharePoint, which is simply a mechanism that creates a new Web Application (it could be the same Host header too, but different Protocol, HTTP vs. HTTPS - with the purpose of offerring different authentication mechanism to different targeted people, e.g. Intranet vs. Extranet, Employees ...
2
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 ...
2
If you extend a web application in SharePoint, a new IIS website will be created. That's one of the purposes of extending: to allow a different configuration.
The necessary bindings will be configured and maintained for you by SharePoint itself, on all servers in the farm. If you make manual changes to these settings, you'll have to do this on all servers. ...
2
You configure the port when you create your web applications, not during installation or configuration. But, the farm setup wizard will probably try to set up the initial web app on port 80, so just skip that and create the web app manually through Central Admin. There, you can specify the port.
1
If SharePoint was already installed when you renamed the host machine then you may need to reinstall SharePoint because, as Louis mentioned, SharePoint doesn't support moving the config DB. Renaming the machine where the configDB is running counts as a move in SharePoint's eyes.
One thing you can try before reinstalling would be to create a SQL Alias on ...
1
Unlike traditional ASP.NET web sites, SharePoint stores much of its information in Database and retrieves them from database so there won't be able to map SharePoint Urls to IIS site structure. For more information. To understand how SharePoint modifies the ASP.NET Pipeline to achieve this, check Microsoft SharePoint Foundation as an ASP.NET Application
If ...
1
One thing you may want to consider if you haven't already is the use of the page viewer web part. You can expose file shares through this and it provides a fairly good interface for doing so.
http://www.sharepointchick.com/archive/2007/11/29/displaying-a-file-or-a-folder-in-the-page-viewer.aspx
1
The finally working hack was to create additional authentication page, as Authenticate.aspx in _layouts folder under main site, which has 2 option - authorize user and make a postback to source page with post params - user login and email.
Thus, when user opens a forum for the first time, forum checks a session variable and tries to get user login using ...
Only top voted, non community-wiki answers of a minimum length are eligible
