I cannot find a good answer to this question and it's been something that's
been a problem for me for quite a while. When installing a full version of
SQL 2005 on a machine that has SQL Express on it (usually as a result of
Backup Exec being installed), the integration services will not install, and
therefore I can't create maintenance plans. In some cases I've also had the
management studio itself will not install. If trying to come back around
and install a second time, the installer will say these are already
installed, but they are not.

I'm not that knowledgeable with SQL2005, so any on why this is
happening and how to overcome it would be appreciated.

If you had installed SSMSE before installing SQL Server 2005 (any edition
other then Express which has not Client Tools in its Setup) then you can not
install SSMS. They does not work side by side. If you want to install SSMS,
then you should uninstall SSMSE before installing SSMS.

You can create Maintanence Plans if you apply SP2 of SQL Server 2005. You do
not need to install SSIS to create Maintanence Plans if you apply SP2.

I do not know about the relationships of the possible problems that you
claim because of Backup Exec. You better check Windows Event Logs to trace
about those errors you mention...

--
Ekrem Önsoy



"Absolutely" <nospam@nospam.here> wrote in message
news:useDtBLpIHA.4760@TK2MSFTNGP06.phx.gbl...
>I cannot find a good answer to this question and it's been something that's
>been a problem for me for quite a while. When installing a full version of
>SQL 2005 on a machine that has SQL Express on it (usually as a result of
>Backup Exec being installed), the integration services will not install,
>and therefore I can't create maintenance plans. In some cases I've also
>had the management studio itself will not install. If trying to come back
>around and install a second time, the installer will say these are already
>installed, but they are not.
>
> I'm not that knowledgeable with SQL2005, so any on why this is
> happening and how to overcome it would be appreciated.
>
>
>

These machines are ones that have never had any management tools installed
prior to the SQL 2005 install. No errors in the event logs. I'm looking at
a Small Business Server right now that has the MSSMLBIZ instance. I cannot
get management tools to install on this machine.


"Ekrem Önsoy" <ekrem@compecta.com> wrote in message
news:F67A386F-7B6D-44CE-8D71-07D36803DB24@microsoft.com...
> If you had installed SSMSE before installing SQL Server 2005 (any edition
> other then Express which has not Client Tools in its Setup) then you can
> not install SSMS. They does not work side by side. If you want to install
> SSMS, then you should uninstall SSMSE before installing SSMS.
>
> You can create Maintanence Plans if you apply SP2 of SQL Server 2005. You
> do not need to install SSIS to create Maintanence Plans if you apply SP2.
>
> I do not know about the relationships of the possible problems that you
> claim because of Backup Exec. You better check Windows Event Logs to trace
> about those errors you mention...
>
> --
> Ekrem Önsoy
>
>
>
> "Absolutely" <nospam@nospam.here> wrote in message
> news:useDtBLpIHA.4760@TK2MSFTNGP06.phx.gbl...
>>I cannot find a good answer to this question and it's been something
>>that's been a problem for me for quite a while. When installing a full
>>version of SQL 2005 on a machine that has SQL Express on it (usually as a
>>result of Backup Exec being installed), the integration services will not
>>install, and therefore I can't create maintenance plans. In some cases
>>I've also had the management studio itself will not install. If trying to
>>come back around and install a second time, the installer will say these
>>are already installed, but they are not.
>>
>> I'm not that knowledgeable with SQL2005, so any on why this is
>> happening and how to overcome it would be appreciated.
>>
>>
>>
>

Look for the following file (It's a common place):
"C:\Program Files\Microsoft SQL
Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe "

If you can't find it, then probably it's not been installed. Then you can
put the SQL Server Media and run "SqlRun_Tools.msi" to install the Client
Tools (including SSMS)

P.S.
I'll not be around till this sunday as I'll left home for a while... I hope
another er will you if you are not satisfied with this answer.

--
Ekrem Önsoy



"Absolutely" <nospam@nospam.here> wrote in message
news:%23cq1tULpIHA.3900@TK2MSFTNGP05.phx.gbl...
> These machines are ones that have never had any management tools installed
> prior to the SQL 2005 install. No errors in the event logs. I'm looking
> at a Small Business Server right now that has the MSSMLBIZ instance. I
> cannot get management tools to install on this machine.
>
>
> "Ekrem Önsoy" <ekrem@compecta.com> wrote in message
> news:F67A386F-7B6D-44CE-8D71-07D36803DB24@microsoft.com...
>> If you had installed SSMSE before installing SQL Server 2005 (any edition
>> other then Express which has not Client Tools in its Setup) then you can
>> not install SSMS. They does not work side by side. If you want to install
>> SSMS, then you should uninstall SSMSE before installing SSMS.
>>
>> You can create Maintanence Plans if you apply SP2 of SQL Server 2005. You
>> do not need to install SSIS to create Maintanence Plans if you apply SP2.
>>
>> I do not know about the relationships of the possible problems that you
>> claim because of Backup Exec. You better check Windows Event Logs to
>> trace about those errors you mention...
>>
>> --
>> Ekrem Önsoy
>>
>>
>>
>> "Absolutely" <nospam@nospam.here> wrote in message
>> news:useDtBLpIHA.4760@TK2MSFTNGP06.phx.gbl...
>>>I cannot find a good answer to this question and it's been something
>>>that's been a problem for me for quite a while. When installing a full
>>>version of SQL 2005 on a machine that has SQL Express on it (usually as a
>>>result of Backup Exec being installed), the integration services will not
>>>install, and therefore I can't create maintenance plans. In some cases
>>>I've also had the management studio itself will not install. If trying
>>>to come back around and install a second time, the installer will say
>>>these are already installed, but they are not.
>>>
>>> I'm not that knowledgeable with SQL2005, so any on why this is
>>> happening and how to overcome it would be appreciated.
>>>
>>>
>>>
>>
>
>