Microsoft Office Servers 2010 FAQ/ReadMe



All known issues below are grouped by application.

All Servers

Upgrade

When attempting to upgrade a database to SharePoint 2010 by doing a database attach process, if the source web application was Windows Auth and the destination is Claims enabled Windows Auth, upgrade can fail.

This issue occurs because the upgrade process is not able to add a windows claims format identity with Full Control as a web application policy for the person performing upgrade.

The mitigation for this is either to upgrade the database by attaching to a legacy Windows Auth web application first to initiate upgrade and then migrating to Claims enabled Windows Auth after upgrade is complete, or to include a “Full Control” web application level policy for the windows claims format for the user doing the database attach upgrade process.

Performing a farm upgrade using the SharePoint 2010 Products Configuration Wizard (PSConfigUI.exe) can result in an error.

The error message might have the following information:

[psconfigui] [SPUpgradeSession] [ERROR] [2/5/2010 1:22:32 PM]: This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.

Attempting to restart upgrade may fail with no entries written to the upgrade logs. This issue can occur if the service account used to run the timer service has expired or is otherwise invalid which prevents the timer service from starting during upgrade. Attempting to restart an upgrade while a server is in this state will prevent upgrade from succeeding.

To solve this issue, you need to update the farm and local machine settings for the timer service with updated password information for the farm account using the following command:

stsadm.exe -o updatefarmcredentials

Once this has been completed successfully, and the timer service has started, you should be able to resume upgrade by restarting SharePoint 2010 Products Configuration Wizard (PSConfigUI.exe).

Reporting Services Integration

When selecting a Reporting Service report file (.rdl), and right clicking to display the context menu, the reporting services specific icons are missing.

The SQL Reporting Services add-in creates new directories and files under the %programfiles%\Common Files\Microsoft Shared\Web Server Extensions\12\Template\images directory. After an in-place upgrade these files and directories are copied to matching locations under the %programfiles%\Common Files\Microsoft Shared\web server extensions\14\ directory, but they have the wrong ACLs on the directories and files which prevents reporting services from displaying its own icons correctly.

To prevent this issue you can upgrade the reporting service web parts to the SQL 2008 R2 version before upgrading to the SharePoint 2010 products, which will prevent the ACL issues that occur during upgrade if using earlier versions of the reporting services web parts.

Alternately, if after upgrading to SharePoint 2010 products, you encounter this issue, you can change the ACLs on the added directories to allow the icons to be displayed. In this case you will have to update the directory ACLs on the server to include read permissions for the Users group on the following directories:

  • ReportServer
  • lg_ReportServer

The above re-ACLing process may also be required if the SQL 2008 R2 version reporting services components are installed or upgraded after installation or upgrade of SharePoint 2010 products on the server.

Document Layout

Microsoft Office 2010 documents may lay out differently on Windows Vista and Windows 2008 Server compared to Windows XP and Windows 7.

Microsoft Office 2010 includes the latest version of several fonts also available in Windows 7. However, Office 2010 cannot install these fonts on Windows Vista or Windows 2008 Server because they are system protected on these operating systems. As a result, Office 2010 documents may lay out differently on e.g., Windows 7 and Windows Vista.

This issue is fixed in an update for Windows Vista and for Windows Server 2008. This update removes the system file protection of some font files.

 Important    Users who have already installed Office 2010 on Windows Vista and Windows 2008 Server, and willing to get the latest version of the fonts, must first uninstall Office 2010, and then install the Windows update prior to re-installing Office 2010.

To install this update, follow the instructions in the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/980248.

Top of Page Top of Page

All Servers (Language Specific)

Setup

FAST Search Server configuration fails on Italian Win2k8 SP2 X64.

Post Setup Configuration fails with this error:

Exception -  : Exception - Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.Exception.DeploymentException: XML Validation error: L'attributo 'modifiedTime' non è valido. Il valore '2010-04-16T14.35.48Z' non è valido per il tipo di dati 'http://www.w3.org/2001/XMLSchema:dateTime' - La stringa "2010-04-16T14.35.48Z" non è un valore XsdDateTime valido.   in Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.SystemModel.SearchInstallation..ctor(String deploymentXML)

Translated into English:

Exception -: Exception - Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.Exception.DeploymentException: XML Validation Error: The attribute 'modifiedTime' is invalid. The value '2010-04-16T14 .35.48 Z 'is invalid for data type' http://www.w3.org/2001/XMLSchema:dateTime '- The string "2010-04-16T14.35.48Z" XsdDateTime is not a valid value.   in Microsoft.SharePoint.Search.Extended.Installer.Mahasen.Common.SystemModel.SearchInstallation .. ctor (String deploymentXML)

Best workaround is to install Win2k8 R2 instead of Win2k8 SP2. Alternative workaround is to delete the file: C:\FASTSearch\etc\deployment.xsd. If that file is not found, schema validation will not take place.

FAST Search Center Setup:

Replacing the default FASTSearch certificate with a new certificate using the provided script: ReplaceDefaultCertificate.ps1 fails on Japanese OS.

Workaround:

  1. Make a backup of the file.
  2. Replace the wrong "-eq" with a new "-eq" and save.

 Note    : This is not recommended in production environments as modifying this file breaks future patching of it. It cannot be replaced by a patch later.

Dialog Boxes (Hindi)

Text is too small in some menus and dialog boxes in the Hindi version of Office 2010 on Windows 7:

In Windows 7 the Mangal font used for Hindi and other Devanagari-based languages was updated to version 5.90 to improve the level of detail in individual characters. A side-effect of this update was to produce smaller text. This made text displayed using the Mangal font difficult to read in menus and dialogs, like in the Hindi version of Office 2010.

Answer:

Install Windows 7 SP1.

Top of Page Top of Page

Assistance Platform

MOSS Web Analytics Web Part

Search Service Application (SSA) needs to be present and Search Content needs to have been crawled in order to make Web Analytics Web Part to work properly. Both of Web Analytics Web Part's data type relies on functioning Search Service Application :

  1. data type "Content" needs to call Security Trimming provided by Search
  2. data type "Queries" uses data gathered during user search activities. 

If the Web Part shows No Result to Show it might because of the absence of Search Service Application.

If the Web Part shows Error occurred while retrieving data, it might because content crawling has not been done.

Do some basic search queries on the Site to see whether Search is working at all, then check ULS log for more information in those situations.

If SSA is absent, go to Central Admin -> Manage Service Applications, or use Farm Configuration Wizard to create one.

