KB Articles

Page 1 of 73712345...102030...Last »

Free/busy lookups stop working in a cross-premises environment or in an Exchange hybrid deployment

Free/busy lookups stop working for users in a cross-premises environment or in a hybrid deployment of on-premises Exchange Server and Exchange Online. Additionally, these issues may extend to other features that rely on the Microsoft Federation Gateway.

If you run the Test-FederationTrust cmdlet, you receive an error message that indicates that the Delegation token has validation issues. For example, you receive an error message that resembles the following:

Id : TokenValidation
Type : Error
Message : Failed to validate delegation token.

This issue occurs if the certificate and other metadata information in the Microsoft Federation Gateway or in the on-premises environment become stale or invalid.
To resolve this issue, refresh the metadata. To do this, run the Get-FederationTrust | Set-FederationTrust –RefreshMetadata command.

Note This command forces the information that’s used for the federation trust to become up-to-date. You won’t have to re-create organization relationships or sharing policies.

To do this, follow these steps:

  1. Open the Exchange Management Shell on the on-premises Exchange 2013 server or on the on-premises Exchange 2010 server.
  2. Run the following cmdlet:
    Get-FederationTrust | Set-FederationTrust –RefreshMetadata
This issue could affect any environment that uses the Microsoft Federation Gateway. These environments include on-premises organizations that have set up free/busy or sharing policies between their organization and other on-premises organizations or Exchange Online in Office 365.

To run the procedure in the “Solution” section as an automated task to prevent future issues, open a command prompt on the Exchange server, and then run the following command. Doing this updates the federation trust daily.

Schtasks /create /sc Daily /tn FedRefresh /tr "C:WindowsSystem32WindowsPowerShellv1.0powershell.exe
-version 2.0 -command Add-PSSnapIn Microsoft.Exchange.Management.PowerShell.E2010;
$fedTrust = Get-FederationTrust;Set-FederationTrust -Identity $fedTrust.Name -RefreshMetadata" /ru System


Still need help? Go to the Office 365 Community

