Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIA
check 1434
and
delete
HKLM\software\microsoft\mssqlserver\client\superso cketnetlib\lastconnect key
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>
|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supers ocketnetlib\lastconnect key
><sql server name or ip>
I will try that, thanks.
[vbcol=seagreen]
>"vze78se7@.verizon.net" wrote:
|||
>check 1434
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supers ocketnetlib\lastconnect key
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?
|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
>
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Thursday, March 22, 2012
changing TCP/IP port breaks "local" connection
Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
I will try that, thanks.
>"vze78se7@.verizon.net" wrote:
>> Hi All:
>> I wanted to change the TCP/IP port a default instance of SQL was
>> running on (from 1433 to something random like 49576) on Win2K AS
>> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
>> MDAC 2.8 is installed.
>> The server has a base IP of 192.168.1.190 and a website running on
>> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
>> database using "local" for the server name.
>> This all runs fine when the SQL server's on 1433, but if I change it
>> to another port, it breaks the connection from the website to the SQL
>> server. Restarting services doesn't help, even rebooting doesn't
>> restore the connection. If I switch the SQL Server back to 1433 it
>> runs fine.
>> I tested the same thing on a server running Win2003, and the website
>> didn't have a problem connecting to the SQL server when I changed the
>> TCP/IP port.
>> Any ideas why this breaks on Win2K?
>> TIA|||>check 1434
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
> >check 1434
> >and
> >delete
> >HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
> ><sql server name or ip>
> >
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>sql
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
I will try that, thanks.
>"vze78se7@.verizon.net" wrote:
>> Hi All:
>> I wanted to change the TCP/IP port a default instance of SQL was
>> running on (from 1433 to something random like 49576) on Win2K AS
>> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
>> MDAC 2.8 is installed.
>> The server has a base IP of 192.168.1.190 and a website running on
>> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
>> database using "local" for the server name.
>> This all runs fine when the SQL server's on 1433, but if I change it
>> to another port, it breaks the connection from the website to the SQL
>> server. Restarting services doesn't help, even rebooting doesn't
>> restore the connection. If I switch the SQL Server back to 1433 it
>> runs fine.
>> I tested the same thing on a server running Win2003, and the website
>> didn't have a problem connecting to the SQL server when I changed the
>> TCP/IP port.
>> Any ideas why this breaks on Win2K?
>> TIA|||>check 1434
>and
>delete
>HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
> >check 1434
> >and
> >delete
> >HKLM\software\microsoft\mssqlserver\client\supersocketnetlib\lastconnect key
> ><sql server name or ip>
> >
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>sql
changing TCP/IP port breaks "local" connection
Hi All:
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect ke
y
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
I will try that, thanks.
[vbcol=seagreen]
>"vze78se7@.verizon.net" wrote:
>|||
>check 1434
>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
>
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>
I wanted to change the TCP/IP port a default instance of SQL was
running on (from 1433 to something random like 49576) on Win2K AS
(sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
MDAC 2.8 is installed.
The server has a base IP of 192.168.1.190 and a website running on
192.168.1.191. The website uses a SQL0LEDB.1 connection to the
database using "local" for the server name.
This all runs fine when the SQL server's on 1433, but if I change it
to another port, it breaks the connection from the website to the SQL
server. Restarting services doesn't help, even rebooting doesn't
restore the connection. If I switch the SQL Server back to 1433 it
runs fine.
I tested the same thing on a server running Win2003, and the website
didn't have a problem connecting to the SQL server when I changed the
TCP/IP port.
Any ideas why this breaks on Win2K?
TIAcheck 1434
and
delete
HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect ke
y
<sql server name or ip>
"vze78se7@.verizon.net" wrote:
> Hi All:
> I wanted to change the TCP/IP port a default instance of SQL was
> running on (from 1433 to something random like 49576) on Win2K AS
> (sp4+). SQL's got TCP/IP and NamedPipes libraries active. I believe
> MDAC 2.8 is installed.
> The server has a base IP of 192.168.1.190 and a website running on
> 192.168.1.191. The website uses a SQL0LEDB.1 connection to the
> database using "local" for the server name.
> This all runs fine when the SQL server's on 1433, but if I change it
> to another port, it breaks the connection from the website to the SQL
> server. Restarting services doesn't help, even rebooting doesn't
> restore the connection. If I switch the SQL Server back to 1433 it
> runs fine.
> I tested the same thing on a server running Win2003, and the website
> didn't have a problem connecting to the SQL server when I changed the
> TCP/IP port.
> Any ideas why this breaks on Win2K?
> TIA
>|||On Mon, 24 Jan 2005 06:05:04 -0800, "Aleksandar Grbic"
<AleksandarGrbic@.discussions.microsoft.com> wrote:
>check 1434
Thanks, Alexsandar. What do you mean by "check 1434"? I have TCP/UDP
1434 disabled because I don't want to broadcast or receive on the
"slammer" port.
>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
I will try that, thanks.
[vbcol=seagreen]
>"vze78se7@.verizon.net" wrote:
>|||
>check 1434
>and
>delete
> HKLM\software\microsoft\mssqlserver\clie
nt\supersocketnetlib\lastconnect k
ey
><sql server name or ip>
>
One other question...Can I avoid this problem by using Named Pipes?
I will only ever be connecting to the local machine from this
website. I thought using "(local)" for the server bypassed TCP/IP
altogether?
Or does this problem have nothing to do with TCP/IP?|||configure alias in client network utility on client
make alias for sql server in alias tab, write sql server alias, sql name and
tcp/ip port
or
make alias with named pipe
"vze78se7@.verizon.net" wrote:
>
> One other question...Can I avoid this problem by using Named Pipes?
> I will only ever be connecting to the local machine from this
> website. I thought using "(local)" for the server bypassed TCP/IP
> altogether?
> Or does this problem have nothing to do with TCP/IP?
>
Monday, March 19, 2012
Changing SQL Domain Account
I need to change the domain account our SQL cluster is running under. The
cluster is Win2k with a single instance of SQL 2000.
I looked in the cluster Administrator and I don't see where it is specified.
Do I use the services applet in control panel to specify the user for
cluster service? I found for SQL in Enterprise manager I can specify the
user there. Is that where I change the SQL user?
I'm thinking...
- Change the user for SQL in Enterprise Manager
- Stop SQL and the Cluster Service
- Change the user for Cluster Service in Control Panel
- Restart Cluster Service
- Restart SQL
Would this be right? Thanks in advance.
You are in luck. Microsoft has a document detailing exactly how to do this.
How to change service accounts for a clustered SQL Server computer
http://support.microsoft.com/kb/239885/en-us
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sam" <sam@.nospam.com> wrote in message
news:AqaZf.3719$i41.904@.newsread1.news.atl.earthli nk.net...
>I need to change the domain account our SQL cluster is running under. The
> cluster is Win2k with a single instance of SQL 2000.
> I looked in the cluster Administrator and I don't see where it is
> specified.
> Do I use the services applet in control panel to specify the user for
> cluster service? I found for SQL in Enterprise manager I can specify the
> user there. Is that where I change the SQL user?
> I'm thinking...
> - Change the user for SQL in Enterprise Manager
> - Stop SQL and the Cluster Service
> - Change the user for Cluster Service in Control Panel
> - Restart Cluster Service
> - Restart SQL
> Would this be right? Thanks in advance.
>
>
|||Thanks for the link. I'm trying to verify if the policies specified in the
article are indeed set for the new account we plan to use. We have already
setup a new Win_2003/SQL_2005 cluster with the new account so my guess it
the account is ok and ready to go.
The article doesn't really give a process however, other than making sure
the change to the SQL service is made with Enterprise Manager. I'm still
not sure where to change the cluster service account, except to guess about
using the Services applet in Control Panel. Is this right?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23$u90$YWGHA.4768@.TK2MSFTNGP05.phx.gbl...
> You are in luck. Microsoft has a document detailing exactly how to do
this.[vbcol=seagreen]
> How to change service accounts for a clustered SQL Server computer
> http://support.microsoft.com/kb/239885/en-us
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Sam" <sam@.nospam.com> wrote in message
> news:AqaZf.3719$i41.904@.newsread1.news.atl.earthli nk.net...
The[vbcol=seagreen]
the
>
|||Enterprise Manager lets you change the SQL service account directly. Do not
use the services applet to change account information in a clustered
environment. EM sets the account properties correctly on each node when you
make the change. EM is also cluster-aware and changes all the nodes at
once.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sam" <sam@.nospam.com> wrote in message
news:JzbZf.1275$Es3.1066@.newsread3.news.atl.earthl ink.net...
> Thanks for the link. I'm trying to verify if the policies specified in
> the
> article are indeed set for the new account we plan to use. We have
> already
> setup a new Win_2003/SQL_2005 cluster with the new account so my guess it
> the account is ok and ready to go.
> The article doesn't really give a process however, other than making sure
> the change to the SQL service is made with Enterprise Manager. I'm still
> not sure where to change the cluster service account, except to guess
> about
> using the Services applet in Control Panel. Is this right?
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23$u90$YWGHA.4768@.TK2MSFTNGP05.phx.gbl...
> this.
> The
> the
>
cluster is Win2k with a single instance of SQL 2000.
I looked in the cluster Administrator and I don't see where it is specified.
Do I use the services applet in control panel to specify the user for
cluster service? I found for SQL in Enterprise manager I can specify the
user there. Is that where I change the SQL user?
I'm thinking...
- Change the user for SQL in Enterprise Manager
- Stop SQL and the Cluster Service
- Change the user for Cluster Service in Control Panel
- Restart Cluster Service
- Restart SQL
Would this be right? Thanks in advance.
You are in luck. Microsoft has a document detailing exactly how to do this.
How to change service accounts for a clustered SQL Server computer
http://support.microsoft.com/kb/239885/en-us
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sam" <sam@.nospam.com> wrote in message
news:AqaZf.3719$i41.904@.newsread1.news.atl.earthli nk.net...
>I need to change the domain account our SQL cluster is running under. The
> cluster is Win2k with a single instance of SQL 2000.
> I looked in the cluster Administrator and I don't see where it is
> specified.
> Do I use the services applet in control panel to specify the user for
> cluster service? I found for SQL in Enterprise manager I can specify the
> user there. Is that where I change the SQL user?
> I'm thinking...
> - Change the user for SQL in Enterprise Manager
> - Stop SQL and the Cluster Service
> - Change the user for Cluster Service in Control Panel
> - Restart Cluster Service
> - Restart SQL
> Would this be right? Thanks in advance.
>
>
|||Thanks for the link. I'm trying to verify if the policies specified in the
article are indeed set for the new account we plan to use. We have already
setup a new Win_2003/SQL_2005 cluster with the new account so my guess it
the account is ok and ready to go.
The article doesn't really give a process however, other than making sure
the change to the SQL service is made with Enterprise Manager. I'm still
not sure where to change the cluster service account, except to guess about
using the Services applet in Control Panel. Is this right?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23$u90$YWGHA.4768@.TK2MSFTNGP05.phx.gbl...
> You are in luck. Microsoft has a document detailing exactly how to do
this.[vbcol=seagreen]
> How to change service accounts for a clustered SQL Server computer
> http://support.microsoft.com/kb/239885/en-us
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Sam" <sam@.nospam.com> wrote in message
> news:AqaZf.3719$i41.904@.newsread1.news.atl.earthli nk.net...
The[vbcol=seagreen]
the
>
|||Enterprise Manager lets you change the SQL service account directly. Do not
use the services applet to change account information in a clustered
environment. EM sets the account properties correctly on each node when you
make the change. EM is also cluster-aware and changes all the nodes at
once.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Sam" <sam@.nospam.com> wrote in message
news:JzbZf.1275$Es3.1066@.newsread3.news.atl.earthl ink.net...
> Thanks for the link. I'm trying to verify if the policies specified in
> the
> article are indeed set for the new account we plan to use. We have
> already
> setup a new Win_2003/SQL_2005 cluster with the new account so my guess it
> the account is ok and ready to go.
> The article doesn't really give a process however, other than making sure
> the change to the SQL service is made with Enterprise Manager. I'm still
> not sure where to change the cluster service account, except to guess
> about
> using the Services applet in Control Panel. Is this right?
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23$u90$YWGHA.4768@.TK2MSFTNGP05.phx.gbl...
> this.
> The
> the
>
Subscribe to:
Posts (Atom)