If SSA is present but crawling is not done, go to Manage Service Applications then manage the SSA (highlight the SSA then click Manage button on the Ribbon). See if Crawl History contains anything (history or errors). Click Content Sources link on the Left-Nav panel under Crawling section then navigate to the Manage Content Sources page. By default there should be Local SharePoint sites listed (or other content sources). Click the content source's name, from the dropdown list choose Start Full Crawling then wait for the crawling to be done.

After any of the fixes mentioned above, perform an IISReset to clear Web Analytics Web Part's cache and let it to retrieve data again.

Top of Page Top of Page

Business Connectivity Services

No issues at this time.

Top of Page Top of Page

Excel and Access Services

No issues at this time.

Top of Page Top of Page

Enterprise Content Management

No issues at this time.

Top of Page Top of Page

IME

IME(JPN)

SharePoint dictionary is installed only in the latest IME. When user installs Office 2007 IME and Office 2010 IME, and installs the SharePoint dictionary, the installed dictionary is only registered in the Office 2010 IME.

Top of Page Top of Page

Mobility

No issues at this time.

Top of Page Top of Page

Office Web Applications 2010

Styles

The Locale I've set for my document library <> English.

When I use the WAC Word editor to create text with a previously unused built-in style such as Heading 4 the style definition is the same as English. Before editing any documents that are language-specific

  1. Set the locale for the site
  2. Close your browser
  3. run IIS Reset

Top of Page Top of Page

Project Server 2010

No issues at this time.

Top of Page Top of Page

SharePoint Business Intelligence

Setup/Configuration

Upgrading: After upgrading from a prerelease version of PerformancePoint Services to the released version, the sample Excel Services workbook that is located in the Business Intelligence Center no longer works.

   

Answer: When upgrading from a prerelease version to the RTM version of PerformancePoint Services, you must replace any sample workbooks that are available in the Business Intelligence Center.

You can either download an updated workbook or you can create a new Business Intelligence Center site.

Setup: Do I need to install any SQL Server redistributables with PerformancePoint Services Beta 2?

   

Answer: If you intend to connect to Analysis Services data sources (that is, you are choosing the Advanced installation option), you must install the December 2008 Feature Pack for Microsoft SQL Server 2005. This feature pack includes two required components: ADOMD.NET and Management Objects Collection (XMO).

