After an install of Office 2k7 last night, I'm getting some errors in my event log when i run BI Studio. The errors occur when i click a tab that tries to browse the metadata of the cube. IE: The calculations tab, or KPI's, etc..
These are the 2 errors:
Event Type: Error
Event Source: MSOLAP$LocalCube
Event Category: (289)
Event ID: 1
Date: 1/09/07
Time: 8:54:08 AM
User: N/A
Computer: WS124
Description:
The description for Event ID ( 1 ) in Source ( MSOLAP$LocalCube ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Message-handling subsystem: The message manager for the 4105 locale cannot be found..
Event Type: Error
Event Source: MSOLAP$LocalCube
Event Category: (289)
Event ID: 0
Date: 1/09/07
Time: 8:54:08 AM
User: N/A
Computer: WS124
Description:
The description for Event ID ( 0 ) in Source ( MSOLAP$LocalCube ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Message-handling subsystem: The message manager for the default locale cannot be found. The locale will be changed to US English. Errors in the metadata manager. The configuration property updates were not persisted. Internal error: An unexpected exception occured..
I am going to have BI Studio reinstalled, to see if that fixes the error. I am curious if anyone else has had/heard of this issue?
Thanks,
C
Hello. Here is a blog post that might help.
http://geekswithblogs.net/darrengosbell/archive/2006/11/17/97367.aspx
I am running Office 2007 with SQL Server 2005 SP2 CTP3(december). I never uninstalled the Office 2003 web components when I upgraded to Office 2007. This mix works without any problems.
HTH
Thomas Ivarsson
|||Thanks,
We are getting the hotfix from MS to give it a go. I will certainly post the results.
C|||
Hi
I got the same problem after installing MS Excel 2007 with the option to remove Excel 2003. I reinstalled Excel 2003 again later for testing purposes.
Chris, you never posted the results of the hotfix so I suppose that it worked!
Problem is, which hotfix did you use and where did you get it?
Thomas the link that you've supplied doesn't work ...
Thanks
Kobus
|||
Hi
Sorry Thomas, your link worked the second time around. Our Service Provider is experiencing problems with our connection so now we are on the backup ISDN line, we don't have T1 in South Africa like you guys in the US. The page may have timed out.
Info on the hotfix is here:
http://support.microsoft.com/default.aspx/kb/926421
More info on the workaround here:
http://sqlug.be/forums/339/ShowThread.aspx#339
You have to contact MS for the hotfix. SQL Server 2005 SP2 will solve the problem and since our company has that, that's the way I'll go.
Word Out
Kobus
|||Sorry Kobus,
You're right, i didn't post my results..
After applying the hotfix, i still ended up having to copy some DLL's around, as per your second link.
After i did that, it worked fine. But then i had some other software installed (i can't remember what it is right now) and it reverted the DLL's, so i had to re-copy them back so they were all the same version again.
Regardless, it should be ok if you install the hotfix, and make sure all the DLL's in those locations are the same version.
C
