We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

XlsIO Assix Bug

Dear All,
I have just downloaded XlsIO and tried to see if it works.
Unfortunately, I think I have found a bug.

I try to open a simple Excel file containing 4 simple charts.
I just can't open the file. I get an exception: Syncfusion.XlsIO.Implementation.Charts.ChartCategoryAxisImpl.

The code I use is:

Syncfusion.XlsIO.ExcelEngine eng = new Syncfusion.XlsIO.ExcelEngine();
IApplication application = eng.Excel;
IWorkbook workbook = eng.Excel.Workbooks.Open(@"d:\101.xls", ExcelOpenType.Automatic);
workbook.Close();

Yuo'll find attached the file I can't open.
Please let me if there is any workaround for this bug.

Thanks a lot.
Andy.



101.zip

14 Replies

AD Administrator Syncfusion Team February 29, 2008 08:21 AM UTC

Hi Andy,

Thank you for your interest in Syncfusion products.

XlsIO Exception:Syncfusion.XlsIO.Implementation.Charts.ChartCategoryAxisImpl:

I am afraid that I was not able to reproduce the issue that you mentioned here. I tried to open your file through XlSIO. It opens without any exception. I have tested this issue in the below environment "Windows XP with SP2, .NET 2.0 Framework, Essential Studio v.61.0.34, Ms Excel 2002 ", but I was not able to reproduce the exception.

I have created a simple sample to test this issue and it is available in the following link:

http://websamples.syncfusion.com/samples/XlsIO.Windows/F72046/main.htm

Please have a look at the above sample and if still the issue exists, could you please try reproducing it in the above sample and send us the modified sample so that we could sort out the cause of the issue and provide you a solution?

Please provide the below details also.
1. Sytem configuration
2. Office version


Regards,
G.Yavana







AN Andy February 29, 2008 09:03 AM UTC


I have downloaded the sample you had created and I get exactly the same exception.

My original environment is:
OS: Windows VISTA (no SP) in Italian
XlsIO base version: 6.102.0.34
FW version: .NET Framework 3.5
IDE: Visual Studio Team System 2008
Excel: Microsoft Excel 2007 and OpenOffice 2.3.1 (both in Italian)

Then I tested the same sample you prepared on my secondary environment:
OS: Windows XP (SP2) in Italian
XlsIO base version: 6.102.0.34
FW version: .NET Framework 2.0
IDE: Visual Studio Professional 2005
Excel: Microsoft Excel 2007 and OpenOffice 2.3.1 (both in Italian)

The only 2 things my systems have in common are:
1. Operating System in Italian (I live in Italy).
2. Excel 2007 and OpenOffice installed (both in Italian).
I don't see anything else in common.

Do you think that having openOffice installed on my Pc might cause this issue? I wouldn't say so, because your library is 100% managed.

Is there anything I could do to provide you more informations on this issue?

I'd realy like to solve this issue because I think your library is just great.

Thanks a lot.
Regards,
Andrej.



AN Andy February 29, 2008 09:13 AM UTC

Dear Yavana,
in my previous email I forgot to thank you very much for your quick reply.

I also forgot to mention that I use .NET Framework in Italian because it's already installed with Windows Vista in Italian (do you think it might be an issue?).

I'd also like to help you find this bug by attaching you the screenshot of the exception. I don't know if it might help you in some way.

Thanks again and best regards.
Andy.



Exception.zip


AD Administrator Syncfusion Team February 29, 2008 05:29 PM UTC

Hi Andy,

1) I have the exact same set up (Vista, .NET framework 3.5, Open office) and it works fine. I assume that the only difference is the Italian OS. XlsIO is fully managed code but it does rely on Windows API to read/write compound files. We will try to reproduce the problem using an Italian OS.

2) Also, if you are not modifying charts in runtime could you please try setting this flas while opening the file

IWorkbook workbook = eng.Excel.Workbooks.Open(@"../../Data/101.xls",ExcelParseOptions.DoNotParseCharts);

This option skips parsing charts in the template but would preserve the chart when you write it back.

3) Also, try setting these options to see if it helps

IApplication application = eng.Excel;
application.UseFastRecordParsing = false;
application.UseNativeOptimization = false;

