Sorry it has taken so long to reply...

Q:    Could it be that you're running app and service at the same time?
A:    Definatly just running the service

Q:   Does the service user have rights to the directory where the 
logfile should be created?
A:   Yes, running as local admin

Q:   If you run it as app does it then create the file/table?
A:   If I run as app the debug file does get created, but the table dosn't

Q:   Are you checking via a remote connection or directly on the system
A:   Always run through RDC using the command 'mstsc /console'

Thanks.

Dirk Bulinckx wrote:
> Could it be that you're running app and service at the same time?
> does the service user have rights to the directory were the logfile should be
> created?
> If you run it as app does it then create the file/table?
> Are you checking this via a remote connection or directly on the system?
>
> Dirk Bulinckx. 
>
> -----Original Message-----
> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
> Peter Shankland
> Sent: Sunday, February 10, 2008 2:40 PM
> To: Servers Alive Discussion List
> Subject: Re: [SA-list] Uptime Logging to Database Problem
>
> I have now got the debug logging to 'stay' with the changes I have made 
> by restarting the service, but even though I have the debug logging 
> enabled and set to maximum, I get no log file created :(. This is the 
> same sort of problem as I am getting with the SQL Uptime logging.
>
> Peter Shankland wrote:
>   
>> It is running as a Service. Whenever I try to enable debug logging to 
>> file, I put in the details, click apply then ok and then when I go back 
>> into the setup the changes I have made revert to defaults, it all the 
>> changes have dissapeared!
>>
>> Very strange
>>
>> Dirk Bulinckx wrote:
>>   
>>     
>>> How is SA running, as service or as app?
>>> Does the debuglog (file based) show any errors?
>>>
>>> Dirk Bulinckx. 
>>>
>>> -----Original Message-----
>>> From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
>>> Peter Shankland
>>> Sent: Sunday, February 10, 2008 1:35 PM
>>> To: Servers Alive Discussion List
>>> Subject: [SA-list] Uptime Logging to Database Problem
>>>
>>> I am using Servers Alive v6.1 and, on the same server, have SQL Express 
>>> 2005 installed as I want to be able to log uptime / downtime to a DB.
>>>
>>> I have created the ODBC connection and it tests ok but when I go into SA 
>>> and Uptime Logging --> To Database, I enter all the correct information 
>>> and press Create Table but the table never does create.
>>>
>>> I have also tried manually creating the DB and then just configuring SA 
>>> to use it but no user tables ever get created.
>>>
>>> Any suggestions / ideas?
>>>
>>> Thanks.
>>>
>>> To unsubscribe send a message with UNSUBSCRIBE as subject to
>>>       
> [email protected]
>   
>>> If you use auto-responders (like out-of-the-office messages), then make sure
>>> that they are not send to the list nor to the individual members of the list
>>> that send a message.  Doing this will get you removed from the list.
>>>
>>> To unsubscribe send a message with UNSUBSCRIBE as subject to
>>>       
> [email protected]
>   
>>> If you use auto-responders (like out-of-the-office messages), then make sure
>>>       
> that they are not send to the list nor to the individual members of the list
> that send a message.  Doing this will get you removed from the list.
>   
>>>
>>>     
>>>       
>> To unsubscribe send a message with UNSUBSCRIBE as subject to
>>     
> [email protected]
>   
>> If you use auto-responders (like out-of-the-office messages), then make sure
>>     
> that they are not send to the list nor to the individual members of the list
> that send a message.  Doing this will get you removed from the list.
>   
>>
>>     
>
> To unsubscribe send a message with UNSUBSCRIBE as subject to 
> [email protected]
> If you use auto-responders (like out-of-the-office messages), then make sure
> that they are not send to the list nor to the individual members of the list
> that send a message.  Doing this will get you removed from the list.
>
> To unsubscribe send a message with UNSUBSCRIBE as subject to 
> [email protected]
> If you use auto-responders (like out-of-the-office messages), then make sure 
> that they are not send to the list nor to the individual members of the list 
> that send a message.  Doing this will get you removed from the list.
>
>
>

To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure 
that they are not send to the list nor to the individual members of the list 
that send a message.  Doing this will get you removed from the list.

Reply via email to