To download this feature pack, visit: Feature Pack for Microsoft SQL Server 2005 - December 2008 (http://go.microsoft.com/fwlink/?LinkId=157389).

Setup: When you upgrade from Microsoft Office SharePoint Server 2007 to Microsoft SharePoint Server 2010, the names of some kinds of Web Parts might not be updated.

   

Key Performance Indicators that were created by using SharePoint Server 2007 are now called Status Indicators in SharePoint Server 2010. and KPI Details that were created by using SharePoint Server 2007 are now called Indicator Details in SharePoint Server 2010. KPIs and KPI Details reports are now created by using PerformancePoint Dashboard Designer.

Workaround: None.

Setup: As a SharePoint site administrator, what do I need to know if I am creating a new Report Center site with PerformancePoint Services Beta 2 after upgrading with the DB-attach method?

   

Answer: Before going live, edit the ONet.XML file that corresponds to the Report Center Site Template to force the site to use the new master page. This will ensure that, when your users create new Report Center sites, the sites will use the new master page.

Setup: When Dashboard Designer is opened, associated SharePoint lists, such as PerformancePoint Content and Data Connections, might not load automatically.

   

This can occur because of how certain security settings are configured in SharePoint Server. In particular, this can occur when security settings are configured such that the FQDN InternetSecurityManager.MapUrlToZone returns the Web site address (URL) as an Internet URL. Valid MapZoneToUrl return values include Local, Intranet, Trusted, Internet, or Restricted; however, when Internet is selected, the necessary SharePoint lists will not load. This can also occur when the IP address is used in place of the URL.

Workaround: Do one of the following:

  • Specify the correct SharePoint Server URL.
    To do this, click the Backstage button, and then click Designer Options. Click the Server tab, and then specify the URL for SharePoint Server. Then click OK.
  • Add the FQDN and IP address as trusted sites.

Setup: Users cannot find Dashboard Designer on their Start menu.

   

Previous versions of PerformancePoint Dashboard Designer are not automatically removed from the Start menu when you upgrade to PerformancePoint Services in Microsoft SharePoint Server 2010.

Workaround: Use the following procedure:

  1. Locate an old version of Dashboard Designer on the Start menu. Browse to one or both of the following locations:
  • Click Start > Programs (or All Programs) > Microsoft Office PerformancePoint Server 2007 > Dashboard Designer.
  • Click Start > Programs (or All Programs) > PerformancePoint Services for SharePoint > Dashboard Designer.
  1. Right-click on Dashboard Designer, and then click Delete.
  2. Install and launch the latest version of Dashboard Designer.

Setup: When you upgrade to Microsoft SharePoint Server 2010, status indicators that are displayed in a KPI Web Part might not display leaf members correctly.

   

This can occur with KPI Web Parts that have multiple columns and that were created by using Microsoft Office SharePoint Server 2007.

Workaround: Remove the multiple columns from the KPI Web Part, and then add them back to the report. The leaf members should then display correctly.

Setup: If you are upgrading from a Beta version to the RTM version of PerformancePoint Services 2010, you may need to manually configure the web.config file to enable the creation of list items.

   

When you upgrade from a Beta version of PerformancePoint Services to the RTM version, the section that contains the list item components is removed. Thus, any attempt to create a new list item will be unsuccessful.

Workaround: To restore the deleted section, edit the web.config file as follows:

  1. Within the "configsections" tags, insert the following code:

<sectionGroup name="Bpm">
<section name="FCODaoProviders"
type="System.Configuration.DictionarySectionHandler" />
</sectionGroup>

  1. Just in front of the "configuration" closing tag (/configuration), insert the following:

<Bpm>

<FCODaoProviders>

<add key="DashboardSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.DashboardSPDao, Microsoft.PerformancePoint.Scorecards.Store,
Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c" />

<add key="DataSourceSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.DataSourceSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add key="FilterSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.FilterSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add key="IndicatorSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.IndicatorSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add key="KpiSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.KpiSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add key="ReportViewSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.ReportViewSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

<add key="ScorecardSPDao" value="Microsoft.PerformancePoint.Scorecards.Store.Dao.ScorecardSPDao, Microsoft.PerformancePoint.Scorecards.Store, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c" />

</FCODaoProviders>

</Bpm>

 Note    Any list items that you attempted to create in the upgraded product will be included in this "Bpm" section.

Data Sources

Data Sources: PerformancePoint Services 2010 does not support SAP BW connectivity.

   

No workaround.

Data Sources: If your data includes ISBN identifiers, in which the first number is typically a zero, the zero is dropped from the ISBN ID.

   

Workaround: Replace the initial zero in ISBN IDs with an alphabetic character.

Data Sources: Why do I get an error message when I attempt to delete a service application?

   

If you attempt to delete a service application that still uses a dependent proxy, you will receive an error message.

Workaround: Delete the service application proxy first, and then delete the service application. To delete either item, select it and then, from the ribbon, delete it.

Data Sources: Why am I unable to create or edit an Excel 2007 workbook data source in PerformancePoint Services?

   

Answer: If you are running Excel 2007 on a 64-bit operating system, you will not be able to create or edit workbook data sources. Only the following environments are supported for this feature:

  • 32-bit OS: Office 2007 Office 14
  • 64-bit OS: Office 14 (x64)

Data sources: If you receive an error message while attempting to use an Excel Web Applications workbook as a data source, it is likely that you have installed a Click-to-Run version of Excel. The error message indicates that Excel is not installed.

   

Microsoft Excel Web App workbooks that use the Click2Run (virtualized) version of Office 2010 cannot be used as a data source within PerformancePoint Services.

Workaround: Use the regular (retail) version of Excel 2010.

Data sources: If you create an analytic report that uses PowerPivot as a data source and then attempt to deploy the report in a dashboard, you may be prompted for user credentials and receive an error message.

   

To use PowerPivot as a data source for a PerformancePoint Services analytic report, you must first install a Windows hotfix (see: KB article: 975954).

Data Sources: Scorecards that use a tabular data source that has been configured to use Time Intelligence can display inaccurate information, depending on which time zone is specified in SharePoint Server.

   

When you create a tabular data source, such as a SharePoint Custom List, and you use the Date-Time column, the values that you add to the list are stored in the UTC time zone by default. This occurs even if you are in a different time zone. However, when you configure that data source to work with Time Intelligence, all input values must use the UTC time zone. Otherwise, incorrect information can be displayed in scorecards that use that data source.

Workaround: Make sure that all tabular data sources that include date-time values use the UTC time zone.

Data Sources: Using Dashboard Designer, when you reopen a KPI, its data source is not displayed in the Details pane.

   

When you reopen one or more KPIs in your workspace in PerformancePoint Dashboard Designer, the data sources used by those KPIs are not automatically opened in the workspace.

Workaround: Locate the data sources that are used by the KPIs and double-click each one to open it in the workspace. Then, in the Details pane, use the Data Source list to select the appropriate data source for each KPI.

Data Sources: When you create scorecards or analytic charts or grids that use data stored in PowerPivot for Excel 2010, you cannot use Named Sets.

   

Named Sets that are created by using PowerPivot for Excel 2010 are available only in the Excel file in which they were created.

Workaround: None.

Data Sources: Dashboard users cannot use Drill Down, Drill Up, or Show Details in a scorecard or an analytic chart or grid that use data stored in PowerPivot for Excel 2010.

   

This can occur because user hierarchies are not supported in PowerPivot for Excel 2010.

Workaround: None.

Data Sources: You cannot import KPIs that are created by using PowerPivot for Excel 2010 as Status Indicators in Microsoft SharePoint Server 2010.

   

You can create KPIs by using PowerPivot for Excel 2010, but you cannot save those KPIs in the data cube.

Workaround: None.

Data Sources: Member properties are not available in analytic reports and scorecards that use PowerPivot for Excel 2010 as a data source.

   

PowerPivot for Excel 2010 does not expose member properties within the data cube.

Data Sources: Certain analytic reports and scorecards do not display numeric formatting that is applied in the data cube.

   

This occurs with scorecards, analytic charts, and analytic grids that use data from PowerPivot for Excel 2010. Formatting that is applied to measure values does not carry over to PerformancePoint reports and scorecards.

Data Sources: When you attempt to display an image in a grid view, the hardcoded URL displays, but not the actual image.

   

PerformancePoint Services cannot display images that are linked with hardcoded URLs to product dimension attributes.

Workaround: Use SQL Server Reporting Services (SSRS) to create a report, and then link that report in PerformancePoint Services dashboards as a SSRS report.

Data Sources: The background color of a shape in a strategy map does not update as performance changes for a KPI.

   

This can occur when the scorecard KPI uses Time Intelligence.

Workaround: None.

Data Sources: Error messages display in scorecard cells instead of numeric values.

   

These errors can occur in scorecards that use calculated members, such as those that use a Time Intelligence formula, a dimension filter, or a calculated measure in a data cube. The errors can also occur because the default aggregation setting for the KPI measures is set to Aggregate.

Workaround: Do one of the following:

  • Do not use calculated cube measures in your scorecard. Instead, select another measure by using the Dimensional Data Source Mapping dialog box. To do this, use the following procedure:
  1. In the Workspace Browser, double-click the KPI that uses the calculated cube measure. Then, in Actual row, locate the Data Mappings column, and double-click the hypertext in the cell. The Dimensional Data Source Mapping dialog box opens.
  2. In the Select a Measure section, use the drop-down list to select a measure.
  3. Click OK to close the Dimensional Data Source Mapping dialog box. Then, in the Workspace Browser, right-click the KPI that you just modified and then click Save.
  4. In the Workspace Browser, double-click the scorecard that contains the KPI that you just modified. In the ribbon, click the Edit tab, and then click Update. The scorecard should render correctly.
  5. In the Workspace Browser, right-click the scorecard that you just modified, and then click Save.
  • Configure the aggregation for KPI Measures by using the Dimensional Data Source Mapping dialog box. To do this, use the following procedure:
  1. In the Workspace Browser, double-click the KPI that uses the calculated cube measure. Then, in Actual row, locate the Data Mappings column, and double-click the hypertext in the cell. The Dimensional Data Source Mapping dialog box opens.
  2. In the Aggregate Members By section, use the drop-down list and select one of the following options: Sum, Minimum, Maximum, Count, or Average.
  3. Click OK to close the Dimensional Data Source Mapping dialog box. Then, in the Workspace Browser, right-click the KPI that you just modified and then click Save.
  4. In the Workspace Browser, double-click the scorecard that contains the KPI that you just modified. In the ribbon, click the Edit tab, and then click Update. The scorecard should render correctly.
  5. In the Workspace Browser, right-click the scorecard that you just modified, and then click Save.

Data Sources: If you receive an Unexpected Error message when attempting to select a data source from the list in Dashboard Designer, you may have encountered a known backwards-compatibility issue.

   

Workaround: To connect to an Excel Services 2007 workbook in Dashboard Designer, you must manually enter the item name. The older-version workbook will not automatically appear on the drop-down list of data sources.

PerformancePoint Reports and Scorecards

Reports: On occasion, all the reports and scorecards in a PerformancePoint dashboard might not render correctly and display an Access Denied error message.

   

This can occur because of a database failover issue.

Workaround: You can refresh the browser window or open the dashboard in a new browser window.

Reports: My PerformancePoint Web Page report does not display properly.

   

This can occur when the Web site address (URL) that is used for the Web Page report exceeds 2048 characters, which is the limit for some browsers. See: http://support.microsoft.com/kb/q208427/.

Workaround: Contact your IT Administrator to verify the permissible length of a URL. If necessary, use a shorter URL.

Scorecards: Scorecard aggregations that include empty cells, do not display the expected results. That is, the empty cells are not shown as having a "zero" value.

   

No workaround.

Scorecards: Some columns in a scorecard appear to be too wide or contain numeric values that overlap indicators.

   

This can occur when an indicator is displayed in a browser (including Internet Explorer, Mozilla Firefox, or Safari) for the first time.

Workaround: First, refresh the dashboard page. The scorecard should render correctly. If it does not, redeploy the dashboard.

Scorecards: When users expand dimension members in a PerformancePoint scorecard that is connected to an analytic chart or grid, an error message occurs.

   

This can occur when the connection is made by using "edit mode" in a SharePoint site or by using SharePoint Designer.

Workaround: Do one of the following:

  • Refresh the dashboard page.
  • Delete the connection between the scorecard and the analytic chart or grid. Then, recreate the connection by using PerformancePoint Dashboard Designer.

Scorecards: When you upgrade from Microsoft Office PerformancePoint Server 2007 SP3 to PerformancePoint Services in Microsoft SharePoint Server 2010, scorecards might display blank or inaccurate indicators.

   

This can occur because of changes in how KPI scores are calculated.

Workaround: Using PerformancePoint Dashboard Designer, open and modify the banding settings for the KPIs that are used in scorecards. Then save your changes to SharePoint Server, and redeploy your dashboards.

Scorecards: When users add an annotation to an objective KPI that is used more than once in a PerformancePoint scorecard, that annotation is displayed in every occurrence of the objective KPI.

   

This can occur even if different dimension members are listed under the KPIs in the scorecard. This is because KPIs are uniquely identified by their name, and not by the scorecard cells in which they appear.

Workaround: Use a unique name for each objective KPI in the scorecard.

Scorecards: When you have a scorecard open in Dashboard Designer and you attempt to add a comment to a scorecard cell, an unknown error message displays.

   

The error message can occur because Enable comments is not selected in Central Administration settings for PerformancePoint Services.

Workaround: None

Scorecards: When I add a comment to a scorecard cell, the comment author is identified as i:Anonymous first time only. Why am I (my user account) not identified as the author?

   

If you have privileges in PerformancePoint Services, but are just not logged into SharePoint, PerformancePoint Services automatically authenticates you based on your Windows credentials when authoring comments in a scorecard. This issue occurs when the Anonymous Users account has been given access to the SharePoint site.

 Note    This automatic authentication only affects comment authoring in the scorecard.

Workaround: Refresh the page.

Reports: If you encounter an error message while attempting to create a strategy map report in Dashboard Designer, you may not have the correct version of Microsoft Visio installed.

   

You must have the version of Visio installed that is compatible with PerformancePoint Dashboard Designer.

  • If you are using the 64-bit edition of Dashboard Designer, then you must install the 64-bit edition of Microsoft Visio 2010.
  • If you are using the 32-bit edition of Dashboard Designer, then you must install the 32-bit edition of either Microsoft Office Visio 2007 or Microsoft Visio 2010.

Reports: When users try to change the analytic grid to another report type, an error occurs. This can occur when issues on the server prevent the SharePoint Server prerequisite installer from including the Microsoft Chart Controls for Microsoft .NET Framework 3.5.

   

Manually install the Microsoft Chart Controls for Microsoft .NET Framework 3.5 (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=130f7986-bf49-4fe5-9ca8-910ae6ea442c&displaylang=en.

Reports: The background color of a shape in a strategy map does not update as performance changes for a KPI.

   

The Strategy Map requires that time intelligence (TI) be displayed on rows; if TI is placed on columns, it will not display properly.

Workaround: None.

Reports: An exception error occurs in the Decomposition tree when attempting to analyze non-cube data (data that is not in a SQL Server Analysis Services multi-dimensional database).

   

Decomposition tree can only be used with Analysis Services data sources. It cannot be used with data that is pulled from the following:

Excel Services, Import from Excel Workbook, SharePoint List, SQL Server Table, or other custom data sources.

The error occurs if the actual or target calculation for a KPI is set to "Data value."

Workaround: Do not set calculation type to "Data value" for non-Analysis Services data sources.

PerformancePoint Dashboard Designer

Dashboard Designer: Dashboard Designer does not launch from the Business Intelligence Center when using the Safari browser.

   

We recommend that you use Internet Explorer to launch Dashboard Designer for the first time. After that, you can launch Dashboard Designer by using the Start menu (Click Start > All Programs > SharePoint > PerformancePoint Dashboard Designer).

Dashboard Designer: On Windows 7 (64-bit): When you attempt to enlarge the display of an analytic report by resizing Dashboard Designer, the resized report renders poorly.

   

Workaround: Minimize and then restore the Dashboard Designer window after resizing.

Dashboard Designer: In Dashboard Designer, when you reopen a KPI, data source for the KPI is not displayed in the Details pane.

   

When you reopen one or more KPIs in your workspace in PerformancePoint Dashboard Designer, the data sources used by those KPIs are not automatically opened in the workspace.

Workaround: Locate the data sources that are used by the KPIs and double-click each one to open it in the workspace. Then, in the Details pane, use the Data Source list to select the appropriate data source for each KPI.

Dashboard Designer: An Unhandled Exception (error code 20604) occurs in the Decomposition Tree after selecting Pivot and then Decomposition Tree.

   

This error occurs if you pivot a report with time-intelligence calculated members and then attempt to analyze the data in the Decomposition Tree. The pivot causes the calculated members to be placed on rows rather than on columns where they can be validated.

Workaround: Do not pivot a report that includes time-intelligence calculated members as these members must remain on columns.

Dashboard Designer: An error may occur when you click Import Items button in Dashboard Designer. The error message Cannot publish Read Only element.

   

This error will occur when the user who saves the workspace file does not have permission to edit one or more of the SharePoint items.

Workaround: In the workspace file, search for all of the ReadOnly attributes using the following string: ReadOnly=. Change any that have their value set as true to false. After saving these changes to the workspace file, you will be able to successfully import the items as expected.

Dashboard Designer: When you attempt to run and install PerformancePoint Dashboard Designer for the first time using Mozilla Firefox, you might get an error message.

   

The error message indicates that you cannot download the application, and that the application is missing required files. This can occur if Microsoft .NET Framework Assistant 1.1 is not installed on your computer.

Workaround: Install the Microsoft .NET Framework Assistant 1.1.

Dashboard Designer: When you open an analytic chart or grid for editing in PerformancePoint Dashboard Designer, its data source is not automatically available. The dashboard item appears to open, but no data source is displayed in the Details pane. In addition, you cannot expand Measures, Dimensions, Named Sets, or other items in the Details pane.

   

This behavior can occur when the data source that is used by the dashboard item is saved in a different SharePoint site or level within a site collection.

Workaround: Manually load the data source by opening it in Dashboard Designer. The data source will display and connect properly if the data source and the analytic chart or grid is in the same workspace.

Dashboard Designer: On rare occasions, a non-English (translated) version of Dashboard Designer will display English text in some dialogs.

   

Workaround: To resolve this issue, restart Dashboard Designer.

Dashboard Designer: How do I prevent nested (extra) scrollbars from displaying in my published report?

   

This issue occurs in reports that connect to data in an Excel Services report. When you attempt to open this type of report in SharePoint, a dialog displays the following: Do you want to enable queries to external data in this workbook? When you click Yes to close the dialog, the report displays with an extra set of scrollbars.

Workarounds: There are three workarounds for resolving this issue. The first workaround applies to any time the extra scrollbars appear.

  1. In Dashboard Designer, apply the Auto-size property to the report.
  2. Configure Excel Services to prevent the dialog from displaying when the report is opened.
  3. Build your dashboard in SharePoint Designer rather than in the Dashboard Designer, and use the native Excel Services Web Part rather than the PPS Excel Services Web Part.

Dashboard Designer: An error message occurs when Dashboard Designer users attempt to put dimension members in the background of an analytic chart or grid.

   

The error message indicates that there was an error running the data source query.

The error message can occur when a Dashboard Designer user puts a dimension in the Background section of an analytic chart or grid, selects the All option in the list of members, and then selects one or more individual members.

Top of Page Top of Page

SharePoint Designer 2010

No issues at this time.

Top of Page Top of Page

SharePoint Server 2010 Core

User Profile Synchronization

Profile Synchronization is not supported in standalone installs.

Use Complete install and run the farm configuration wizard for similar experience.

Connection to an AD or LDAP source can't be created.

In order to do incremental sync with AD, the connecting account (specified during connection creation) must have DirSync privileges in AD. These privileges don't allow writing into AD but permit the account to request/perform incremental queries, allowing the incremental sync to run efficiently. Similar permissions (to read the changelog) are required for supported LDAP servers, when changelog can be setup for the LDAP server.

New OUs added to AD/LDAP are automatically selected without any notification.

A SharePoint admin has created a connection, say with OU1 and OU2 selected. Additional OUs are added in AD/LDAP by the AD/LDAP admin, for example, because of some reconfiguration or acquisition scenario. SharePoint admin edits the connection for some reason, expands the container tree and clicks OK. The new OUs added to AD/LDAP are automatically selected without any notification. Subsequent imports bring in users/groups in these OUs.

Always double-check the OUs that are selected. If users/groups do come in and shouldn't have been imported, either deselect the OU and/or delete them by using the central admin user profile management UX.

Setting up a connection can be complex or slow.

Example:

Set up AD Connection

  1. Go to the UPA management page: Central admin Site -> Application Management -> Manage Service Applications, and choose the UPA, and click Manage.
  2. In the UPA management, choose Configure Synchronization Connections to go to connection management page.
  3. Click Create a New Connection to go to connection editing page.
  1. To import profiles from AD, choose Connection Type Active Directory.
  2. Fill the connection information.
  3. Click OK (Be patient as it may take a little bit time)
  4. If the connection is created successfully, the page is redirected to the connection management page and the connection is listed in the connection management page.
  1. (Optional) You can set exclusion filter for the connection so as to exclude certain users/groups from being imported to MOSS
  1. In the Connection Management page, choose the connection you want to set exclusion filter, right click Edit Connection Filter.

All property mappings are strongly typed.

For example, an AD property of string type cannot be mapped to an attribute of type int in the profile store.

Delete the property and recreate it with the same name and the right type. This will result in data loss for upgrade scenario but this data can be recovered if the property is remapped to the source (e.g. AD) and a sync is run. Since we didn't allow export in previous versions, data being mapped should be available in this external store.

Export and safe-keep the encryption key needed for any move or backup/restore scenarios.

Without these keys, you'd have to re-provision and rerun full sync. HIGHLY RECOMMENDED: Export the sync encryption key and save it in a safe place. Along with saving the key in a safe place, you can also import it on all machines in the farm. This simply adds information to the registry of these machines, in case you were to move the service to this machine.

If re-starting profile synchronization on the same machine, the export/import encryption key step is not needed.

  1. Save FIM encryption key. in the machine where the profile sync service is running, go to the folder:
    %program files%\Microsoft Office Servers\14.0\Synchronization Service\bin, and run the following command to export the encryption key to a file:
  • miiskmu.exe /e [filename] /u:[domain\user] [password] where
  • /e – File to save the exported keys.
  • /u – the service account that has the keys
  1. Stop Profile Synchronization service. Stop the profile synchronization service on the machine where it is running: in Central Admin Site -> Manage Services on Server, choose the machine and click to stop the profile synchronization service. Wait till profile synchronization service being stopped.
  2. Start Profile Synchronization service. Then in the same service management page, choose another machine, and then click to start the profile synchronization service.

 Note    The profile synchronization service is kept in the status Starting. Checking the Windows EventLog, you may find the error message from FIM synchronization service that is indicating certain encryption key missing.

  1. Import FIM encryption key. Log in to the machine where the profile synchronization service is to run, go to the folder %program files%\Microsoft Office Servers\14.0\Synchronization Service\bin, run the following command using the account which is specified in exporting encryption key  to import the encryption key:
  • miiskmu.exe /I [filename]
    {0E19E162-827E-4077-82D4-E6ABD531636E}

where

  • /i – Filename which was exported in step 1.
  1. (Optional). To check that the encryption key is imported correctly, run the following command to
  • miiskmu.exe /c
    {0E19E162-827E-4077-82D4-E6ABD531636E}
  1. Wait till the profile synchronization service is started on the new machine.

User Profile Synchronization service doesn't obey the failover parameters.

The User Profile Synchronization service relies on the synchronization components from the Forefront Identity Manager (FIM, previously known as MIIS). These components utilize encryption and failover mechanisms which can be utilized per the article below.

If faced with a situation wherever failover server was not prepped in advance for synchronization service, a new db can be attached to the service and the sync service will resynchronize with the source. Since the sync service db is used as a staging for data whose source is either in SharePoint or another Directory source, while it's time consuming, the re-sync process shouldn't result in data loss. 

http://technet.microsoft.com/en-us/library/cc739274(WS.10).aspx 

MIISactivate: Server Activation Tool

Activates a standby server running Microsoft® Forefront Identity Manager (FIM) 2010, making it the primary server running FIM.

Syntax

miisactivate [FileName] [UserName {Password | *}] [/q]

Parameters

FileName

Specifies the file name, including the path, of the encryption key file.

UserName

Specifies the Forefront Identity Manager Service credentials.

MIISactivate supports the following formats:

• [Domain\]UserName

• [Domain.com\]UserName

• UserName@Domain.com

Password

Password for the Forefront Identity Manager Service. Specify * to be prompted for password.

/q

Runs in quiet mode, with no dialog boxes.

/?

Displays help at the command prompt.

Remarks

  • If password synchronization is enabled, you must run pcnscfg.exe, the password change notification configuration utility, before you activate the standby server. The password change notification service must be directed to the standby server before password synchronization can resume.
  • MIISactivate.exe is located in the InstallationDirectory\Bin folder.
  • Local Administrator privileges are required to run MIISactivate.exe.
  • If you receive the error message Exception: 0x80230443 when running MIISactivate.exe, this indicates a schema mismatch. This can occur when a service pack has been applied to the primary server, but not to the warm standby server. You should update the warm standby server with the same service pack used to update the primary server, and then run MIISactivate.exe again.
  • If you activate a standby server and are unable to open Synchronization Service Manager, it may be because the FIMSyncAdmin groups were created as local groups instead of domain groups. You will need to create the new domain group, re-run FIM setup in repair mode and specify the new domain group.

Example

To activate a backup server running FIM and make it the primary server running FIM, type:

miisactivate miis_keys.bin FIMAdmin *

If a reference attribute, such as an employee's manager exists across domains and different connections are created for the employee and manager domains, the reference attribute is not resolved.

This applies to any reference attribute (e.g. Person - colleague, manager or a custom Person attribute)

It's highly recommended, that regardless of this issue, you create one connection per directory service forest. This allows synchronization service to resolve all references within the same forest.

A synchronization run is stopping due to a large number of errors.

Certain synchronization activities result in the creation of temporary error conditions that are eventually resolved once the synchronization has had the opportunity finish running. In environments where extremely large numbers of objects are being processed the number of these errors may exceed the default error limit of 5000 causing the synchronization process to terminate before it has finished processing all objects.

Increase the error limit to a sufficient value so that synchronization can finish processing all objects before the error limit is reached. Given the opportunity to finish, the synchronization process will eventually resolve the temporary error conditions. The error limit is configured by adding the ErrorLimit (REG_DWORD) entry to the following registry subkey:

HKEY_LOCAL_MACHINE\System\

CurrentControlSet\Services\miisserver\

Parameters

The value is an integer in the range of 0-100000.

  • Value set to 0 = Error limit set to 100000
  • Value in the range of 1-99999 = Error limit set to value
  • Value set to 100000 = Error limit set to 100000
  • Value set greater than 100000 = Error limit set to 100000
  • No key present = Default error limit set to 5000

Note:

The FIMSynchronizationService service must be restarted after modifying this registry key

There is no interface for pausing or resuming the user profile synchronization process

User Profile Synchronization is a complex state machine and pausing/resuming it completely can have adverse impact and can result in complete restart of the synchronization process. In order to accomplish the end-objective of pause/resume, which is normally needed to slow-down the resource consumption by the service during peak hours, administrator can set the following registry keys on the machine where user profile synchronization service is running.

  • HKLM\System\CurrentControlSet\Services
  • \FIMSynchronizationService
  • \Performance\MaxObjectImportRate (DWORD)

This key specifies the number of objects per second that should serve as an upper bound of any Import run profile executed on the server.  During an import run, the number of objects per second measured by the “Objects Read /sec” performance counter must remain below the value set in MaxObjectImportRate. The domain for this value is 1 to Max(Int32). A value of 0, or the absence of the key will be treated as having no maximum value defined.

  • HKLM\System\CurrentControlSet\Services
  • \FIMSynchronizationService\ Performance
  • \MaxObjectSynchronizationRate (DWORD)

This key specifies the number of objects per second that should serve as an upper bound of any Synchronization run profile executed on the server.  During a synchronization run, the number of objects per second measured by the “Objects Synchronized / sec” performance counter must remain below the value set in MaxObjectSynchronizationRate. The domain for this value is 1 to Max(Int32). A value of 0, or the absence of the key will be treated as having no maximum value defined.

  • HKLM\System\CurrentControlSet\Services
  • \FIMSynchronizationService\Performance
  • \MaxObjectExportRate (DWORD):

This key specifies the number of objects per second that should serve as an upper bound of any Export run profile executed on the server.  During an export run, the number of objects per second measured by the “Objects Exported / sec” performance counter must remain below the value set in MaxObjectExportedRate. The domain for this value is 1 to Max(Int32). A value of 0, or the absence of the key will be treated as having no maximum value defined.

Running incremental sync doesn't bring in values for properties that were mapped after the last full sync was run.

For a configuration change, such as a new mapping of properties, data will not flow for existing records, unless a full sync is performed. Perform full sync.

Deployment

Different language version of OOB workflows is not available even after installing LPK in sub site.

(A user installed ENG MOSS 2010 and created a site collection. And then installed JPN LPK to use JPN OOB workflows but they are not available in the newly created site collection.)

[Detail]If the root site of the site collection was created before installation of the LPK, and the other-language sub-site is created after installation of the LPK, then the OOB workflow feature of the LPK language will not be available in the sub-site (and will not be shown in the list of available workflows).

For example, if a user installs ENG SharePoint Server, creates an ENG site collection, and then installs the JPN LPK and creates a JPN sub-site, he/she cannot see the JPN OOB workflow until he/she re-activates the “Workflows” feature via the Site Collection Settings page. Conversely, if an ENG site collection is created after the JPN LPK is installed, the JPN OOB workflow will be available.

Technically we move workflow files to under _catalog folder at feature activation time. So, to use newly installed OOB workflow feature users need to deactivate and activate Workflows feature in Site Settings | Site Collection Settings page.

User Profile Service

General SQL Perf tuning tips

  • Disk Configuration, RAID array with multiple spindles - OS,
  • Database & DB log files on separate volumes
  • Gig network between services and SQL box
  • Enable named piper if services running on same box as SQL
  • Mark CPUs for I/O affinity
  • Boost SQL Priority

OOB Workflow

Due date in workflow start notification email is shown as Due by 1/1/0001 12:00:00 AM when we start OOB workflows without setting due date.

This is confusing and annoying because we don't want to see due date if we didn't set it when we start workflows. And workflow task also has same issue. New task notification email also shows Due by 1/1/0001 when we didn't set due date when we start workflows.

Due to late change in SPD side (#3708517) some "If" statement always evaluate condition to "FALSE " so we always show incorrect due date.

There are a couple of ways we can do for fixing this problem using SPD as following: (we will take OOB "Approval - SharePoint 2010" workflow for an example)

  1. Manually modifying rule file
  • Open SPD and navigate to Site Objects > All Files > _catalogs > wfpub > Approval - SharePoint 2010 using left-side "Navigation" pane. (for copied workflow Site Objects > All Files > Workflows > {workflow name}
  • Open ReviewApproval_{LanguageID}.xoml.rules (for English build LanguageID is 1033) using Notepad. (for copied workflow open {workflow name}.xoml.rules file)
  • Search 1900-01-01 and replace it with 0001-01-01 and save.
  • Publish workflow again.
  1. Changing "If" statement
  • Open SPD and load Approval - SharePoint 2010 workflow to edit.
  • Click Approval process in workflow designer
  • Click Change the behavior of the overall task process
  • Find "If" statement we use for initial due date comparison in When the Task Process Starts slab (If Parameter: Due Date for All Tasks equals 12/31/1899 4:00:00 PM)
  • Create a new string-type like "InitialDueDateString" and assign Parameter: Due Date for All Tasks to InitialDueDateString (i.e. Set Variable: InitialDueDateString to Parameter: Due Date for All Tasks) before "If" statement.
  • Change "If" statement to "If Variable: InitialDueDateString equals 1/1/0001 12:00:00 AM"
  • Now we can see None for due date when we don't set due date at workflow start time. Similar logic can be applied to other area of workflow logic.

Users can solve this issue yet another way as necessary by using other action/condition or variables.

Top of Page Top of Page

SharePoint Server 2010 Core (Language Specific)

East Asian Group Approval

When the MOSS 2007 East Asian version is upgraded to MOSS 2010, the left navigation pane of customized 'PersonalFolder.aspx' is not displayed correctly.

For resolving this problem, the admin should update 'EawfDocLib.master' page using SharePoint Designer.

Top of Page Top of Page

SharePoint Workspace

SharePoint Workspace 2010 Web Services

When a user creates a new Folder Sharing workspace on Windows Vista, Windows Explorer will launch, but the Folder Sharing taskbar does not display.

This creates confusion about how to share the folder using SharePoint Workspace. Rebooting the computer should resolve the issue.

List item conflicts occur.

When a conflict is caused because a list item is added to a SharePoint site (server) and the same list item is edited in the SharePoint workspace (client), both having a field which needs to be unique but ends up being the same, the user is presented with 3 options in SharePoint Workspace. The 3 options are:

  1. Fix the SharePoint Workspace item
  2. Keep the server copy
  3. Keep both

In this scenario keeping both does not make sense because keeping both does not resolve the conflict.

 Note    In the opposite scenario where the item is created in SharePoint Workspace (client) and edited on the SharePoint site (server), the user is provided with 2 options in SharePoint Workspace. The 2 options are:

  1. Edit/fix the item
  2. Delete the item (keeps the server copy)
Since keeping both copies does not really resolve the issue, the user should either modify the item in SharePoint Workspace or keep the server copy, which in essence deletes the SharePoint Workspace item. Either should resolve the conflict.

Web Services Registry Key Changes and Web Services Limitations

Office SharePoint Workspace 2010 provides Web services that are compatible with the Web services available in Groove 2007. There are three significant changes: The location of the keys in the registry has changed.

The LocalRequestKey and LocalResponseKey are encrypted using DPAPI CurrentUser encryption.

There is no web service access to tool data in 2010 workspaces. Access to Groove 2007 compatible workspaces is unchanged from the access available in Groove 2007 SP1.

Registry Key Changes

In SharePoint Workspace 2010, all web services keys are in the following location in the registry:

HKEY_CURRENT_USER\Software\Microsoft\Office\Groove\WebServices

These keys are:

  • GrooveHTTPDesiredPort
  • GrooveHTTPPort
  • GrooveLocalHTTPPort
  • GrooveLocalHTTPServerPID
  • LocalRequestKey
  • LocalResponseKey

The meaning of these keys has not changed from Groove 2007. See the Groove Web Services Developer Reference for more information.

In order to get the string values for the LocalRequestKey and LocalResponseKey, you should call the Unprotect method. For example: 

Microsoft.Win32.RegistryKey grooveWebServicesRegKey =

  Microsoft.Win32.Registry.CurrentUser.OpenSubKey(

  "Software\\Microsoft\\Office\\Groove\\WebServices");

if (grooveWebServicesRegKey != null)

{

  keyValue = grooveWebServicesRegKey.
GetValue("LocalRequestKey");

  if (keyValue != null)

  {

    byte[] unprotectedData = ProtectedData.
Unprotect((byte[]) keyValue, null, DataProtectionScope.CurrentUser);

    string localRequestKey =
Encoding.Unicode.GetString(unprotectedData);

    return localRequestKey;

  }

In order to call the Unprotect method, you must add a reference to System.Security in your C# project and add the following line to your C# file:

using System.Security.Cryptography;

The Unicode GetString method is in the System.Text library.

Web Services Access to 2010 Groove Workspaces

You can use any GrooveSpaces operation with a 2010 workspace.

Although the GrooveSpaces.Read operation returns a URL for the GrooveTools service, you cannot perform any operations on a 2010 workspace with the GrooveTools, GrooveCalendar, GrooveForms2, or GrooveFilesBase64 service. 2010 Workspaces currently have a Space.Version major version number 19, but this may change during development.


 Notes 

If you call GrooveTools.ReadAvailableTools on a 2010 workspace, it returns an empty list since there are no tools that you can add. GrooveSpaces.Create operation creates a Groove 2007 compatible workspace.

Web Services Access to SharePoint Workspaces

In order to read SharePoint Workspaces with GrooveSpaces.Read, you must specify the following SpaceType:

  “urn:groove.net:Groove.Core.Tools.System.TelespaceTypes.SiteClient”.

The only operations that you may perform on a SharePoint Workspace using Web Services are:

  • GrooveSpaces.ReadSpace
  • GrooveSpaces.Delete
  • GrooveSpaces.UpdateUnreadMarks
  • GrooveLocal.View

All other operations are illegal. Your application should not call any other operation using a SharePoint workspace.SharePoint Workspaces currently have a Space.Version major version number 18, but this may change during development.

Web Services Access to Shared Folders

Access to Shared Folders is unchanged from the access available in Groove 2007 SP1 to Groove File Sharing workspaces. Shared Folders currently have a Space.Version major version 18, but this may change during development.

Other Web Services Notes

GrooveProperties.Read returns a major version number of 14 for SharePoint Workspace 2010.

A hotfix to Groove 2007 provides additional Web Services operations as Groove Web Services Version 2.1. These additional operations are not available in SharePoint Workspace 2010. A Software Development Kit is available with this Beta release. It includes the Groove Web Services documentation, samples, and WSDL definition files.

Office Communicator Integration

If Office Communicator is installed and running, but the user is not logged in, when double-clicking a contact in SharePoint Workspace nothing happens. 

The expectation is that an Office Communicator instant message window opens as it does when the user is logged in. The following describes the expected behavior:

When Office Communicator is installed, running and the user is logged in, when double-clicking a contact in SharePoint Workspace, an Office Communicator instant message window opens. When Office Communicator is installed and not running, double-clicking a contact in SharePoint Workspace opens a SharePoint Workspace message.

To resolve the issue of no window opening when double-clicking a contact in SharePoint Workspace, either sign in to Office Communicator to open an Office Communicator instant message or exit Office Communicator to open a SharePoint Workspace message.

If Office Communicator is installed and running, but the user is not logged in, when double-clicking a contact in SharePoint Workspace nothing happens.

The expectation is that an Office Communicator instant message window opens as it does when the user is logged in. The following describes the expected behavior:

  • When Office Communicator is installed, running and the user is logged in, when double-clicking a contact in SharePoint Workspace, an Office Communicator instant message window opens.
  • When Office Communicator is installed and not running, double-clicking a contact in SharePoint Workspace opens a SharePoint Workspace message.

To resolve the issue of no window opening when double-clicking a contact in SharePoint Workspace, either sign in to Office Communicator to open an Office Communicator instant message or exit Office Communicator to open a SharePoint Workspace message.

Legacy Groove 2007 Custom Tools

Cannot update design of Custom Forms Tools in SharePoint Workspace 2010

Custom tools created using the Groove 2007 Forms or InfoPath Forms tools can be used in Microsoft SharePoint Workspace 2010. However, access to the Designer in these tools is disabled in this software release. If you need to update the design in one of these tools, these updates must be accomplished by a workspace member who is still running Groove 2007. In addition, this member must have designer access, which is typically available to managers. Once the Groove 2007 member publishes an updated design, all workspace members will be able to use the updated design.

Syncing Lists

Syncing a Library/List after adding a Lookup column fails to sync.

By default, SharePoint server throttling is set to limit 8 Lookup columns. Document libraries already have 4 or 5 lookup columns by default, so adding too many lookup columns to a library will cause the sync to fail.

No workaround.

When a user takes a site offline and the user does not have permissions that allow them to add new items or modify existing items, the user will see an error indicating so, but is not told how to resolve the problem.

The scenario is as follows:

  1. User selects Sync to SharePoint Workspace from the SharePoint site for which the user does not have permissions to add/modify.
  2. Once the site is offline, the user creates a new list item in one of the lists.
  3. When the user syncs, the Resolve tab in the ribbon appears.
  4. When the user tries to resolve the error, a dialog appears indicating there is a permissions issue, with an option to fix the error.
  5. Selecting the Fix Error option opens the item in edit mode. If the user then saves and closes the item, the problem is not resolved.

The user has two options:

  1. Try syncing again with the proper permissions.
  2. Delete the item they added to the workspace.

When a user takes a site offline for a server whose credentials are cached with a fully qualified domain name yet the user is synching the site using the unqualified domain name, attachments on items may not sync.

This is a known Windows issue. To resolve the problem, the unqualified domain name for the server should be cached as well.

When syncing an out of the box Project Task List, a user in SharePoint Workspace will be unable to create new summary tasks.

Create the Summary Task on the SharePoint site.

Syncing OneNote files

SharePoint Workspace cannot sync OneNote files.

If a user attempts to launch an OneNote file, SPW will prompt to launch from the SharePoint site.

No workaround. OneNote 2010 handles all of its syncing within the application; SPW is not needed to keep OneNote 2010 notebooks up-to-date.

Syncing IRM document Libraries

SharePoint workspaces will not sync against IRM document libraries.

From the SPW UI the IRM'd document library will be in error.

No workaround.

Creating SharePoint workspaces

If a user deletes a SharePoint workspace and then soon after attempts to re-create the workspace starting from the SharePoint site in a Web browser, the user may receive an error message:

The error message might include the following information:

Cannot navigate to a deleted workspace. If you are trying to re-create a workspace you just deleted, please try again later.

Users sometimes need to wait an indeterminate amount of time before attempting to re-create the workspace using the Action menu on the SharePoint site in a Web browser. As a workaround, the user can create the SharePoint workspace from the Launch bar. Open the Create SharePoint Workspace window, and then enter the SharePoint site URL in the location box.

Top of Page Top of Page

Microsoft Visio Services

No issues at this time.

Top of Page Top of Page

 
 
Applies to:
Excel Web App, PerformancePoint Dashboard Designer, PowerPoint Web App, Project Server 2010 Administration, SharePoint Server 2010, Word Web App