New answers tagged

0

Managed to get it right somehow. Seems when I was trying to restore it using a SiteCollectionBackup it gave an error: Restore-SPSite: Version String portion was too long or too short. When it gave that error it also deleted the Host Named Site Collection. So after when i tried to restore again using Import-SPWeb it couldn't find the URL for the HNSC ...


2

1) Yes. This is possible. The scope of your requirements have not been defined, so if you require anonymous access, I have included links for how to do that. If not, ignore those links. For Anonymous users : You need to first Enable Anonymous Access on the web application in Central Admin (Check out Authentication Providers). You will then need to make some ...


0

This was really misunderstood the error given by visual studio. It was happen due to the fact that the unexpected shutdown of my machine, it affected to the ongoing process of taking site collection backup. This was found after so many blogs read and so many user permissions changed in SharePoint. This mainly happen due to power shell command being ...


1

Make sure you have started visual studio using an account that has necessary permissions. Alternatively you can try deploying using SharePoint Management She'll.


0

It caused due to changes made in Master page. There are 2 types of master pages; seattle.html and seattle.master. On changing master page I set seattle.html as default and forgot to set seattle.master as default. I did check this on website and it showed both .html and .master were default master pages. however through designer I encountered that .master is ...


0

You can delete site collection using powershell by using following command $tmpRoot = Get-SPWebApplication -Identity http://SP:2000 $tmpRootColl=$tmpRoot.Sites #Enumerate through each site collection for ($index=$tmpRootColl.Count-1 ; $index-ge 0 ; $index–-) { Remove-SPSite -Identity $tmpRootColl.Item($index) -GradualDelete -Confirm:$false } ...


0

You can delete site collection using powershell by using following command $tmpRoot = Get-SPWebApplication -Identity http://SP:2000 $tmpRootColl=$tmpRoot.Sites #Enumerate through each site collection for ($index=$tmpRootColl.Count-1 ; $index-ge 0 ; $index–-) { Remove-SPSite -Identity $tmpRootColl.Item($index) -GradualDelete -Confirm:$false } ...


0

Try a combination of Search and query result Webpart that concentrates on Websites that are sitecollections. Remember the Limit of 50 entries that could be shown... if you have more entries than you have to configure paging to the Webpart ;)


0

For outgoing email, you can set it through PowerShell. $site = Get-SPSite https://siteUrl $site.OutgoingEmailAddress = 'myAddr@example.com


-1

May not be exactly what your after but an easy inbuilt way (depending on what you already have set up) is to simply make a document library at the root site and enable incoming emails into that document library. To enable incoming emails you need a SMTP server (I set one up on the same server that has SP) to create the domain. Using Central Admin you then ...


0

PowerShell is just a wrapper for the object model. You can create Web Template & create Sites and Site Collections from that Custom Web Template using method mentioned in below reference. Programmatically creating Sites and Site Collections from a Custom Web Template ---------------------EXAMPLE 1----------------------- Move-SPSite ...


0

This is an example from MSDN using SSOM. SPWebApplication webApp = new SPSite("http://MySiteCollection").WebApplication; SPSiteCollection siteCollections = webApp.Sites; SPSite newSiteCollection = siteCollections.Add("sites/Site_Name", "Site_Title", "Site_Description", 1033, "STS#0", "DOMAIN\\Owner", "Owner_Display_Name", "Owner_Email", ...


0

Yes, they get created when you save the site as a template. Try using SharePoint client browser and get the Feature ID, then use PowerShell to delete/remove them using -Force attribute. You can also retrieve feature id from the Site settings page. Site Settings > Site Collection Administration > Site collection features Then use FireBug/IE ...


0

You can either extend the web application or use host-named site collection http://dinushaonline.blogspot.com/2014/04/extend-sharepoint-host-named-site.html


0

You need to extend your Web application using below mentioned URL. Extend claims-based web applications in SharePoint 2013 By extending the web application, it will point the same web application with having another URL. So now you can set permission to readonly for every user (as per your need).


0

The issue you are experiencing is that the cmdlet cannot properly pipe SPWebApplication object. (at least from the error) If you try: $w = Get-SPWebApplication http://intranet.vspserver.test-lab.local. You should get an error as well, maybe more descriptive this time. Other thing is that I can defo see an issue with your URL, is it correct that it ...


1

Can you get to Central Admin? Can you try to create a new site collection? How about PowerShell? Try to see if your Distributed Cache is up and running. Here is a good msdn article about troubleshooting your Distributed Cache. https://blogs.msdn.microsoft.com/sambetts/2014/03/19/sharepoint-2013-distributed-cache-appfabric-troubleshooting/


1

Projectsite is new template introduced in the SharePpint 2013, that site does not required the Project server licensing. You can read in depth about this template over here: On the PWA templates called project web app which are part of Project Server( Project service Application) and required extra configuration. i.e project server configuration, provision ...


1

A project site, ProjectSite#0, is a standard SharePoint project site template. A Project Web Access site, PWA#0, is a special template for those using Project Pro/Project Web Access for project management. If you don't have anyone using MS Project, stick to ProjectSite#0 templates.



Top 50 recent answers are included