Error HRESULT E_FAIL has been returned from a call to a COM component..

Question

0.00/5 (No votes)

See more:

I have a project which will genereate excel sheet with data which we get from data base.

its working fine in test and validation environment. when we push it to production we are getting an exception and stopping all the process. but here we are not getting this problem daily. we will get this exception once in week or twice.

The exception is
17:30:40 PM Error occurred while creating file: D:\FDR\eRPT_Staging\10_03_13\SUB0926201307973\FDR_537819_R5287_ESRD_10_03_13_FINAL.xlsx

17:30:41 PM Stopped eRPT FDR batch after processing 57 transactions. Error message: Error HRESULT E_FAIL has been returned from a call to a COM component..

This exception not throwing immediately after the process started first it will create 10 to 20 spread sheet and then it is throwing this exception.Any one could you please help me how to figure out the problem or let me know what cause the problem

Posted 4-Oct-13 5:55am

sailaja reddy 2

Updated 4-Oct-13 6:51am

v4

Add a Solution

Comments

Richard MacCutchan 4-Oct-13 12:19pm

Well we cannot see your code and we have no idea what component is throwing the error so it's impossible to suggest anything much. You could try adding some more debug code to your application.

KmgKrishnan 5-Oct-13 1:21am

What COM component that you are using? Also, can you place the piece of code that uses it?

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)