Re: Warning: cannot write logfile
- From: "Russell Fields" <russellfields@xxxxxxxxxx>
- Date: Tue, 8 Jul 2008 14:43:03 -0400
Monica,
Under what account is this job running? And what version of SQL Server?
If the account is not a sysadmin, then the SQL Agent Proxy account will be
used. (In a SQL Server 2000 server that was upgraded to SQL Server 2005, you
may see a proxy named UpgradedProxyAccount that uses UpgradedProxy.)
If this account does not have rights to write to the directory, the job will
run, but you will get the error.
If I remember correctly, a non-sysadmin in SQL Server 2000 cannot write to a
file. (But test it and see.) If that is the case, another option is to
check Append Output to Step History, which would allow you to see the output
using Enterprise Manager, going to the Job Step Advanced tab and pressing
View.
RLF
"Monica" <Monica@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:039D65F6-B272-4555-BBA3-6CD1A7B09D59@xxxxxxxxxxxxxxxx
Hello,
I am scheduling a simple job to run a query. I want the result of that
query
written to a text file.
When I am scheduling the job, in the step section I am creating a step of
type "Transact-SQL Script (TSQL)" where I define the query. In the
advanced
tab of the Step section there is an option to put an output file and there
I
put the path where I want the text file created.
When I run the job, it runs successfuly but the file is not created. I get
a
Warning:cannot write logfile message.
Can anyone give any ideas to fix this?
.
- Follow-Ups:
- Re: Warning: cannot write logfile
- From: Monica
- Re: Warning: cannot write logfile
- Prev by Date: RE: datetime comparison broken???
- Next by Date: Re: Warning: cannot write logfile
- Previous by thread: datetime comparison broken???
- Next by thread: Re: Warning: cannot write logfile
- Index(es):
Relevant Pages
|
Loading