(http://community.office365.com/)

website or the Exchange TechNet Forums

(http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver)

.

Article ID: 2928514 – Last Review: September 17, 2014 – Revision: 6.0


Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2013 Enterprise
o365e o365m o365022013 o365 o365a hybrid KB2928514

More:
Free/busy lookups stop working in a cross-premises environment or in an Exchange hybrid deployment

Excel: How to Troubleshoot Excel Opening Blank when double-clicking on icon or file name

When you double-click an icon or file name for a Microsoft Excel workbook, Excel starts but displays a blank screen where you expect the file to appear.

To resolve this problem, try the following methods, as appropriate, in the given order.

Method 1: Ignore DDE

Collapse this imageExpand this image

This problem may occur if the Ignore other applications that use Dynamic Data Exchange (DDE) check box in Excel options is selected.

When you double-click an Excel workbook in Windows Explorer, a dynamic data exchange (DDE) message is sent to Excel. This message instructs Excel to open the workbook that you double-clicked.

If you select the “Ignore” option, Excel ignores DDE messages that are sent to it by other programs. Therefore, the DDE message that is sent to Excel by Windows Explorer is ignored, and Excel does not open the workbook that you double-clicked.

To correct this setting, follow these steps:

  1. On the Tools menu, click Options.
  2. Click the General tab.
  3. Clear the Ignore other applications that use Dynamic Data Exchange (DDE) check box, and then click OK.

Note For more information about how to turn off DDE, see the following Microsoft Knowledge Base article:

211494

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

“There was a problem sending the command to the program” error in Excel

If these steps do not resolve the problem, go to Method 2.

Collapse this imageExpand this image

Method 2: Repair User Experience Virtualization (UE-V)

Collapse this imageExpand this image

If you are running Update User Experience Virtualization (UE-V), install hotfix 2927019. To do this, see the following Microsoft Knowledge Base article:

2927019

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

Hotfix Package 1 for Microsoft User Experience Virtualization 2.0

If you are not sure whether you are running UE-V, examine the program list in the Programs and Features item in Control Panel. An entry for “Company Settings Center” indicates that you are running UE-V.

If these steps do not resolve the problem, go to Method 3.

Collapse this imageExpand this image

Method 3: Reset file associations

Collapse this imageExpand this image

To check whether the file associations in the system are performing correctly, reset the Excel file associations to their default settings. To do this, follow the steps for your operating system.

Windows 8
  1. On the Start screen, type Control Panel.
  2. Click or tap Control Panel.
  3. Click Default Programs, and then click Set your default programs.
  4. Click Excel, and then click Choose default for this program.
  5. On the Set Program Associations screen, click Select All, and then click Save.
Windows 7
  1. Click Start, and then click Control Panel.
  2. Click Default Programs.
  3. Click Associate a file type or protocol with a specific program.
  4. Select Microsoft Excel Worksheet, and then click change program.
  5. Under Recommended Programs, click Microsoft Excel.
  6. If Excel does not appear in this list, click Browse, locate the Excel installation folder, click Excel.exe, and then click Excel.

If these steps do not resolve the problem, go to Method 4.

Collapse this imageExpand this image

Method 4: Repair Office

Collapse this imageExpand this image

Try to repair your Office programs. To do this, follow the steps for your installation type and operating system.

For an Office 365 Click-to-Run installation
Windows 8
  1. On the Start screen, type Control Panel.
  2. Click or tap Control Panel.
  3. Under Programs, click or tap Uninstall a program.
  4. Click or tap Microsoft Office 365, and then click or tap Change.
  5. Click or tap Online Repair, and then click or tap Repair. You may have to restart your computer after the repair process is finished.
Windows 7
  1. Click Start, and then click Control Panel.
  2. Double-click Programs and Features.
  3. Click Microsoft Office 365, and then click Change.
  4. Select Online Repair, and then click Repair.

    Note You may have to restart your computer after the repair process is complete.

    Collapse this imageExpand this image

For an Office 2013, Office 2010, or Office 2007 installation

To repair Office 2013, Office 2010, or Office 2007, follow the steps in the following Office website topic:

Repair Office programs

(http://office.microsoft.com/en-us/outlook-help/repair-office-programs-HA010357402.aspx)

If these steps do not resolve the problem, go to Method 5.

Collapse this imageExpand this image

Method 5: Turn off add-ins

Collapse this imageExpand this image

Excel and COM add-in programs can also cause this problem. These two kinds of add-ins are located in different folders. For testing, disable and isolate the conflict by turning off each add-in one at a time. To do this, follow these steps:

  1. On the File menu, click Options, and then click Add-Ins.
  2. In the Manage list at the bottom of the screen, select COM Add-Ins item, and then click Go.
  3. Clear one of the add-ins in the list, and then click OK.
  4. Restart Excel by double-clicking the icon or file name for the workbook that you are trying to open.
  5. If the problem persists, repeat steps 1-4, except select a different add-in in step 3.
  6. If the problem persists after you clear all the COM Add-ins, repeat steps 1-4, except select Excel Add-Ins in step 2, and then try each of the Excel add-ins one at a time in step 3.

If Excel loads the file, the add-in you last turned off is causing the problem. If this is the case, we recommend that you visit the manufacturer’s website for the add-in to learn whether an updated version of the add-in is available. If a newer version of the add-in is not available, or if you don’t have to use the add-in, you can leave it turned off.

If Excel does not open the file after you turn off all the add-ins, the problem has a different cause.

If these steps do not resolve the problem, go to Method 6.

Collapse this imageExpand this image

Method 6: Disable hardware acceleration

Collapse this imageExpand this image

To work around this problem, disable hardware acceleration until a fix is released by your video card manufacturer. Make sure to check regularly for updates to your video card driver.

To disable hardware acceleration, follow these steps:

  1. Start any Office 2013 program.
  2. On the File tab, click Options.
  3. In the Options dialog box, click Advanced.
  4. In the list of available options, select the Disable hardware graphics acceleration check box.

    The following screen shot shows this option in Excel.

    Collapse this imageExpand this image

  5. Click OK.

Note For more information about hardware acceleration, see the following Microsoft Knowledge Base article:

2768648

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

Performance and display issues in Office 2013 client applications

Collapse this imageExpand this image

If you still experience this problem after you try all these methods, contact Microsoft Support

(http://support.microsoft.com/contactus/?ws=support)

for additional troubleshooting help.

More:
Excel: How to Troubleshoot Excel Opening Blank when double-clicking on icon or file name

Reminders do not fire, e-mail stays in the Outbox, the To-Do Bar displays an error or Windows Desktop Search frequently rebuilds the indexing of Outlook items

In Outlook, you may experience one or more of the following issues:

  • Outlook reminders do not fire.

There was a problem reading one or more of your reminders. Some reminders may not appear.

This group of folders is associated with an e-mail account. To remove the account, click the File Tab, and on the Info tab, click Account Settings. Select the e-mail account, and then click Remove.

or

This group of folders is associated with an e-mail account. To remove the account, on the Tools menu, click Account Settings, select the account, and then click Remove.

The error you receive depends on your version of Outlook.

  • Windows Desktop Search frequently rebuilds the indexing of Outlook items.

These problems can occur if your mailbox is on Exchange Server 2010 SP1 (or later) and you have Full Access Permission configured for your own Exchange mailbox. With these versions of Exchange, the Auto Mapping feature utilizes the msExchDelegateListLink attribute in Active Directory is used to determine the mailboxes for which you have Full Access Permission and provides this information to Autodiscover. When Outlook connects with a mailbox on an Exchange 2010 SP1 (or later) server, the Autodiscover information retrieved by Outlook includes the mailboxes to which you have Full Access permission (which originated from the msExchDelegateListLink attribute in Active Directory). These mailboxes are then displayed in the Navigation Pane.

In this problem situation, when you run the Test E-mail AutoConfiguration tool in Outlook and examine the resultant information on the XML tab, you will see the user’s mailbox also listed under <AlternativeMailbox> with <Type>Delegate. An example of this data is shown below:

      
        Delegate
        E14 User1
        /o=WINGTIPTOYS/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=E14 User1
        E2010CASHUB.Wingtiptoys.com
     

In the above example, the Test E-mail AutoConfiguration tool was run on the Outlook client for E14 User1. In this problem configuration, the mailbox for E14 User1 was also listed as a Delegate mailbox in the XML information retrieved from Autodiscover.

To resolve this problem, remove the Full Access Permission given to your account on your own mailbox.

To do this, use the following steps:

  1. In the Exchange Management Console, under Recipient Configuration, select Mailbox and then select the mailbox for which you want to manage Full Access Permission.
  2. In the Actions pane, select Manage Full Access Permission.
  3. In the Manage Full Access Permission dialog box, select the account for which you want to remove Full Access Permission and then click the Remove button.
  4. Click Manage.
  5. Click Finish.

Note, if you are using Exchange 2010 SP2 (or later), you can use a cmdlet similar to the following example to remove Full Access Permission from a mailbox.

Remove-MailboxPermission -Identity <user> -User <user> -AccessRights FullAccess

Note: In order for additional mailboxes to appear in the Navigation Pane in Outlook 2007 (due to the Auto Mapping feature), you must have the following update, or later installed:

Description of the Office Outlook 2007 hotfix package (Outlook-x-none.msp): October 26, 2010
http://support.microsoft.com/kb/2412273  

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: 2548313 – Last Review: September 16, 2014 – Revision: 19.0


Applies to
  • Microsoft Outlook 2010
  • Microsoft Exchange Server 2010 Enterprise

More:
Reminders do not fire, e-mail stays in the Outbox, the To-Do Bar displays an error or Windows Desktop Search frequently rebuilds the indexing of Outlook items

How to re-create the Reports.dic file in Microsoft Dynamics GP

This article describes how to re-create the Reports.dic file in Microsoft Dynamics GP and in Microsoft Business Solutions – Great Plains. This article describes how to do this when you use these programs on a computer that is running Microsoft SQL Server.
To recreate the Reports.dic, use one of the methods below:

METHOD 1:  UTILITIES (RECOMMENDED)

1. Make sure that all computers use the same version and service pack of Microsoft Dynamics GP. Additionally, they must use the same version of Dexterity. To verify the version, in Microsoft Dynamics GP click on Help and then click About Microsoft Dynamics GP.

2. Then synchronize the modified forms and reports by using these steps:

a. Exit out of Microsoft Dynamics GP. 

b. On the server, click on Start, click All Programs, click Microsoft Dynamics to expand it, click GP 2013 (or appropriate version), and then click GP Utilities.

c. Select the Server, User ID and Password, and click OK. (Typically the ‘sa’ credentials are used.)

d. On the Welcome to Dynamics GP Utilities window, click Next.   The product version information will be verified. 

e. On the Upgrade Microsoft Dynamics GP window, click Next.

f. The Additional Tasks window will open. Click the drop-down list and choose Synchronize forms and reports dictionaries and click Process.

g. For the Locate Launch File, path out to the Dynamics.set file in the respective GP code folder and click Open. (The default path is c://Program Files (x86)/Microsoft Dynamics /GP.) Then click Synchronize.

3. Copy the Dynamics.dic file in the GP code folder to any workstation that is not working correctly. 

METHOD 2: MANUAL

To manually export out the modified reports, rename the Reports.dic and reimport in the modified reports, follow these steps:

Step 1: Export Modified Reports from the current Reports.dic file

  1. In Microsoft Dynamics GP, click Microsoft Dynamics GP, point to Tools, point to Customize, and then click Customization Maintenance.
  2. Select the forms or the reports that you want to export from the current dictionary files. Use the SHIFT key or the CTRL key to select more than one resource.
  3. Click Export.
  4. In the Please select a package file dialog box, select the location where you want to save the file, name the package file, and then click Save.

    Note By default, the package file name is “PackageNumber.Package.” The Number placeholder is a placeholder for the number that is incremented every time that an export is performed.

A progress bar shows the status of the export. If an error occurs during the export, the error is listed on the screen. Generally, reports that appear in the error list are not exported.

Step 2: Rename the existing Reports.dic file

  1. Make sure that all users exit Microsoft Dynamics GP.
  2. Using Windows Explorer, navigate to the GP code folder. Right-click on the Reports.dic file and rename it to Reports.bac. (The file or files may exist on the server or on the workstation. Review the local Dynamics.set file for the correct path.)
  3. Start Microsoft Dynamics GP and click on Tools under Microsoft Dynamics GP, point to Customize and click Report Writer. A new Reports.dic file will be automatically created.

Step 3: Import Modified Reports back into the new Reports.dic file

  1. In Microsoft Dynamics GP, click Microsoft Dynamics GP, point to Tools, point to Customize, and then click Customization Maintenance.
  2. Click  Import.
  3. In the Import Package File dialog box, locate the package file that you created during the export process, and then click Open.
  4. In the Import Package File dialog box, click OK to start the import.

    Notes

    • The Import Package File dialog box lists all the resources that exist in the package file.
    • A progress bar shows the status of the import. If an error occurs during the import, the error is listed on the screen. Generally, reports that appear in the error list are imported. However, users may be unable to print the reports.

(ALTERNATE STEP 3) Import the reports from within Report Writer

  1. Make sure that all users exit Microsoft Dynamics GP.
  2. Rename the Reports.dic file to Reports.bac. The Reports.dic file may be located on the server or on the workstation.
  3. Start Microsoft Dynamics GP.
  4. On the Tools menu, click Customize, and then click Report Writer. When Report Writer starts, a new Reports.dic file is created.
  5. Click Reports. The Modified Reports list is empty. If the Modified Reports list is not empty, you renamed the wrong Reports.dic file in the “Step 2: Rename the existing Reports.dic file” section. Find the appropriate Reports.dic file, and then start over in that section.
  6. In Report Writer, click Import.
  7. Click the ellipsis button () next to the Source Dictionary box. Locate the Reports.bac dictionary file that you named in step 2, and then click Open.
  8. In the Source Dictionary Reports list, select the modified reports that you want to import, and then click Insert. The reports are listed in the Reports to Import list.
  9. Click Import. When the Reports to Import list is empty, the modified reports have been imported into the new Reports.dic file.

Note If you created your own table relationships, the table relationships will be removed when you rename the Reports.dic file. After you import the reports, the table relationships that you created will be restored. If you created the relationship but did not link the relationship to a report, you must create the relationship again.

Article ID: 850465 – Last Review: September 15, 2014 – Revision: 6.0


Applies to
  • Microsoft Dynamics GP 2013
  • Microsoft Dynamics GP 2010
  • Microsoft Dynamics GP 10.0, when used with:
    • Report Writer
    • System Manager
kbinfo kbmbsmigrate KB850465

Read more here:
How to re-create the Reports.dic file in Microsoft Dynamics GP

Microsoft Dynamics CRM for Outlook Configuration Wizard Error Code 80044501

The error code 80044501 may occur when the Microsoft Dynamics CRM for Outlook Client Configuration Wizard fails to configure to the CRM organization. The user error may show:

“This version of the Microsoft Dynamics CRM for Outlook client isn’t compatible with your company’s version of Microsoft Dynamics CRM Server” 

This error when the user is running a version of CRM for Outlook that is incompatible with the older server version of Dynamics CRM.
Upgrade to a version of the Microsoft Dynamics CRM for Outlook client that is compatible with your CRM Server version.
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: 3001178 – Last Review: September 15, 2014 – Revision: 1.0


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

Read the article:
Microsoft Dynamics CRM for Outlook Configuration Wizard Error Code 80044501

You cannot access an Exchange Server 2013 mailbox if your mailbox is located in Exchange Server 2010

Issue 1

Consider the following scenario:

  • You have a mailbox on a Microsoft Exchange Server 2010 server.
  • You have the permissions to a shared mailbox that is located on a Microsoft Exchange Server 2013 server.
  • You log on to your mailbox in Microsoft Outlook, and you can see the shared mailbox.

In this scenario, you cannot expand the shared mailbox in Outlook.

Issue 2

Assume that you log on to an administrator mailbox that exists on an Exchange Server 2010 server. You create a profile for a mailbox that is located on an Exchange Server 2013 server. In this situation, the profile is created. However, you cannot log on through the profile.

To resolve this issue, install the following update rollup:
2917508

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

Description of Update Rollup 5 for Exchange Server 2010 Service Pack 3

This issue occurs because Exchange Server 2010 generates an incorrect Autodiscover response for the Exchange Server 2013 mailbox. Specifically, the AlternativeMailbox part of the Autodiscover response shows a server name that is not valid for an Exchange Server 2013 mailbox.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.

Article ID: 2930478 – Last Review: September 12, 2014 – Revision: 1.0


Applies to
  • Microsoft Exchange Server 2010 Service Pack 3, when used with:
    • Microsoft Exchange Server 2010 Enterprise
    • Microsoft Exchange Server 2010 Standard
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2930478

More:
You cannot access an Exchange Server 2013 mailbox if your mailbox is located in Exchange Server 2010

Error 0x8a010101 when you try to activate Office for Mac 2011

When you try to activate Microsoft Office for Mac 2011 version 14.3.9 or an earlier version, you receive the following error message: 

Sorry, there is a problem while trying to connect to your account. (Error code:0x8a010101)

A recent update that expands the allowable product key range on the Microsoft activation server causes earlier versions of Office for Mac 2011 to be unable to complete the activation process.
To resolve this problem, install Office for Mac 2011 version 14.4.3 or a later version. To do this, go to www.microsoft.com/mac

(http://www.microsoft.com/mac)

, click Downloads, and then choose the latest update available. Make sure you download the correct language version.

For more information about this update, click the following article number to view the article in the Microsoft Knowledge Base:  

2978808

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

 Microsoft Office for Mac 2011 14.4.3 Update  

For more information about how to install updates for Office for Mac 2011, go to the following Microsoft Office website: 

Article ID: 2996961 – Last Review: September 12, 2014 – Revision: 2.0


Applies to
  • Microsoft Office for Mac Standard 2011
  • Microsoft Office for Mac Academic 2011
  • Microsoft Office for Mac Home and Business 2011

Read the article:
Error 0x8a010101 when you try to activate Office for Mac 2011

Blind transfer from an anonymous response group agent fails in Lync Server

Consider the following scenario:
  • A response group receives an incoming call in Microsoft Lync Server 2010.
  • The workflow for the response group has the Enable agent anonymity option selected.
  • An anonymous response group agent accepts the incoming call.
  • The agent transfers the call to another response group.

In this scenario, the call transfer fails. Additionally, the following notification and error message are received:

Cannot complete the transfer
When contacting your support team reference error ID 503 (source ID 239).

To work around this issue, follow these steps after the anonymous response group agent accepts the incoming call:
  1. Click the Transfer call to another person or device button that is located on the Lync 2010 call window.
  2. In the Transfer to Others category, click Another Person or Number.
  3. Use the Transfer Call dialog to locate and select the response group contact to transfer the call.
  4. Click the down arrow and then click View more options.
  5. Click the Lync Call feature from the list.

The anonymous transfer for the call will succeed.

Article ID: 2764961 – Last Review: September 12, 2014 – Revision: 2.0


Applies to
  • Microsoft Lync Server 2010 Enterprise Edition
  • Microsoft Lync Server 2010 Standard Edition
  • Microsoft Lync 2013
kbsurveynew kbexpertiseinter kbtshoot KB2764961

Read More:
Blind transfer from an anonymous response group agent fails in Lync Server

July 8, 2014 update for Office 2010 (KB2837606)

This article describes update 2837606 for Microsoft Office 2010 that was released on July 8, 2014.

This update improves efficiency of the algorithm for Office applications to determine whether legacy shapes or modern shapes should be loaded.  

About Office Shapes
Legacy shapes are the shapes that you created by using Office 2003 or earlier Office versions. Modern shapes were added in Office 2007, Office 2010 and Office 2013. The modern shapes support some effects such as Shadow and 3D-Rotation. 

Windows Update

Use Windows Update

(http://update.microsoft.com/microsoftupdate/v6/default.aspx)

to automatically download and install the update.

Download Center

This update is also available for manual download and install from the Microsoft Download Center. If you are not sure what platform (32-bit or 64-bit) you’re running, see Am I running 32-bit or 64-bit Office

(http://office.microsoft.com/en-001/support/am-i-running-32-bit-or-64-bit-office-HA010361023.aspx)

.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591

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

How to obtain Microsoft support files from online services

Virus-free claim

Collapse this imageExpand this image

Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.

Collapse this imageExpand this image

Restart information

You do not have to restart the computer after you install this update.

Prerequisites

To apply this update, you must have either Microsoft Office 2010 Service Pack 1 (SP1) or Service Pack 2 (SP2) installed. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

2460049

(http://support.microsoft.com/kb/2687455/en-us)

Description of Office 2010 SP1

2687455

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

Description of Office 2010 SP2

File Information

Collapse this imageExpand this image

This update contains the files that are listed in the following tables.

32-bit

Oartconv-x-none.msp file information

Collapse this tableExpand this table

File name File version File size Date
Oartconv.dll 14.0.7128.5000 11,139,264 11-Jun-2014


64-bit

Oartconv-x-none.msp file information

Collapse this tableExpand this table

File name File version File size Date
Oartconv.dll 14.0.7128.5000 19,217,600 11-Jun-2014

How to uninstall this update

Collapse this imageExpand this image

Windows 7, Windows Vista and Windows XP

  1. Click Start, and then click Run.
  2. Type Appwiz.cpl, and then click OK.
  3. Use one of the following procedures, depending on the operating system that you are running.
    • Windows 7 and Windows Vista

      1. Click View installed updates.
      2. In the list of updates, locate and click update KB2837606, and then click Uninstall.
    • Windows XP
      1. Click to select the Show updates check box.
      2. In the list of updates, locate and click update KB2837606, and then click Remove.

Windows 8

  1. Swipe in from the right edge of the screen, and then tap Search. If you are using a mouse, point to the lower-right corner of the screen, and then click Search.
  2. Type windows update, tap or click Settings, and then tap or click View installed updates in the search results.
  3. In the list of updates, locate and then tap or click update KB2837606, and then tap or click Uninstall.

Collapse this imageExpand this image

The Office System TechCenter contains the latest administrative updates and strategic deployment resources for all Versions of Office. For more information about the Office System TechCenter, go to the following Microsoft website:

Article ID: 2837606 – Last Review: September 12, 2014 – Revision: 3.0


Applies to
  • 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
atdownload kbexpertisebeginner kbsurveynew KB2837606

Continue reading here:
July 8, 2014 update for Office 2010 (KB2837606)

Blank screen when you try to open an Excel workbook by double-clicking its icon or file name

When you double-click an icon or file name for a Microsoft Excel workbook, Excel starts but displays a blank screen where you expect the file to appear.

To resolve this problem, try the following methods, as appropriate, in the given order.

Method 1: Ignore DDE

Collapse this imageExpand this image

This problem may occur if the Ignore other applications that use Dynamic Data Exchange (DDE) check box in Excel options is selected.

When you double-click an Excel workbook in Windows Explorer, a dynamic data exchange (DDE) message is sent to Excel. This message instructs Excel to open the workbook that you double-clicked.

If you select the “Ignore” option, Excel ignores DDE messages that are sent to it by other programs. Therefore, the DDE message that is sent to Excel by Windows Explorer is ignored, and Excel does not open the workbook that you double-clicked.

To correct this setting, follow these steps:

  1. On the Tools menu, click Options.
  2. Click the General tab.
  3. Clear the Ignore other applications that use Dynamic Data Exchange (DDE) check box, and then click OK.

Note For more information about how to turn off DDE, see the following Microsoft Knowledge Base article:

211494

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

“There was a problem sending the command to the program” error in Excel

If these steps do not resolve the problem, go to Method 2.

Collapse this imageExpand this image

Method 2: Repair User Experience Virtualization (UE-V)

Collapse this imageExpand this image

If you are running Update User Experience Virtualization (UE-V), install hotfix 2927019. To do this, see the following Microsoft Knowledge Base article:

2927019

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

Hotfix Package 1 for Microsoft User Experience Virtualization 2.0

If you are not sure whether you are running UE-V, examine the program list in the Programs and Features item in Control Panel. An entry for “Company Settings Center” indicates that you are running UE-V.

If these steps do not resolve the problem, go to Method 3.

Collapse this imageExpand this image

Method 3: Reset file associations

Collapse this imageExpand this image

To check whether the file associations in the system are performing correctly, reset the Excel file associations to their default settings. To do this, follow the steps for your operating system.

Windows 8
  1. On the Start screen, type Control Panel.
  2. Click or tap Control Panel.
  3. Click Default Programs, and then click Set your default programs.
  4. Click Excel, and then click Choose default for this program.
  5. On the Set Program Associations screen, click Select All, and then click Save.
Windows 7
  1. Click Start, and then click Control Panel.
  2. Click Default Programs.
  3. Click Associate a file type or protocol with a specific program.
  4. Select Microsoft Excel Worksheet, and then click change program.
  5. Under Recommended Programs, click Microsoft Excel.
  6. If Excel does not appear in this list, click Browse, locate the Excel installation folder, click Excel.exe, and then click Excel.

If these steps do not resolve the problem, go to Method 4.

Collapse this imageExpand this image

Method 4: Repair Office

Collapse this imageExpand this image

Try to repair your Office programs. To do this, follow the steps for your installation type and operating system.

For an Office 365 Click-to-Run installation
Windows 8
  1. On the Start screen, type Control Panel.
  2. Click or tap Control Panel.
  3. Under Programs, click or tap Uninstall a program.
  4. Click or tap Microsoft Office 365, and then click or tap Change.
  5. Click or tap Online Repair, and then click or tap Repair. You may have to restart your computer after the repair process is finished.
Windows 7
  1. Click Start, and then click Control Panel.
  2. Double-click Programs and Features.
  3. Click Microsoft Office 365, and then click Change.
  4. Select Online Repair, and then click Repair.

    Note You may have to restart your computer after the repair process is complete.

    Collapse this imageExpand this image

For an Office 2013, Office 2010, or Office 2007 installation

To repair Office 2013, Office 2010, or Office 2007, follow the steps in the following Office website topic:

Repair Office programs

(http://office.microsoft.com/en-us/outlook-help/repair-office-programs-HA010357402.aspx)

If these steps do not resolve the problem, go to Method 5.

Collapse this imageExpand this image

Method 5: Turn off add-ins

Collapse this imageExpand this image

Excel and COM add-in programs can also cause this problem. These two kinds of add-ins are located in different folders. For testing, disable and isolate the conflict by turning off each add-in one at a time. To do this, follow these steps:

  1. On the File menu, click Options, and then click Add-Ins.
  2. In the Manage list at the bottom of the screen, select COM Add-Ins item, and then click Go.
  3. Clear one of the add-ins in the list, and then click OK.
  4. Restart Excel by double-clicking the icon or file name for the workbook that you are trying to open.
  5. If the problem persists, repeat steps 1-4, except select a different add-in in step 3.
  6. If the problem persists after you clear all the COM Add-ins, repeat steps 1-4, except select Excel Add-Ins in step 2, and then try each of the Excel add-ins one at a time in step 3.

If Excel loads the file, the add-in you last turned off is causing the problem. If this is the case, we recommend that you visit the manufacturer’s website for the add-in to learn whether an updated version of the add-in is available. If a newer version of the add-in is not available, or if you don’t have to use the add-in, you can leave it turned off.

If Excel does not open the file after you turn off all the add-ins, the problem has a different cause.

If these steps do not resolve the problem, go to Method 6.

Collapse this imageExpand this image

Method 6: Disable hardware acceleration

Collapse this imageExpand this image

To work around this problem, disable hardware acceleration until a fix is released by your video card manufacturer. Make sure to check regularly for updates to your video card driver.

To disable hardware acceleration, follow these steps:

  1. Start any Office 2013 program.
  2. On the File tab, click Options.
  3. In the Options dialog box, click Advanced.
  4. In the list of available options, select the Disable hardware graphics acceleration check box.

    The following screen shot shows this option in Excel.

    Collapse this imageExpand this image

  5. Click OK.

Note For more information about hardware acceleration, see the following Microsoft Knowledge Base article:

2768648

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

Performance and display issues in Office 2013 client applications

Collapse this imageExpand this image

If you still experience this problem after you try all these methods, contact Microsoft Support

(http://support.microsoft.com/contactus/?ws=support)

for additional troubleshooting help.

View article:
Blank screen when you try to open an Excel workbook by double-clicking its icon or file name

Page 1 of 73712345...102030...Last »

Recent Comments

    Archives

    Categories