Can''t configure Features on Clustered Server

Hi, I am a relative newbie to SQL Server and I need some help trying to configure an existing clustered server. Using surface area configuration with "local" checked, I can see all of the components as pictured here. However, checking one (i.e. DatabaseMail) results in a pop-up message with "You cannot configure surface area of clustered services by connecting to a computer name. Connect to the virtual server to configure clustered services".

Ok. Fair enough. I then go back, check "remote" and enter the name of the cluster. After connecting, it only shows me a partial list of services as pictured here.

I first encounterd this while trying to enable Databasemail. However, I need to get an understanding of what I need to do be able to configure services or features on a clustered server using SAC.

Thanks for any help.

Just wondering if anyone else has had a similar problem and how they solved it.

I've inherited this problem and still have not found a resolution. Any response would be appreciated.

Can''t configure Features on Clustered Server

Hi, I am a relative newbie to SQL Server and I need some help trying to configure an existing clustered server. Using surface area configuration with "local" checked, I can see all of the components as pictured here. However, checking one (i.e. DatabaseMail) results in a pop-up message with "You cannot configure surface area of clustered services by connecting to a computer name. Connect to the virtual server to configure clustered services".

Ok. Fair enough. I then go back, check "remote" and enter the name of the cluster. After connecting, it only shows me a partial list of services as pictured here.

I first encounterd this while trying to enable Databasemail. However, I need to get an understanding of what I need to do be able to configure services or features on a clustered server using SAC.

Thanks for any help.

Just wondering if anyone else has had a similar problem and how they solved it.

I've inherited this problem and still have not found a resolution. Any response would be appreciated.

sql

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476[/url]
BUTTONS:
OK
Everything else in the Management Studio works fine. Can anyone
interpret this?
I can't interpret or solve, but I can confirm that it also happens on our
clusters.

> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476
--
BUTTONS:
OK
--
Everything else in the Management Studio works fine. Can anyone
interpret this?I can't interpret or solve, but I can confirm that it also happens on our
clusters.
> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>|||Interesting...I found out that when I was trying to view the logs, for
some reason it was trying to direct me to the virtual servername used
by the Data Group of the cluster. I don't know why it would do that.
I created an alias for the data group name, and pointed it to the ip
address of the sql server instance, and it connects properly now.
Not sure if I explained this right, I'm kinda new to clusters, but
hopefully this will help you.
Aaron Bertrand [SQL Server MVP] wrote:
> I can't interpret or solve, but I can confirm that it also happens on our
> clusters.
>
>
> > Everything else in the Management Studio works fine. Can anyone
> > interpret this?
> >

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
http://go.microsoft.com/fwlink?Prod...=0&LinkId=20476
BUTTONS:
OK
--
Everything else in the Management Studio works fine. Can anyone
interpret this?I can't interpret or solve, but I can confirm that it also happens on our
clusters.

> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>|||Interesting...I found out that when I was trying to view the logs, for
some reason it was trying to direct me to the virtual servername used
by the Data Group of the cluster. I don't know why it would do that.
I created an alias for the data group name, and pointed it to the ip
address of the sql server instance, and it connects properly now.
Not sure if I explained this right, I'm kinda new to clusters, but
hopefully this will help you.
Aaron Bertrand [SQL Server MVP] wrote:[vbcol=seagreen]
> I can't interpret or solve, but I can confirm that it also happens on our
> clusters.
>
>

Cannot use file for clustered server

