B
BruceS
For the super techies...
We just upgraded our NT server to 2003. After the upgrade, we moved an A2K
database that updates records in a back end to the server and set it up in
Scheduler to run with a command parameter. The backend resides on the same
physical computer and drive as the .mdb. The program had been working fine
on a WinXP Pro workstation (also using a command parameter) with local copies
of the backend databases.
Since installing on the new server, about every 4th or 5th time the
application tries to run, it throws the following error:
Application failure msaccess.exe 10.0.2627.1 at offset 0x0000a8f3
When you view the details, you see the following:
Exception information:
Code: 0x00000b20
Flags: 0x00000000
Record: 0x00000000c0000005
Address: 0x00000000
On most occasions, but not all, this results in a lock file for the front end.
To try to find out what was going on, we put extensive error trapping and
logging into the front end .mdb. Nothing shows up, not even in the Form_Open
of the form that is automatically opened when the app starts. We've run the
program on the XP Pro development machine at least one hundred times trying
to get it to fail. Nada, nothing. It works perfectly.
The problem appears to be compatibility issues with 2003 Server. Has anyone
heard of anything like this going on?
Any input/help deeply appreciated.
Thanks,
Bruce
We just upgraded our NT server to 2003. After the upgrade, we moved an A2K
database that updates records in a back end to the server and set it up in
Scheduler to run with a command parameter. The backend resides on the same
physical computer and drive as the .mdb. The program had been working fine
on a WinXP Pro workstation (also using a command parameter) with local copies
of the backend databases.
Since installing on the new server, about every 4th or 5th time the
application tries to run, it throws the following error:
Application failure msaccess.exe 10.0.2627.1 at offset 0x0000a8f3
When you view the details, you see the following:
Exception information:
Code: 0x00000b20
Flags: 0x00000000
Record: 0x00000000c0000005
Address: 0x00000000
On most occasions, but not all, this results in a lock file for the front end.
To try to find out what was going on, we put extensive error trapping and
logging into the front end .mdb. Nothing shows up, not even in the Form_Open
of the form that is automatically opened when the app starts. We've run the
program on the XP Pro development machine at least one hundred times trying
to get it to fail. Nada, nothing. It works perfectly.
The problem appears to be compatibility issues with 2003 Server. Has anyone
heard of anything like this going on?
Any input/help deeply appreciated.
Thanks,
Bruce