[AccessD] Document Caused Serious Error

What OS is the server running, Windows 2003?

I would look through the event log, and look for any errors in the
system or application logs. (Then google those events, to start tracking
down the problem).


Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson
Sent: Thursday, January 03, 2008 1:19 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Document Caused Serious Error

OK - Further test results:

1) The same problem happens when I try it direct on the server.
2) I have applied all the Microsoft Office Updates - Same Problem.
3) I have run Detect and Repair from the help menu (ticking reset 
defaults as well) - Same Problem.
4) I find that I don't even need to open the database program.  If I 
open Access, then close it, then open it again, I get a message 
"Access failed to start correctly last time.  Starting Access in safe 
Mode will help you correct or isolate a start up problem in order to 
successfully start the program.  Some functionality may be disabled 
in this mode.".  Starting in safe mode doesn't seem to offer any 
advice on how to solve the problem.

Any further thoughts?

David

At 3/01/2008, you wrote:
>Yes, do that, technically, TS and Remote Desktop (on a TS Server) are
>the same thing.
>
>Drew
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David
Emerson
>Sent: Tuesday, January 01, 2008 12:12 PM
>To: Access Developers discussion and problem solving
>Subject: Re: [AccessD] Document Caused Serious Error
>
>I am getting the error in TS, but also when I use remote desktop to
>access the server direct.
>
>I need to go into the clients office and try it direct on their server.
>
>David
>
>At 2/01/2008, you wrote:
> >Is it giving you this error in terminal server?
> >
> >We use Terminal Server at work, and I get various 'serious errors'
from
> >time to time from different apps.  This is basically someone using an
> >app, then killing their session, without properly logging off.
> >
> >Drew
> >
> >-----Original Message-----
> >From: accessd-bounces at databaseadvisors.com
> >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David
>Emerson
> >Sent: Sunday, December 30, 2007 11:58 AM
> >To: accessd at databaseadvisors.com
> >Subject: [AccessD] Document Caused Serious Error
> >
> >I have an Access XP ade which is being opened in Access 2003 SP3
> >through terminal server.
> >
> >About every second time that I open it, I get an error message saying
> >that the document caused a serious error last time it was opened.  I
> >follow the instructions for removing it from the disabled items list
> >but it keeps coming back.  I have replaced the file but it makes no
> >difference.
> >
> >If I ignore the message then the database opens ok and seems to run
> >fine.
> >
> >Anyone have any pointers on how to permanently fix this?
> >
> >Regards
> >
> >David Emerson
> >Dalyn Software Ltd
> >Wellington, New Zealand

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com