"Tom" <mcseman@hotmail.com> wrote in message
news:uLq$VLAJGHA.1848@TK2MSFTNGP12.phx.gbl...
> I'm installing SQL2005 ent. on a active/passive win2003-sp1 2 node
> cluster.
> Just before installation finishes I get an error:
>
> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
> in the COM+ catalog.
> Error: -2146233087 Error message: Unknown error 0x8013150 Error
> description: The transaction has aborted.
> For help, click:
> http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29549&EvtType=sqlca%5csqlassembly.cpp%40Do_sqlAssemblyRegSvcs%40Do_sqlAssemblyRegSvcs%40x80131501
>
>
> Error pops up when Workstation components (last step) installation is
> running and 'Removing backup files' is indicated in progress bar...
> If I click 'Ignore', setup finishes a couple of minutes later with all
> components installed. SQL seams to work OK, failover too.
> Error states that some notification service component failed to install
> but I'm not even trying to instal Notification services. I only selected
> Database, integration and workstation components during setup.
> Above link says that SQL can not verify if MSDTC is running. BOL says that
> MSDTC should be present as a clustered resource. Is that realy necessary?
> In SQL2000 there were no such error or requirement on win2003 cluster.
> Can I leave installation in a condition as it is since everything seams to
> work and application does not need MSDTC?
> Funny thing is that I got the same error on second node when I was
> installing Inegration and Workstation components on it since they are only
> installed on first node during initial installation of SQL2005 on cluster.
> It seams that Workstation components are the one that are causing the
> error..
>
> Anyone with the same problem?
>
> Tom
>

"Tom" <mcseman@hotmail.com> wrote in message
news:OqRP4vaJGHA.1032@TK2MSFTNGP11.phx.gbl...
> Solved the problem!
> MSDTC needs to be added as a clustered resource. After that I just
> reinstalled Workstation components on both nodes and is all OK now..
>
> Tom
>
>
>
> "Tom" <mcseman@hotmail.com> wrote in message
> news:uLq$VLAJGHA.1848@TK2MSFTNGP12.phx.gbl...
>> I'm installing SQL2005 ent. on a active/passive win2003-sp1 2 node
>> cluster.
>> Just before installation finishes I get an error:
>>
>> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
>> Server\90\NotificationServices\9.0.242\Bin\microsoft.sqlserver.notificationservices.dll
>> in the COM+ catalog.
>> Error: -2146233087 Error message: Unknown error 0x8013150 Error
>> description: The transaction has aborted.
>> For help, click:
>> http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29549&EvtType=sqlca%5csqlassembly.cpp%40Do_sqlAssemblyRegSvcs%40Do_sqlAssemblyRegSvcs%40x80131501
>>
>>
>> Error pops up when Workstation components (last step) installation is
>> running and 'Removing backup files' is indicated in progress bar...
>> If I click 'Ignore', setup finishes a couple of minutes later with all
>> components installed. SQL seams to work OK, failover too.
>> Error states that some notification service component failed to install
>> but I'm not even trying to instal Notification services. I only selected
>> Database, integration and workstation components during setup.
>> Above link says that SQL can not verify if MSDTC is running. BOL says
>> that MSDTC should be present as a clustered resource. Is that realy
>> necessary? In SQL2000 there were no such error or requirement on win2003
>> cluster.
>> Can I leave installation in a condition as it is since everything seams
>> to work and application does not need MSDTC?
>> Funny thing is that I got the same error on second node when I was
>> installing Inegration and Workstation components on it since they are
>> only installed on first node during initial installation of SQL2005 on
>> cluster. It seams that Workstation components are the one that are
>> causing the error..
>>
>> Anyone with the same problem?
>>
>> Tom
>>
>
>