Page 22 of 726« First...10...2021222324...304050...Last »

Can’t receive email after a mailbox is moved to Exchange Server 2013 in Office 365 dedicated/ITAR

After a mailbox is moved to Microsoft Exchange Server 2013 in Microsoft Office 365 dedicated/ITAR, you experience the following symptoms:
  • You can’t receive new email messages.
  • The mailbox is in a disconnected state.

However, you can access your mailbox contents by using Microsoft Outlook Web App (OWA).

This problem occurs because the legacyExchangeDN attribute that’s stored in the Outlook profile can’t be resolved by the server that’s running Exchange Server. Therefore, the Outlook client is directed to be resolved by the Autodiscover service.

This problem typically occurs in a hybrid Exchange deployment (that is, mailboxes are running on on-premises servers and in a managed environment) if the following conditions are true:

  • Autodiscover first points to the source environment, and then redirects to the managed environment.
  • In the managed environment, the legacyExchangeDN attribute is not listed as an X500 address in the source environment.
To resolve this problem, repair the Outlook client. To do this, follow these steps:

Outlook 2007

  1. In Outlook 2007, click Tools, and then click Account Settings.
  2. On the Email tab, select your account (profile), and then click Repair.
  3. Follow the prompts in the wizard, and restart Outlook after the wizard is completed.

Outlook 2010 or 2013

  • In Outlook 2013 or Outlook 2010, click File.
  • Click the down-arrow next to Account Settings, and then click Account Settings.
  • On the Email tab, select your account (profile), and then click Repair.
  • Follow the prompts in the wizard, and restart Outlook after the wizard is completed.
In a hybrid Exchange deployment, we recommend that you list the managed legacyExchangeDN attribute as an X500 address in the source environment. This makes sure that the mailbox is resolved by Exchange and that the Outlook profile is updated by using the new Exchange 2013 server.

Article ID: 2977016 – Last Review: June 16, 2014 – Revision: 1.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal
vkbportal226 hybrid KB2977016

More:
Can’t receive email after a mailbox is moved to Exchange Server 2013 in Office 365 dedicated/ITAR

Custom fonts are not displayed in on-premises Office Web Apps 2010 programs

You do not see custom fonts displayed in a web browser when you view or edit files in an on-premises installation of any Microsoft Office Web Apps 2010 program. For example, you do not see the Microsoft company logo displayed correctly in an Excel spreadsheet, a Word document, or a PowerPoint presentation that you view or edit.
This issue occurs because custom fonts are not installed on servers in the Windows SharePoint farm part if those fonts are not included in the templates or are not embedded when .xlsx, .docx, or .pptx files are created in Office Web Apps programs. Therefore, the required fonts are not available when you view or edit files that contain custom elements.
To resolve this problem, follow these steps on all Front End and Application servers in the SharePoint farm:
  1. Copy the custom font (such as MSLogo.ttf) to a temporary location on the SharePoint servers. For example, copy the font file to C:Temp.
  2. Open the temporary location folder, and then locate the font file that you copied.
  3. Double-click the file, and then click Install in the font display window. Or, right-click the file, and then click Install.

    Note This action copies the file to the C:WindowsFonts folder and updates the font file-related registry entries.

  4. Restart the servers.

Notes

  • A server restart is required to completely update the files and provide access to the custom font.
  • You must follow these same steps on client computers to enable the custom font to be displayed.

Article ID: 2655084 – Last Review: June 16, 2014 – Revision: 10.0


Applies to
  • Microsoft Word Web App
  • Microsoft Excel Web App
  • Microsoft PowerPoint Web App
kbsurveynew kbexpertiseinter kbtshoot KB2655084

See more here:
Custom fonts are not displayed in on-premises Office Web Apps 2010 programs

AppFabric Connect for Biztalk Server 2010

Abstract: One of the key requirements in development of cloud based applications is to be able to leverage existing on-premise assets by exposing them as web services. However, since most of the organizations are firewall protected, the on-premise web services are typically not accessible to external clients running outside the organization’s firewall, unless these web services are explicitly hosted in DMZ. More often than not, hosting services in the DMZ is a cumbersome process. Azure AppFabric Service Bus provides the capability to extend the reach of on-premise web services to external clients (without having to host them in the DMZ) in a secure way.

