Exceptions caught when setting C1PrintPreviewControl.Document

Exceptions caught when setting C1PrintPreviewControl.Document

Posted by: garret.richardson on 25 April 2018, 6:24 am EST

• 

  garret.richardson

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 25 April 2018, 6:24 am EST

  I’m getting some log notifications of exceptions caught when I run the print preview sample you guys have provided here:
  
  https://www.grapecity.com/en/blogs/combining-the-usage-of-c1report-and-c1printdocument

  Specifically, when the form runs and loads the print preview, I get the following:

  Exception thrown: '#cje.#bje.#dje' in C1.C1Report.4.dll
  Exception thrown: 'System.Reflection.TargetInvocationException' in mscorlib.dll
  Exception thrown: '#cje.#bje.#dje' in C1.C1Report.4.dll
  Exception thrown: 'System.Reflection.TargetInvocationException' in mscorlib.dll
  

  This occurs on line 61 where the PrintPreviewControl.Document setter is called:

  
  C1PrintPreviewControl1.Document = C1PrintDocument1
  
  

  These exceptions don’t cause the application to crash, so I’m assuming they’re being handled within C1. However, I’m getting similar exceptions caught and handled in my own codebase when I set the same property. The exception i get looks like this, although I’m assuming it might be for similar reasons:

  
  Exception thrown: '#Wvd.#Mje' in C1.C1Report.4.dll
  
  

  Would it be possible to get some feedback on why these types of exceptions occur, so I can see if there’s anything that needs to be done differently?

  We’re doing a Proof-of-concept with a new version of .NET and C1Report, so I need to chase this problem down to see if it’ll surface as an issue later.

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 25 April 2018, 4:22 pm EST - Updated 3 October 2022, 11:16 pm EST

  Hello,

  We are aware of the exception “‘#Wvd.#Mje’ in C1.C1Report.4.dll” and the issue is already with the concerned team (Internal Tracking ID: 304981). We have also updated it with the exception you observe while running the C1Report in C1PrintDocument sample. However, please note that we could not observe the exception with the particular sample.

  We would need the following information from you to investigate further:

  1. Does your sample which throws the exception “‘#Wvd.#Mje’ in C1.C1Report.4.dll”, works in the same way on a different machine as well?
  2. Also, please share the control version you are using at your end along with the system environment details.
  3. Go to Tools->Options. Select Debugging on the left and then General (under Debugging). Enable ‘Enable Just My Code’ by checking it (refer the attached screenshot). Inform if you still observe the error.

  Thanks,
  
  Esha
  
  

  

  882×553 25.7 KB

• 

  garret.richardson

  • Post Options:
  • Link
    Copy

  Posted 27 April 2018, 5:31 am EST

  1. Yes, I get the same exception printed if I build and run on a different machine.
  2. We’re on version 4.0.20173.282. We’re targeting .NET 4.6.2, running on Win 7 64 bit. The application is 32-bit.
  3. The exceptions don’t log to the console with “Just My Code” enabled, as expected.
• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 29 April 2018, 4:50 pm EST

  Hello,

  Thank you for the information. We are sharing the same with the team and will get back to you once we hear from them.

  Best Regards,
  
  Esha

• 

  garret.richardson

  • Post Options:
  • Link
    Copy

  Posted 30 April 2018, 5:28 am EST

  Thanks for your help Esha.

  Can you give me any of this additional information? It will help us with our Proof-of-Concept:

  1. What are the effects of this exception?
  2. Is there a version of Componentone that does not have this issue?
  3. Is the exception logged out anywhere (in temp or windows event viewer, for example)?

  I’m testing to see if I can find answers on my own, but if you have information you can share it would be appreciated.

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 30 April 2018, 4:22 pm EST

  Hello,

  As of now, the exception is observed in all the recent versions.
  
  However, we are discussing with the team, to work over and answer your questions, on priority.

  We’ll get back to you as soon as it is done.

  Thanks,
  
  Esha

• 

  esha.dhir

  

  • Post Options:
  • Link
    Copy

  Posted 2 May 2018, 5:49 pm EST

  Hello,

  As per the developers, the exception is internally thrown. An internally thrown and caught exception is not a bug, In some cases, it cannot be avoided. However, there are no effects of the exception on the final result and hence, it does not require a fix.

  Best regards,
  
  Esha