Backup/Maintenance plan problems

[primate]

Hi,

Been scratching my head about this for a while and I can't seem to find a solution....

I have two MSDE 2000 databases on separate boxes.

I have SQL Enterprise Manager installed on another server.

I can succesfully connect to both MSDE instances and take manual backups by using the SQL Enterprise Manager console.

However I want to automate this, but whenever I create a maintenance plan or a backup plan, whilst I can enter all the data and the wizard confirms that the plan was created succesfully, if I later check the details of the plan, such as time and date to run a backup, they are all empty and the plan does not run. This occures if I login under SQL account or using Windows Authentication.

SQLMaint.exe is installed on both MSDE database servers, MS articles seemed to suggest that this might be the source of the problem but in this case it isn't....

Has anyone got any suggestions?

Thanks

 

[jawan]

did you try to login as SQL Admin user, also check the plan is active or not.

 

[primate]

Yes I did login as SQL Admin, as for whether the plane is active or not, I can't find anything to say set it to be inactive, after I create the plan it appears under maintenance plans but without the schedule I set...

 

[BuGlen]

I had the same issue. Whenever I tried to use the DB Maintenance Plan, it would go through the wizard but the backup schedules would not keep their parameters. This is a posting in one of the MS news groups that helped me fix the problem. I hope it helps you as well:

----
This is a known issue and is logged as bug #364064. We don't currently have a fix available, but we have tested a workaround for this issue.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If you add the BackupDirectory registry value for the instance SQL server in registry, you will be able to add, save, and edit the maintenance job.

For example, (if you have a default instance), put it in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer.
The String value is "BackupDirectory" and the data value is "C:\Program Files\Microsoft SQL Server\MSSQL\BACKUP"

For example, (if you have a named instance), put it in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<instancename>\MSSQLServer.
The String value is &quot;BackupDirectory&quot; and the data value is &quot;C:\Program Files\Microsoft SQL Server\MSSQL$instancename\BACKUP&quot;
----


Glen Appleton

VB.Net student.

 

[primate]

Thanks for your help I will give this a go when I am back in work on Monday

 

[BuGlen]

Let me know if it works out for you. If it does, I'm thinking about writing a little utility that will correct this for all installed instances.


Glen Appleton

VB.Net student.

 

[primate]

That worked great, thanks for the tip.