Microsoft Knowledge Base Email Alertz

Garbage characters may be included in an .odc file when the file is created in Excel 2010 or in Excel 2007

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 983109 - Last Review: August 26, 2011 - Revision: 2.2

Garbage characters may be included in an .odc file when the file is created in Excel 2010 or in Excel 2007

SYMPTOMS

Consider the following scenario:
  • You have a site collection on Microsoft SharePoint Server that is running a non-English version of Windows such as Japanese.
  • In Microsoft Excel 2010 or in Microsoft Office Excel 2007, you connect to the server that is running Microsoft SQL Server and Microsoft SQL Analysis Services.
  • You specify a cube or a SQL Server relational database that contains non-ASCII characters in its name. For example, the cube name or the database name contains Double Byte Character Set (DBCS) characters. 
  • You save the connection as an .odc file. By default, the .odc file name contains the cube name or the database name.
  • In Report Center on the server, you upload the .odc file to the Data Connections document library.

In this scenario, the Title box on the ReportCenter tab contains garbage characters where the non-ASCII characters should be displayed. Additionally, you may receive an error message when you try to load the same .odc file from the document library to Excel again.

Note The non-ASCII characters are displayed correctly in the Name box of the ReportCenter tab.

WORKAROUND

To work around this problem, do not use non-ASCII characters in a cube name or in a SQL Server database name.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Excel 2010
  • Microsoft Office Excel 2007
Keywords: 
kbsurveynew kbprb kbexpertiseinter KB983109
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate