OWC10 xmlurl (passes) vs. OWC11 xmlurl (fails)

[nalenb]

I have an xml spreadsheet created by exporting from Excel (2002) which
is about 16megs (yes, megs). I created a simple asp.net project in
vs.net 2003 and added the owc10 dll to it. I create a new spreadsheet
object and set the xmlurl property to my file which exists locally and
the asp.net user has access to. OWC10 properly loads the spreadsheet
and all is fine.

I change the project by deleting the owc10 reference and put in the
owc11 reference. I compile and run the web page. owc11 throws an error
on the xmlurl line:

Exception Details: System.Runtime.InteropServices.COMException:
Unspecified error

Looks like error 0x80004005

Any ideas what could be wrong? The xml file has the proper rights,
works fine with owc10 and Excel. It does have pivot tables and other
stuff in it.

I was hoping that loading this file and manipulating it would be faster
in owc11 but it appears that I might have to go back to owc10.

I really wish MS would clean up Excel itself so that I could use it
from asp.net to load the actual xls and use it (I present nothing from
Excel to the user, Excel is just used to do the backend calculations).
However, Excel has problems with multi threading and sometimes pops up
dialog boxes on the server which blocks everything from then on,
obviously not a good solution on the server.

Thanks
Bill

 

[Alvin Bruney - ASP.NET MVP]

just try re-registering the owc11 at the command prompt. It may be broken

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006

 

[nalenb]

Nope, same error. I'm not surprised since I just installed owc 11 today
and haven't made any changes since installing it. I'm really hoping
that your book fills the documentation hole that MS has totally left us
in. I'm absolutely shocked at how much my company has paid (per
processor even) for a license to use OWC and has received no support
from MS in return.

 

[Alvin Bruney - ASP.NET MVP]

Let's start over then. Create a simple test project. set the CSVDATA
property of the file to a hard coded value "1,2,3,4" for instance. See if
that loads. Then try a simple XMLURL locally see if that loads. If the both
load locally, the problem lies in your code, otherwise it lies in the
components. Next, modify the simple examples to load the same file but using
a remote source http://localhost/csvdat.txt for instance, followed by the
url. If it still loads correctly, your data source is likely the cause of
the issue.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006

 

[nalenb]

I created a simple workbook using Excel, basically just a couple
numbers, then saved it to my web folder as an xml file. I put that file
name in my project, rebuilt, and ran the web app (which just loads owc
and sets the xmlurl. It works just fine as I suspected.

My other xml file is in the same place and fails to open with owc11,
but works fine in owc10. So I'm sure it has something to do with the
contents of the workbook.

Here's my beef, MS obviously changed something between 10 and 11. But
now there's no way to get support for why my xml is failing in 11. I'll
probably have to spend a lot of my company's time figuring out exactly
what in this gigantic spreadsheet is causing the problem. All this
despite the fact that MS is charging us $20,000 per processor to use
this "free" control on our server.

Since I don't think a solution is going to come quickly, I suppose you
can just ignore this thread now Amazon says your book should be
here on Tuesday, hopefully that can shed some light on things to avoid
in creating the spreadsheets.

 

[Alvin Bruney - ASP.NET MVP]

what in this gigantic spreadsheet is causing the problem. All this

despite the fact that MS is charging us $20,000 per processor to use
this "free" control on our server.

OWC is not available on a per processor basis. The cost of the license is
tied to the Office product that is installed on the desktop.

I think you have a quote in your data body "'". You can try looking for this
or replacing all quotes with some other character. I did spend 7 days
trouble-shooting a similar problem.

By the way, you do have support options. Call MS and open a trouble-ticket
based on any one of your licensed office products. You have 3 trouble
tickets that are free per product. After that, it costs $100.00


--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006