Opening Access Forms causes crash.

[Michael Freidgeim]

Since yesterday when I try to open most Access forms on my machine, the
access crashes with errors:
Faulting application msaccess.exe, version 10.0.6771.0, faulting module
unknown, version 0.0.0.0, fault address 0x001fc858.
Some forms can be opened successfully, but most caused a crash(fault
address can be different). The error happened for both Access XP and
Access XP run-time.
The similar error shown in Access 2003 :
Faulting application msaccess.exe, version 11.0.6566.0, stamp 42cdb33e,
faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0,
fault address 0x001ce278.

When I tried to start a new database, It allowed me to create a new
form in design mode, but new form wizard crashed.
Multiple reports has been send to Microsoft® Online Crash Analysis,
but it doesn't give me any suggestions.
I've uninstall Access XP,Access 2002 run-time and Access 2003 and then
re-install Access XP back. It didn't help.
I've tried to open debugger , and it shows stack of calls including
VBE6.DLL,oleaut32.dll,ole32.dll.

The only recent change (that I am aware of) is install of VS 2005 SP1.
Could it cause the errors? Does anyone else has similar problems?
What else should I try to re-install?

 

[Guest]

Hi Michael ,

Try re-registering the Accwiz.dll, Msado15.dll and DAO360.dll files.
Click on Start > Run. Then enter the commands:

Regsvr32 Accwiz.dll
Regsvr32 "C:\Program Files\Common Files\system\ado\Msado15.dll"
Regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\Dao360.dll"

Hopefully, this will fix the problem for you.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Michael Freidgeim]

Tom,

Thank you for your suggestion, I've re-register these 3 DLLs, but it
didn't help.

Do you have any other suggestions?

Regards,

Michael Freidgeim
Blog: http://geekswithblogs.net/mnf/

 

[Guest]

Although you mentioned completely removing two versions of Access, and then
re-installing Access 2002, you didn't indicate how you went doing this. Here
is a KB article for Office XP (sorry, I don't see a similar article for
Office 2003):

How to manually remove the Microsoft Office XP Developer
installation from your computer
http://support.microsoft.com/kb/827428

After following all of the steps in this article, try re-installing Office
XP (or Access 2002). After the installation, make sure to install the latest
service pack (SP-3) along with the latest service pack for the JET database
engine (SP-8). Use this KB article as a guide:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528


Good Luck!

Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Michael Freidgeim]

Tom,
Thank you for your suggestions.
Unfortunately they didn't help.
I gave up with my development machine and installed Access XP
Development enviroment on another PC.
Later on I will try to install Access 2007, may be it will work better.

 

[Guest]

If you completely removed Office per the instructions, reinstalled it, and
are still having problems, then my guess is that you either have a corrupted
registry, or you have a hardware problem (for example, a defective RAM memory
chip or perhaps one or more bad clusters on your hard drive). You can
initiate a check disk operation which should mark any bad clusters to prevent
them from being re-used. If the problem is registry corruption, you might be
time ahead to back up all your data files (something you should be doing
anyway), and then use FDISK to start completely over.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[prolix21]

We've had this exact same issue arise on a server in our data center.
It's a 2003 terminal server, and the users run office xp. Over the
past week all of their access databases have begun crashing everytime
you open. They all have forms like the original post describes, and we
can open access, but anytime you do anything with forms it crashes.

I've run a repair on office xp, uninstalled-reinstalled, with no
results. Has there been any luck in resolving this? There are no
hardware issues on this system and all disk/filesystem integrity
checks pass 100%...

 

[Tony Toews]

We've had this exact same issue arise on a server in our data center.
It's a 2003 terminal server, and the users run office xp. Over the
past week all of their access databases have begun crashing everytime
you open. They all have forms like the original post describes, and we
can open access, but anytime you do anything with forms it crashes.

Antivirus software? Updates have been known to make Access
performance extremely slow until a new update.

I gotta think about this one a bit.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[prolix21]

Well, we actually figured it out this AM. Another software VAR had
gone in and turned off the "Application Experience Service" because of
some issue with their app. It looks like turning this off resulted in
ms access basically dying. The second it was turned back on, all
issues were fixed. odd...

 

[Tony Toews]

Well, we actually figured it out this AM. Another software VAR had
gone in and turned off the "Application Experience Service" because of
some issue with their app. It looks like turning this off resulted in
ms access basically dying. The second it was turned back on, all
issues were fixed. odd...

Whoa. Wield one.

Thanks *VERY* much for posting back the resolution.

Hmm, that would be officially known as " Application Experience Lookup
Service "? As in Description of the Application Experience Lookup
Service in Windows Server 2003 SP1
http://support.microsoft.com/kb/902196 That makes no sense as to why
that would be causing the problem.

Given that it is new in Windows 2003 Server SP1 I'd expect more
problems when it is running.

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[Tony Toews [MVP]]

Well, we actually figured it out this AM. Another software VAR had
gone in and turned off the "Application Experience Service" because of
some issue with their app. It looks like turning this off resulted in
ms access basically dying. The second it was turned back on, all
issues were fixed. odd...

Congratulations. The Access team at Microsoft has confirmed this is
a problem.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm