Hot answers tagged

4

You have to Create a Site Collection in your Web Application. Go to Central Administration and choose Create Site Collection in the Application Management group. Enter a title in your Site Collection, select template to use and the primary site collection administrator: This can be done using PowerShell as well. Don't forget to Set Execution Policy ...


3

when you create a webapplication in sparepoint central admin, you would then need to goto iis -> domain name -> click on "web sites". You should be able to see a list of web applications e.g. ssp.example.com hello.example.com test.example.com that and oviously the correlating ip's and port number ect , as you can see its not sites or site collections ...


3

My recommendation would be that you shouldn't. You should start from scratch again and develop your Web-Application to be deployed below the _layouts folder in SharePoint using a WSP package and all of your code should be in code behind which is compiled into a dll deployed to the GAC. You can technically get your solution to work, but it's a hack, that ...


3

Do you have the backup of your content Database which are attached to web app(deleted) if yes. 1) from central admin create new Web Application and mention the same port(6666). 2) configure the Web Application settings i.e object cache settings, adding appPool account to USer Profile, AAM etc. 3) now detach the Content DB you created during the web ...


3

Those are not log files, it's your actual search index. It is recommended to move the index to it's own drive so that the index (or any other log files) cannot consume all disk space on the C drive. Moving the index means that you need to clone the search topology and then move the clone to another drive. This is kind of a complicated procedure as you have ...


3

Seems like your SharePoint WFE is out of synchronization as the web application is created in one server and it is not created in the other. You can solve issue by deleting the web application first you just created. Restart the timer services in both the WFE and try creating a web application Or you can also try this STSADM command before performing ...


2

The normal configuration for your scenario is to rely on the alternate access mappings (AAM). I'm not sure what setup your are using for your web application, but the best practice approch would be: Create new web applciation with SSL Url: https://customesite.com (Zone = Default) Add internal URL for this web app in the AAM configuration Internal Url: ...


2

There is quite a bit of setup required to deploy a provider-hosted App in a local (on-premises) SharePoint farm. Eric Shupps has a blog post that details everything you need to do to get this working. Configuring High Trust Apps for SharePoint 2013


2

Add your new URL to the intranet zone in Internet Explorer will make SSO work property, if that's what missing for you?


2

As a good practice, deploying SharePoint customizations should always be done via features, packaged into solutions. This way, SharePoint takes care of the deployment to all web servers in the farm. Of course there are also other benefits such as help with upgrading your features. More info: ...


2

You want to do this with the SPIisSettings class. There is a method in that class called AllowAnonymous which you can set to True and then update the object. That will enable Anon for the Web Application on the specified zone. http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spiissettings_members.aspx


2

It may come as a surprise to you (which only shows how little it has been written about this) but most of the ‘important’ things in SharePoint are actually done through unmanaged code and the SharePoint .NET object model provided by the Microsoft.SharePoint.dll is a sort of a wrapper to this unmanaged world. Understanding how your code does what ...


1

This requirement is very specific to your project. You can fulfil it by writing a HTTP Module which intercepts every SharePoint request, and converts it to Lowercase, see below: public void Init(System.Web.HttpApplication Appl) { //Hookup the function that does the lowercase Appl.BeginRequest += new ...


1

I seriously doubt you want to do anything to the IIS Configuration for SharePoint sites, as the Central Admin service looks after the IIS settings and the replication of those across all your servers. Any changes you do will probably be overwritten by a future service pack or other update, and may also introduce instability in current and future versions.


1

If you turn on the Microsoft SharePoint Foundation Web Application, SharePoint will automatically provision the IIS sites and Application Pools for your SharePoint Web Apps.


1

It could be accomplished by specifying more narrow match pattern for url For example, let's discuss the scenario, where requests from: http://{ServerName}/_layouts/teamsiteA/userdisp.aspx?ID=1 should be redirected to: http://{ServerName}/SitePages/UserInfoA.aspx?userID=1 and requests from: http://{ServerName}/_layouts/teamsiteB/userdisp.aspx?ID=1 ...


1

We had a problem with the Update Panel and SharePoint 2007 with our Custom Web Parts. We found that when we had an update panel on the page we could not create our controls in the standard CreateChildControls() method without experiencing the same error. Instead we had to create them in the Init event. I believe this is still true for SharePoint 2010 when it ...


1

IE6 is an unsupported browser for SP2010, 1 REASON BEING all the javascript SP2010 uses. http://technet.microsoft.com/en-us/library/cc263526.aspx#supportmatrix


1

The simplest solution would be to use remote blob storage to move the file content out of SQL to actual disk storage. AvePoint DocAve Extender is free. See http://www.prweb.com/releases/2010/03/prweb3743974.htm on how to get the free license.


1

You can create a customm web part the uploads the file to a normal folder, and another web part to show the files in a proper structure (Folders / Tree like). But doing this prevent you from using the ready-made features in SharePoint.


1

Not sure I understand how you end up with multiple Virtual folders, probably you have to share more insight on how you created the Web Applications. On the other hand, if you have multiple machines in the farm, and you perform manual changes you need to manually update all of the web.config for that particular Web-App. The only way changes are pushed are ...


1

An easier no code solution is to configure IIS to handle it for you. Create a new site setup with the hostheader customsite.com, and on port 80. Within the site, select HTTP Redirect under the IIS group: From here you can redirect to https://customsite.com.


1

In IIS you can find only web application. The sites that you creates in this application are stored in the content data base of SharePoint. You can use central administration to see and manage them.


1

Did you check the loopback settings? Can't pass authentication to browse a sharepoint site Also, is you AAM setup to support those other urls?


1

Disabled all features IIS restart machine from command line activate features: start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures; IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors; IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility; ...


1

Check your code, are objects disposed properly? If you have too many visits at the same time I would say CPU high would be normal. Check that you are using page cache, output cache, object cache and blob cache, that will reduce roundtrips to db server and should lower cpu usage. and last, but not least you have to identify somehow which pages are the ...


1

What the performance Impact on the SharePoint Sites, loading slowly or normal? I would check the ULS logs as well as enable the Developer Dashboard, then check which item causing this issue. Did you try to recycle the App Pool? also make sure, if you have custom webpart or other customization, no memory leak from them. You can also try to close the web ...


1

It wasn't the installation of SharePoint that took over your default web site, it was the provisioning of a new web app at port 80 that did it. To retain your default web site, just keep away from port 80 for your web applications. If you used the farm configuration wizard, you'll need to either skip it or skip the part that provisions the initial web app, ...


1

Have you tried starting VS2010 as an administrator account that has permission to perform IISRESET? It could be that the user you are currently running VS2010 does not have this permission and give you this error when VS2010 is trying to reset IIS. If Run As Administrator does not work you can use the Runas command from the CMD to start VS2010 as which ...


1

As long as you use Host Headers for both web applications, you should be fine. Take a look at the New-SPWebapplication cmdlt and be sure to specify the hostheader parameter when creating the web applications.



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