Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SEHException #164

Open
SSDiver2112 opened this issue Feb 14, 2019 · 8 comments
Open

SEHException #164

SSDiver2112 opened this issue Feb 14, 2019 · 8 comments
Labels
Unconfirmed

Comments

@SSDiver2112
Copy link

SSDiver2112 commented Feb 14, 2019 •
edited by mrworkman
Loading

I am getting this error System.Runtime.InteropServices.SEHException: 'External component has thrown an exception.' When accessing xlsx files. No changes to the code, it just stopped working.

var excel = new ExcelQueryFactory(FullFileName);
List<string> wsNames = excel.GetWorksheetNames().ToList();

This works for xls files but not xlsx files.

Thank You,
Scott
@mrworkman
Copy link
Collaborator

mrworkman commented Feb 14, 2019 •
edited
Loading

@SSDiver2112, can you tell me the following:

  • Which version of LinqToExcel?
  • Which version of the ACE driver are you using (if applicable), including whether it is 32 or 64 bit.
  • Please include the full stack-trace, so I can see where the error occurred.
  • Also, attach an xlsx file that you are seeing this problem with (I need to rule it out as a cause). You can create a new xlsx file, as long as it still reproduces the problem.

Thanks

@mrworkman
Copy link
Collaborator

Duplicates #163.

@mrworkman mrworkman mentioned this issue Feb 14, 2019
Closed
@SSDiver2112
Copy link
Author

SSDiver2112 commented Feb 19, 2019 via email

@mrworkman
Copy link
Collaborator

@SSDiver2112, github is lame and doesn't allow attachments on issues, apparently. Can you send a link to the file on OneDrive/DropBox/Google Drive ?

@SSDiver2112
Copy link
Author

SSDiver2112 commented Feb 22, 2019 via email

@mrworkman
Copy link
Collaborator

Thanks. I should be able to check it out this weekend, but I notice you're using a v1 version of LinqToExcel. There's a v2 in pre-release (on nuget) that you could try in the meantime.

@SSDiver2112
Copy link
Author

SSDiver2112 commented Mar 12, 2019 via email

@mrworkman
Copy link
Collaborator

Hi @SSDiver2112,

Unfortunately, I'm not able to reproduce the problem. Looking up OleDb SEHException 0x80004005, I see a number of possible causes most notably:

  • Platform bitness (x64 project & x32 ACE, or vice versa). I doubt this is your problem, usually you'd get an ACE exception instead.
  • Some kind of endpoint protection software. Are you experiencing this issue on a work PC?

Aside from that, it's difficult to tell with the error that was thrown. 0x80004005 is just E_FAIL, which could mean anything. But such a generic error could indicate that something else is killing your DB connection (like endpoint protection / av) -- this would jive with the fact that you didn't make any code changes that could have lead to the failure.

I assume you've already done the re-install of the ACE driver, and other basic troubleshooting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Unconfirmed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mrworkman @SSDiver2112