Re: A2K on 2003 Server
- From: BruceS <bruce \at\ springthorpe.org>
- Date: Tue, 21 Nov 2006 21:13:02 -0800
Allen,
Don't know if you're still montioring this one or not.
We installed the Office updates right after you suggested doing so. Have
double-checked the updates for Server2003. All are current. They have been
monitoring while I've been on vacation.
Incidence of problems is reduced, but still there. Now about 1 out of 10
times. We run it three times each night on three different back ends. No
consistency on when it fails, but any subsequent jobs don't run after the
first failure. We check each morning, but kind of defeats purpose of
scheduling at night.
The SA is freaking, saying it's my program. I think it's the server because
it runs perfectly on WinXP Pro. Got to get this resolved, though, so do you
have any more suggestions?
Thanks,
Bruce
"Allen Browne" wrote:
Not sure why the particular combination is causing it to fault, but you.
desperately need to apply some service packs to your Office 2002.
You may also need service packs for JET:
http://support.microsoft.com/kb/239114
Once you have both those sorted out, open the front end (holding down Shift
to bypass any opening form/code/macro), and choose:
Tools | Database Utilities | Compact/Repair
The front end caches info relating to the attached tables. That info will be
wrong after your upgrade. Compacting the front end causes Access to drop
that cached info, and can prevent crashes.
--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"BruceS" <bruce \at\ springthorpe.org> wrote in message
news:5E50A70C-227C-48E5-9FB2-C0B31F548168@xxxxxxxxxxxxxxxx
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
- Follow-Ups:
- Re: A2K on 2003 Server
- From: Allen Browne
- Re: A2K on 2003 Server
- References:
- Re: A2K on 2003 Server
- From: Allen Browne
- Re: A2K on 2003 Server
- Prev by Date: Re: Linking Table in Forms
- Next by Date: Re: If Exists help
- Previous by thread: Re: A2K on 2003 Server
- Next by thread: Re: A2K on 2003 Server
- Index(es):
Relevant Pages
|
|
