Re: error message not being logged to windows event log
From: Alan J. McFarlane (alanjmcf_at_yahoo.com.INVALID)
Date: 03/24/04
- Next message: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Previous message: Joe Ross: "General Network Error = DBNetLib throwing NE_E_NOMEMORY"
- In reply to: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Next in thread: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Reply: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 11:59:17 -0000
Sue Hoegemeier <Sue_H@nomail.please> wrote:
> Anon restarted SQL Server after making the changes which
> solved the problem.
> Logging to the Windows event log is enabled by default for
> SQL Server. The auditing is logged to the SQL Server error
> log and the Windows Application event log if you haven't
> changed the default settings. You can find more information
> on this in books online under startup options.
>
Ah ha, shows that I truly don't know much on this subject.
Interestingly my MSDE appears to be started with -sINSTANCE
and -d... -e... -l..., but no -n, hmm. I think I better talk to the folks
who created the installer for it, to see what odd way they have configured
it...
-- Alan J. McFarlane http://homepage.ntlworld.com/alanjmcf/ Please follow-up in the newsgroup for the benefit of all.
- Next message: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Previous message: Joe Ross: "General Network Error = DBNetLib throwing NE_E_NOMEMORY"
- In reply to: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Next in thread: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Reply: Sue Hoegemeier: "Re: error message not being logged to windows event log"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|