Link to home
Start Free TrialLog in
Avatar of jacksonm1234
jacksonm1234Flag for United States of America

asked on

URGENT -- Vb.Net Excel COM Problem!

I desperately need your help experts!

I have a program written that opens and manipulates Excel files. I have been writing it for a couple weeks, and up until now, I have been able to work with Excel files with no issues whatsoever.  Last night, I worked on the program from home via a terminal client, again with no issues (i have done this many times before).  This morning, I log in like usual, but now I get the following error:

"Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE))."

The error comes up on this line:
Dim oApp As New Excel.Application

Here's the most interesting part -- this is NOT, I repeat, NOT an ASP.Net app.  This is a basic Windows Application, so I dont know why the error is talking about server execution.  I've tried rebooting and creating a new project, but nothing has worked so far.

I know there is a process out there to go into DCOMCNFG, but another issue is that I do not have admin rights to my computer.

I dont know why this has happened so suddenly! It was working great last night, but not this morning.

Please HELP!
ASKER CERTIFIED SOLUTION
Avatar of graye
graye
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I agree with graye, find out what happened last night from the IT dept.
Avatar of jacksonm1234

ASKER

Thank you for the help!
Because of youre guys' response, I decided to dig a little deeper with my IT department. It turns out I had two different versions of Office installed on my machine (XP and 2007), and they were causing problems with each other.  An IT guy uninstalled XP and deleted my Office registry information, and now everything appears to be working fine again!  Thanks for your help!
Although I did not get a solution from them, the commenters helped me get there.