Maintenance Plan for SQL Server 2005 64-bit doesn't work!

Hi all,
We have a SQL Server 2005 64-bit, and recently I upgrade from build 3042 to 3054 and I try to do a maintenance plan for transaction logs(TL) backup, including cleanup for two days (have full backup every night).

Problem I have is that I want the TL files to dump in a different location(due to disk space), so I put in the UNC path in the "Create a backup file for every database - >Folder:\\FileServer\TL\DBLogs"

NB: if using the local drives, it work

Check List
Security:
- The account that I used to create the plan is an sa account
- The location that I dump the TL files, I have full access to the folder

SQL Statement:
exec xp_cmdshell 'dir \FileServer\TL\DBLogs' (it list all files)

Is this a bug for 64-bit? because I can do this on SQL Server 2005 32-bit and it's work perfectly

Resolved: permission problems, u need to give permission to the folder for SQL Server Agent account

Maintenance Cleanup Task (SQL 2005 64-bit)

I have a maintenance cleanup task in a maintenance plan. There are no other
objects in the maintenance plan. The task is set to remove files older than 1
day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
When I run it, it returns a success (as does the job), but it does not
delete any files.
Any suggestions would be appreciated.
I have an addition. Even when I change the folder to a name that does not
exist, the Maintenance Cleanu Task return a success. This task apparently
does not return a failure (or log a reason for a failure).
"Ron Sellers" wrote:

> I have a maintenance cleanup task in a maintenance plan. There are no other
> objects in the maintenance plan. The task is set to remove files older than 1
> day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
> When I run it, it returns a success (as does the job), but it does not
> delete any files.
> Any suggestions would be appreciated.

Maintenance Cleanup Task (SQL 2005 64-bit)

I have a maintenance cleanup task in a maintenance plan. There are no other
objects in the maintenance plan. The task is set to remove files older than 1
day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
When I run it, it returns a success (as does the job), but it does not
delete any files.
Any suggestions would be appreciated.I have an addition. Even when I change the folder to a name that does not
exist, the Maintenance Cleanu Task return a success. This task apparently
does not return a failure (or log a reason for a failure).
"Ron Sellers" wrote:
> I have a maintenance cleanup task in a maintenance plan. There are no other
> objects in the maintenance plan. The task is set to remove files older than 1
> day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
> When I run it, it returns a success (as does the job), but it does not
> delete any files.
> Any suggestions would be appreciated.

Maintenance Cleanup Task (SQL 2005 64-bit)

I have a maintenance cleanup task in a maintenance plan. There are no other
objects in the maintenance plan. The task is set to remove files older than
1
day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
When I run it, it returns a success (as does the job), but it does not
delete any files.
Any suggestions would be appreciated.I have an addition. Even when I change the folder to a name that does not
exist, the Maintenance Cleanu Task return a success. This task apparently
does not return a failure (or log a reason for a failure).
"Ron Sellers" wrote:

> I have a maintenance cleanup task in a maintenance plan. There are no othe
r
> objects in the maintenance plan. The task is set to remove files older tha
n 1
> day old from a UNC drive (\\server\ALSDESQL2TapeBackup).
> When I run it, it returns a success (as does the job), but it does not
> delete any files.
> Any suggestions would be appreciated.sql

MAIL on SQL Server 2000 Standard on Windows Server 2003 64-bit

I've read about 2005 Enterprise Edition 64-bit and 2000 Enterprise Edition 64-bit and those mail issues. But, my particular situation is running SQL Server 2000 Standard Edition (32-bit) on Windows 2003 Server (64-bit). I got the mail profile set up ok for the SQL Server Service Account using Outlook 2000 and can send and receive mail using Outlook. But, even after restarting the SQL Server Services, there's no profile to choose in the SQL Mail or Agent Mail drop-down box. I have tried ON the server and remotely. Locally, the drop-down box doesn't even really 'drop down'. Remotely, I get the drop-down but it is empty. I don't need a primer on configuring SQL Mail for SQL 2000. I just need to know if this combination of SQL Server Editions and OS Editions will even support SQL Mail. Maybe adding the appropriate values in the registry will enable me to use this mail profile for SQL Server?
What about that smtp client that's out there. I've not used it on any machine and don't want to make this goofy one the guinea pig if it hasn't been proven to work.
No, we can't go to SQL Server 2005 yet on this server. It hosts a purchased system that isn't supported on SQL Server 2005.
Thanks for your help,
Michelle
I rebooted the server and was able to configure the mail profile and select it from my client/enterprise manager. It seems like things generally require a reboot more often on this server than I've experienced on other servers. I tested agent mail, xp_sendamail, and dts send mail tasks all to success. Now I'm fighting with installation of the SQL Server Health & History Tool.
Just wanted to document that sql mail DOES seem to work with this configuration. Keep trying and I'm sure that you'll get it to work, too :)