Docstoc

_SP1_ in SharePoint 2010 and the Office Server ... - EPM Central

Document Sample
_SP1_ in SharePoint 2010 and the Office Server ... - EPM Central Powered By Docstoc
					Issues Fixed by Service Pack 1 (SP1) in SharePoint 2010 and th
Notes
1. Service Pack 1 includes a rollup of all Cumulative Updates released through April 2011 and all Public Updates released thro
included in the list below, which is specific to changes that are shipping for the first time in SP1.
2. Because we relied on experts of each product to write the text below, the phrasing throughout the table is not 100% consis
describes a problem that was fixed by SP1, while other text describes the problem and the new behavior after installing SP1. W
please keep in mind that, despite the individual phrasing of each description, all of the issues listed should be fixed in SP1 .
3. In addition to the fixes listed below, SP1 contains additional changes which are less visible, but improve various aspects of t
reducing the number of crashes, improving security, and fixing other issues that were deemed to be too specific to include in th


Resources
Issues Fixed by Service Pack 1 (SP1) in the Office 2010 desktop products
Complete List of all Microsoft Office 2010 Service Pack 1 (SP1) packages (KB 2510690)
Complete List of all Microsoft SharePoint 2010 and Office server Service Pack 1 (SP1) packages (KB 2510766)


Table of Contents
Excel Services
FAST Search Server
Office Web Apps
PerformancePoint Services
Project Server
Search Server
SharePoint


Fix Descriptions
Product
Excel Services
Excel Services

Excel Services

Excel Services
Excel Services
Excel Services

Excel Services
Excel Services
Excel Services
Excel Services
Excel Services
FAST Search Server
FAST Search Server


FAST Search Server
FAST Search Server

FAST Search Server




FAST Search Server
FAST Search Server
FAST Search Server


FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server

FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server

FAST Search Server
FAST Search Server

FAST Search Server

FAST Search Server

FAST Search Server

FAST Search Server
FAST Search Server


FAST Search Server

FAST Search Server
FAST Search Server


FAST Search Server
FAST Search Server
FAST Search Server

FAST Search Server

FAST Search Server


FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server
FAST Search Server




FAST Search Server

FAST Search Server

FAST Search Server

FAST Search Server

FAST Search Server




FAST Search Server

FAST Search Server

FAST Search Server
FAST Search Server

FAST Search Server


FAST Search Server
FAST Search Server

FAST Search Server


FAST Search Server
FAST Search Server


FAST Search Server

FAST Search Server
FAST Search Server
FAST Search Server

FAST Search Server

FAST Search Server
FAST Search Server

Office Web Apps
Office Web Apps
Office Web Apps



Office Web Apps
Office Web Apps

Office Web Apps
Office Web Apps
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services

PerformancePoint Services
PerformancePoint Services

PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services

PerformancePoint Services
PerformancePoint Services

PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services
PerformancePoint Services

Project Server
Project Server

Project Server

Project Server

Project Server

Project Server

Project Server
Project Server


Project Server
Project Server
Project Server
Project Server


Project Server


Project Server

Project Server
Project Server
Project Server

Project Server
Project Server

Project Server

Project Server

Project Server

Project Server
Project Server
Project Server

Project Server
Project Server
Project Server

Project Server

Project Server

Project Server

Project Server
Search Server
Search Server

Search Server

Search Server

Search Server
Search Server
Search Server
Search Server

Search Server

Search Server

Search Server

Search Server

Search Server

Search Server




Search Server
Search Server
Search Server
Search Server
Search Server
Search Server

Search Server

Search Server
Search Server
Search Server
Search Server

Search Server

Search Server
Search Server

Search Server

Search Server

Search Server

Search Server

Search Server
Search Server
Search Server


Search Server
Search Server
Search Server

Search Server

Search Server

Search Server
Search Server

Search Server


Search Server

Search Server
Search Server




Search Server


Search Server
Search Server

Search Server

Search Server

SharePoint
SharePoint
SharePoint

SharePoint

SharePoint
SharePoint
SharePoint

SharePoint
SharePoint


SharePoint

SharePoint
SharePoint


SharePoint

SharePoint

SharePoint
SharePoint

SharePoint
SharePoint




SharePoint

SharePoint

SharePoint
SharePoint

SharePoint
SharePoint

SharePoint




SharePoint

SharePoint
SharePoint


