SQL Server 2008导出DTSX维护计划报错，寻求技术支持

Hey there, let's tackle this DTSX export headache you're facing step by step. I’ve dealt with similar glitches on 2008 instances before, so here are the most reliable fixes to try:

1. Verify SQL Server Agent Service Permissions #

Maintenance plans are tightly linked to SQL Server Agent, so its service account needs sufficient rights to export DTSX files:

• Open Services (run services.msc), find SQL Server Agent
• Right-click > Properties > Log On tab
• Ensure the account has local administrator privileges on the server, or is assigned the sysadmin role in SQL Server
• Restart the SQL Server Agent service after adjusting permissions

2. Try Alternative Export Paths in SSMS #

Sometimes the right-click export option acts up—switch to these methods instead:

• Expand Management > Maintenance Plans, select your plan, then click the top menu File > Export
• Or use the SSIS route: Open SQL Server Integration Services, connect to your server, navigate to the maintenance plan's associated SSIS package, then export it from there

3. Repair SQL Server Components & Apply Latest Patches #

Corrupted SSIS components or outdated software often cause export failures:

• Go to Control Panel > Programs and Features, find Microsoft SQL Server 2008
• Click Change > Repair, follow the wizard to fix damaged components
• Install SQL Server 2008 Service Pack 4 (the final SP for this version)—it resolves dozens of compatibility and permission bugs

4. Export via Command Line with dtutil #

If the GUI fails, the dtutil tool is a robust fallback:

1. Open Command Prompt as Administrator
2. Navigate to the SSIS Binn directory:

   cd "C:\Program Files\Microsoft SQL Server\100\DTS\Binn"
   

3. Run the export command (replace placeholders with your details):

   dtutil /SQL "\Maintenance Plans\YourMaintenancePlanName" /EXPORT "C:\YourSavePath\YourPlan.dtsx" /QUIET
   

5. Dig into Event Logs for Detailed Errors #

If none of the above works, check the Windows Event Viewer for specific clues:

• Open Event Viewer > Windows Logs > Application
• Look for errors tagged with SQL Server or SSIS—these will include error codes and root causes (like write permissions on the export path, missing dependencies, or corrupted plan metadata)

If you can share the exact error message text you’re seeing, I can help narrow down the fix even faster!

内容的提问来源于stack exchange，提问作者prasad540