declare @year char(4),@month char(2)

set @year=convert(char(4),getdate(),120)

set @month=right(convert(char(7),getdate(),120),2)

select @month + '-' + @year

try logging in using the sql server account and try to access the shared folder..

Also try executing the backup the cmd as part of a job..

If you are able to...

More Info:

http://support.microsoft.com/?id=319723

is the awe memory enabled?

And also is sql server clustered? If so were multiple instances active on one node at any point of time??

check the error log to see the...

set nocount on

declare @output varchar(8000)

create table #output  (outputtext varchar(8000))

insert into #output

exec master..xp_cmdshell "type C:\test.txt"

select @output=outputtext from #output

drop table #output

print @output

set nocount on

declare @output varchar(8000)

create table #output  (outputtext varchar(8000))

insert into #output

exec master..xp_cmdshell "type C:\test.txt"

select @output=outputtext from #output

drop table #output

print @output

master..xp_cmdshell "type C:\test.txt"

Administrator tools->Services->SQL Server And Agent Properties->Log on..

Alternatively, enterprise manager->SQL Server Properties->Security and for SQL Agent....enterprise manager->Managemet->SQL Server Agent->Properties...

use dynamic properties task and pass the name as global variable...

Check On which node is the service active and try starting from there..

And also how are you trying to start the service? use cluster administrator or the sql service manager..

shrink the log file and release the space to OS..You can find more info abt in BOL..

Remove/Modify the where caluse criteria and see the results...

Scheduling the log backups frequently should log file size in check..

To congifure the log file to grow in MB's instead of percent...

Enterprise Manager->Database Properties->Transaction Log-> Auto Grow file->In MegaBytes... or...

also backing up the log file more frequently would help to keep the log file size in check...

Modify the above select statement to the following for skipping the columns which doesn't allow nulls so that the unnecessary checks can be avoided...

select c.[name], c.[colid]

from sysobjects o

inner join syscolumns...