SharePoint

SharePoint

SharePoint

SharePoint


SharePoint
SharePoint
SharePoint
SharePoint
SharePoint

SharePoint


SharePoint
SharePoint


SharePoint


SharePoint

SharePoint

SharePoint

SharePoint
SharePoint

SharePoint

SharePoint

SharePoint


SharePoint
SharePoint

SharePoint
SharePoint

SharePoint

SharePoint
SharePoint
SharePoint
SharePoint

SharePoint

SharePoint

SharePoint

SharePoint

SharePoint

SharePoint
SharePoint


SharePoint

SharePoint
SharePoint

SharePoint

SharePoint
SharePoint
SharePoint
SharePoint


SharePoint

SharePoint
SharePoint
SharePoint


SharePoint
SharePoint

SharePoint
SharePoint


SharePoint




SharePoint

SharePoint

SharePoint
SharePoint

SharePoint
Service Pack 1 (SP1) in SharePoint 2010 and the Office Server Applica

p of all Cumulative Updates released through April 2011 and all Public Updates released through June 2011. They are not
s specific to changes that are shipping for the first time in SP1.
 of each product to write the text below, the phrasing throughout the table is not 100% consistent. Some of the text simply
ed by SP1, while other text describes the problem and the new behavior after installing SP1. When reading the list below,
e the individual phrasing of each description, all of the issues listed should be fixed in SP1 .
below, SP1 contains additional changes which are less visible, but improve various aspects of the product. This includes
 improving security, and fixing other issues that were deemed to be too specific to include in this list.



P1) in the Office 2010 desktop products
fice 2010 Service Pack 1 (SP1) packages (KB 2510690)
arePoint 2010 and Office server Service Pack 1 (SP1) packages (KB 2510766)




             Text
             -
             Sparklines are not displayed in a web part in named object view if there are no named items published when the
             workbook is saved.
             In Excel Services, when you filter a slicer that is connected to PowerPivot, Excel Services becomes unresponsive.

             Controls that are bound to an expression in the form header do not work in Internet Explorer 9.
             The SUBTOTAL and AGGREGATE formulas show incorrect values when you undo a filter operation.
             The user receives the "An Error Has Occurred" message on the server when the TREND, LINEST, LOGEST, or
             GROWTH are used with external references on the Excel client and then the file is uploaded to the server.
             Excel Services cannot connect to Analysis Services over an HTTP connection.
             Values that include array formulas are not updated when you copy the values between worksheets.
             Summing formulas that contain defined names produce a #VALUE error.
             Data is lost when you copy or cut data and then paste it into a filtered range.
             Certain function names are not localized for some languages.
             -
The link and click-through analysis engines break when you set up a multi-node installation for which the
hostnames in the deployment file use different casing than the hostnames that are given to the Post Setup
Configuration script.
When indexing documents which cause warning or errors, indexing speed drops significantly.
Information on the backup and crawler configuration are missing from the infotool report when FAST Search
Server is installed in a folder whose name includes a white space character.
If you try to create a new rank profile that has an illegal name (such as a name that contains angle brackets), the
schema update will fail on the FAST Search servers, but you will not receive an error message in the PowerShell
console. Subsequent index schema updates might also fail without any error message in the PowerShell console.

