Excel pivot table. Any language you like as long as its US English

Hi,
I have created an OLAP Cube in SQL Server 2005 CTP2 and can browse it fine in the Analysis Studio / Browse tab. When I use the pivot table feature in Excel (2003) I get:
XML for Analysis parser: The LocaleIdentifier property is not overwritable and cannot be assigned a value.
Any help is appreciated.
Cheers,
Adam
I have the same problem.
I'm using the September ctp on Win XP Us

My current windows user is a french user.

I have no idea, I try 3 installations and I always have the same pb: Excel returns me the message, and the BI Visual Studio ML Browser doesn't work.
|||Same problem...no clue at all
win xp sp2, ctp sept....|||I have the same problem - sept. ctp Windows 2003 Server with SP1
Czeslaw|||Yup, me too.... WinXP sp2, SS2005 sept ctp, Office 2003. Any help would be appreciated.

Regards
Kjetil|||Hi.
As you can see on my other post, I had the same problems but after scratcing my head for a few hours, I tried to change the regional settings in Windows controlpanel from Norwegian to English (United States) and VOILA - up popped the pivottable in Excel.

There might be a way to change the settings in SSAS to concur with the regional settings in Windows but I haven't gotten that far yet.

PS: I first tried to remove Norwegian from the MS Office 2003 Language settings but that didn't help...

Hope this will solve your problems too.

Regards
Kjetil |||I can confirm that this fix works for me. Good work Kjetil.|||

I believe you'll find that the problem is actually a missing locale message table. The problem is with the OLEDB driver. Here's how to check:

a) naviagate to the location of the oledb driver. It should be in: C:\Program Files\Common Files\System\Ole DB.

b) check the entries in msmdsrv.log. You should see that it's complaining about a missing message manager. You should notice that the locale ID matches the value set in Control panel.

Now a workarround that I applied, without having to change the control panel was to copy the directory in .\resources\1033 (US english) to .\resources\4105 (Canadian English). This uses the US english entries until Microsoft releases the fix.

Note: remember, this would have to be done on every client PC, accessing AS.

|||

I use Japanese version.
I can solve the problem.

September CTP
Windows XP Pro. with SP2
Office 2000 with SP3

[controlPanel]-[regional settings]
Japanese To English (United States)

thanks!

|||Hi all,

Thank you for all the suggestions, only one worked was changing the regional settings.

This problem means that this CTP has effectively failed before even starting, not very good!!!

Anyone know if there is a fix yet?

Iain

|||

Hello again.

I finally found the solution to this problem: Update to the latest version of Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider found at :

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

This also solved a memory problem I had earlier with the error message:

"Memory error: While attempting to store a string, a string was found that was larger than the page size selected. The operation cannot be completed."

Thanx to Dave Wickert who gave the tip!

Regards

Kjetil

|||

I installed the latest version of Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider , but still have the "LocalIdentifier" problem as soon as I change the regional settings from US English to something else.

Any more ideas ?

Thanks.

|||

Was: Excel pivot table. Any language you like as long as its US English

I have this message appearing in Excel when connecting to Analysis Services 2000 and 2005 cubes. I have never used languages other than English in the application and the locale settings were NOT changed.

Installing the the latest version of Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider does NOT solve the issue which appears to be intermittent.

Immediately prior to the error I was trying (in vain) to use scripts to control the behaviour and "protection" of OWC web published components.

A fix is needed urgently.

|||

Something you may want to try.

a) Had a similar issue, & narrowed down to a conflict between AS_OLEDB Version 8 & 9 installed on same PC. Seems the upgrade to 9 doesn't clean up the old version. To resolve this, run uninstall of the existing oledb driver, go to C:\Program Files\Common Files\System\Ole DB & delete all files in this directory if they exist, re-install AS_OLEDB 9.0.

P.S. Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider (OLEDB 9.0) available at www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc

b) Check analysis server default language.

i.e. SQL Management studio, connect to Analysis Server, Properties (right click on server), Language/Collation, set to US English.

|||

Hi,

I realise that this is an old post but as we had this issue for some of our users january 2006 it might help someone...

We had an old version of IntelligentApps installed (4.5.0.29) on the clients where we had the XMLA-LocaleIdentifier issue. When we disabled that plugin the problem went away.

If you need to use that plugin to access 2000-cubes and don't want to upgrade it is an easy task to disable/enable the plugin (you will find a shortcut under "start->program->intelligentapps->excel edition->Enable or disable excel addins".

Thanks

Gabriel