Thanks,
Stephen.





AN Andy February 29, 2008 05:40 PM UTC

Dear Stephen,
thanks a lot for your help.

I modified my code in this way:
ExcelEngine engine = new ExcelEngine();
IApplication application = engine.Excel;
application.UseFastRecordParsing = false;
application.UseNativeOptimization = false;
// Opening the Existing Worksheet from a Workbook
IWorkbook workbook = application.Workbooks.Open(@"..\..\Data\101.xls", ExcelParseOptions.DoNotParseCharts);


You won't believe it; I still get the same exception.

Is there anything else I might do to help you find out the bug?

Thanks again,
Andy.



AD Administrator Syncfusion Team March 3, 2008 12:15 PM UTC

Hi Andy,

Sorry for the delay in responding.

XlsIO Exception:Syncfusion.XlsIO.Implementation.Charts.ChartCategoryAxisImpl

I am able to reproduce the issue with an Italian Os. The issue mentioned here is suspected to be a defect and we have sent this to our development team for more analysis. We will update you once we get back from our development team.

Please let me know if you have any other concerns.

Regards,
G.Yavana





AN Andy March 4, 2008 07:50 AM UTC

Dear Yavana,
thank you very much for your reply.

Well, I hope to see a new bug-solving release very soon. Once you solved the issue will you create a new release or you'll just tell me what I can do to avoid this bug.

Thanks a lot.
Andy.



AD Administrator Syncfusion Team March 4, 2008 10:49 AM UTC

Hi Andy,

Thank you for your update.

Our development team will update you regarding this issue within two days.

Please let me know if you have any other concerns.

Regards,
G.Yavana



AN Andy March 13, 2008 02:27 PM UTC

Dear Yavana,
do you have any updates for me.
Have you figured out any workaround for my issue.

Thanks a lot and best regards.
Andy.



AD Administrator Syncfusion Team March 17, 2008 10:59 AM UTC

Hi Andy,

Thank you for your patience.

The issue of 'Exception is thrown when the file is opened with an OS in Italian and Excel 2007' has been confirmed as a defect and a defect report has been created. You can track the status of this defect in the following link:

http://www.syncfusion.com/support/issues/xlsio/Default.aspx?ToDo=view&questId=9147

I will get back to you once this issue has been fixed.

Regards,
Manopriya



AD Administrator Syncfusion Team March 26, 2008 04:37 AM UTC

Hi Andy,

Thank you for your patience.

The issue of ''Exception is thrown when the file is opened with an OS in Italian and Excel 2007' has been verified and fixed. The fix for this defect will be available in our next weekly development build.

I will get back to you once the fix is available in development build.

Regards,
Manopriya




AN Andy March 28, 2008 01:51 PM UTC

Dear Manopriya,
thank you very much for your reply.

As far as I can understand, you have fixed it and it will be available in the next development version (something like 6.2.0.x).
My problem is that I found the bug while I was using the evaluation version with the evaluation key.
Will the same key work also with the development build?
Is there any way I could get a key (in case that evaluation key won't work with the development builds) in order to be able to test your library?

Thanks a lot and Regards,
Andy.



AD Administrator Syncfusion Team March 31, 2008 04:05 AM UTC

Hi Andy,

Thanks for the update.

Could you please email regarding this to our sales team.
salessupport@syncfusion.com.

Regards,
Bhuvana




SI Sierra March 31, 2008 06:55 PM UTC

Hi Andy,

You can insert the 6.2.0.x trial key @362e322e30TejKOaB/BYh1Z9ZLzXmtVsrUyPVq7iLuZyQFu8qjaEs= to evaluate that development build for two weeks.

If you run across any issues with that key, please email salessupport@syncfusion.com.

Best,
Sierra

>Dear Manopriya,
thank you very much for your reply.

As far as I can understand, you have fixed it and it will be available in the next development version (something like 6.2.0.x).
My problem is that I found the bug while I was using the evaluation version with the evaluation key.
Will the same key work also with the development build?
Is there any way I could get a key (in case that evaluation key won't work with the development builds) in order to be able to test your library?

Thanks a lot and Regards,
Andy.




Loader.
Live Chat Icon For mobile
Up arrow icon