PHWinfo - Afficher un message

31/10/2006, 09h34

Hello Claus,

I understand that you cannot create maintenance plan on your SQL 2005
server and you received the error message

An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)

The specified '@subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)

If I'm off-base, please let's know.

Based on my experience, you will get this error if SSIS is not installed on
SQL server 2005 and you try to create maintenance plans.

To resolve the issue install SSIS on the server and then create the
maintenance plans. In SQL 2005, maintance plan is based on SSIS components.
You could run setup program of SQL 2005 via Add/Remove Programs, and check
"Entire feature will be installed on local hard drive"

If you did have SSIS component installed, from the error summery we can
figure out that the problem is occurring in stored procedure
"sp_verify_subsystem".

I checked the code stored procedure and i found that there is one statement
which is checking the available subsystems in the MSDB.subsystems table and
matching the value of a variable which has a subsystem value which it
carried from wizard with the values of subsystem available in the
msdb.subsystems table.

A select in on server on subsystem table returns 11 rows, and the last row
is for SSIS.

select * from from subsystems

You may want to run the query on your system to see if SSIS is listed. If
not, you may want to remove/reinstall SSIS to see if it s.

Also, I wonder if you have a named instance of SQL 2005 and default
instance is sql 2000. So if you have default instance as SQL 2000 and a
named instance as SQL 2005 it will connect to SQL server 2000 and if we you
try to browse the stored packages and expand MSDB container it will throw
the following error.

Failed to retrieve data for this request data for this request.
(Mircorsoft.SQLServer.SmoEnum)

However you can configure SSIS to save packages in any of the local
instances of SQL Server installed on the machine. You have to modify the
MsDtsSrvr.ini.xml file by adding the instances that you want to save
packages to.

1.Using the SQL BI Dev Studio create a SSIS Pacakge
2. Select the FILE menu and then select “Save copy of Package.dtsx As”
3. In “Save Copy of Package” dialog select:
Package Location = SQL Server
Server = MachineName\InstanceName
Package Path = /Maintenance Plans/PackageName
4. Edit the Configuration file MsDtsSrvr.ini.xml in the following path:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn
5. Change the string “<ServerName>.</ServerName>” as following:
<ServerName>MachineName\InstanceName</ServerName>
6. Save the file and Re-Start SSIS Service
7. In SQL Management Studio Under “CONNECT” select “Integration Services”
8.Select New Server Registeration and connect to the Default Instance
9. When you look at the Stored Packages you will see that these are the
one’s saved to the Named Instance

Before:
<?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>

After:

<?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 INSTANCE1</Name>
<ServerName>HOSTNAME\INSTANCENAME1</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..\Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

If you have further questions on the issue, please feel free to let's know.
Thank you.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

31/10/2006, 09h34	#2
Peter Yang [MSFT] Messages: n/a Hébergeur:	RE: problems creating maintenanceplan Hello Claus, I understand that you cannot create maintenance plan on your SQL 2005 server and you received the error message An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The specified '@subsystem' is invalid (valid values are returned by sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234) If I'm off-base, please let's know. Based on my experience, you will get this error if SSIS is not installed on SQL server 2005 and you try to create maintenance plans. To resolve the issue install SSIS on the server and then create the maintenance plans. In SQL 2005, maintance plan is based on SSIS components. You could run setup program of SQL 2005 via Add/Remove Programs, and check "Entire feature will be installed on local hard drive" If you did have SSIS component installed, from the error summery we can figure out that the problem is occurring in stored procedure "sp_verify_subsystem". I checked the code stored procedure and i found that there is one statement which is checking the available subsystems in the MSDB.subsystems table and matching the value of a variable which has a subsystem value which it carried from wizard with the values of subsystem available in the msdb.subsystems table. A select in on server on subsystem table returns 11 rows, and the last row is for SSIS. select * from from subsystems You may want to run the query on your system to see if SSIS is listed. If not, you may want to remove/reinstall SSIS to see if it s. Also, I wonder if you have a named instance of SQL 2005 and default instance is sql 2000. So if you have default instance as SQL 2000 and a named instance as SQL 2005 it will connect to SQL server 2000 and if we you try to browse the stored packages and expand MSDB container it will throw the following error. Failed to retrieve data for this request data for this request. (Mircorsoft.SQLServer.SmoEnum) However you can configure SSIS to save packages in any of the local instances of SQL Server installed on the machine. You have to modify the MsDtsSrvr.ini.xml file by adding the instances that you want to save packages to. 1.Using the SQL BI Dev Studio create a SSIS Pacakge 2. Select the FILE menu and then select “Save copy of Package.dtsx As” 3. In “Save Copy of Package” dialog select: Package Location = SQL Server Server = MachineName\InstanceName Package Path = /Maintenance Plans/PackageName 4. Edit the Configuration file MsDtsSrvr.ini.xml in the following path: C:\Program Files\Microsoft SQL Server\90\DTS\Binn 5. Change the string “<ServerName>.</ServerName>” as following: <ServerName>MachineName\InstanceName</ServerName> 6. Save the file and Re-Start SSIS Service 7. In SQL Management Studio Under “CONNECT” select “Integration Services” 8.Select New Server Registeration and connect to the Default Instance 9. When you look at the Stored Packages you will see that these are the one’s saved to the Named Instance Before: <?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> After: <?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 INSTANCE1</Name> <ServerName>HOSTNAME\INSTANCENAME1</ServerName> </Folder> <Folder xsi:type="FileSystemFolder"> <Name>File System</Name> <StorePath>..\Packages</StorePath> </Folder> </TopLevelFolders> </DtsServiceConfiguration> If you have further questions on the issue, please feel free to let's know. Thank you. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscripti...ult.aspx#notif ications <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at <http://msdn.microsoft.com/subscriptions/support/default.aspx>. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.