After a MOSS 2007 to SharePoint 2010 migration, some site collections in a web application may need to stay in the MOSS 2007 (version 3) UI. This could either be for legacy web parts, custom branding, customer needs, etc. The first step is to identify the sites to be "black listed" in the upgrade process. Next, create a new .ps1 file with code below. Copy the $sitesToIgnore lines and replace the URL for as many site collections as required. From the SharePoint 2010 Management Shell on one of the SharePoint servers, run the the script and when prompted, enter the root web of the web application to start the script.
$webAppURL = Read-Host "Enter URL for the Root Web of the Web Application"
$webApp = Get-SPWebApplication $webAppURL
$sitesToIgnore = New-Object "System.Collections.Generic.List``1[System.String]"
foreach($site in $webApp.Sites)
write-output "$site ignored"
write-output "Updating $site"
After a new install of SharePoint Server 2010, the following errors may be displayed in the application log on any/all servers in the SharePoint farm:
The super user account utilized by the cache is not configured. This can increase the number of cache misses, which causes the page requests to consume unneccesary system resources.
The super reader account utilized by the cache does not have sufficient permissions to SharePoint databases.
$webApp = Get-SPWebApplication -Identity "NAMEOFWEBAPPLCIATION" $webApp.Properties["portalsuperuseraccount"] = "DOMAIN\SUPERUSERACCOUNT" $webApp.Properties["portalsuperreaderaccount"] = "DOMAIN\SUPERREADERACCOUNT"$webApp.Update()
To install iOS 6 Beta:
While navigating to a SharePoint Server 2010 site on the local server where SharePoint is installed, the following error may persist in the Application Log:
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed
The registry setting to disable loopback check needs to be entered. In MOSS 2007, logging in to a SharePoint site from the server would result in a timeout and/or error message. In SPS 2010, the server returns an error upon first load to the GUI and upon refresh will display the requested page.
To set DisableLoopBackCheck:
1. Click Start
2. Search for "regedit"
3. Right click on regedit.exe and select Run as Administrator
4. Expand the tree to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
5. Right click on LSA and click New --> DWORD Value
6. Enter the name DisableLoopbackCheck
7. Right click on DisableLoopBackCheck and click Modify
8. Enter 1 for the Value and click OK
9. Restart the server
Upon navigating to the SharePoint site, the application log should no longer be populated with errors for "SSPI handshake failed with error code 0x8009030c"
Issue:When attempting to start a site through Internet Information Services (IIS) Manager, the error message "The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)" is displayed in a prompt.
Cause:Another service or web server is listening on the same port as the IIS site.
Resolution:To find the service or web server listening on the same port:1. Note the bindings in the IIS site (right click on the site and select Edit Bindings)2. Open up command prompt as administrator and type "netstat -ano > netstatresults.txt"3. Navigate to the folder where the command prompt was ran and open up netstatresults.txt4. Note the PID number LISTENING on the IIS site's port (the port will be after the ":" in the Local Address column)5. Open up the Task Manager (right click on the Task Bar and click Start Task Manager)6. Click the Services tab7. Filter the PID column and locate the PID noted in step 48. Right click on the entry and select Stop Service
Note:The service may automatically start upon login or reboot. The service should be investigated, stopped permanently, or the port renamed to prevent further conflicts.
If all users who are sysadmin in SQL server have been removed from the role/locked out/unavailable in an emergency, or the sa account is no longer working, there is a built in operation to regain administrative access to the SQL server.
To start SQL Server in Single User Mode:First stop the SQL Server and SQL Server Agent services on the server.Open up a new command prompt as Administrator.Change to the default instance BINN directory (e.g. C:\Program Files\Microsoft SQL Server\MSSQL11\MSSQL\Binn)Type “sqlserver.exe –m” to start SQL Server in single user mode.Open up SQL Management Studio as you normally would.Make any permissions changes needed.
To restart SQL Server normally:Close the command prompt.Right click on the server name in SQL Management Studio and click on Start.
To send an email in a SharePoint solution using C#, add the following using statements at the top of your code (after referencing the Microsoft.SharePoint DLL in Visual Studio):
In your class, add the following method:
/// Send an email from a SharePoint Web
//send the email
SPUtility.SendEmail(web, false, false, Email, Subject, Body);