[AccessD] Access Development PC Keeps Dying

Gustav, David, Doug,

Thanks for the help with this question.

For some reason, I didn't think that XP had much for logging, as this was an area that I had never worked with before.

I am still not sure why the one PC is dying, but I now have more tools in my bag-of-tricks.

Thanks again,
Brad 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Steele
Sent: Monday, June 17, 2013 10:21 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access Development PC Keeps Dying

System logs in Win XP:

Right click on My Computer.  Select 'Manage'.  You should get the Computer Management console window.

Select System Tools/Event Viewer/System.  This should give you the System log messages in the right hand screen.  You can right click on each message and look at its Properties for more info.

Hope this helps

Incidentally, it is this message log that various phone scammers get you to look at, as it has lots of warning messages and errors.  Then they try to convince you that they can 'fix' your problems by getting you to buy and download their malware.

Doug


On Mon, Jun 17, 2013 at 9:55 AM, David A Gibson < davidalangibson2010 at gmail.com> wrote:

> It's been a while  but I seem to remember a puter we had doing the 
> same thing.  Automatic Updates were turned on and set to run in the early AM.
>  It
> was choking on a particular update and then restarting.  It would then 
> try again during the next cycle and choke again.
>
> David Gibson
>
> -----Oprindelig meddelelse-----
> Fra: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] På vegne af Brad Marks
> Sendt: 17. juni 2013 17:53
> Til: Access Developers discussion and problem solving
> Emne: [AccessD] Access Development PC Keeps Dying
>
> All,
>
> We have a single PC set up for Access Development  (The only PC with 
> the Full Version of the Office Suite).
>
> I use Remote Desktop to access this PC.
>
> Recently, it has been going offline about two or three times per week 
> and must be manually rebooted.  This happens at night when it is not 
> being used.
>
> I have a couple questions.  These really aren't Access questions but I 
> thought that others in this group may shed some light on them.
>
> Is there some sort of log (XP SP3) that would help me discern why this 
> PC is dying?  I came from the IBM Mainframe realm and I am familiar 
> with mainframe system logs.
>
> Also, I would like to set up an automated process (Perhaps with VB 
> Script) to discern when this development PC goes offline.  This script 
> would run on another server a few times each day and then send an 
> e-mail if it detects that the Access Development PC has died.  Does 
> anyone have ideas on how to do this?  I have limited VB Script 
> experience.  Perhaps this would be possible with VBA, I am not sure.
>
> Thanks,
> Brad
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
This message was scanned by ESVA and is believed to be clean.
Click here to report this message as spam. 
http://h0stname/cgi-bin/learn-msg.cgi?id=4B19628CB0.0EF60