Maintenance plan exporting problem on named instance

Madeira Team
Dec 21, 2009
2 min read

Problem

I installed SQL server 2005 Developer edition with a named instance on my computer. I created a database in order to check some SQL server advanced tools. I created a maintenance plan to backup the DB and some other things. The problem occurred when I decided that I want to export the maintenance plan from MSDB to FS and copy it onto another computer. When I tried to connect to Integration services with my named instance (server name = instance name), I got an error:

Then I tried to connect only to a server name and I succeeded to connect, but when I tried go to Stored Packages -> MSDB -> Maintenance Plans, I got this error:

I checked the Configuration Manager and everything was OK… I tried to restart the service, but it didn’t help. I tried to write “.” instead of server name, but it didn’t work either.

Solution

From the first error I understood that SSIS doesn’t support multi-instance, but I had only one instance and it was named. From the second error I understood that SSIS installation is good, because I managed to connect to SSIS with only a server name, but when I tried to go to the MSDB, I got an error. This happened because there is no MSDB on this server (MSDB is on a named instance), so I can’t connect to it. When I tried to connect with “. “ as the server name, I succeeded to connect, but got the same error when I tried to go to MSDB. I understood that the solution must be in the configuration of SSIS connection to the server. So I found a server configuration file named MsDtsSrvr.ini.xml in this path C:Program FilesMicrosoft SQL Server90DTSBinn. The file contains:

XHTML

<?xml version="1.0" encoding="utf-8"?> <DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders> <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>.</ServerName> </Folder> <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..Packages</StorePath> </Folder> </TopLevelFolders>� </DtsServiceConfiguration>

<?xml version="1.0" encoding="utf-8"?>

</Folder>

<Name>File System</Name>

<StorePath>..Packages</StorePath>

</Folder>

</TopLevelFolders>�

</DtsServiceConfiguration>

You can see that there is server name configuration there and its “.”, it means that SSIS connects to the server name only. I changed “.” to a server nameinstance name and saved the changes.

XHTML

<?xml version="1.0" encoding="utf-8"?> <DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown> <TopLevelFolders> <Folder xsi:type="SqlServerFolder"> <Name>MSDB</Name> <ServerName>Mycomputernatalie</ServerName> </Folder> <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..Packages</StorePath> </Folder> </TopLevelFolders>� </DtsServiceConfiguration>

<?xml version="1.0" encoding="utf-8"?>

<ServerName>Mycomputernatalie</ServerName>

</Folder>

<Name>File System</Name>

<StorePath>..Packages</StorePath>

</Folder>

</TopLevelFolders>�

</DtsServiceConfiguration>

Then I stopped and started SSIS service. I tried to connect again with “.” as server name and I succeeded. I managed to go to Stored Packages -> MSDB -> Maintenance Plans and see my Maintenance plan and to export it as I planned. And I learned something new….

#configuration #SSIS #maintenance

33 Comments

Guest

Dec 18, 2025

While dealing with technical issues like a maintenance plan exporting problem on named instance, many professionals often overlook the importance of planning for long-term infrastructure durability. Interestingly, this connects to the broader considerations in construction, where selecting the right materials upfront can save significant time, cost, and effort over the years. Just as in IT systems, where the right configuration ensures smooth operation, choosing the right building materials, like a high-quality steel roof, ensures structural reliability and minimizes future maintenance headaches.

Another factor to consider is cost-efficiency. In technology environments, exporting and maintaining complex plans can be resource-intensive if not properly managed. Similarly, in the construction sector, opting for materials that provide long-term value is crucial. A steel roof has gained…

hsol

Dec 18, 2025

Dealing with a maintenance plan exporting problem on named instance can be frustrating for database administrators. Often, such technical challenges highlight the importance of structured planning, precise monitoring, and efficient systems management. Interestingly, this concept of meticulous planning and systematic oversight is not limited to IT or database management—it finds a surprising parallel in modern poultry farm operations. Just as a database requires careful configuration, error checks, and timely updates to function optimally, a poultry farm thrives on well-structured processes, precise environmental control, and consistent monitoring.

This connection might not be obvious at first, but the principles are strikingly similar. For instance, in a modern poultry farm, farmers must implement comprehensive systems that track bird health, feeding schedules, and environmental conditions. Any lapse—just…

hsol

Dec 18, 2025

Encountering a maintenance plan exporting problem on a named instance can be frustrating, especially when multiple stakeholders rely on accurate and timely data for operational decisions. Issues like these often highlight underlying process inefficiencies that may not be immediately visible. Interestingly, challenges in database management or system operations can serve as a practical example of why structured improvement methodologies are essential in any organization. Just as resolving technical problems requires a step-by-step approach, improving broader operational processes benefits from a systematic framework. This connects to the DMAIC methodology, which provides a structured, data-driven approach to enhancing processes and achieving measurable improvements.

When IT teams face repetitive issues like exporting errors, root causes often involve gaps in planning, inconsistent data management, or…

Guest

Dec 16, 2025

While technical challenges like a maintenance plan exporting problem on a named instance may seem far removed from legal remedies, there is an interesting parallel in the way structured procedures and frameworks help resolve complex issues—whether in IT systems or the judicial process. Just as database administrators rely on precise protocols to export and manage maintenance plans without errors, the Indian judicial system relies on structured legal mechanisms to ensure justice is served effectively. This connects to the broader legal landscape, where tools like the Special Leave Petition (SLP) and transfer petition play a crucial role in maintaining procedural fairness.

In the Indian judicial system, a special leave petition in Supreme Court allows an aggrieved party to seek extraordinary relief when normal remedies are…

Guest

Dec 16, 2025

Interestingly, just as database maintenance plans require careful attention to avoid unexpected issues, our daily dietary habits also demand mindfulness to prevent long-term complications. While IT professionals troubleshoot maintenance plan exporting problems on a named instance to ensure system stability, individuals face a similar challenge in managing their health—particularly when it comes to sweet cravings and sugar cravings. Both scenarios involve identifying underlying causes, implementing preventative strategies, and maintaining consistent routines for optimal outcomes.

This connection may seem surprising at first, but it highlights an important truth: small, overlooked factors can create cascading problems, whether in technology or personal health. For instance, understanding the reasons for craving sugar is crucial if we want to manage our diet effectively. Often, sugar cravings are not…