PowerPoint SlideShow (.ppsx) files are not searchable when you use the latest Microsoft Filter Pack.
Feeding fails after customization of the inclusion dictionary.
The default schema settings produce irrelevant results because unnecessary content is indexed. The default
schema also produces inconsistent SiteName values between indexed content from the SharePoint and FAST
Lotus Notes connectors.
Indexer ignores errors when it copies directories.
Indexer crashes and corrupts the document index.
You cannot remove crawled property mappings for a managed property in SharePoint Central Admin.
The indexer goes into an invalid state and does not shut down.
The Configuration process (PSConfig) throws an error and terminates at resourcesstoreinstall.exe execution.
Titles and dates for Microsoft Office documents in search results do not correctly reflect the contents of the
documents.
Incorrect FQL conversion occurs when a query uses type (type=kwany)/(type=kwall) with custom indexes.
Functionality to add search columns to a live system is lacking.
The crawler becomes unresponsive when it is looking up DNS host entries for a large set of websites.
The "total size of documents (bytes)" value that is reported by the Indexer process does not decrease correctly
when documents are removed from the search index.
Document preview does not work in search results when https is used.
When an I/O exception occurs during index activation, the system enters a state in which no more data is
indexed.
When the same managed property is added and deleted many times (more than 20), memory consumption for
several processes continues to increase, even if the actual schema remains the same.
An error occurs when you use the command line tool "crawleradmin" together with the "--nodestatus" option to
query the status of multiple web crawlers.
The deployment file templates contain recommended and commonly used components and services for servers
in a FAST Search farm. These templates are out of date.
The terms in simplified Chinese language multi-term queries are automatically combined into a phrase.
If a refiner's mapped property has uppercase characters in the refinement panel, the refiner will not be returned
from the FAST backend. This will also happen if programming interfaces, such as query web service, federation
OM, or query OM, are being used.
When a user is authenticated by a third-party system through form-based authentication, search results do not
list documents to which anonymous users have read access.
SAM configuration files are not patchable.
FAST scope filters are dropped if they are longer than the maximum size, but no warning message is returned. In
this situation after the fix, the filter is reverted to the last known good string, and a warning is displayed in the
user interface.
An uncaught exception makes the click through log analysis stop processing new data.
The master indexer becomes unresponsive during long index copies.
Adding items using the FAST database connector and multi-row normalizer functionality may cause the string
"NULL" to be indexed instead of the value NULL.
If the click-through analysis engine fails to write its internal state to disk, the file that contains the state is
truncated, and the application cannot restart.
If you have a crawl that uses sitemaps as start URIs, you may observe that certain documents are removed from
the index by the crawler after a number of refresh cycles, even though these documents still exist on the web
server and are also still linked by the sitemap.
The indexer can run out of disk space when old fixml data is not cleaned up.
Backup indexer or search may fail when disk space is low.
Search fails until samworker or qrproxy services are restarted.
In cases where indexing fails due to corrupt data new content will not become searchable.
After startup, the backup indexer gets out of sync with the master indexer with respect to index copying. As a
result, the backup indexer does not have the necessary indexes available in case of failover, and everything will
have to be re-indexed. Error logs may include this message: "Communication error when registering file receiver
from ...: File receiver unavailable."
When an item processor cannot send link data to the link analysis engine, the item processor stores the data
until it can be sent. In some cases, the data is never sent, performance suffers, and errors are logged.
Feeding performance for large batches, with many links per document or many documents per batch, is
unexpectedly poor.
Administrators experience a performance drops in feeding due to the overhead of error-handling and
resubmitting of batches.
Temporary index directories that remain when the search controller is stopped are not cleaned up, which wastes
disk space.
Consider a scope that has a FAST specific scope filter for which the filter string contains one or more managed
property restrictions, and the managed property names contain uppercase letters. When this scope is used in a
query, the error message, "Property doesn't exist or is used in a manner inconsistent with schema settings" is
returned.
Due to duplicate removal, the maximum query throughput (QPS) is roughly 50 divided by the number of columns
(for example, a 10 column system would have a throughput of 5).
FastSearch feeding and indexing hangs when feeding recovery is triggered and there are many content feeding
sessions running at the same time.
The click-through analysis engine (SPRel) breaks when error handling is triggered during feeding.
Corruption of the search index stops deletion of expired normalized dictionaries. Those files might never be
cleaned up, wasting disk space.
In a fault tolerant setup under certain circumstances when the amount of available memory is low on the master
indexer node, the master indexer shuts down. This can cause the backup indexer to loose sync. After the
incident, the indexers must be manually synchronized.
In some scenarios, the crawler crawls documents in the wrong order and may not return the expected results.
Installation on the Italian language version of Windows 2008 Server fails in the post-setup configuration stage.

If the user updates the crawler configuration on a multi-node crawler setup that specifies a proxy for crawling,
the crawling comes to a halt and all requests fail. This leads to no documents being updated or added to the
index.
The infotool does not pick up the pipeline extensibility and schema files from the admin node. This information is
very useful for troubleshooting schema and document processing scenarios.
When you run the SecureFASTSearchConnector.ps1 script in silent mode, a message is printed to the console
that states that the script was not successful even if it was successful. This fix corrects that problem and resolves
a problem of several log messages being printed to the console while the script is run in silent mode.
During crawling by the FAST Search Web Crawler when JavaScript support is enabled, the Browser Engine
suddenly stops processing certain documents. Therefore, these documents are not crawled and indexed.
Users are unable to search with Greek lemmatization and spell checking.
Custom property extractors are limited.
When the user stops a process by using the command line tool nctrl, the message "Failed to stop the following
process" is displayed, However, the process might just be taking a long time to stop.
The fsearch process grows in memory size until all system memory is used under a sustained heavy query load.

