Access 97 closes with no error on 2003 terminal servies server

[Pieter Wijnen]

It does, though.

Btw I've always manually updated the dll's etc associated with a runtime
install to ensure they're up to date
the microsoft solution of having them in a 'developer folder' is simply
ridicolous
I only use the microsoft Distribution tool once (to get everything I need) &
thereafter I manually (well, not *really*) change the packages for a
spesific solution

Pieter

 

[Guest]

Well, we can't get it to work and i've spent about a week goofing with it,
and googling, and even hiring a consluting firm and no luck.

Basically, on our systems, a 2003 server with a fresh install of access 97
doesn't work completely...you can do everything we want to do besides use
buttons on forms, and that is necessary for our environment. If you have any
more ideas on how to manually do the dll files or whatever, I'd be happy to
try them.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

I have installed sp2, but not sp1.

Um, no, you haven't. If you can install SP2, you had SP1 before.

Or your installation disks were SP2 in the first place.

Have you installed the last Jet 3.5 service pack? This machine I'm
working on has the last Jet 3.5 SP that I've ever used installed on
it and the version of msjet35.dll in the Windows System32 folder is
3.51.3328.0. I'm not certain if that's the last version of that DLL
that ever existed, but I do know it's a stable version when used in
conjunction with A97 SP2.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

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

What's the underlying OS that VMWare is running on top of? Windows?
Or Linux? If it's Linux, well, all bets are off, as I can't say how
a Terminal Server will interact with the file system underlying the
virtual machine it's running in.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

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.

Yes, it does. But you have a faulty base installation of A97 which
is preventing you from patching it to the last stable version. This
is not so much A97's fault as it is the fault of MS's weirdly
bizarre registry machinations.

Arvin is right that you should try the registry cleaner. If you
can't find Eraser97.exe, I've got a copy I can put up on my website
for you to try.

I've run A97 on Terminal Servers (2000 and 2003) without any
problems.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

Well, we can't get it to work and i've spent about a week goofing
with it, and googling, and even hiring a consluting firm and no
luck.

Well, next time try hiring a *consulting* firm, and it may be more
successful (likely won't be as "interesting", though .

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

Basically, on our systems, a 2003 server with a fresh install of
access 97 doesn't work completely...you can do everything we want
to do besides use buttons on forms, and that is necessary for our
environment. If you have any more ideas on how to manually do the
dll files or whatever, I'd be happy to try them.

What is your base A97 installation coming from? A standalone A97
install disk? An Office Pro disk? I have found that I sometimes have
installations of A97 that can't be patched to SP1 or SP2, and it
usually is an installation that was created from Small Business
Edition + standalone A97. The solution has always been to remove all
of them and re-install Office Pro, which then works.

Of course, I haven't had to do that in ages, as I've got Office Pro
97 SR2 installation disks.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

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.

They don't have the problem with A97, but with the release version
of A97 (SR0). It exhibited exactly this kind of problem (was that
the VBA332 issue, or was that in the horrid, dreaded A95?). SR1 and
SR2 fixed all of these issues, and the SR2 version of A97 with the
last Jet 3.5 service pack is very robust and stable.

But you apparently are unable to patch A97 beyond the release
version, from what you've said, so that's the problem.

 

[Guest]

The application doesn't work on any of our 2003 machines, so I have to assume
thei installation is bad on all of them based on your information. I do not
have any registry cleaner

I have office 97 pro for my install.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

The application doesn't work on any of our 2003 machines, so I
have to assume thei installation is bad on all of them based on
your information. I do not have any registry cleaner

I have office 97 pro for my install.

What service release? If the CD doesn't say, then it's SR0.
Otherwise, it will say SR1 or SR2. If you can't install the SR1 or
SR2 patches, then I don't know what the problem is.

The registry cleaner for Office 97 is a program they created for the
purpose of clearing out all the crud put in the registry by an
Office installation. It's called Eraser97. It used to be
downloadable from the MS website.

 

[Arvin Meyer [MVP]]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=
news:[email protected]:

The registry cleaner for Office 97 is a program they created for the
purpose of clearing out all the crud put in the registry by an
Office installation. It's called Eraser97. It used to be
downloadable from the MS website.

Eraser should be on the Office 97 CD. There's another version on the Office
2000 CD that will also work. I've used it to clean an Access 97 registry. On
the Office 2000 CD, I believe it's called something like: ofcln.exe and it's
in the CD root directory.

One cannot install Access SP2 unless SP1 is installed , unless the CD is
already preloaded with both of the SPs. There are a few serious bugs in
Access 97 which require that both SPs be installed.

 

[Guest]

I have sr0. I install access, then sr1, then sr2 with no problems. I
downloaded the eraser 97 and it says it isn't supported by my version of
windows.

 

[Pieter Wijnen]

Believe it or not but it's related to the Tahoma Font
Rename/Delete The Font prior to installing Access '97

HtH

Pieter

see http://support.microsoft.com/kb/241141

 

[Pieter Wijnen]

That is the Hatten.ttf, not tahoma
Pieter

"Pieter Wijnen"

 

[Guest]

I got the install to work after an uninstall by renaming the font; however,
still have the problem and teh reglceaner won't run on 2003 fo rme.

 

[David W. Fenton]

Eraser should be on the Office 97 CD.

Depends on the version of the CD -- it didn't exist at the time
Office 97 was released.

There's another version on the Office
2000 CD that will also work. I've used it to clean an Access 97
registry. On the Office 2000 CD, I believe it's called something
like: ofcln.exe and it's in the CD root directory.

One cannot install Access SP2 unless SP1 is installed , unless the
CD is already preloaded with both of the SPs. There are a few
serious bugs in Access 97 which require that both SPs be
installed.

I carry the patches with me at all times, and have them on the hard
drive of every standalone machine I install O97 on (and every server
on every LAN where O97 is running). I install from SR0 all the time
and apply the service releases in turn, then run the last Jet 3.5
service pack.

 

[David W. Fenton]

"Pieter Wijnen"
<it.isi.llegal.to.send.unsollicited.mail.wijnen.nospam.please@online.
replace.with.norway> wrote in

Believe it or not but it's related to the Tahoma Font
Rename/Delete The Font prior to installing Access '97

No, it has *nothing* to do with fonts. But renaming or deleting one
of the fonts installed with O97 (usually the recommendation is to
renamen Hatten.ttf) triggers the installer to refresh more than just
the missing font, and fixes the license problem.

 

[David W. Fenton]

=?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=

I got the install to work after an uninstall by renaming the font;
however, still have the problem and teh reglceaner won't run on
2003 fo rme.

What is that program named, and what is its version? I have
Eraser97, which is version ... oops, it's not on this machine, and
the other machine takes a gazillion years to boot. If you want to
know the version/date, I can get back to you.

 

[Guest]

It doesn't say the version...but I downloaded it from microsoft and its
called Eraser97.

 

[markosj]

To solve this issue perform the following steps.


1. Right click "My Computer" and click properties

2. Click the "Advanced" tab

3. Click the "Performance" settings button

4. Click the "Data Execution Prevention" Tab

5. Click the lower most radial button "Turn on DEP for all programs and services except those I select."

6. Check the box below that says "Microsoft Access." If it is not listed then add it.

This should solve your issue. Microsoft Access 97 does not have the "whitelisting" included in it's install script.