I have a clustered server with a clustered instance of SQL Server 2000
running on it. I'm attempting to restore several databases to the clustered
server from our production, non-clustered database server. I also want to do
a move of log files at the same time. On the production server, the database
and log files are on the same raid array. On the clustered server, I've
created two raid arrays, drive H: for the databases which is in cluster group
0 and drive g: for the logs which is in cluster group 1. The database server
on the cluster is in group 0, by the way. I'm doing a restore using an sql
file that works restoring databases and logs to a backup server on different
drives so I'm reasonably sure that the restore syntax is correct. When I
attempt to do a restore of the log files on the cluster server, I receive the
following error.
Msg 5184, Level 16, State 2, Line 1
Cannot use file g:\logs\ims.ldf for clustered server. Only formatted files
on which the cluster resource of the server has a dependency can be used.
What does that mean? Does that mean that I have to put the log array in the
same group as the clustered instance of sql server? If that's the case, how
do I do that?
TIA
Ernie
Move the G: Drive into the SQL Group (group 0 from you post).
Stop the SQL clustered group.
Double click SQL Server resource and add G: Drive as a dependency.
Bring the SQL Group back online.
Restore away
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://www.msmvps.com/clustering - Blog
"ebferro" <ebferro@.discussions.microsoft.com> wrote in message
news:24628F06-9C5C-4B4F-B7C6-50E82D24CF8F@.microsoft.com...
>I have a clustered server with a clustered instance of SQL Server 2000
> running on it. I'm attempting to restore several databases to the
> clustered
> server from our production, non-clustered database server. I also want to
> do
> a move of log files at the same time. On the production server, the
> database
> and log files are on the same raid array. On the clustered server, I've
> created two raid arrays, drive H: for the databases which is in cluster
> group
> 0 and drive g: for the logs which is in cluster group 1. The database
> server
> on the cluster is in group 0, by the way. I'm doing a restore using an
> sql
> file that works restoring databases and logs to a backup server on
> different
> drives so I'm reasonably sure that the restore syntax is correct. When I
> attempt to do a restore of the log files on the cluster server, I receive
> the
> following error.
> Msg 5184, Level 16, State 2, Line 1
> Cannot use file g:\logs\ims.ldf for clustered server. Only formatted
> files
> on which the cluster resource of the server has a dependency can be used.
> What does that mean? Does that mean that I have to put the log array in
> the
> same group as the clustered instance of sql server? If that's the case,
> how
> do I do that?
> TIA
> Ernie
|||Rod:
Many thanks for the help. My restore appears to be running nicely right now
so I think that fixed the problem.
"Rodney R. Fournier [MVP]" wrote:

> Move the G: Drive into the SQL Group (group 0 from you post).
> Stop the SQL clustered group.
> Double click SQL Server resource and add G: Drive as a dependency.
> Bring the SQL Group back online.
> Restore away
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://www.msmvps.com/clustering - Blog
>
> "ebferro" <ebferro@.discussions.microsoft.com> wrote in message
> news:24628F06-9C5C-4B4F-B7C6-50E82D24CF8F@.microsoft.com...
>
>

Cannot start DTC in Enterprise Mgr

Hello, experts!

On Sunday, as part of routine maintenance, we had to shut down our clustered servers. When we tried to bring them back up, they would not recognize our array unless we disabled the cluster service. It was agreed that we should disable the cluster service (it's caused nothing but problems due to poor implementation and vendor software support), but now we're having difficulties with SQL Server. We're having several "small" problems (i.e. unable to remove our old instance of SQL Server), but the main issue is that our client cannot connect to our server. They are able to ping us and connect to our development database (not affected by the failure), but cannot connect to the production database. Currently, the most obvious difference between production and development is that development displays a green icon (running) for both Distributed Transaction Coordinator and Full-Text Search in Support Services (Enterprise Mgr), whereas production has a red (stopped) icon for both. Also, we previously identified that MSDTC was not running and that it was inaccessible in Component Services, so we uninstalled and reinstalled. We were then able to access MSDTC in Component Services. That said, when I attempt to start DTC or Full-Text Search in Support Services, I receive the following error message:

An error 1722 - (The RPC server is unavailable) occurred while performing this service operation on the MSDTC service.

I've troubleshot this error message and verified that both RPC and DTC are started in the Services menu, that both services are set to start automatically and that both are using "Network Service" login. At this point, I have no idea what could possibly be causing this problem or if this could even be related to our client's inability to connect to our SQL database. We're running SQL Server 2000 SP4 on Win Server 2003 Dell machines. Any assistance is much appreciated.

Thanks!

Can you discuss what steps you took to disable the cluster service? Also, was this MSCS, Veritas Cluster or other?

When an instance is installed as clustered, the configuration is set up to only run under the cluster. This may be causing some of the troubles.

|||

Hi Kevin,

Thank you for the response. We're using MSCS. We disabled the Cluster Disk Driver in Device Manager, then disabled the Cluster Service in Services.

How would we go about utilizing a previously clustered server in a non-clustered capacity? Would we have to rebuild the server with a clean install of Windows Server and SQL Server?

|||

Did you cluster MS DTC? If not, that is most likely your issue. On a clustered implementation, DTC needs to be clustered as well. It's done at the OS level.

Try this: http://support.microsoft.com/kb/294209/ or http://support.microsoft.com/kb/243204/en-us