New answers tagged

0

It is a usual behavior of SharePoint... When you deploy SharePoint package , it will place the files & it's related DLLs to their appropriate location.. It is necessary to reset is to connect those file with each other to get a reference from different locations ... This is the simple definition from my end to understand why it's necessary to reset the ...


2

Actually, there's no such thing as "deploying a Web part to a site collection". You deploy a Web part with a WSP package; WSP packages (at least ones that contain Web parts) are deployed against specific Web applications. After that the feature containing the Web part is activated per site collection, but "activating a feature" is only a SharePoint logic ...


0

I don't think it is SharePoint Design issue, It is more IIS issue. When you deploy a solution, it deploys the DLL in GAC folder. IIS can't read those Dll until iisreset performed.Basically, IISreset does two things clear the memory reload all the DLLs from the GAC folder. One thing you can do, During your code you can't set Reset Web Server property to ...


0

We had this issue many times, In our cases. The fix was, Make sure site is not locked. For some reason, SharePoint restore process put a Lock on the Site collection which causes this issue. Could you please check this from Central admin > application management > Configure Quota and Locks...On this make sure your site is not locked.


1

Host Header: Host header is nothing but providing a related name as the URL for the web application, by default SharePoint takes only the local server name as a URL and then render the data's from the content DB. If you want to configure you web application on port 443 than you will get better idea from below links. SSL Sites with Hostnames in SharePoint ...


0

The host header is the URL on which the web application will respond. If you specify a host header during the creation of a web application, you'll notice that a binding with the same URL is added in IIS Manager as well. This allows IIS (and thus SharePoint) to respond with the correct content when you request a specific URL. The web application host ...


1

You have to use the Get-SPAlternateURL, it will return url from all zone then you will be know if one you are requesting being used or not The Get-SPAlternateURL cmdlet returns all alternate URLs that match the scope given by either the optional Identity parameter or by a combination of the optional WebApplication, Zone, or Resource parameters. ...


0

Your steps looks good, I would make sure following things. As you are using the Database Mounting method, I would make sure that dev farm version level should be same or higher( mount contentDatabase will upgrade to higher version). Web Applications configuration means, any change in web.config file, Object cache Settings(if configured), Authentication ...


0

Those are good steps. In order to mount your database to the new Web Application in the development environment, use Mount-SPContentDatabase on the dev SharePoint server. This will automatically assign the appropriate permissions to the restored Content Database. I would install the WSP(s) prior to mounting the Content Database. Not strictly required, but ...


1

It is depend upon your requirement( storage, SharePoint usage, #of users, customization, #department, Security etc). Either you go with root level Site collection with many sub sites or use a managed path site collection with many subsites, things will be same except the URL. http://webapplication.com to http://webapplication.com./sites/sitename. One ...


0

There are many considerations to be done. Anyway, I will just give a quick and dirt answer to point at some issues. The first option is easier to manage as you will have a single site collection with many subsites in it. This can be an option if the site is not too big as for example there is a 200 GB supported limit for content db and a site collection ...


1

There is no any issue of using a different language (VB.NET) master page in SharePoint. The SharePoint Server comes with a Publishing feature as an out of the box component so that you can use its rich functionalities to build and deploy custom branded sites using master pages, layout pages etc. These functionalities are not available out of the box in ...



Top 50 recent answers are included