Error Creating Maintenance Plan

I have a new installation of SQL 2005 x64 SP 1 Standard Edition installed on
Windows 2003 x64 SP 1 Standard Edition. I installed using unattended
install. In the ini file for unattended install I specified ADDLOCAL and
amoung other features I specified SQL_Tools90, which according to the
template.ini in the install file will install management tools. And I
thought they were installed because I can use SQLWB, Performacne tools,
configuration tools, etc. But when I tried to create a maintenance plan I
got the error below. So I ran an additional install manually and indicated
to install management tools. But the installer told me they were already
installed.
Also, I don't know if it makes a difference but I installed using the MSDN
iso image.
///////////////////////////////////////////////////////////////////////
Error Message:
The action you attempted to perform on a remote instance of SQL Server has
failed because the action requires a SQL Server component that is not
installed on the remote computer. To proceed, install SQL Server 2005
Management Tools on the remote computer, and then try again. For more
information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server
2005 Books Online, or find the article on MSDN at
http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)
For help, click: http://go.microsoft.com/fwlink/?LinkID=57083
///////////////////////////////////////////////////////////////////////
Please help!I found the solution - SSIS wasn't installed. We aren't using it at all so I
didn't install it. Apparently it's needed.
For due credit, this is where I found the problem:
http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
Mark|||The issue is fixed in SP1. SSIS doesn't have to be installed
if you are on SP1. Refer to the maintenance plans section in
the following:
A list of the new features and improvements that are
included in SQL Server 2005 Service Pack 1
http://support.microsoft.com/?id=916940
-Sue
On Fri, 11 Aug 2006 16:13:52 -0600, "Mark Miller"
<mark_n_0-s*p..am@.maxpreps.com> wrote:
>I found the solution - SSIS wasn't installed. We aren't using it at all so I
>didn't install it. Apparently it's needed.
>For due credit, this is where I found the problem:
>http://sqljunkies.com/Forums/ShowPost.aspx?PostID=9920
>Mark
>|||Thanks. You are right, however, the information on that page is wrong.
I ran SELECT @.@.VERSION and it returns "Microsoft SQL Server 2005 -
9.00.2047.00 (x64) Apr 14 2006 01:11:53"
Which matches the version number reported for SP 1 here:
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en
The only thing that doesn't match up is the file size (the SP 1 install I
used is 311,007 KB) and the date 4/14 when the date in the link above is
4/18. I think I downloaded the SP from msdn. Could they be different?
I'm going to download the one from the link above and verify.
Mark|||I checked and according to the file properties in windows explorer, the two
files (the one I downloaded from MSDN and the one from
http://www.microsoft.com/downloads/details.aspx?familyid=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC&displaylang=en )
are the exact same size, version number, and build date. So it appears that
Microsoft did NOT fix the bug in SP 1.
However, I would like to thank Sue for her response. It wasn't her fault the
documentation was incorrect.
Mark