Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / English Query / July 2008

Tip: Looking for answers? Try searching our database.

Warning: cannot write logfile

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Monica - 08 Jul 2008 15:07 GMT
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?
Russell Fields - 08 Jul 2008 19:43 GMT
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

> Hello,
>
[quoted text clipped - 12 lines]
>
> Can anyone give any ideas to fix this?
Monica - 09 Jul 2008 15:38 GMT
I am using SQL 2000. I changed the user to SA and it worked.

Thanks for your advice.

> Monica,
>
[quoted text clipped - 31 lines]
> >
> > Can anyone give any ideas to fix this?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.