Error exporting budget

Business Central/NAV Developers Forum
1

Hi! When exporting a budget to excel I get an error message stating “This message is for C/AL programmers. An exception occurred from an external component. The component did not provide the exception description” This occurs when the progress bar hits about 3 % Can anyone tell me why this happens and, if possible, go one better and tell me how to fix it? If it is any help, i am running Windows 2000 professional and Excel 2000 Thanks in advance! John

2

Hi, If your Account Schedule code is having special characters like /*% etc. then you will get such error. Kindly check your Accout schedule code.

3

Thanks for your help Rajesh Just to clear your comments up a bit, did you mean if those symbols exist in the exported data or in the actual object? The error is occuring in two different systems with standard objects. I hope this information is of some help. Thanks again[:)] John

4

Are you Windows 2000 and Excel 2000 fully service packed?!?! [:D] This is the typical Microsoft response - I know, but a good place to start. [:)]

5

quote:

Originally posted by John Small
Hi! “This message is for C/AL programmers. An exception occurred from an external component. The component did not provide the exception description”

I’ve worked with export to Excel a lot. This error runs when computer is angry [:D] But in many cases it runs when wrong parameters are given to Excel Automation. Can you use debugger and tell me where does it crash?

6

Thanks for the suggestions! I will try them and let you know how i get on. Watch this space…

7

Hi John, I know that this is an old topic but I have just hit the same problem as you when ticking the “Include Totalling Formulas” check box. It seems that the problem is due to a bit of (dodgy?) code in the SumIf function in Table 370. If you replace the references in the exit statement from ‘;’ to ‘,’ then all should be fine. Regards Simon

8

Hi Simon, Thanks for the information. We managed to fix the problem a while back. What had happened to us was that the upgrade toolkit had gone a bit crazy and replaced some of the objects code with text constants. This meant that the incorrect parameters were being passed to the excel automation as Arthur had pointed out. With a bit of fiddling it was a fairly easy fix thankfully. We will have a look at the area you mention and make sure that this won’t affect us in future though! Thanks for the help!! Regards John