Intermittent issues with feeding performance.
The dump file (.dmp) that is created when Contentdistributor, Indexingdispatcher, or Nameserver crashes is
unusable.
-
Text that is in shapes on PowerPoint slides is not editable in the PowerPoint Web App.
In Internet Explorer 9, various problems occur in PowerPoint Web App's edit view, including text that does not
wrap correctly, text that is partially out of view, and difficulty scrolling.


Spell checker does not find spelling errors in various language versions.
When the Open in Client feature fails in WebKit browsers, you cannot save your work until you refresh the page.

AutoCorrect does not work in various language versions.
AutoCorrect does not correct text in various language versions.
-
When you edit the Named Set filter in Dashboard Designer, the wrong named set is selected.
For a SharePoint list data source, only the default view can be selected for a custom list.
If all values in a multi-select filter are "unchecked," the filter does not return to the default selection.
An unexpected error occurs on a chart that has custom MDX.
Webpage URLs that have spaces or special characters are not renderered in the dashboard.
You cannot export or view a web part menu that was opened by using the display report option of the
PerformancePoint content list.
The Cascading Filters Apply button web part displays the dialog box title as blank ("untitled").
Consistency problems occur for non-empty filters when you switch between grid view and chart view on the
dashboard.
When you navigate from the decomposition tree to grid view, hierarchies break and might lose members.
Quotation marks around an XML IT attribute value in an Analysis Services filter cause an error.
You cannot create row and column links by dragging from a scorecard to an analytic view.
When you double-click a checkbox in Member Selector, the checkbox remains unchecked even though it is
actually selected. You have to click OK an extra time to close the dialog box.
The selected items number format does not match the Windows number format in Member Selector.
An error occurs in Dashboard Designer when you try to delete PerformancePoint content that is stored on a
SharePoint site that has the recycle bin disabled.
Decomposition Tree service does not work on a scorecard that is filtered by a SharePoint filter.
When you change filter values for a Custom Table filter that is linked to a Query Mode analytic chart, the chart is
not correctly updated.
The GenerateView web service does not receive page filters.
The "clear filter" option is disabled for value filters on a bar chart report.
Scorecards that have a "blank" KPI indicator cannot be exported to PowerPoint or to Excel.
PerformancePoint Server 2007 filters that use column member or row member display values and that are from
a migrated 2007 version scorecard do not work.
-
Bulk update of project sites does not succeed when the project site URL does not include a trailing slash mark
("/").
The date ranges in the timephased grid for statusing are shifted by a day when a daylight savings time change
occurs.
A project administrator wants to create a team site that is not related to a specific project in a Project Web App
site collection. But webparts cannot be added to that site, which makes it unusable.
When you switch to a view for which a subtask is filtered out after you delete the summary task, the view does
not load.
When an update is applied to upgrade Project Server, but the database is not upgraded, an unhelpful "Unknown
error" message is displayed.
With SP1, Project Server now supports SQL Server Code Name "Denali" (SQL 11).
Before SP1, you could not have a rule auto-publish when the rule was auto-approved. Starting with SP1, you can
set rules to automatically publish updates to project plans after they are run on the Create/Edit Rules page.

