Access 97 closes with no error on 2003 terminal servies server

G

Guest

I have a brand new install of terminal server 2003, and access 97 with up to
date service packs. Anytime I go to click a button on a form, or create a
button on a form, Access pauses and then closes with no errors. The event
viewer shows the following error:

Faulting application msaccess.exe, version 8.0.0.5903, faulting module
unknown, version 0.0.0.0, fault address 0x00202878.

Any ideas on what would be causing this?
 
A

Arvin Meyer [MVP]

I've run Access 97 on terminal servers for years without problems, although
I must admit that I haven't run Access 97 on TS 2003 yet.

Most Terminal Server problems come from the not having a split database with
users not having their own copy of the front-end running separately from all
other users. I do this with separate folders. Each user can only access his
or her own folder after logging in.
 
P

Pieter Wijnen

I have (even RunTime)
Runtime Tends to crash first time you open access via a shortcut.
Probably down to MsAccess.srg
I have been planning to investigate , and will post when I have done so
temporary workaround is to have a shortcut with /Compact /Repair & run that
first

HtH

Pieter
 
G

Guest

That isn't the issue of multi users...its all users, and even the
administrator local account, where teh problem happens.

I can create a brand new database, try to add a button on a form, and it
closes without an error...but event viewer shows the error I have listed. I
do this while logged in as the admin on the local machine, not even through a
TS session and one that no one would even have access to.
 
G

Guest

compact / repair doesn't solve the issue either.

Each time it is closed by itself, the lock file is still in place, so I know
it isn't closing correctly.
 
A

Arvin Meyer [MVP]

Also, msaccess.srg should only run once unless there are later versions of
Access on the same machine. If that is the case, locate that file and rename
it to msaccess.srg.old and create an empty text file named msaccess.srg. The
srg files in Office 97 try to silently register their executables and file
types. By creating blank ones, they are unable to do so and the later
version files take precedence.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"Pieter Wijnen"
 
G

Guest

I have set permissions and that didnt' solve the problem. I have renamed
msaccess.srg and created a new blank text file called msaccess.srg and placed
it in the same directory, still have the same problem.

I like the idea of missing references as I read that 2003 doesn't have the
same references as, say, xp and causes 97 to fail. Any ideas 0on what
references I would need?

I currently have Visual Basic for Applications, Microsoft Access 8.0 object
library, and Microsoft DAO 3.51 Object library.
 
D

David W. Fenton

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=
I currently have Visual Basic for Applications, Microsoft Access
8.0 object library, and Microsoft DAO 3.51 Object library.
Click to expand...

And none are marked missing?

Well, have you decompiled and recompiled the MDB on the Terminal
Server? I have frequently had A97 databases need to be recompiled
for the target machine, even when they had (so far as I could tell)
all the same versions of all the Access and VBA files.
 
G

Guest

None are marked missing. I do not see any reason to decompke and recompile
as this happens on a brand new database, and it fails BEFORE the button is
even entered. I start the button wizard for a form and it fails. I click on
an existing button on a form and it fails. a brand new database not ever
touched by anyone and it fails.
 
A

Arvin Meyer [MVP]

Make sure you have BOTH Service Pack 1 and 2 installed. If that doesn't fix
it, decompile and recompile anyway, whether you think it needs it or not.:

http://www.mvps.org/access/bugs/bugs0008.htm

If you are still getting page fault crashes like the one you mentioned in
your previous answer to me, you'll need to call Microsoft, or the mfg of the
machine. MSFT doesn't really support Office 97 any more, so the machine
mfg., might be the only recourse. I've never seen an Access app that didn't
respond to decompiling and recompiling or using the more extreme
Application.SaveAsText/LoadFromText to fix a corruption.
 
G

Guest

When i try to install sp1, I get an error stating the patch can not be
updated at this time...please close all applications.

I will give the server a reboot at end of business today and re-try the
install. I have installed sp2, but not sp1.
 
G

Guest

Not sure if it matters or not, but the terminal service cpu is on a vmware
server, so the install is an instance.
 
G

Guest

I have done some testing...it appears all of our 2003 servers have the same
problem with access 97. One server gave this error:

The instruction at "0x00194b78" referenced memory at "0x00194b78". The
memory could not be "written".

Clik ok to terminate the program.
Click cancel to debug the program.

Hitting cancel simply closes it.
 
G

Guest

I have done another fresh install, installed service pack 1, tested, didn't
work. I then installed service pack 2, didn't work.

I can't even create buttons on a form without it closing.
 
A

Arvin Meyer [MVP]

G

Guest

We have decided to do remote pc's to use access 97 on windows xp. Microsoft
does'nt support 97 anymore, so this is pretty much a bust...access 97 simply
doesn't work with server 2003.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

dao360.dll Crash 3
Database Access Crashes on Windows 2003 Terminal Server 3
Access crashes after second print and event ID 1000 logged. 3
Access 2002 crashes when preview report 7
Opening Access Forms causes crash. 10
Access97 on WinXP: Slow, error-prone, and ??? 8
Shared Access 2003 Database Crashing 0
access 2003 sp3 1

Top