Internal error 33 in Module 35

gregorybrunner

Hi Folks

We have installed NAS on our Navision Server and now there is the
following error message in the event log.

Internal error 33 in Module 35

What does it mean and how can we solve this problem ???

Regards Greg

eromein

sry mate,

On the partner guide there is a post with explanation about this error, but it's in Italian.

WHY ARE NON ENGLISH POSTS STILL BEING ANSWERED???

Maybe there is an Italian somewhere that can translate this for you!

Error 33 modulo 35-
Problem Summary: Reabrierta 26.08: Hola Nacho he podido investigar más a fondo y he podido comprobar que si el cliente tiene instalado office 2000 o XP el proceso da error, en cambio sobre office 97 el proceso no da ningun error y se ejecuta perfectamente.

Un saludo.
Es un poco urgente ya que el cliente ha actualizado todos los equipos a 2000 y no puede ejecutar proceso que es bastante importante.

Gracias por adelantado.



Os remito un error que se produce cuando ejecuto un proceso que para cada fichero que trata abre un fichero excel introduce la informacion y después lo cierra y así con todos los registros. El cliente me comunicó que le daba este error cuando la seleccion de registros es de más de un registro. Haciendo pruebas el problema es que el error no lo da siempre, es decir es aleatorio, y he revisado el proceso y creo que no hay ningun error.

¿Porque se produce este error?.

Gracias por adelantado.-







Gabriel...

El error del que nos informas se debe a una incompatibilidad de tipos de datos al integrar Attain con otros software a través de variables de tipo OCX y/o Automation.

Desde DK dicen que es dificil saber a ciencia cierta cual es la causa, pero resaltan dos posibilidades:

Que un tipo de datos no coincida en la llamada a un método a través de este tipo de variables, bien sea en un parametro pasado o en el valor de retorno devuelto. Comprueba el desarrollo, pero yo descartaría esta opción porque en tu nota intuyo que este desarrollo ha estado funcionando ¿verdad? En caso de que no haya funcionado o que se hallan hecho modificaciones en él comprueba este extremo.
Que la versión del OCX o Automation que se esté utilizando no coincida con la versión del software a la que accede. Es decir si estás usando MS Excel 2000 (Excel 9) debería usar la versión 1.3 de Automation. Este error puede haber sido motivado por una actualización en la versión de Excel en el servidor y no en el cliente. Y fijate que te digo versión y esto incluye el que varie el idioma de una misma versión. Este tipo de enlaces es estremadamente sensible y a veces basta con la modificación en la instalacción de Office para que empieze a fallar. Preguntando a los especialista en integración, me dicen que esta causa pordría producir fallos alatorios dependiendo que se haga en la hoja Excel en uno y otro caso.

Si puedes descartar estas dos causas y sigue sin funcionar, reabre el caso y los escalo, pero antes vamos a acotar el problema en estas dos direcciones a ver si hay suerte ¿vale?

Un saludo.

Nacho P.
______________________________

26Ago02 - IP

Gabriel...

Según lo que me cuentas, parece claro que estamos en la segunda de las dos posibilidades que te daba. Para que la integración funcione debes asegurarte la concordancia de la versión del OCX o Automation y la de Excell. Manteniendo distinta versiones de Excell en los clientes no vas a poder obtener esta concordancia en el ciento por cien de los clientes.

Un saludo.

Nacho P.

sabato

Hello,

well first of all it's spanish not italian.
And i just tried to translate it with google.com. I think its not to bad and i hope you can understand it.

_______________________________________________
Error 33 I modulate 35- Problem Summary: Reabrierta 26.08:

Hello Nacho
I have been able to investigate more thoroughly and I have been able to verify that if the client has installed office 2000 or XP the process gives error, however on office 97 the process does not give ningun error and it is executed perfectly. A greeting. He is a little urgent since the client has updated all the equipment to 2000 and she cannot execute process that is quite important.
Thanks in advance.

______________________________

I send an error to you that takes place when I execute a process that stops each file that treats opens to a file excel introduces the information and later it closes it and thus with all the registries. The client communicated to me that she gave east error him when the selection of registries is of more of a registry. Testing the problem is that the error always does not give it, is to say is random, and has reviewed the process and believes that error is no ningun. Because east error takes place.
-Thanks in advance. -

______________________________

Gabriel...
The error into which you inform to us must to a mutual incompatibility of data types when integrating Attain with other software through variables of type OCX and/or Automation. From DK they say that he is dificil to know for a fact as is the cause, but emphasize two possibilities: That a data type does not agree in the call to a method through this type of variables, or is in parametro happened or the value of given back return. He verifies the development, but I would discard this option because in your note I intuit that this development has been working truth? In case that it has not worked or that is fact modifications in him verifies east end. That the version of the OCX or Automation that is being used does not agree with the version of the software to which accedes. It is to say if you are using MS Excel 2000 (Excel 9) would have to use version 1,3 of Automation. This error can be motivated by an update in the version of Excel in the servant and not in the client. And fijate that I say to you version and this includes the one that varie the language of a same version. This type of connections is estremadamente sensible and sometimes coarse with the modification in the instalacción of Office so that empieze to fail. Asking the specialist in integration, they say that to this cause pordría to me to produce alatorios failures depending that become in the Excel leaf in both case. If you can discard these two causes and follows without working, it reopens the case and them burglary, but before we are going to limit the problem in these two-way traffic to see if there is luck is worth?

A greeting. Nacho P.


______________________________
- IP Gabriel...
According to which you tell me, it seems clear that we are in second of the two possibilities that he gave you. So that integration works you must asegurarte the agreement of the version of the OCX or Automation and the one of Excell. Maintaining versions from Excell in the clients different you are not going to be able to obtain this agreement in the one hundred percent of the clients. A greeting. Nacho P.


Well I hope this helps, I tried my best or should I say Google tried his best


Greetings
sabato

eromein

Spanish, Italian, French... All the same!


Just joking guys, just joking.... don't go posting angry replays now!

sabato

Yeah almost, but try to tell this google

Janire

I solved it doing CLEAR of the Application Variable before and after use it.