Access 97 closes with no error on 2003 terminal servies server
dzirkelbh...@discussions.microsoft.com
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?
![Arvin Meyer [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWNeBaELXBA4T-Yh0e0NpfK3HiG4ga607fRgadqcjevhVaQ=s40-c)
Arvin Meyer [MVP]
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.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:C09A68FC-C81F-4E8F...@microsoft.com...
Pieter Wijnen
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
"Arvin Meyer [MVP]" <a...@m.com> wrote in message
news:OJrnAoFB...@TK2MSFTNGP04.phx.gbl...
dzirkelbh...@discussions.microsoft.com
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.
dzirkelbh...@discussions.microsoft.com
Each time it is closed by itself, the lock file is still in place, so I know
it isn't closing correctly.
Arvin Meyer [MVP]
for all Windows platforms since 1998. I'm now doing the same for Access
2003. I am not seeing any problems that can be attributed to anything but
missing references. Between the 2 versions there are over 2000 copies in
use.
"Pieter Wijnen"
<it.isi.llegal.to.send.unsollic...@online.replace.with.norway>
wrote in message news:OnlfEuFB...@TK2MSFTNGP06.phx.gbl...
Arvin Meyer [MVP]
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.
"Pieter Wijnen"
<it.isi.llegal.to.send.unsollic...@online.replace.with.norway>
wrote in message news:OnlfEuFB...@TK2MSFTNGP06.phx.gbl...
Arvin Meyer [MVP]
permissions except Full Control on the folders which house Access files.
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:1A5B0B1B-4E29-4EB2...@microsoft.com...
dzirkelbh...@discussions.microsoft.com
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.
Arvin Meyer [MVP]
should be at:
C:\Windows\System32\stdole2.tlb
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:1923F3ED-9B1B-46CB...@microsoft.com...
David W. Fenton
<dzirkelbh...@discussions.microsoft.com> wrote in
news:1923F3ED-9B1B-46CB...@microsoft.com:
> I currently have Visual Basic for Applications, Microsoft Access
> 8.0 object library, and Microsoft DAO 3.51 Object library.
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.
--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
dzirkelbh...@discussions.microsoft.com
Faulting application msaccess.exe, version 8.0.0.5903, faulting module
unknown, version 0.0.0.0, fault address 0x0020c080.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
dzirkelbh...@discussions.microsoft.com
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.
Arvin Meyer [MVP]
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.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:EE05B300-298F-4B80...@microsoft.com...
dzirkelbh...@discussions.microsoft.com
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.
dzirkelbh...@discussions.microsoft.com
work. I then installed service pack 2, didn't work.
I can't even create buttons on a form without it closing.
dzirkelbh...@discussions.microsoft.com
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.
dzirkelbh...@discussions.microsoft.com
server, so the install is an instance.
Arvin Meyer [MVP]
then reboot, then reinstall. You may also need a registry cleaner before the
reinstall.
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:606D14DD-E91F-4EDE...@microsoft.com...
dzirkelbh...@discussions.microsoft.com
does'nt support 97 anymore, so this is pretty much a bust...access 97 simply
doesn't work with server 2003.
Pieter Wijnen
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
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:A672127A-7131-4796...@microsoft.com...
dzirkelbh...@discussions.microsoft.com
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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:86229750-9122-4A25...@microsoft.com:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:50DC24F8-75AE-4002...@microsoft.com:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:A672127A-7131-4796...@microsoft.com:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:B7569A36-1998-4779...@microsoft.com:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:B7569A36-1998-4779...@microsoft.com:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:DB3BEE68-7C77-454A...@microsoft.com:
> 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.
dzirkelbh...@discussions.microsoft.com
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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:1B26B55C-4B50-49F5...@microsoft.com:
> 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]
news:Xns99BFDF5E31C24f9...@216.196.97.142...
> =?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=
> <dzirkelbh...@discussions.microsoft.com> wrote in
> news:1B26B55C-4B50-49F5...@microsoft.com:
> 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.
dzirkelbh...@discussions.microsoft.com
downloaded the eraser 97 and it says it isn't supported by my version of
windows.
On my last install it says "Microsoft Access Can't start because there is no
license for it on this machine." What is that?
Pieter Wijnen
Rename/Delete The Font prior to installing Access '97
HtH
Pieter
see http://support.microsoft.com/kb/241141
"dzir...@hotmail.com" <dzirkelbh...@discussions.microsoft.com> wrote
in message news:16309E24-59C3-4A98...@microsoft.com...
Pieter Wijnen
Pieter
"Pieter Wijnen"
<it.isi.llegal.to.send.unsollic...@online.replace.with.norway>
wrote in message news:OZf31R1B...@TK2MSFTNGP06.phx.gbl...
dzirkelbh...@discussions.microsoft.com
still have the problem and teh reglceaner won't run on 2003 fo rme.
David W. Fenton
news:uUglvHwB...@TK2MSFTNGP06.phx.gbl:
> "David W. Fenton" <XXXu...@dfenton.com.invalid> wrote in message
> news:Xns99BFDF5E31C24f9...@216.196.97.142...
>> =?Utf-8?B?ZHppcmtlbGJAaG90bWFpbC5jb20=?=
>> <dzirkelbh...@discussions.microsoft.com> wrote in
>> news:1B26B55C-4B50-49F5...@microsoft.com:
>
>> 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.
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
<it.isi.llegal.to.send.unsollicited.mail.wijnen.nospam.please@online.
replace.with.norway> wrote in
news:OZf31R1B...@TK2MSFTNGP06.phx.gbl:
> 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
<dzirkelbh...@discussions.microsoft.com> wrote in
news:304B0161-505E-4456...@microsoft.com:
> 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.
dzirkelbh...@discussions.microsoft.com
called Eraser97.