The "Mark Complete" button on the "My Tasks" page is disabled when it shouldn't be.
AutoFilter performance in Resource Center is slow when large numbers of resources are in the view.
Calculated measures are not upgraded correctly when you upgrade from Project 2007.
A project that belongs to an Enterprise Project Type whose property was changed from Workflow to Non-
Workflow (or vice versa) does not appear or does not appear correctly on the Change or Restart Workflows
settings page.
Creation of a Project Workspace does not succeed, but a record that the creation was successful is written to the
publish database in Project Server. After the fix, the mistaken record is no longer written to the publish
database.
Actual work time that is submitted through MyTasks in Project Web Access is moved to a different day when the
project is opened in Project.
The server scheduling engine does not support effort-driven or fixed work tasks in the Schedule WebPart.
When updates are accepted, task start and finish dates change unexpectedly.
A policy was added in SP1 to automatically redirect extensions to use the latest version of the Project Server
Library DLL.
Approval fails for self-assigning team tasks.
"Work value used is invalid" error occurs when you save a resource plan that has very small time-phased work
values in Project Web Access.
When you update an Enterprise task Custom Field by using the Project Server Interface (PSI), the task duration is
changed to 100-percent complete for the updated task.
When a user submits changes through My Tasks and the updates are accepted by the project manager, the start
date of the task is changed unexpectedly.
Users who have appropriate permissions receive an error message when they try to access a subproject in a
master project in Project Center view.
In certain language versions, you cannot load views in Project Server 2010 after you upgrade from Project Server
2007.
Resource-synced tasks are not editable in the schedule web part when in edit mode.
Beginning with SP1, team member support is included for the Mozilla Firefox and Apple Safari browsers. For
example, team members can now use these browsers to submit time and status information on their tasks.
When you click "Assign To Me" for tasks that are assigned to a pool resource, an error occurs.
The Set-SPProjectWebInstance cmdlet does not work to update the host header site.
When you modify status through Project Web Access or through the Project APIs, changes to "Actual Work" on
manually scheduled tasks that have a 0-hour duration do not persist.
Summary tasks create virtual links to their subtasks. This causes scheduling to be determined by subtask instead
of by rollup summary.
When you have a view filter that excludes one or more inserted subprojects, the view does not load when you
try to expand all inserted subprojects.
When the Projectproxy.QueueUpdateProject PSI method is used to change the start date of a task on a server
that has protected actuals enabled, the actuals will incorrectly move along with the start date of the project.
When a Project Web Access subscription is deleted, the path cannot be reused.
-
Fileshare crawls will fail with "access denied" if the default access account or the account specified by a crawl
rule to run the crawl does not have access to the search temp folder.
Disallow directives in robots.txt files are not parsed in a way that is consistent with the de facto robots exclusion
standard.
PowerShell example help for "New-SPEnterpriseSearchServiceApplication" incorrectly references "New-
SPIisWebServiceApplicationPool" instead of "New-SPServiceApplicationPool."
A people search query returns inaccurate results.
A Notes item cannot be crawled if a non-user/group/role string is in the Readers field of the item.
The system cannot crawl PPSX files.
Host redistribution doesn't make progress if the SQL Server with the configuration database is unavailable for
longer than 10 minutes.
When the search system is computing relevance statistics in the background, query performance can be
affected, and end-users may experience slow queries.
Many documents that were upgraded from earlier versions have the author listed as "-1;#;"on the search results
page.
If you are using the TR-TR Language Pack, you experience a JavaScript error when you try to create a crawl
schedule.
When you assign a host to a search crawl database and the host name contains an underscore character ("_"),
the rule cannot be created.
An inaccurate result count is estimated for queries that have multiple sub-queries. (And an unnecessary "next"
button may appear on the results page.)
If a user attempts a config-only restore on a farm different from the one on which the backup was taken, the
restore fails with the following error: "System.ArgumentException: localStoragePath at
Microsoft.Office.Server.Search.Administration.SearchApi.AssertParameter(String parameterName, Boolean
condition).
People search results are duplicated starting on page 8.
An upgrade does not succeed if the Search SSA administrator no longer exists in the Active Directory.
After topology changes, crawls are stalled for several hours.
Topology changes that add or remove a crawl store are not restartable if they are not successful.
If a search crawl host redistribution operation is interrupted by a temporary connectivity problem, the progress
indicator of the operation is no longer accurate.
When you rename a crawl store, entries for the old name and the new name appear in the topology
administration pages.
When a crawl store is removed, outgoing anchor links to documents in content sources that were not crawled
yet are not redistributed.
A restarted host redistribution creates duplicate anchor text data in the redistributed store.
Querying in the Serbian language does not work.
When you search for an HTML file, the result contains several words that are not separated by spaces.
In certain languages, tooltips appearing over the search crawl logs filter specification dropdown lists contain
code characters not intended for reading.
Health Analyzer in Microsoft Search Server Express displays a false warning: "Trial period for this product is
about to expire."
Crawls in FAST Search for SharePoint stop responding. A search service restart is required to recover.
Search does not index the File Server Resource Manager properties of Windows files that are not Office files,
such as .txt files.
The page for administering search crawl rules displays an English error message in non-English language versions
when a non-valid site name is encountered.
If a query component is not mirrored and its index becomes corrupted, the corrupted component is shown as
“Not responding”. An index reset does not resolve the situation.
You issue a query that includes a phrase as a synonym to one of the terms. If more than one instance of that
phrase occurs in a URL, a crash occurs.
When the dedicated web front end servers (WFEs) for a search deployment are down, search redirects traffic to
all the remaining WFEs. This overloads the system.
The crawler stops responding after processing a large number of links.
Phonetic People Search does not work correctly for the Russian and Korean languages.
Search administration reports for a larger SharePoint farm (with multiple search service applications or multiple
web frontends and query servers) show a query rate that exceeds the actual number of queries that users are
executing.
The search crawl log page includes obscure error information about index deletions.
You cannot create a new search service application by using pre-existing empty databases.
If you enter a query that begins with a double-quotation mark but does not end with a double-quotation mark,
an error message is returned.
The search content sources administration page loads very slowly when there are many content sources defined.