Feature overview:
BizTalk Server 2010 AppFabric Connect for Services brings together the capabilities of BizTalk Server and Windows Azure AppFabric thereby enabling enterprises to extend the reach of their on-premise Line of Business (LOB) systems and BizTalk applications to cloud.

Collapse this imageExpand this image

(file:///C:/Users/harsh/AppData/Local/Temp/WindowsLiveWriter-429641856/supfiles4094BC4/ACFS-feature3.png)

Business Scenario:
With the advent of cloud platforms and people building cloud based applications, it is still true that a lot of data for these applications resides in on-premise LOB systems. More often than not, these applications would also want to leverage existing on-premise applications. To build such hybrid applications with components residing on-premise as well as on cloud, a secure mechanism to connect an enterprise’s on-premise assets with those on cloud is the need of the hour.

Prerequisites:

a)      BizTalk Server 2010 or BizTalk Server Adapter Pack 2010 must be installed to use this feature.
b)      You must have Azure AppFabric SDK version 1.0 (September update or later) installed. You can install it from http://go.microsoft.com/fwlink/?LinkId=204209

(http://go.microsoft.com/fwlink/?LinkId=204209)

.

c)      You must have configured a Service Bus namespace. You will require this for hosting the Service Bus relay service on the Azure Service Bus. Instructions on configuring the Service Bus namespace are available here (http://go.microsoft.com/fwlink/?LinkId=204209

(http://go.microsoft.com/fwlink/?LinkId=204209)

).

Note: AppFabric Connect for Services can be used to only host services on Windows Azure AppFabric 1.0.

d)      Recommended: You can also install Windows Server AppFabric. This enables you to configure auto start that would otherwise be cumbersome. You can download the Windows Server AppFabric installer from here (http://go.microsoft.com/fwlink/?LinkId=204210

(http://go.microsoft.com/fwlink/?LinkId=204210)

).

Important: If you choose to install Windows Server AppFabric, you must also install the hotfix 980423 (http://go.microsoft.com/fwlink/?LinkId=204211

(http://go.microsoft.com/fwlink/?LinkId=204211)

). This fixes some issues with Windows Server AppFabric.

How to use this feature:

This section provides a quick walkthrough of how to expose your on-premise BizTalk Orchestrations and LOB data as a WCF Service on cloud. A more detailed tutorial can be accessed from here.

§  BizTalk Orchestrations:

1.      Run BizTalk WCF Service Publishing Wizard

Collapse this imageExpand this image

(file:///C:/Users/harsh/AppData/Local/Temp/WindowsLiveWriter-429641856/supfiles4094BC4/1.-Intro14.png)

2.      Choose BizTalk Orchestration(s) to publish

Collapse this imageExpand this image

3.      Extend the reach of the BizTalk Orchestration(s) to cloud

Collapse this imageExpand this image

4.      Configure Service Bus endpoints

Collapse this imageExpand this image

Collapse this imageExpand this image

LOB systems:

1.      Run BizTalk WCF Adapter Service Development Wizard

Collapse this imageExpand this image

2.      Choose the LOB artifact(s) to publish

Collapse this imageExpand this image

(file:///C:/Users/harsh/AppData/Local/Temp/WindowsLiveWriter-429641856/supfiles4094BC4/2.-ChooseOperations4.png)

3.      Extend the reach of the LOB artifact(s) to cloud

Collapse this imageExpand this image

4.      Configure Service Bus endpoints

Collapse this imageExpand this image

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2449478 – Last Review: June 16, 2014 – Revision: 2.1


Applies to
  • Microsoft BizTalk Server Enterprise 2010
  • Microsoft BizTalk Server Developer 2010
  • Microsoft BizTalk Server Standard 2010

See the original article here:
AppFabric Connect for Biztalk Server 2010

SDP355c68b60-e40d-4d4e-b292-29d77fc6c7f3 Host Integration Server Diagnostic

This diagnostic package collects data used to troubleshoot issues related with Host Integration Server. The data includes Host Integration Server specific registry settings and file information. In addition, it also captures Windows specific information that can effect Host Integration Server such as installed hotfixes, file information and print drivers.

Information Collected

Enviroment Variables Information

Collapse this tableExpand this table

Description File name
Enviroment Variables File ComputerName_enviromnetVariablesSet.TXT

File Version Information (Chksym)

Collapse this tableExpand this table

Description File name
File version information from %windir%system32Spool*.* ComputerName_sym_PrintSpooler.*
File version information from drivers currently running on the machine ComputerName_sym_RunningDrivers.*
File version information from processes currently running on the machine ComputerName_sym_Process.*

General Information

Collapse this tableExpand this table

Description File name
List of Installed Updates and Hotfixes installed ComputerName_Hotfixes.*
Show if machine is running on a Virtual Environment and describes the virtualization environment resultreport.xml
System Information – MSInfo32 tool output ComputerName_msinfo32.nfo
ComputerName_msinfo32.txt

HIS Configuration and Setup Log Files

Collapse this tableExpand this table

Description File name
config*.log located in TEMP folder ComputerName_ConfigLogs.zip
Setup*.log located in TEMP folder ComputerName_SetupLogs.zip

HIS Configuration and Trace Files

Collapse this tableExpand this table

Description File name
Host Integration Server configuration file located in %snaroot%configcom.cfg ComputerName_com.cfg
Host Integration Server trace files located in %snaroot%..traces ComputerName_Traces.zip

HIS Service and Configuration Registry Keys

Collapse this tableExpand this table

Description File name
HKLMSOFTWAREMicrosoftSnaBase
HKLMSYSTEMCurrentControlSetServicesSnaBase
ComputerName_reg_SnaBase.TXT
HKLMSYSTEMCurrentControlSetServicesSnaDDM ComputerName_reg_SnaDDM.TXT
HKLMSYSTEMCurrentControlSetServicesSnaPrint ComputerName_reg_SnaPrint.TXT
HKLMSOFTWAREMicrosoftSna Server
HKLMSYSTEMCurrentControlSetServicesSnaServr
ComputerName_reg_SnaServer.TXT

HIS Transaction Integrator Registry Keys

Collapse this tableExpand this table

Description File name
HKLMSOFTWAREMicrosoftCedar ComputerName_reg_Cedar.TXT

Host Integration Server Installation Registry Keys

Collapse this tableExpand this table

Description File name
HKLMSOFTWAREMicrosoftHost Integration Server ComputerName_reg_HostIntegrationServer.TXT

Print Drivers and Printers information

Collapse this tableExpand this table

Description File name
Information about Print drivers and printers, including print monitors, processors, and print driver file version information ComputerName_PrintInfo.*

Print Registry

Collapse this tableExpand this table

Description File name
Cluster Print Registry File ComputerName_reg_*ClusterPrintKey.txt
HKCUPrinters
HKLMSOFTWAREMicrosoftWindows NTCurrentVersionPrint
HKLMSYSTEMCurrentControlSetControlPrint
ComputerName_reg_*Print.txt

In addition to collecting the information that is described earlier, this diagnostic package can detect one or more of the following symptoms:

  • Detect if this machine is a Virtual Machine running in Windows Azure
  • Event Logs Messages
  • Print Drivers and Printers information

References

For more information about the Microsoft Automated Troubleshooting Services and about the Support Diagnostics Platform, please open the following Microsoft Knowledge Base article:

2598970

(http://support.microsoft.com/kb/2598970/
)

Information about Microsoft Automated Troubleshooting Services and Support Diagnostic Platform

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2830735 – Last Review: June 16, 2014 – Revision: 2.1


Applies to
  • Microsoft Host Integration Server 2004 Developer Edition
  • Microsoft Host Integration Server 2004 Enterprise Edition
  • Microsoft Host Integration Server 2004 Service Pack 1
  • Microsoft Host Integration Server 2004 Standard Edition
  • Microsoft Host Integration Server 2006
  • Microsoft Host Integration Server 2006 Developer Edition
  • Microsoft Host Integration Server 2006 Enterprise Edition
  • Microsoft Host Integration Server 2006 Service Pack 1
  • Microsoft Host Integration Server 2009
  • Microsoft Host Integration Server 2009 Developer Edition
  • Microsoft Host Integration Server 2010
  • Microsoft BizTalk Adapters for Host Systems
  • Microsoft BizTalk Adapters for Host Systems 2.0
  • Microsoft BizTalk Adapters for Host Systems 2.0 Developer Edition

Read More:
SDP355c68b60-e40d-4d4e-b292-29d77fc6c7f3 Host Integration Server Diagnostic

URL Rewrite 2.0 leaks memory when an outgoing rule is processed against a multivalue server variable

When an outgoing rule is processed against a multivalue server variable, Internet Information Services (IIS) URL Rewrite 2.0

(http://www.iis.net/downloads/microsoft/url-rewrite)

may leak memory. This problem occurs if the rule does not match all the values of the variable. For example, if there is an outgoing rule that changes a specific cookie in the Set-Cookie: header when there are multiple cookies set on a response, URL Rewrite may leak memory on each request in which the outgoing rule occurs.

This problem occurs because of an error in URL Rewrite 2.0.

Hotfix information

The following file is available for download from the Microsoft Download Center:
Learn about how to obtain Microsoft support files from online services

(http://support.microsoft.com/kb/119591/
)


Prerequisites

There are no prerequisites for installing this hotfix.

Restart information

You must restart the computer after you apply this hotfix.

Replacement information

This hotfix does not replace any previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

For all supported x86-based versions of IIS URL Rewrite 2.0

Collapse this tableExpand this table

File name File version File size Date Time Platform
Rewrite.dll 7.1.1917.0 310,952 29-May-2014 22:53 x86
For all supported x64-based versions of IIS URL Rewrite 2.0

Collapse this tableExpand this table

File name File version File size Date Time Platform
Rewrite.dll 7.1.1917.0 389,800 29-May-2014 22:53 x64
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 2974666 – Last Review: June 12, 2014 – Revision: 1.0


Applies to
  • Microsoft Internet Information Services 8.5
  • Microsoft Internet Information Services 8.0
  • Microsoft Internet Information Services 8.0 Express
  • Microsoft Internet Information Services 7.5
  • Microsoft Internet Information Services 7.0
kbautohotfix kbqfe kbhotfixserver kbfix kbexpertiseinter kbsurveynew kbbug KB2974666

More:
URL Rewrite 2.0 leaks memory when an outgoing rule is processed against a multivalue server variable

"Multiple objects with LiveIdMemberName" error when an admin tries to connect to Exchange Online by using remote PowerShell

When an admin tries to connect to Exchange Online by using the Remote Desktop Services module for Windows PowerShell, the admin receives an error message that resembles the following:
Connecting to remote server xxxxx.outlook.com failed with the following error message:

ClientAccessServer=xxxx,BackEndServer=,RequestId=45a309a7-d4d2-4fd5-9d1c-ba5c0e08e74b,TimeStamp=5/28/2014 4:45:51 AM FailureCategory=Cafe-HttpProxyException Multiple objects with LiveIdMemberName @contoso.onmicrosoft.com were found

When you verify a custom domain (for example, contoso.com) in Office 365, a new SMTP proxy address for that domain is added to each user in the organization. For example, if you verify contoso.com in the contoso.onmicrosoft.com organization, the admin@contoso.onmicrosoft.com user now has an SMTP proxy address that is admin@contoso.com. In this example, this problem occurs if the admin@contoso.com and admin@contoso.onmicrosoft.com SMTP addresses exist in two separate accounts.
To resolve this problem, follow these steps:
  1. Connect to Exchange Online by using remote PowerShell. To make the connection, do one of the following:
    • Use a different admin account.
    • Use an address that’s not being used by your organization. For example, if you were logging into remote PowerShell as admin@contoso.com, change the address to admin001@contoso.com, if this address is not used in your organization.
  2. Run the following command:
    Get-Mailbox | where $_.EmailAddresses -match "username" | ft Name, RecipientType, EmailAddresses

    Note In this command, username is the SMTP address that’s experiencing the problem.

  3. Determine whether any duplicate SMTP addresses are returned.
  4. Run the following command:
    Get-Recipient | where $_.EmailAddresses -match "username" | ft Name, RecipientType, EmailAddresses

    Note In this command, username is the SMTP address that’s experiencing the problem.

  5. Determine whether any duplicate SMTP addresses are returned. If you find a duplicate SMTP address, remove it.
  6. If you changed the address of the admin account in step 1, revert it to the original address.
For more information about how to connect to Exchange Online by using the Remote Desktop Services module, see Connect to Exchange Online using remote PowerShell

(http://technet.microsoft.com/en-us/library/jj984289(v=exchg.150).aspx)

.

For more information about how to edit or remove SMTP addresses, see the “Edit or remove email aliases” section of Add an email alias to a user account

(http://office.microsoft.com/en-us/office365-suite-help/add-an-email-alias-to-a-user-account-HA104072264.aspx)

.

Article ID: 2974367 – Last Review: June 12, 2014 – Revision: 2.0


Applies to
  • Microsoft Exchange Online
o365e o365m o365p o365022013 o365 o365a KB2974367

Original post:
"Multiple objects with LiveIdMemberName" error when an admin tries to connect to Exchange Online by using remote PowerShell

SQL based reports fail to execute for Microsoft Dynamics CRM

After installing the Microsoft Dynamics CRM Reporting Extensions, SQL based reports, such as the out of the box reports, fail to run within Microsoft Dynamics CRM. The SQL Server Reporting Services (SSRS) log files show the following:

processing!ReportServer_####!MM/DD/YYYY-HH:MM:SS:: e ERROR: Data source ‘ORGANIZATIONUNIQUENAME’: An error has occurred. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source ‘ORGANIZATIONUNIQUENAME’. —> Microsoft.ReportingServices.DataExtensions.ReportServerDataProvider.RSDPException: You have specified integrated security or credentials in the connection string for the data source, but the data source is configured to use a different credential type. To use the values in the connection string, you must configure the unattended report processing account for the report server.
   at Microsoft.ReportingServices.DataExtensions.ConnectionExtension.FailIntegratedSecurity()
   at Microsoft.ReportingServices.DataExtensions.ConnectionExtension.AppendCredentials()
   at Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapperBase.get_ConnectionString()
   at Microsoft.ReportingServices.DataExtensions.ConnectionExtension.Open()
   at Microsoft.ReportingServices.DataExtensions.SqlConnectionWrapperBase.Open()
   at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.OpenConnection(IProcessingDataSource dataSourceObj, DataSourceInfo dataSourceInfo, IDbConnection conn)
   — End of inner exception stack trace —
   at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.OpenConnection(IProcessingDataSource dataSourceObj, DataSourceInfo dataSourceInfo, IDbConnection conn)
   at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.HandleImpersonation(IProcessingDataSource dataSource, DataSourceInfo dataSourceInfo, String datasetName, IDbConnection connection, Action afterImpersonationAction)
   at Microsoft.ReportingServices.Diagnostics.DataExtensionConnectionBase.OpenDataSourceExtensionConnection(IProcessingDataSource dataSourceObj, String connectString, DataSourceInfo dataSourceInfo, String datasetName)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSource.OpenConnection(DataSource dataSourceObj, DataSet dataSetObj, OnDemandProcessingContext pc, DataProcessingMetrics metrics)
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSource.OpenInitialConnectionAndTransaction()
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSource.InitializeDataSource()
   at Microsoft.ReportingServices.OnDemandProcessing.RuntimeAtomicDataSource.Process(Boolean fromOdp)

NOTE: Please review the following article for the location of the SSRS log files:
http://technet.microsoft.com/en-us/library/ms156500.aspx

(http://technet.microsoft.com/en-us/library/ms156500.aspx)

The account running the SSRS service is a virtual or local account such as LocalSystem. These virtual or local accounts do not have the necessary permissions to query the FilteredViews. The SQL permissions required to query the FilteredViews is a custom role called CRMReaderRole. This role is given to the Active Directory group named PrivReportingGroup. During installation of the Reporting Extensions, the SSRS service account is added to the PrivReportingAccount. Virtual or Local accounts cannot be added to an Active Directory group.
1. Run the SSRS service under the context of Network Service.  For increased security, run the SSRS service as a managed service account, a low privileged user in Active Directory. To change the service account, please refer to the following article:
http://technet.microsoft.com/en-us/library/bb522727.aspx

(http://technet.microsoft.com/en-us/library/bb522727.aspx)

2. Manually give the CRMReaderRole role to the account running the SSRS service on each of the CRM databases. To accomplish this, please refer to the following article:
http://msdn.microsoft.com/en-US/library/ms187750.aspx

(http://msdn.microsoft.com/en-US/library/ms187750.aspx)

NOTE: If option 2 is chosen, then anytime a new Organization is created, the SSRS service account will need to be added to this new database

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2923525 – Last Review: June 11, 2014 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
  • Microsoft Dynamics CRM 2013
kbmbsmigrate kbsurveynew KB2923525

Continue Reading:
SQL based reports fail to execute for Microsoft Dynamics CRM

After applying Update Rollup 12 or higher, the ribbon no longer appears in the "Users: Primary Email (Pending Approval)" grid after opening the window through the "Pending E-mail Approval" dialog box in Microsoft Dynamics CRM 2011

After installing Update Rollup 12 or higher for Microsoft Dynamics CRM 2011, the ribbon no longer appears in the Users Primary Email (Pending Approval) view after opening the grid through the “Pending E-mail Approval” dialog box upon logging into the system. This issue only occurs in Internet Explorer.
Microsoft has confirmed that this is a known issue in Microsoft Dynamics CRM 2011.
While this issue is fixed in Microsoft Dynamics CRM 2013, users may work around this issue by completing the following steps:
  1. In the ribbon, click on Advanced Find.
  2. In the Look For field, select “Users”. In the Use Saved View field, click “Users: Primary Email (Pending Approval)”
  3. Click Results.

Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2917035 – Last Review: June 11, 2014 – Revision: 2.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2917035

Read More:
After applying Update Rollup 12 or higher, the ribbon no longer appears in the "Users: Primary Email (Pending Approval)" grid after opening the window through the "Pending E-mail Approval" dialog box in Microsoft Dynamics CRM 2011

Excel hangs if a spreadsheet pathname includes the "支" character

Consider the following scenario:
  • You have a computer that is running Microsoft Excel 2003.
  • You use Excel to open a spreadsheet that is located on a network share.
  • The file name or one of the folder names in the file path starts with the “支” character.

In this scenario, Excel hangs for a few seconds.

This problem occurs because Excel does not parse the pathname correctly.

Hotfix information

A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:

Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2

Registry information

To enable this fix, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix. 

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information

Collapse this imageExpand this image

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows 7/Windows Server 2008 R2″ on the page. Always refer to the “Applies to” section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Collapse this tableExpand this table

    Version Product SR_Level Service branch
    6.1.760
    0. 16xxx
    Windows 7 and Windows Server 2008 R2 RTM GDR
    6.1.760
    0. 20xxx
    Windows 7 and Windows Server 2008 R2 RTM LDR
    6.1.760
    1. 17xxx
    Windows 7 and Windows Server 2008 R2 SP1 GDR
    6.1.760
    1. 21xxx
    Windows 7 and Windows Server 2008 R2 SP1 LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the “Additional file information for Windows 7 and Windows Server 2008 R2″ section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7

Collapse this tableExpand this table

File name File version File size Date Time Hashes Platform
Linkinfo.dll 6.1.7601.22677 22,016 07-May-2014 02:14 MD5: C439C53060D586F59A23D4C8934C6143
SHA1: 34C5CE3197BFE777A8867AE36031EEF28FBF04D5
x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2

Collapse this tableExpand this table

File name File version File size Date Time Hashes Platform
Linkinfo.dll 6.1.7601.22677 29,696 07-May-2014 02:35 MD5: A42C0DCCFB7A7D90370F389EB1BA7BE9
SHA1: 9FF9E2167F380CEC15BB9D8F97ABFD8C93CD6EF3
x64
Linkinfo.dll 6.1.7601.22677 22,016 07-May-2014 02:14 MD5: C439C53060D586F59A23D4C8934C6143
SHA1: 34C5CE3197BFE777A8867AE36031EEF28FBF04D5
x86
For all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name File version File size Date Time Hashes Platform
Linkinfo.dll 6.1.7601.22677 60,416 07-May-2014 01:47 MD5: 55DD98BD139B702C8B4C9DE195582A14
SHA1: DD4F8DDC4F558EA7F363FD7713B5B5EED1B214E8
IA-64
Linkinfo.dll 6.1.7601.22677 22,016 07-May-2014 02:14 MD5: C439C53060D586F59A23D4C8934C6143
SHA1: 34C5CE3197BFE777A8867AE36031EEF28FBF04D5
x86

Additional file information

Additional file information for Windows 7 and Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

Collapse this tableExpand this table

File name X86_6ca03c4f230c3ad9ae183f767f931465_31bf3856ad364e35_6.1.7601.22677_none_a7d677585f555c81.manifest
File version Not Applicable
File size 696
Date (UTC) 07-May-2014
Time (UTC) 12:01
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name X86_microsoft-windows-linkinfo_31bf3856ad364e35_6.1.7601.22677_none_3ab843611ce1d7d3.manifest
File version Not Applicable
File size 2,390
Date (UTC) 07-May-2014
Time (UTC) 02:39
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2

Collapse this tableExpand this table

File name Amd64_274e0ec6e857353ca712822e3f4279a7_31bf3856ad364e35_6.1.7601.22677_none_1b4a89d918fa130e.manifest
File version Not Applicable
File size 700
Date (UTC) 07-May-2014
Time (UTC) 12:01
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name Amd64_3f133049d769c9126a5d4e68dada3a2b_31bf3856ad364e35_6.1.7601.22677_none_af0337e7347d79b5.manifest
File version Not Applicable
File size 1,042
Date (UTC) 07-May-2014
Time (UTC) 12:01
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name Amd64_microsoft-windows-linkinfo_31bf3856ad364e35_6.1.7601.22677_none_96d6dee4d53f4909.manifest
File version Not Applicable
File size 2,392
Date (UTC) 07-May-2014
Time (UTC) 03:05
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name Wow64_microsoft-windows-linkinfo_31bf3856ad364e35_6.1.7601.22677_none_a12b893709a00b04.manifest
File version Not Applicable
File size 2,392
Date (UTC) 07-May-2014
Time (UTC) 02:29
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2

Collapse this tableExpand this table

File name Ia64_b88751263bbbb21b72eeb2a9bd77f97c_31bf3856ad364e35_6.1.7601.22677_none_aeea83b1afdae37f.manifest
File version Not Applicable
File size 1,040
Date (UTC) 07-May-2014
Time (UTC) 12:01
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name Ia64_microsoft-windows-linkinfo_31bf3856ad364e35_6.1.7601.22677_none_3ab9e7571cdfe0cf.manifest
File version Not Applicable
File size 2,391
Date (UTC) 07-May-2014
Time (UTC) 02:30
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable
File name Wow64_microsoft-windows-linkinfo_31bf3856ad364e35_6.1.7601.22677_none_a12b893709a00b04.manifest
File version Not Applicable
File size 2,392
Date (UTC) 07-May-2014
Time (UTC) 02:29
Platform Not Applicable
SHA-1 hash Not Applicable
MD5 hash Not Applicable

Collapse this imageExpand this image

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
Learn about the terminology

(http://support.microsoft.com/kb/824684/
)

that Microsoft uses to describe software updates.

Article ID: 2966148 – Last Review: June 11, 2014 – Revision: 1.0


Applies to
  • Microsoft Office Excel 2003
kbautohotfix kbqfe kbhotfixserver kbfix kbbug kbexpertiseinter kbsurveynew KB2966148

See original article:
Excel hangs if a spreadsheet pathname includes the "支" character

Office 2010 cumulative update for June 2014

The cumulative update packages for June 2014 contain the latest hotfixes for Microsoft Office 2010 and for the Office 2010 servers.

We recommend that you test hotfixes before you deploy them in a production environment. Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous update package. We recommend that you consider applying the most recent fix release that contains the hotfix that you need.

How to obtain the June 2014 cumulative update packages

A set of supported cumulative update packages are now available from Microsoft. However, each package is intended to correct only the applications that are listed in this article. Apply the packages only to systems that are experiencing these specific problems. If you are not severely affected by any of these problems, we recommend that you wait for the next update package that contains the hotfixes in these cumulative update packages.

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for a specific cumulative update package. To create a separate service request, visit the following Microsoft website:

Packages that are included in the June 2014 cumulative update

A link to a Microsoft Knowledge Base article that discusses each hotfix will be released as the article becomes available. To obtain a specific hotfix, please contact support and ask for the hotfix by referencing the Knowledge Base article number.

For more information about the Office 2010 issues that are fixed in this cumulative update, click the following article numbers to view the articles in the Microsoft Knowledge Base.

Office 2010 client updates

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
Excel-x-none.msp
2881057

(http://support.microsoft.com/kb/2881057/
)

Hotfix 2881057 for Excel 2010 June 10, 2014 (Excel-x-none.msp)

Excel 2010
Kb2428677-x-none.msp
2881056

(http://support.microsoft.com/kb/2881056/
)

Hotfix 2881056 for Office 2010 June 10, 2014 (Kb2428677-x-none.msp)

Office 2010
Outlook-x-none.msp
2881055

(http://support.microsoft.com/kb/2881055/
)

Hotfix 2881055 for Outlook 2010 June 10, 2014 (Outlook-x-none.msp)

Outlook 2010
Oart-x-none.msp; Oartconv-x-none.msp
2878267

(http://support.microsoft.com/kb/2878267/
)

Hotfix 2878267 for PowerPoint 2010 June 10, 2014 (Oart-x-none.msp; Oartconv-x-none.msp)

PowerPoint 2010
Project-x-none.msp
2880537

(http://support.microsoft.com/kb/2880537/
)

Hotfix 2880537 for Project 2010 June 10, 2014 (Project-x-none.msp)

Project 2010
Word-x-none.msp
2881059

(http://support.microsoft.com/kb/2881059/
)

Hotfix 2881059 for Word 2010 June 10, 2014 (Word-x-none.msp)

Word 2010

Rollup updates for SharePoint Foundation 2010, SharePoint Server 2010 and Project Server 2010

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
Project server-package
2880974

(http://support.microsoft.com/kb/2880974/
)

June 10, 2014 Cumulative Update for Project Server 2010

Project Server 2010
SharePoint server-package
2880972

(http://support.microsoft.com/kb/2880972/
)

June 10, 2014 Cumulative Update for SharePoint Server 2010

SharePoint Server 2010
SharePoint Foundation server-package
2880975

(http://support.microsoft.com/kb/2880975/
)

June 10, 2014 Cumulative Update for SharePoint Foundation 2010

SharePoint Foundation 2010

Individual server updates

Collapse this tableExpand this table

Hotfix package name Knowledge Base article number Product
Wss-x-none.msp
2880532

(http://support.microsoft.com/kb/2880532/
)

Hotfix 2880532 for SharePoint Foundation 2010 June 10, 2014 (Wss-x-none.msp)

SharePoint Foundation 2010
Coreserver-x-none.msp
2880544

(http://support.microsoft.com/kb/2880544/
)

Hotfix 2880544 for SharePoint Server 2010 June 10, 2014 (Coreserver-x-none.msp)

SharePoint Server 2010
Wasrvwfe-x-none.msp
2760773

(http://support.microsoft.com/kb/2760773/
)

Hotfix 2760773 for SharePoint Server 2010 June 10, 2014 (Wasrvwfe-x-none.msp)

SharePoint Server 2010
Ifswfe-x-none.msp; Ifsmui-.msp
2880547

(http://support.microsoft.com/kb/2880547/
)

Hotfix 2880547 for SharePoint Server 2010 June 10, 2014 (Ifswfe-x-none.msp; Ifsmui-.msp)

SharePoint Server 2010

Prerequisites

Prerequisites are listed in the KB articles for the individual packages.

Article ID: 2970263 – Last Review: June 10, 2014 – Revision: 1.0


Applies to
  • Microsoft Excel 2010
  • Microsoft Office Home and Business 2010
  • Microsoft Office Home and Student 2010
  • Microsoft Office Professional 2010
  • Microsoft Office Professional Academic 2010
  • Microsoft Office Professional Plus 2010
  • Microsoft Office Standard 2010
  • Microsoft Office Starter 2010
  • Microsoft Outlook 2010
  • Microsoft PowerPoint 2010
  • Microsoft Project Professional 2010
  • Microsoft Project Standard 2010
  • Microsoft Word 2010
  • Microsoft SharePoint Foundation 2010
  • Microsoft SharePoint Server 2010
  • Microsoft Project Server 2010
kbsurveynew kbexpertiseinter KB2970263

Read the article:
Office 2010 cumulative update for June 2014

Page 22 of 726« First...10...2021222324...304050...Last »

Recent Comments

    Archives

    Categories