Access Error

[Lewis Cooper]

We have a complex Access application with a SQL rear-end, we having been
running it for almost 10 years now, usually about 25-30 users. Starting about
a month ago we began getting fatal errors ie. the big blow out, the user is
kicked clear out of the app to the desktop. The error is not easy to
replicate ie. sometimes goes for hours no errors. We usually can solve any
code related error in munutes but this oine has us stumped. The system
application event log shows this error:

Faulting application msaccess.exe, version 11.0.6566.0, stamp 42cdb33e,
faulting module msjet40.dll, version 4.0.9505.0, stamp 45cd064f, debug? 0,
fault address 0x000282f8.

Any advice would be greatly appreciated.

 

[Dorian]

If this affects only one user and other users continue to operate ok, I'd
suspect the user is out of memory on their PC. How much ram do they have and
how many other applications are open?
Access applications grow in memory requirements over the years if data is
never deleted. When was the database last compacted?
-- Dorian
"Give someone a fish and they eat for a day; teach someone to fish and they
eat for a lifetime".

 

[Lewis Cooper]

Dorian

This issue is across the board, the application is being deployed using
Terminal Server and RDP, the server has 14 Gig of RAM. Do you know how to
delve into the specifc ACcess error?

Thanks

Lewis

 

[Jerry Whittle]

That's where I would start: one user or all users? If one user, there might
be a problem with the PC, network connection, or the office install.

If all users, time to ask what has changed? Any other programs having
problems? Any recent hardware or software changes? Patches applied lately?

 

[Lewis Cooper]

Jerry

At first we always think code change, but we rolled back onto several older
versions and still had issue. Then we looked at Office and MS Updates, they
have been in place for quite a while before issue appeared. Very frustrating,
the error has been oin pointed to a couple specific events but the code in
these areas has not changed in a very long time. How do I go about getting
help with the error fromn the app event log or is it just a vauge catch all
error? I am to the point of getting expert level help at any cost. Keep in
mind this error cannot be replicated and is intermitant ie the save and order
without issue and an hour or 8 hoiurs later they save an order and it blows
them out to the desktop. Is tehre a pay for support option that we might use?
I was alos wondering about a corrupt dll issue, never had one before but
wouldn't it happen for all users all the time if it wa a corrupt dll?

Thanks

Lewis

 

[Albert D. Kallal]

First of all, leaving out the detail that your running terminal server is
rather LARGE detail to leave out.

The #1 thing on the list to check is does each user get their own copy of
the front end?

This includes terminal server users where thus EACH LOGGED ON USER MUST get
their own copy of the front end. That means a separate copy of the front end
needs to be launched by EACH user on the terminal server. You do NOT want to
allow more then one user to launch the same copy of the front end at the
same time.

So, the above is if the first issue I would clear up here. If you allowing
more then one user to log on using the same remote name, then you breaking
the above suggestion.

 

[Lewis Cooper]

Albert

I was hoping someone could specifically address the error code itself thats
why I did not go into the exact deployment method.

Yes each user has their own copy of the app.

This app has been running without issue for nearly 10 years, the whole time
deployed via RDP. We are current on Service PAcks for both Office and MS. We
checked all our SQL tables using the SQL utility. Like I mentione before we
have never not been able to resolve an issue prior, usually some code issue,
but the nature of this error ie. blows user clear out of app and cannot
replicate makes this an especially tought one, the user only gets the
message, do you wan to send error report to MS.

Sorry for omitting key info.

 

[Albert D. Kallal]

Sorry for omitting key info.

You gave a really good explain as to why you left out TS being used. That
means you thought about this, and made your question around that thinking
here. I have VERY much respect for you in this regards. In other words, even
if I did not agree with your reasoning for leaving out details, you very
much took time ad considering into your question here. So, you are not being
just lazy or not thinking here. And, by the way in fact I agree with your
reasoning here anyway.

However, I am thinking that the JET error might be in fact due to using TS
here.

Since you folks been running this for such a good amount of time, then it
hard to come up with something you are missing, or something special to that
error message. I would ensure that all office sp packs are installed. I
would also ensure that updates to JET are installed also (there is updates
to both). I can't say that I seen a frequent (or even one) post here that
has the same error numbers you show.

I would also consider always using a mde for the front end, they can be more
stable as they don't become un-compiled like a mdb front end, but this
suggestion of mine is a long shot (and, it good possible that you already
using a mde for each front end).

 

[Tony Toews [MVP]]

Faulting application msaccess.exe, version 11.0.6566.0,

That's a bit old. My version of A2003 has version 11.8212.8221 from
Help >> About or 11.0.8212 on the msaccess.exe.

The newer versions are either security patches or hotfixes.

Hmm, here's one that could possibly be relevant.
http://support.microsoft.com/kb/945674/ Are there any bit fields in
the tables?

I came across an interesting website while searching on the version
number. http://www.mskbfiles.com/msaccess.exe.php Regretfully it
doesn't have any such lists of KB articles for msjet40.dll but it
looks like you're fairly up to date on that one.

Tony