[RESOLVED] Excel 2007 Custom UI XML macro parsing error

[doasidont]

I am having a new problem adding personal macro buttons to the Quick Access Toolbar.

I set 'Show Add-in User Interface Errors' in the Advanced tab of Excel Options and get this error when I open a workbook with personal macro buttons added to the QAT:

Error loading in Custom UI XML:
Line: 1
Column: 411
Error code: 0x80004005
A name contained an invalid character.
Error parsing 'doc:C:_Documents_and_Settings_myusername_Desktop_Book6.xlsm_Macro1_1' as Qname datatype.
The attribute 'idQ' with value 'doc:C:_Documents_and_Settings_myusername_desktop_Book6.xlsm_Macro1_1' failed to parse.

I deleted the macros and manually keyed some simple command (msgbox 1) into a new macro and still got this error message.

I set 'Show Add-In User Interface Errors' on a remote server (where I do not have this problem) and I do not get this error message when loading workbooks with customized QAT.

Any help would be appreciated.

[Siddharth Rout]

I have replied to your other thread...

Just a quick question? Have you uninstalled Excel 2003 completely and then installed 2007?

[doasidont]

No, I am using 2003 for another application that cannot be migrated to 2007 at this time.

[doasidont]

I have been running Excel 2003 and Office 2007 with Excel 2007 for some time. I did a complete uninstall of Office 2007, Registry clean, and reinstall of Office 2007 with SP2. Did not fix the problem.

[Siddharth Rout]

I have been running Excel 2003 and Office 2007 with Excel 2007 for some time. I did a complete uninstall of Office 2007, Registry clean, and reinstall of Office 2007 with SP2. Did not fix the problem.

Hmmm... I thought so... This my friend is not recomended....

http://support.microsoft.com/kb/928091/en-us

Hope this helps...

[doasidont]

This problem was finally resolved by uninstalling Office 2003 and Office 2007 and then reinstalling 2003 and then 2007. I have been running both versions for some time. My suspicion is that some Windows Update fix (which is not automatically installed but I generally apply as recommended) caused this problem. I haven't yet identified which one(s) it may be.