Home › Forums › eaDocX queries › Error in opening Excel Workbook
Home › Forums › eaDocX queries › Error in opening Excel Workbook
- This topic has 16 replies, 4 voices, and was last updated 12 years ago by Adrian Support.
-
AuthorPosts
-
15 November 2012 at 4:45 pm #6323Werner SchoenmaekersParticipant
I get this error when I try to create or open a new Excel in EADocX
What goes wrong?I can work with Word docs in EADocx, only Excel does not work…
15 November 2012 at 7:38 pm #6324eaDocX Web Support TeamParticipantPlease give more information
15 November 2012 at 10:53 pm #6325Werner SchoenmaekersParticipantI just to to the plug-in menu, select there eadocx and click on “new excel”.
The James light be alittle different because Im not werking on my pc now and I can’t see the menu.Then i get aan error screen with the eadocx logo on it and it has à message “error in opening excel workbook”….
16 November 2012 at 7:10 am #6326eadocX SupportParticipantI’m sorry to keep asking, but in order to resolve your problem, we really do need some more information:
– Operating system
– Version of Office
– Version of eaDocX
– Version of EA
…and exactly which part of eaDocX you were using when the error occurred.
Without this, we are totally in the dark !Thanks
16 November 2012 at 1:37 pm #6327Werner SchoenmaekersParticipantWindows7 Enterprise SP1- 4GB – 32 bit
Excel 2007 (12.0.6425.1000) SP2
EADOCX 3.2.5.2
EA 9.3What I did: extensions – EADocx – EAXL – Create new workbook
Then I get
Error1
Error2
And the I see “screen after errors”Note that
– EADocX – Word does work on this machine.
– EaXl does not work on this machine, and does not work on 2 other of my machines ( which is very strange )Wkr
Werner16 November 2012 at 5:31 pm #6328Adrian SupportParticipantHello Werner,
I have tried to reproduce your error without success although we don’t have a Windows 7 Enterprise edition to hand to test against the rest of the configuration is the same. FYI: the errors you are getting relate to some exceptions when we try to open Excel. So possibly need to add some instrumentation to get more detail from a small area of code.
But to start with a few more questions, if I may:
1. Can I verify that the version of Office 2007 is a full installation of Excel and not the ClickToRun version – we know there are problems with ClickToRun as Office may not have installed all the bits we need. We need to confirm that Excel is fully installed and accessible.
2. Do you get the same results regardless of how you try to open Excel e.g. if you use select a package in the project browser | Right click | Extensions | eaDocX | Open in Excel do you get the same errors
3. You say that you are getting the error on other machines – can you confirm that they are all the same configuration
We will update eaXL with some additional instrumentation ready to enable us to perform more checks should that be needed.
Regards
17 November 2012 at 11:08 am #6329Werner SchoenmaekersParticipantHi,
I can’t test it now on the Windows7 32b machine which is at work) , as I’m at home now.
At home I have Win 7 64bit Enterprise
EA 9,3
EADocxX 3.2.5.2
Office 2007 ( 12,0,4518,1014) fully functional, no install on first run etc… so Excel is working on my home-pcI have exactly the same errors as I descibed.
To answer your questions:
1. Yes, Excel (office) is fullt installed and working.
2, Yes, I get exactly the same errors when I try to open from the Project browser.
3, They are not exactly the same. But they all have Win7 (32 or 64 bit ) and all Office 2007I think it’s best to concentrate on just one config at a time.
Instrumentation will certainly help to pinpoint the problem. Or maybe a seperate test program ( which you could reuse for other customers ).
Wkr
Werner19 November 2012 at 2:25 pm #6330Adrian SupportParticipantHi Werner,
Think I have found a possible cause of the problem you observe.
To check this I have produced a simple test application which I would ask you to run and check the results – there is an executable and text file with instructions in the attached zip.
As it says in the instructions – please ensure that you do not have any other instances of Excel running when you run the test application – and then if you could send the results back as per the notes that would be great.
You will see that if you can create an instance of Excel by pressing the button create then I have a solution for you 🙂
Any questions please ask.
BR
Adrian
19 November 2012 at 3:19 pm #6331Werner SchoenmaekersParticipantI do not see any excell notebook when I create a new one.
Trace:
Row ID info
1 @ 1/01/0001 16:18:36
2 Start of eaXL_Pane New @ 1/01/0001 16:18:36
3 eaXL_Pane – _xlPresent @ 1/01/0001 16:18:36
4 eaXL_Pane – _xlPresent – total procID before = 0 @ 1/01/0001 16:18:36
5 eaXL_Pane – _xlPresent – total procID after = 2496 @ 1/01/0001 16:18:36
6 eaXL_Pane – _xlPresent – xl application process ID = 2496 @ 1/01/0001 16:18:36
7 Start of eaXL_Pane New @ 1/01/0001 16:18:36
8 eaXL_Pane – _xlPresent @ 1/01/0001 16:18:36
9 eaXL_Pane – _xlPresent – total procID before = 2496 @ 1/01/0001 16:18:36
10 eaXL_Pane – _xlPresent – total procID after = 7916 @ 1/01/0001 16:18:36
11 eaXL_Pane – _xlPresent – xl application process ID = 5420 @ 1/01/0001 16:18:36
12 ID2: @ 1/01/0001 16:18:36 End of Panel Load Event
13 ID2: @ 1/01/0001 16:18:36 XLMain Load event
14 ID2: @ 1/01/0001 16:18:58 Create New Click Button
15 ID2: @ 1/01/0001 16:18:58 Start Load Document
16 @ 1/01/0001 16:18:58
17 eaXL_Pane – start of openDocument @ 1/01/0001 16:18:58
18 eaXL_Pane – xlApplication = Microsoft Excel @ 1/01/0001 16:18:58
19 eaXL_Pane – Exception 0 System.Runtime.InteropServices.COMException (0x80028018): Old format or invalid type library. (Exception from HRESULT: 0x80028018 (TYPE_E_INVDATAREAD))
at Microsoft.Office.Interop.Excel.Workbooks.Add(Object Template)
at eaXL_ExcelTest.eaXL_Pane.openDocument(String filename) @ 1/01/0001 16:18:58
20 ID2: @ 1/01/0001 16:18:58 End Load Document
21 ID2: @ 1/01/0001 16:19:08 Start of Copy list view to Clipboard19 November 2012 at 3:52 pm #6332Adrian SupportParticipantHi Werner
Thanks for this it is really helpful.
It looks like an Excel process was created OK but then it complains about adding a workbook – not what I expected at all.
It indicates that the library it is trying to use is incompatible.
I’ve found some information on the Microsoft site (if your interested!! http://support.microsoft.com/default.aspx?scid=kb;en-us;320369)Briefly looks like this is an Excel bug – quoting MS
“If the client computer runs the English version of Excel and the locale for the current user is configured for a language other than English, Excel will try to locate the language pack for the configured language. If the language pack is not found, the error is reported. ”
I’ll look at this in more detail and review solution.
Strange that with all the licenses we have sold in non-English countries we haven’t seen before! I assume most have used their local version of Excel so we haven’t seen this issue.
Hopefully back to you soon.
BR
Adrian
19 November 2012 at 4:12 pm #6333Werner SchoenmaekersParticipantHi Adrian,
Yes, it’s weird…certainly because MS Word does work within EA , it’s just Excell which isn’t…
Maybe the others have the language pack installed?
Wkr
Werner19 November 2012 at 5:38 pm #6334Adrian SupportParticipantHi Werner
I must assume that they have a local language version of Excel or the Multilingual User Interface Pack for your version of Office.
Also the origins of Excel and Word were different and this still shows up in their API’s so I’m not totally surprised.
Ideally I can configure a non-English system and produce the same error.
I’ll do my best to resolve in a timely manner
BR
Adrian
20 November 2012 at 10:58 am #6335Adrian SupportParticipantHi Werner,
I’ve spent some time looking at the problem you identified and been able to reproduce the Excel bug exactly.
And yes it is due to running an English version of Excel on a computer for which the regional settings for the computer are configured for a non-English language.As in the link I sent previously (http://support.microsoft.com/default.aspx?scid=kb;en-us;320369) this is a Microsoft Bug and looking at the solutions it looks like the quickest, based on the Microsoft support answer, is for you to install the Multilingual User Interface Pack for your version of Office.
This is the first time we have seen the error – and will be looking at it further as we want to ensure it doesn’t impact users, however the other solutions require code changes and the extent of these is unknown until we have reviewed further, and of course we then need to make the changes and do regression testing, so not a quick solution.
You may also be able to change your locale temporarily and test in English(!) – I assume this should work.
I know this is not the response you want to hear (or we want to send), however I hope it provides you with a workaround to explore eaDocX further.
BR
Adrian
20 November 2012 at 12:38 pm #6336Werner SchoenmaekersParticipantthe Multilingual User Interface Pack for your version of Office.
You mean probably the Multilingual User Interface Pack for your version of “Windows”?
20 November 2012 at 1:49 pm #6337Adrian SupportParticipantHi Werner,
Well I took the description directly from MS support so i do believe they were referring to an a version for Office.
However in having a quick look there are Multilingual User Interface Packs for Office 2003 but can’t find versions for 2007!
In fact looks like this was a common question – so probably need to explore further. Many of the comments I can see state that each version of Excel is single language – which creates an issues with a mixed language situation such as yours where you have an English version of Excel with non-English regional settings.
BR
Adrian
-
AuthorPosts
- You must be logged in to reply to this topic.
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download