Explanation of error opcode=40 when Interbase terminates abn |
|
Hi all,
We are using Interbase XE3 version 810 for several customers. Lately we are getting errors in Interbase which causes Interbase to restart.
Interbase log shows some errors with different numbers :
opcode=40, opcode=68, opcode=67, opcode=62, opcode=29
process_packet() servicing opcode=40
Access violation.
The code attempted to access a virtual
address without privilege to do so.
This exception will cause the InterBase server
to terminate abnormally.
An application connecting to the databases is probably the cause of these errors.
We have no clue where to look for the problem.
Is there a list of opcodes where the different numbers are explained.
Thanks,
Arnold Schepers (TANS BV)
|
Re: Explanation of error opcode=40 when Interbase terminates |
|
The opcode report here is reporting that InterBase got data it did not
expect. There is no list of opcodes, but if there was, all it would tell
you is invalid data was received.
The only way I have seen this type of error is with port scanning
software attempting to find a software vulnerability.
Where I would start is try to find out what people were doing when the
failure occurs.
Tans Ontwikkelaar wrote:
> Hi all,
>
> We are using Interbase XE3 version 810 for several customers. Lately we are getting errors in Interbase which causes Interbase to restart.
> Interbase log shows some errors with different numbers :
> opcode=40, opcode=68, opcode=67, opcode=62, opcode=29
>
> process_packet() servicing opcode=40
> Access violation.
> The code attempted to access a virtual
> address without privilege to do so.
> This exception will cause the InterBase server
> to terminate abnormally.
>
> An application connecting to the databases is probably the cause of these errors.
> We have no clue where to look for the problem.
>
> Is there a list of opcodes where the different numbers are explained.
>
> Thanks,
>
> Arnold Schepers (TANS BV)
>
|