> > Working with the integration of the AX with the DLL to generate CobreBem > billet from the online diary, an internal error is usually displayed at each > slip printed, but the process continues normally. > > Well, although in my case the problem was the architecture that was > implemented in the integration, I found that this error occurs a lot when we > work in the handling of tables and records to generate XML (xml method () of > the table) that have fields of type MEMO, is normally used for fields that > no longer exist in newer versions of the application. > > To check tables that have this problem and also to replicate the error, > follows a simple job to understand what I mean: > view source > print? > 01 static void exibirErro25 (Args args) > 02 > 03 ( > 04 > 05 EmplTable emplTable / / Table of officials > 06 > 07 select firstOnly emplTable / / Getting the first. record of the > Employees table > 08 > 2009 info (emplTable.xml ()); > 10 > 11) > > The job above does nothing more than display the error mentioned in this > article. > > To solve the problem, override the method rss () and treat the fields with > the code below: > view source > print? > 01 / / Create data dictionary table officials > 02 > 03 SysDictTable sysDictTable = new SisDictTable (tablenum (EmplTable)); > 04 > 05 SysDictField sysDictField; > 06 > 07 Types dataType; > 08 > 09 int index, / / Position array > 10 > / 11 / ... Following the code to generate xml > 12 > 13 for (index = 1; index <= sysDictTable.fieldCnt (); index) > 14 > 15 ( > 16 > 17 dictField = new SysDictField (TableID, dictTable.fieldCnt2Id (index)); > 18 > 19 dictField.baseType dataType = (); > 20 > 21 if (dataType == Types:: varString) / / If the field is MEMO > 22 > 23 ( > 24 > 25 continue; / / Ignore the field to generate the xml. > 26 > 27) > 28 > 29 / / ... Continued generation xml > 30 > 31st) >
On Fri, Aug 13, 2010 at 3:39 AM, James Flavell <djf1...@gmail.com> wrote: > > > Thanks Edvandro > > Sorry any chance can get in English somehow? > > Thanks > James > > > > > > *From:* Axapta-Knowledge-Village@yahoogroups.com [mailto: > axapta-knowledge-vill...@yahoogroups.com] *On Behalf Of *Edvandro Santos > *Sent:* 13 August 2010 04:57 > *To:* Axapta-Knowledge-Village@yahoogroups.com > *Subject:* Re: [Axapta-Knowledge-Village] AX4.0 Internal error number 25 > in script > > > > > > Hi James, > > Herre is the solution: > http://www.axfordummies.com/2009/03/x-erro-interno-script-numero-25/ > > Regards, > > On Sun, Aug 8, 2010 at 3:05 AM, James Flavell <djf1...@gmail.com> wrote: > > > > Dear all does anyone have any ideas for this error happening in batch > processing: > > > > > > > > There was some hotfix for non SP for this error but we are running Ax4.0 > SP2 so should be included. > > > > We have basically the following batch jobs in 2 companies: > > Alerts – change abd due date based every 10 mins > > OLAP – > > Custom import/export of data – > > > > Looking at the entries in the batch list the alerts ran at 21:10:29 and so > would only be running at 21:20 the next time. All the other tasks also were > not scheduled to run at the time it happened which was 21:10:48 > > > > I saw there was another hotfix for SP2 regarding *sending email* from > AR/AP module can get this error. The KB said it applied to the .NET > connector but we are not using that (unless it is by default used when > sending email?). But was wondering since alert is no doubt setup to send > email notification whether there might be something related to the area of > email sending? > > > > Has anyone else faced this error message as all batch jobs stop and the > client crashes when we go to the batch client and click OK? > > > > As always a big thanks for taking the time to read this > > James > > > > > > > -- > Santos, Edvandro > Microsoft Dynamics Development Consultant > fale...@edvandro.com > http://www.edvandro.com > http://www.axfordummies.com > > > -- Santos, Edvandro Microsoft Dynamics Development Consultant fale...@edvandro.com http://www.edvandro.com http://www.axfordummies.com
<<image002.png>>
<<image001.png>>
