Tried to install a fresh copy of Microsoft SharePoint on Windows Server 2012 r2 and had the following prerequisite failed:-
OK so looks like we need to install a few things:-
Install Windows Identity Foundation
Open Powershell (as Administrator)
Install the Microsoft Identity Extensions
Install Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Server AppFabric
Download the Windows Server AppFabric exe and save it to your Server. Then run the PreRequisiteInstaller from the SharePoint 2016 ISO (CD) using the following command line (as Administrator):-
prerequisiteinstaller.exe /appFabric:[Dir where you saved the AppFabric exe]\WindowsServerAppFabricSetup_x64.exe
Note- it will do a reboot after installation.
Install Microsoft ODBC Driver 11 for SQL Server
Install Microsoft WCF Data Services 5.6 (rename this download to WcfDataServices56.exe)
Install Microsoft Information Protection and Control Client (MSIPC)
Install IIS 6 Management Compatibility component
Open PowerShell (as Administrator)
The following maybe needed, but it was not for me.
CU 1 for AppFabric 1.1 (KB2671763):
Then try installing SharePoint 2016 again and all should be well.
Had another strange SharedPoint issue when trying to edit the front page of our
WSS 3.0 SharePoint Web Site.
Clicked Site Actions
Clicked Edit Page
Clicked Edit dropdown on the Web Part I wanted to change
Hmmm - where did "Modify Shared
Web Part" go?
Checked permissions - yep had sufficient rights. So what could it be?
I was using IE9, and noticed before it does some weird things so put it into Compatibility mode - and bingo working again!
When running SharePoint
2013 Management Shell you might get the following error:-
The local farm is not accessible.
Cmdlets with FeatureDependencyId are not registered.
Just right click and "Run as Administrator"
Whilst trying to deploy a newly created SharePoint 2010 Visual Web Part I came across this lovely error:-
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
is a bit of a strange error as I'm not sure why having a long name would create such an error. However the fix was quite simple for me, just make sure the fully directory name + project name + files are not longer than 248 characters. A lot of people seem to put their projects in something like C:\Users\Celtic_Coder\Documents\Visual Studio 2010 which is already using up 50 character from that 248 character limit!
Had a interesting issue, our WSS 3.0 (SharePoint) internal site wasn't allowing users to upload/edit or delete files in the document library. On closer inspection everything was correct with the library permissions. Then I noticed the "View All Site Content" hyperlink was also missing. So what had happened to SharePoint? Well it seemed the morning's backup had failed and SharePoint had placed the site in a read only state (I presume to protect users adding more content when we didn't have a good previous backup file).
Open SharePoint 3.0 Central Administration
Select "Application Management tab"
Under "SharePoint Site Management" section - select "Site collection quotas and locks" hyperlink
"Site Lock Information" section is something other than "Not Locked" selected (ours was set to Read-only (blocks additions, updates, and deletions).
Just tick "Not locked" and your site should now work correctly.
When looking at their computer I notice a script error in IE:-
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.3)
Message: Library not registered.
It seems that when Outlook 2003 was uninstalled and Outlook 2010 was installed a dll gets unregistered and not re-registerd again. The file is called name.dll.
So to Fix:-
In CMD navigate to:-
C:\Program Files (x86)\Microsoft Office\Office14
And run the following command:-
Then close all IE windows and try it again and all should be good.
Trying to connect to my local SharePoint 2010 site using Visual
Studio 2010 Asp.Net on Local IIS Web server Version 7.5 (Windows 7 x64) e.g.
SPSite oSpSite = new SPSite("http://LocalPCName:81");
I got the following error (FileNotFoundException):-
The Web application at http://LocalPCName:81 could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.
Check what account the App Pool for "SharePoint Central Administration V4" is running under. I use a generic account say Domain\SharePointAdmin.
Make sure this account is under the "WSS_ADMIN_WPG" local accounts group.
Make sure this account is site administrator for the site you are trying to connect to.
"Use Local IIS web server" rather than "Use Visual Studio Development Server" for Visual Studio Project Web debugging. e.g. in Visual Studio for your project select Project - XXX Properties... - select Web (left tab) - tick "Use Local IIS Web server" - then click "Create Virtual Directory".
Once created open Internet Information Services (IIS) Manager and find the newly created Web Application. Select the web application and click "Advanced Settings...". Change the Application Pool to the same one as the "SharePoint Central Administration v4".
The following I have seen people blog about that fixes their issues, but this was not necessary for me:-
Make sure the App Pool account has DB_Owner access to the SharePoint Configuration Database and the SharePoint Content Database.
Make sure your code runs under Platform Target: x64 (although I find Any CPU works better) - just make sure it is not x86 because SharePoint 2010 was only x64 bit hence it would not work.
When developing Web Part's for SharePoint 2007 (WSS 3.0) in Visual Studio 2008 and referencing the Microsoft.SharePoint.dll sometimes when running the code you will get the following error:-
Could not load file
or Assembly 'Microsoft.SharePoint.Search, Version=18.104.22.168, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. An attempt was made to load a program with and incorrect format.
To Fix this add the following to the Projects Post-build event command line:-