You try to perform a restore, but the restore fails. You receive an error message that identifies the cause but not
the location (the component from which the error originated).
After a search restore is performed, the "dedicated" setting of a crawl store is lost.
After a restart of the Search service, the crawler sometimes stops responding, and a service restart is required.

You set the "Has Multiple Values" field for a built-in date/time managed property that is part of the restricted set
of managed properties that are retrieved on each query. In this scenario, all queries return "Internal server
exception."
Before SP1, it was cumbersome to write a new web part or to extend an OOB web part. Starting with SP1, a new
API is available (LocationConfigurationsCollection object) that makes these jobs easier.
A malformed query exception occurs when you execute a full-text query that includes an integer multivalued
property in the where clause.
Administrators are able to create a crawled property whose name is non-numeric, using the SharePoint Search
Windows PowerShell cmdlet "New-SPEnterpriseSearchMetadataCrawledProperty", with the "-IsNameEnum" flag
set to $true. This crawled property breaks the search schema, and will cause subsequent search crawls to be
stuck in the "Starting" state.
QueryManager.GetResults() is not public. Starting with SP1, QueryManager.GetResults() is public. This clarifies
for developers that you have to add the LocationList to the queue QueryManager before you execute a query.

You cannot determine which result page is the source of a logged click.
A query logging search session lasts for a full day and may end in the middle of an actual search session. The fix
requires PSConfig to be run after applying SP1.
You try to index some HTML files that contain noindex div blocks. However, some text in the noindex div blocks
gets indexed and is searchable.
You cannot create a scope filter of greater than 2,047 characters (although the defined maximum is 51,200
characters).
-
The server contacts template opens as read-only in the Access client.
WebDav requests from a client-side application to a particular site can skew the web analytics results for that
site
When the report consolidator tries to create a new partition and the system is out of disk space, the reports that
use data in the new partition will show no data.
When a task for Approval Workflow is deleted, the"Deleted By" information is incorrect.
Search crawls the Drop Off Library although it is only temporary storage and should not be indexed.
The copy/move operation is visible in the site manager user interface for users who are not site collection
administrators.
When the w3wp process starts, first-time hits to Metadata Navigation take a long time to complete.
In a document library there are shared content types between documents and documents sets. If one of the
fields in these shared content types is marked as shared in the document set, that field becomes read-only for all
documents that are outside of the document set in that document library.
When nonalphanumeric characters, such as an ampersand, are entered as part of the alternate text of a
publishing image, the alternate text becomes overencoded.
Users cannot access the local taxonomy group to create local taxonomy fields by using code.
A subweb in a site contains nonalphanumeric characters, and a document library within that web is set to open
Office documents by using the Web Viewer. An HTTP 400 error occurs when you click a document ID link in this
scenario.
The audit trail is lost when an item is sent to the drop off library and does not automatically get routed to the
final destination.
If a user creates a site collection, deletes it, and then re-creates the site collection by using the same name, the
site collection group is not re-created in the term store.
The Japanese translation for "Make Homepage" is inccurate.
A user writing custom administration tools using TypeDescriptor.MergeXml gets server-side
InvalidProgramException errors.
"ArgumentException: The provided URI scheme 'https' is invalid; expected 'http'" error occurs when Business
Connectivity Services is used to connect by using HTTPS to a WCF line-of-business system that is based on SOAP
1.1.
“Argument must be between 0 and 3. Parameter name: fieldCount” error occurs when the user tries to view the
summary of the external content type in the ViewBDCApplication.aspx page or the details of the external
content type in the ViewBDCEntity.aspx page, if the version of an external content type does not contain build or
revision components.
A call to GetLobSystemById or to GetLobSystemInstanceById public APIs on the remote administration web
service with performErrorCheck set to false returns ArgumentNullExceptions.
When a user's profile picture is deleted, the entire folder is deleted if the user's pictureURL field is set to valid
folder URL.
Workflow cleanup process is inefficient.
Prior to SP1, SharePoint administrators could not set a limit on the number of Broadcast Slideshow attendees
through a PowerShell cmdlet. Beginning with SP1, this functionality is included.
User cannot recover deleted SPSite and SPWeb objects.
Output caching does not work when a web part is configured to target an audience that contains users who
belong to more than one audience.
Generation of news feeds on My Sites is governed by the Activity Feed Timer Job. Before SP1, this timer job was
turned off by default over privacy concerns regarding news feeds. Therefore, no activities were generated on the
My Site news feed by default. Starting with SP1, a setting on the My Site Settings page for User Profile Service
Administrators provides control over news feed behavior. The Activity Feed Timer Job is now always enabled,
but administrators can use this new setting to opt in or opt out of news feeds.
You cannot customize the runtime behavior of the Social Security Trimmer, which is used when you retrieve
social data, such as tags, notes, ratings, or Newsfeed data.
Before SP1, SharePoint Server 2010 did not support SQL Server Code Name "Denali" (SQL 11).
Starting with SP1, a new -RbsProviderMapping parameter is added to the Move-SPSite PowerShell cmdlet to let
the operation keep file content stored in RBS in the same location when the same RBS provider is configured on
both the source and the target content databases.
When you use the Chart Web Part on a page in a site that is enabled for anonymous access, the Chart Web Part
will crash and return "Object reference not set to an instance of an object" message.
A call to listdata.svc will fail for lists that contains a calculated field for which the validation formula returns a
boolean value and for which the data type is set to "Yes/No."
Using Linq to SharePoint in partially trusted code applications will fail if the Linq query contains reference to local
variables.
Before SP1, there was no way for developers for obtain custom errors and exceptions back for Listdata.svc.
Starting with SP1, developers can set the CallStack property to "true" in the web.config file to obtain the actual
error message and the call stack.
Image URLs are broken after you apply a theme.
A date field in a MySites page does not let user enter a date in the user's native date format.
Parentheses are positioned incorrectly in "right-to-left" languages in Group By view.
Users cannot use the My Site Settings page to accept "Secondary My Site Owner" input.
When you add the colleagues web part to your My Content page and then click the link to manage colleagues
from the colleagues web part, you receive an error message.
The user adds a Media Player Silverlight control on a SharePoint page and then loads an unsupported video file
into the control. In this scenario, there is no convenient way for the user to access the file through an alternative
media player.
Before SP1, there was no convenient way for users to select a video frame to set as the Thumbnail. Starting with
SP1, this functionality is provided through the "Video Thumbnail Picker" feature.
You use the Silverlight-based Organization Browser to find a specific person, and then you visit another
webpage. If you then click "Back" in the browser, the specific (person found) webpage is not remembered. The
default page is displayed instead.
When the Silverlight-based Organization Browser is included on a page that is not in the same web application as
the profile page where the browser is included by default, the browser will prompt for a username/password or
just not work.
When you view a list that is displayed as "Group By" sections, the dates in those sections are not localized.
Therefore, those dates may seem to be wrong.
Hebrew dates that are displayed in group headers in an XSLTListViewWebPart are incorrect when grouping is
enabled.
The Media section of the ribbon contains two buttons that are nonfunctional for editing or creating blog posts,
"Audio and Video" and "From SharePoint" under Images.
Users cannot see how their SharePoint storage is being used.
The upgrade progress indicator in the SharePoint 2010 Products Configuration Wizard get stuck at "10%" while
you are running an upgrade after you apply an update.
If third-party code fails while it reacts to SharePoint password changes, the password change process is not
completed.
If you create a one-letter list name, the tree view control will display the wrong information and issue an
expensive query.
You cannot create a new OneNote notebook in a OneNote 2010 document library. The following error appears:
"'New Document' requires a Microsoft SharePoint Foundation-compatible application and web browser. To add
a document to this document library, click the 'Upload Document' button."
Performance issues exist when downloading large files.
When you edit permissions, the keyboard focus on browsers other than Internet Explorer is not correctly placed
in the dialog box when you click the Grant Permissions ribbon button.
Small ribbon buttons may be read as "javascript:" by screen readers.
A JavaScript error occurs when using the Picture Library Slideshow Webpart and there is a carriage return in the
picture description.
A SharePoint managed account user receives repeated password expiration warnings even though the account's
password is set to never expire.
An email alert is not sent when a document is deleted that does not have a major (published) version.
The Document expiration column gets modified when a full crawl is run.
Alerts do not function correctly in several scenarios.
If you have a required multiple value lookup that is not included in the view, when you switch to datasheet view,
duplicated entries are displayed.
The browser is not automatically refreshed after a form is saved to the form library by using the "Edit in
Microsoft Office InfoPath" functionality.
SPWeb.GetSiteData(SPSiteDataQuery) that filters on an indexed field has poor performance when list items are
organized into folders.
The default settings on content databases for maximum number of site collections and for warning level for site
collections are higher than the current published guidelines recommend.
When a user uploads a document that has a very large number (such as 1 million) of links, the database
becomes bogged down.
After you apply an update but before the build-to-build upgrade is run, some components, such as the
"Microsoft SharePoint Foundation Usage Data Import” timer job, are not executed.
Deleting a Recycle Bin item takes too long.
After a full crawl, items that were deleted between the last incremental crawl and the full crawl remain in the
index and remain searchable. Starting with SP1, these deleted items are removed from the search index after a
full or incremental crawl.
Operations, such as "stsadm -o backup", "stsadm -o mergecontentdbs", or the Move-SPSite Windows
PowerShell cmdlet, do not work correctly for some language sites.
Orphan data is left behind in the database after versioned list items are deleted from the Recycle Bin.
You move a site collection, but the config database updates fails. Therefore, the site collection is not available in
the new location. It is also not available in the original location because was deleted.
When you issue an SPQuery that uses list joins and projections, the query returns a "One or more field types are
not installed properly ... " error message.
On Galician blog sites, the date box on the left side of a blog entry shows the month and the day reversed.
When you click "Test Link" in the Image Viewer web part, the browser crashes.
Users experience publishing failures.
When you send a meeting request that has an exception to a SharePoint calendar, only the last exception is
displayed on the Calendar. If you try to send that same meeting request again, the last exception is duplicated,
and the duplicate event cannot be deleted.
When you delete a folder that is inside a list, attachments to the list items that are contained in the folder are
not deleted.
The JAWS screen reader reads ribbon menus incorrectly in Firefox.
Right and left alignment icons in the Ribbon are mirrored incorrectly in "right-to-left" language versions.
Before SP1, you could not have some pages rendered in Internet Explorer 9 document mode (instead of Internet
Explorer 8). Starting with SP1, a control is available that lets you set individual pages to be rendered in Internet
Explorer 9.
Calendar view is not rendered correctly when the browser window is resized.
If a SharePoint managed account is removed in Active Directory, the account cannot be unregistered from
SharePoint.
When you try to search in Help as a non-administrator, no results are returned.
URLs to documents in document libraries are very long and include the Source parameter when the URL is
copied (e.g., by right-clicking and selecting Copy Shortcut). In SP1, the Source parameter is not included in a
copied URL, so the URL is much shorter.
On a single page, if a combination of a CAML list view (or any non-XSLT list view, such as Calendar) and an XSLT
list view (list or document library) is present and Group By views is enabled on the XSLT view, a problem occurs
when groups in the XSLT list view are expanded. After a page refresh, a script error occurs and the groups cannot
be expanded again.
When you use the Backup-SPSite Windows PowerShell cmdlet with the -UseSqlSnapshot parameter, an error
occurs.
After a user changes a doclib content type field from required to hidden, they cannot check in a file of that
content type.
The Quick Launch is difficult to navigate using accessibility tools.
Before SP1, the Title field on attachments was a required field. Therefore, users had to supply a title to save a
document. Starting with SP1, the Title field is no longer a required field.
Group owners cannot delete the SharePoint groups that they own.
erver Applications

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:3/26/2013
language:English
pages:23