I have restored a content database to SharePoint 2010 (which we completely broke after upgrading TFS to 2013).
When I open the content site, all the sub-sites are listed, but clicking one of these "sub-sites" goes to page not found. (The sub sites were created from TFS 2012 when new team projects were created).
How do I get the team project sites to work again?
You likley do not have a managed path configured for your SharePoint sites. If you look at the URL of the sites that you can't see you should be able to figure out the managed paths to add.
http://technet.microsoft.com/en-us/library/cc261845(v=office.15).aspx
You are kinda defining mount points for site collections here. Without that mount point SharePoint will not render your sites.
Related
Ok, I am in the dangerous place of knowing enough to cause trouble but not enough to do things correctly; and yet still have to be the one who does the work.
When I edit a sharepoint site, I see one thing, users see something else.
I have SP2013 Enterprise, On premise, SQL 2012.
I have configured Excel Services, Analysis Services - and they work
I developed an excel workbook with PowerPivot and deployed to a Sharepoint site via Excel WebPart
Permissions are set correctly as users have to login to open the site
However...
When other users go to the site, they don't see the information I posted, they only see the default screen. By default it looks like a business intelligence site before I added anything.
In short - the content I have put on my SP site is not being seen by anyone else. WTF do I do now???
Thanks
Did you perform a check-in of your page ?
If publication feature is enabled, did you publish the page ?
A page has to be "checked in" for others to see your modifications.
And if publishing is enabled, it should be published.
If the content of your page references other sharepoint content (file,page,...) they should be checked-in also to be visible to others.
Our company has a SharePoint server where we have to store all of our documents, our TFS 2013 has links to this SharePoint server. We have been told that the company is getting a new SharePoint server which will have a different url
This means that all links within our TFS need to be repointed to the new SharePoint site
Does anyone know of a way to change the links without someone having to go in to each PBI; see if it has any links; if it does then remove the old link and add a new one?
We have 100's of documents and would rather not have to do this manually so any help will be much appreciated
This is all beyond my control, all I've been told is they are migrating our SharePoint site to another server...
You can write a PowerShell script that will open all PBIs and change the links to the new SharePoint. In order to get access to TFS from PowerShell scripts you have to install Team Foundation Server 2013 Power Tools and check the PowerShell Cmdlets option during installation.
I was unable to work out how to do this using the PowerShell Cmdlets but I have been able to write a program to do this using Team Foundation Work Item Tracking Client
I have looped through each of the work items and their external links, if the link is to our old SharePoint site then:
I remove the old link
Add a new link with location of the same document on the new SharePoint
I'm working on remolding my companies current exsisting Sharepoint site. I installed the SP ZAP Slideshow webpart and went to the sharepoint site to insert it, and absolutely no webparts were listed. I went into the provided Sharepoint 2010 central administration and realized that everything seems to be listed as
//usmvwc0wtf1srv.ww005.work.net/sitepages/
When the website were hosting, and it should be listing is
//usmvwc0wtf1srv.ww005.work.net/sites/
I went to the /sitepages website and all the webparts exsisted and worked, however i need to get them working on the /sites page. Is there some way to switch it so it will not default all the webparts and content i'm uploading to the wrong page? I feel as though the wrong default page is listed? sorry new to all this!
Web Parts, which you see listed and are able to insert on a page when you edit it, come from the Web Part Gallery in the site collection. They are usually installed to the gallery when you activate their site collection-scope feature. Check what features you didn't activate in the new site collection - I suspect that one of them is responsible for the installation of Web Parts you are looking for. (The scope of the feature can be site collection or site - check both.)
i have a bit of stupid question, but i'm really having trouble with it.
I have a wsp project which i have successfully added to MOSS 2007 using stsadm.exe and deployed it via sharepoint central administration. This has created a new folder in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\ with solution files, so my issue is how to use/create workspace using this solution. I have no new feature, site type etc. in my sharepoint. The solution had been created by another developer whom i cannot contact.
Deploying it through Central Admin isn't the same as activating the feature.
There are several scopes in which a feature could belong:
Web
Site
Web Application
Farm
Only solutions targeted to Web or Site can be activated within SharePoint UI. The others are done through Central Administration. On activation of the feature is when work is performed.
Site: Site Collection Features
Web: Site Features
If you want to see what's in the WSP, you can make a copy and change the extension to .CAB and browse the files. Any DLLs will be likely deployed to the GAC.* If you look at the other XML files you can see what's in them and guess where they are going. Chances are pretty big the feature is Site or Web scoped. If it contains a SharePoint Timer Job, it'll be either Web or Farm scoped but could be Site scoped as well.
The only thing that could be complicated is features can be marked as hidden. If this is the case, the feature won't show in the Site- or Site Collection Features area. Instead you'll have to activate using an STSADM command (activatefeature) passing the name or GUID along with the URL where you'd like the feature activated. You can find this info by opening the WSP and looking at the XML files within.
*Some DLLs might just be feature receivers - code that will run on Feature Activation or Deactivation to do some additional things through the OM.
I would like to use Sharepoint Designer 2007 as an html editor. I have a web site with a lot of files in a folder on my hard drive. I do not want Sharepoint Designer to make a web site out of this. I just want to use Sharepoint Designer to edit the html files, locally.
If I ever make a mistake and click on a tool for Sites, such as summary or report, Sharepoint Designer will decide that my folder is now a web site. From that point on, Sharepoint Designer is painfully slow whenever I open a file contained in the folder that Sharepoint decided is my web site, instead of being instantaneous like it was before.
I can resolve this situation by renaming the folder containing my web site -- everything gets fast again. I can also fix it by uninstalling and reinstalling Sharepoint Designer. Neither of these is a good solution. Is there a place in Sharepoint Designer, or in application data or the registry that I can kill off the Sharepoint Designer web site that's associated with a folder on my hard drive?
I'm not certain this will fix your issues (as I can't easily recreate the situation you describe). But I do know where SharePoint Designer tucks away metadata about the websites you open and edit.
The next time SPD converts your folder to a web, shut down SPD and delete the contents of the following folders:
WebsiteCache:
XP: C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\WebsiteCache
Vista/7: C:\Users\<username>\AppData\Local\Microsoft\WebsiteCache
There is one file in WebsiteCache you may wish to keep, which is Websites.xml. This contains the "shortcuts" you see when you go to File > Open Site...
Web Server Extensions:
XP: C:\Documents and Settings\<username>\Application Data\Microsoft\Web Server Extensions\Cache
Vista/7: C:\Users\<username>\AppData\Roaming\Microsoft\Web Server Extensions\Cache
Whenever SPD gets wonky about reporting which files are checked out/in, really slow to open, or just generally weird, we clean out these folders and things return to "normal".
Hope this helps!