What’s new in SharePoint 2010 SP1
What's new in SharePoint 2010 SP1
With all the latest buzz on the release of SharePoint 2010 Service Pack1, here is what SharePoint 2010 SP1 adds:
Site Recycle Bin: With this new feature, administrators can restore site collections and/or sites that have been accidentally deleted by their owners. How often does this happen? Hopefully not too often. But when it does, having recoverable copies without getting out backups is a plus. We've had the Recycle Bin feature in SharePoint for lists, libraries, and documents for while now; this is a nice additional safety net.
Broader browser support: SharePoint 2010 SP1 adds support for IE9 in Internet Explorer 8 Standards Mode, as well as for Google Chrome.
Shallow Copy: This new feature allows you to move site collections to new content databases without having to move all the Remote Blob storage content. Thus, only the ownership information is moved, without having to copy the unstructured data in the file store. The Move-SPSite PowerShell cmdlet has been enhanced to allow this feature
StorMan.aspx (Storage Space Allocation page: StorMan.aspx has been reintroduced in SharePoint 2010 SP1. It was removed from the original version of SharePoint 2010. Now that it is back, it adds the ability to display better information to users regarding their quota information. That makes it easier for users to clean up their sites by deleting content they may not need.
Support for SQL Server "Denali" (aka SQL Server 2011) ): Given that SharePoint is heavily integrated with SQL, it stands to reason that new features in the forthcoming Denali version of SQL Server will only make SharePoint 2010 better.
Cascading filters in PerformancePoint Services: Filters values can now be passed from one filter to the next.
Event ID 3351-Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’
Today 01/04/2011, as part of my monthly checks, I noticed a whole bunch of 3351 errors in the event log on the SharePoint front end web server.
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Database
Event ID: 3351
Date: 1/4/2011
Time: 12:44:45 AM
User: N/A
Computer: MOSSSERVER
Description:
SQL database login failed. Additional error information from SQL Server is included below.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
Resolution: First I started to check the application pool account of the portal site and found they were all set as defined. After a thorough investigation found that the Windows SharePoint Services VSS Writer account is running as local system account. Changed the account to the AD Farm Account and found that the issue is resolved.
Event ID 107:Report Server Windows Service cannot connect to the Report Server Database
Today 11/01/2010, when I was doing the routine event log checks for errors as a scheduled task on the first of every month. One of My SQL server had a whole bunch of Report Server Windows errors with event ID 107.
Please see the error below:
Report Server
Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 11/1/2010
Time: 9:12:49 AM
User: N/A
Computer: MOSSSQLSERVER
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Resolution: Go to Services. msc and Make sure all the services for SQL Server Database engine and Reporting Services were in the running state. Then Open the Report Services Configuration Wizard, Connect to the specified SQL Server Database Server and then I found that the connection to the Report Server Database was set to some other database. Modified the settings doe the Database setup and connected the Report Server Database and save the settings.