installing management studio on a cluster

Hi,
I am installing sql 2005 on a two node cluster. I have managed to complete
the installation and then wanted to add the sql management studio on to the
cluster. I installed disk two and chose the support tools but have way
through the installation it failed with the following error:
Failed to install and configure assemblies C:\Program Files\Microsoft SQL
Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2146233087
Error message: Unknown error 0x80131501
Error description: The Transaction Manager is not available. (Exception from
HRESULT: 0x8004D01B)
I was installing this on the first node which had ownership of the shared
disks
Any ideas
Looks like you need to install a clustered instance of MSDTC.
http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/bts06clustering/55b0c81f-44a5-4069-b065-57df1cce19ac.mspx?mfr=true
Ignore the incoming caller stuff. That is for Biztalk.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:D07341A6-EDDA-4448-9C8A-23A1727E565B@.microsoft.com...
> Hi,
> I am installing sql 2005 on a two node cluster. I have managed to complete
> the installation and then wanted to add the sql management studio on to
> the
> cluster. I installed disk two and chose the support tools but have way
> through the installation it failed with the following error:
> Failed to install and configure assemblies C:\Program Files\Microsoft SQL
> Server\90\NotificationServices\9.0.242\Bin\microso ft.sqlserver.notificationservices.dll
> in the COM+ catalog. Error: -2146233087
> Error message: Unknown error 0x80131501
> Error description: The Transaction Manager is not available. (Exception
> from
> HRESULT: 0x8004D01B)
> I was installing this on the first node which had ownership of the shared
> disks
>
> Any ideas

Installation problem

I have installed SQL Server Express Edition using SQLServer2005_SSMSEE.msi.
All was fine.
But, when I managed to connect to the server when
I choosed <browse for more ...> in the server name combo
the application was unable to find a server (either local or remote. I think that the server should be a local one if I installed it locally on the machine).
I tried many combinations for the server name based on the machine and domain name:

MACHINE
MACHINE\MACHINE
DOMAIN\MACHINE

but all the times the following error occured:
TITLE: New Server Registration

Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK
Can anyone help me to register a server?

Thanks,

Radu

Hi.

Try " (local)\SQLEXPRESS"

The default instant name of Sql Server 2005 Express Edition is SQLEXPRESS (case-insensitive)

".\SQLEXPRESS" Will work if you have TCP/IP access enabled (See your SQL Server service manager)

MACHINE\SQLEXPRESS should work too.

Hope this helps

|||

I having issues with SQL Express remote issues, I have turned remote on in the area configuration and enabled all protocols.

MachineName/SQLEXPRESS on remote machines worked for about a day and than on remote machines in the network no longer can use the Management tool to see SQL engine. I checked and the MachineName/SQLEXPRESS is definitely registered.

Everything seems to work as expected on the local machine. The puzzeling thing is it did work for about a day and nothing changes on the network.

Any help would be very appreciated

Installation problem

I have installed SQL Server Express Edition using SQLServer2005_SSMSEE.msi.
All was fine.
But, when I managed to connect to the server when
I choosed <browse for more ...> in the server name combo
the application was unable to find a server (either local or remote. I think that the server should be a local one if I installed it locally on the machine).
I tried many combinations for the server name based on the machine and domain name:

MACHINE
MACHINE\MACHINE
DOMAIN\MACHINE

but all the times the following error occured:
TITLE: New Server Registration

Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK
Can anyone help me to register a server?

Thanks,

Radu

Hi.

Try " (local)\SQLEXPRESS"

The default instant name of Sql Server 2005 Express Edition is SQLEXPRESS (case-insensitive)

".\SQLEXPRESS" Will work if you have TCP/IP access enabled (See your SQL Server service manager)

MACHINE\SQLEXPRESS should work too.

Hope this helps

|||

I having issues with SQL Express remote issues, I have turned remote on in the area configuration and enabled all protocols.

MachineName/SQLEXPRESS on remote machines worked for about a day and than on remote machines in the network no longer can use the Management tool to see SQL engine. I checked and the MachineName/SQLEXPRESS is definitely registered.

Everything seems to work as expected on the local machine. The puzzeling thing is it did work for about a day and nothing changes on the network.

Any help would be very appreciated