Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts

Thursday, March 29, 2012

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

Tuesday, March 27, 2012

Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance

Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!

My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:

IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0

IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0

IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0

IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0

IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0

IPALL
TCP Dynamic Ports 2020
TCP Port 2020

Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?

I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.

I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?

Regards, Mike

2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.

I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.

In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).

To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:

0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS

1. Stop cluster service on all nodes

2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources

Change the following parameter from this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER

to this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion

on all nodes

3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP

4. Start the cluster service on all nodes.

5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)

6. Move this cluster group to all nodes and let it fail on all nodes.

6b. Verify that the TCP/IP parameters are still good on all nodes.

7. Take your group completely offline.

8. Revert the registry replication changes you made in step 2 back to what they should be.

9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.

10. cycle the SQL browser service on all nodes for good measure.

11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.

12. Verify that the SQL instance comes back on all nodes.

This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.

-EDF

This sucks Beavis.

|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||

Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.

UJ

|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||

Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.

If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:

1. move the failed instance to a node

2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll

3. checkpoint the cluster using the tool on that node

4. bring the instance on line

5. repeat this process on each node.

I hope this helps someone else!

|||Thanks for posting this solution. It worked like a charm for me.sql

Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance

Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!

My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:

IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0

IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0

IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0

IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0

IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0

IPALL
TCP Dynamic Ports 2020
TCP Port 2020

Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?

I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.

I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?

Regards, Mike

2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.

I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.

In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).

To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:

0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS

1. Stop cluster service on all nodes

2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources

Change the following parameter from this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER

to this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion

on all nodes

3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP

4. Start the cluster service on all nodes.

5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)

6. Move this cluster group to all nodes and let it fail on all nodes.

6b. Verify that the TCP/IP parameters are still good on all nodes.

7. Take your group completely offline.

8. Revert the registry replication changes you made in step 2 back to what they should be.

9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.

10. cycle the SQL browser service on all nodes for good measure.

11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.

12. Verify that the SQL instance comes back on all nodes.

This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.

-EDF

This sucks Beavis.

|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||

Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.

UJ

|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||

Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.

If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:

1. move the failed instance to a node

2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll

3. checkpoint the cluster using the tool on that node

4. bring the instance on line

5. repeat this process on each node.

I hope this helps someone else!

|||Thanks for posting this solution. It worked like a charm for me.

Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance

Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!

My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:

IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0

IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0

IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0

IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0

IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0

IPALL
TCP Dynamic Ports 2020
TCP Port 2020

Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?

I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.

I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?

Regards, Mike

2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.

I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.

In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).

To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:

0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS

1. Stop cluster service on all nodes

2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources

Change the following parameter from this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER

to this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion

on all nodes

3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP

4. Start the cluster service on all nodes.

5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)

6. Move this cluster group to all nodes and let it fail on all nodes.

6b. Verify that the TCP/IP parameters are still good on all nodes.

7. Take your group completely offline.

8. Revert the registry replication changes you made in step 2 back to what they should be.

9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.

10. cycle the SQL browser service on all nodes for good measure.

11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.

12. Verify that the SQL instance comes back on all nodes.

This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.

-EDF

This sucks Beavis.

|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||

Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.

UJ

|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||

Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.

If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:

1. move the failed instance to a node

2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll

3. checkpoint the cluster using the tool on that node

4. bring the instance on line

5. repeat this process on each node.

I hope this helps someone else!

|||Thanks for posting this solution. It worked like a charm for me.

Can't change TCP Port using configuration manager for x64 SQL 2005 SP1 virtual instance

Hi, I hope someone can help me! I changed the TCP port that the default instance of SQL 2005 x64 SP1 is listening on and now SQL server won't start as the port is being used - no problem I say to myself, I'll just change it again, however I can't!

My problem is that I can not change the TCP Port back again using Configuration Manager - no matter what values I put in, after a restart of the instance it comes up with this in the IP Addresses tab for TCP/IP Properties and SQL Server won't start:

IP1
Active Yes
Enabled No
IP Address aaa.bbb.ccc.111
TCP Dynamic Ports
TCP Port 0

IP2
Active Yes
Enabled No
IP Address aaa.bbb.ccc.222
TCP Dynamic Ports
TCP Port 0

IP3
Active Yes
Enabled No
IP Address aaa.bbb.ccc.333
TCP Dynamic Ports
TCP Port 0

IP4
Active Yes
Enabled No
IP Address 10.1.1.1
TCP Dynamic Ports
TCP Port 0

IP5
Active Yes
Enabled No
IP Address 127.0.0.1
TCP Dynamic Ports
TCP Port 0

IPALL
TCP Dynamic Ports 2020
TCP Port 2020

Interestingly, the ip address that the server is listening on aaa.bbb.ccc.444 is not reported in the list of IP addresses in the configuration manager for this instance, yet it is when I view the available IP addresses for the other two instances - is this significant?

I have tried failing to the other node, changing it there, changing it at the console and also while logged onto the the virtual machine remote desktop, rebooting both nodes, etc, etc. There are two other instances on this cluster that are still working fine but I hvae not attempted to change the TCP ports they listen on.

I used the same method to change this default instance as I did for a named instance on a similarly configured cluster and it worked fine. How to fix this?

Regards, Mike

2007-02-27 12:03:17.69 Server Server is listening on [ aaa.bbb.ccc.444<ipv4> 2020].
2007-02-27 12:03:17.71 spid9s Starting up database 'tempdb'.
2007-02-27 12:03:17.72 Server Error: 26023, Severity: 16, State: 1.
2007-02-27 12:03:17.72 Server Server TCP provider failed to listen on [ aaa.bbb.ccc.444<ipv4> 2020]. Tcp port is already in use.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0xa.
2007-02-27 12:03:17.75 Server Error: 17182, Severity: 16, State: 1.
2007-02-27 12:03:17.75 Server TDSSNIClient initialization failed with error 0x2740, status code 0x1.
2007-02-27 12:03:17.75 Server Error: 17826, Severity: 18, State: 3.
2007-02-27 12:03:17.75 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-02-27 12:03:17.77 Server Error: 17120, Severity: 16, State: 1.
2007-02-27 12:03:17.77 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

BWAHAHAHAHAHAHA!!!!! The same thing happened to me today! What a nightmare! I came about 10min away from nuking my virtual server instance and restoring 50+ databases. It was supposed to be such a simple change... I even tested it on a non-clustered box first. Oh well.

I had *exactly* the same setup as you, except 32bit. I think the problem was that I made the change on my passive node. My cluster has multiple instances spread over all nodes, but the virtual instance I was changing wasn't changed on the active node. I think that's what did me in.

In my situation, the IP settings I ented in caused the SQL Server instance to not start (too lazy to check the actual error at the moment). What happens is that the cluster service is configured to replicate the registry settings that govern the TCP/IP paramenters. If you edit the parameters incorrectly (or at least the way I did) then the cluster service continues to replicate those parameters to all nodes. Mind you, I used the SSCM too! The registry replication occurs when the cluster group changes nodes. If the SQL Server service does not start, then the cluster quorum logs never get cleared. In other words, the cluster doesn't think the registry params got applied correctly. No matter what you do to the registry on each node, the cluster quorum logs will continue to apply the replicated settings until SQL starts successfully (which never happens).

To fix it, I had to stop MSCS from replicating the bad registry params so that I could manually rebuild them. Here's how I did it, YMMV:

0. (I forgot a step) Set your broken SQL instance cluster resource to not restart automatically in MSCS

1. Stop cluster service on all nodes

2. Locate the SQL Server instance cluster resource you're having issues with here: HKLM\Cluster\Resources

Change the following parameter from this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER

to this:

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion

on all nodes

3. Fix the following registry branch on all nodes to what they were before (use your other instances as a guide if necessary):

Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\supersocketnetlib\TCP

4. Start the cluster service on all nodes.

5. SQL Server will not start because you've messed with the registry replication params. (but it'll be a different error than before)

6. Move this cluster group to all nodes and let it fail on all nodes.

6b. Verify that the TCP/IP parameters are still good on all nodes.

7. Take your group completely offline.

8. Revert the registry replication changes you made in step 2 back to what they should be.

9. Clean up Software\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLSERVER\CurrentVersion. (It'll be messed up from the forced registry replication. Do this on all nodes.

10. cycle the SQL browser service on all nodes for good measure.

11. Bring your broken SQL instance back to life. I had to cycle SQL Browser one more time while I was doing this.

12. Verify that the SQL instance comes back on all nodes.

This worked for me. Good luck. Oh, and for my gratification, how about you try changing the IP address parameters from the Active node using SSCM while SQL is up? Let me know it if works :) and I'll attempt it on my cluster again.

-EDF

This sucks Beavis.

|||Thanks EDF. This looks very promising. I actually made my changes while RDP'd to the virtual instance name so it must have been the active node but maybe making the change through Remote Desktop stuffed it. I'll give it a go tomorrow and try my IP config changes again from the active node at the console and let everyone know how it goes. Thanks again.|||I tried the above changes but it did not help. I am going to raise a call with MS Support and I'll post the resolution.|||

Gengleman, did either of you successfully change the IP address of the cluster? We are currently attempting this and although I did it once before I think I got lucky. I'd love to see the steps followed.

UJ

|||Yeah, I did. It turns out that "Listen on All IP Addresses" *really* means "Listen on All IP Addresses in the cluster group". Move all your SQL instances to one node. Log into that node and start the IP binding configuration tool, SSCM. Leave the entry for "listen all"=Yes (totally against all that is good & right in me...). I wanted all my SQL instances to listen on the same port (2048), but diff IP addresses. On the IP Addresses tab, I set all my IP addresses entries to Enabled=No. At the bottom, I set IPAll entry so that TCP Dynamic Ports was NULL (not 0) and TCP Port=2048. On start up, each SQL instance then only attempts to bind port 2048 to it's own IP address. Certainly NOT what I would have expected, but I suppose it makes sense.|||

Hi, I was trying to change the port, not the IP address, when somehow it got screwed up - I guess I mis-typed something. I ended up calling in PSS and they fixed it for me as I couldn't reproduce the fix that fischere suggested. It is very easy to screw up your TCP/IP config with the SSCM - the MS tech used it to corrupt his installation to reproduce my problem so it would be a good idea to play around with it on an environment that isn't important first and then make sure you follow the process exactly on your other instances.

If you end up screwing up the instance (by changing IP addresses, ports, etc) so that it won't start, you can reset it back to what it was using the Cluster Server Recovery Utility (ClusterRecovery.exe) which is available for download from the MS website. It's main purpose seems to be to recover from failed drives, but it has the ability to override the registry entries that cluster services wants to apply to a node using the "checkpoint" option. This allows you to overcome the problem of not being able to reset the values that the SSCM tries to write to the registry on each node because when you try and bring an instance on line or fail to another node the settings get restored from cluster services as fischere points out. To fix a failed instance using this tool, follow these steps:

1. move the failed instance to a node

2. change the registry settings to what they should be on that node, eg HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Tcp\IPAll

3. checkpoint the cluster using the tool on that node

4. bring the instance on line

5. repeat this process on each node.

I hope this helps someone else!

|||Thanks for posting this solution. It worked like a charm for me.

Can't back up Encryption Key

I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91

> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)

I have tried with passwords with different combination but none of them seem to help. Any ideas?

It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.

In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003

-Tudor

|||

Hi quantum_csfb

Have you had any luck resolving this?

I am getting the same error.

I am running XP Pro SP2.

Thanks.

|||

Gr8 :-)

Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine

Many Thx

|||

Hi

I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.

Any other suggestions?

Can't back up Encryption Key

I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91

> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)

I have tried with passwords with different combination but none of them seem to help. Any ideas?

It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.

In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003

-Tudor

|||

Hi quantum_csfb

Have you had any luck resolving this?

I am getting the same error.

I am running XP Pro SP2.

Thanks.

|||

Gr8 :-)

Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine

Many Thx

|||

Hi

I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.

Any other suggestions?

Can't back up Encryption Key

I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91

> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)

I have tried with passwords with different combination but none of them seem to help. Any ideas?

It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.

In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003

-Tudor

|||

Hi quantum_csfb

Have you had any luck resolving this?

I am getting the same error.

I am running XP Pro SP2.

Thanks.

|||

Gr8 :-)

Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine

Many Thx

|||

Hi

I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.

Any other suggestions?

Thursday, March 8, 2012

Cannot uninstall SQL Server Express

Hi!

I uninstalled Visual Studio 2005, but then I get this error when trying to uninstall SQL Express:

"The SQL Server System Configuration check cannot be executed due to WMI configuration on the machine XXX: Error: 2147746132 (0x80040154)"

I don't even know what WMI is!

I have these installed (none of which can I uninstall):

Microsoft SQl Server 2005

Microsoft SQl Server Mobile [ENU] Developer Tools

Microsoft SQl Server Native Client

Microsoft SQl Server Setup Support Files (English)

Microsoft SQl Server VSS Writer

Help!

It sounds like WMI is corrupted on your machine. First, make sure you still have .Net Framework 2.0 installed. If this is the case you should search http://support.microsoft.com for WMI errors. There are a few articles out there that discuss how to recover from a corrupted WMI state.|||

After much searching, I found the way to repair WMI here:

"Re-registering WMI"

http://blogs.msdn.com/smguest/archive/2005/03/18/398883.aspx

There are many potential fixes out there, but this one worked for me (fingers crossed).

Then, I had to download Windows Installer 3.1 from:

http://www.microsoft.com/downloads/Search.aspx?displaylang=en

Jess

Cannot uninstall SQL Server Express

Hi!

I uninstalled Visual Studio 2005, but then I get this error when trying to uninstall SQL Express:

"The SQL Server System Configuration check cannot be executed due to WMI configuration on the machine XXX: Error: 2147746132 (0x80040154)"

I don't even know what WMI is!

I have these installed (none of which can I uninstall):

Microsoft SQl Server 2005

Microsoft SQl Server Mobile [ENU] Developer Tools

Microsoft SQl Server Native Client

Microsoft SQl Server Setup Support Files (English)

Microsoft SQl Server VSS Writer

Help!

It sounds like WMI is corrupted on your machine. First, make sure you still have .Net Framework 2.0 installed. If this is the case you should search http://support.microsoft.com for WMI errors. There are a few articles out there that discuss how to recover from a corrupted WMI state.|||

After much searching, I found the way to repair WMI here:

"Re-registering WMI"

http://blogs.msdn.com/smguest/archive/2005/03/18/398883.aspx

There are many potential fixes out there, but this one worked for me (fingers crossed).

Then, I had to download Windows Installer 3.1 from:

http://www.microsoft.com/downloads/Search.aspx?displaylang=en

Jess

Wednesday, March 7, 2012

Cannot start SQL Server Browser

Hello,

I use SQL Server 2005 for multi-user access. In the Surface Area Configuration, I changed the protocol from TCP/IP to Named Pipes and restarted the service. Then I went to SQL Server Browser, stopped it and clicked on Start to restart. I am getting a message "An error occurred while performing this operation". I am not able to get the Browser started.

Any help would be greatly appreciated.

Check the Windows event log and report back with the errors listed by SQL Browser service this will help with diagnosis.|||

I checked the error log and found a few messages for SQL Browser. Here they are:

1. SQL Browser Service was unable to establish SQL instance and connectivity discovery
2. The SQL Browser service port was unavailable for listening, invalid
3. The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
4. The SQL Browser is enabling SQL instance and connectivity discovery support
5. The SQL Browser service has started
6. The SQL Browser service has shut down

|||

The key one is "The SQLBrowser service port is unavailable for listening, or invalid.".

So what happens is SQL Browser starts up and enumerates all network interfaces and attempts to bind to UDP port 1434 on each one found. If it cannot bind to any of the network interfaces, you will get the above error.

So run this from a command prompt first to locate the process id bound to UDP 1434 ->

netstat -aon -p UDP

Look for things bound to 1434, like for example PID 4736 below:

Proto Local Address Foreign Address State PID
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 1156
UDP 0.0.0.0:1025 *:* 1792
UDP 0.0.0.0:1026 *:* 1792
UDP 0.0.0.0:1027 *:* 1792
UDP 0.0.0.0:1434 *:* 4736
...

Next look up the PID in Task Manager to see what process this is. If it's a SQL Server process try shutting down all SQL Server instances and then restart SQL Browser. If it is some other process let me know what it is.

It is also possible that SQLBrowser did not find any network interfaces to bind to, for example if the computer has no NICs. Let me know if this is a NIC-less PC.

|||

check whether firewall is enabled on this machine.. check UDP port 1434 is excempted.... Refer http://msdn2.microsoft.com/en-us/library/ms165724.aspx

Madhu

|||Thank you Matt for your help. I tried the "netstat -aon -p UDP" command. The Windows 2000 Server does not seem to support the -o switch which shows the Process ID. I could only do "netstat -an -p UDP", without the "o". I can see that 1434 was listed, but do not know the process ID. How may I proceed?|||

Most likely it is another SQL Server service, do you see sqlservr.exe in the Task Manager? So go to control panel Services and stop all SQL Server services you see, then start SQL Browser. Once SQL Browser loads up it will automatically disable the other SQL Server services from binding to UDP 1434. Then you can restart the other SQL Server services. Look in Services for things like MSSQL$<Something> these are SQL Server instances.

Try running this from command prompt to find the running SQL Services (I think it might work on Windows 2000):

sc query | findstr /I "MSSQL"

Look for things like:

SERVICE_NAME: MSSQLSERVER

or

SERVICE_NAME: MSSQL$INSTANCE1

Then stop these services, start SQL Browser, then restart the SQL Services.

|||

I followed your suggestion and stopped the SQL Server services (MS SQL Server and SQL Server (SQLExpress). Then I was able to start the SQL Server Browser. Then I restarted the Database Engine Service from Surface Area Configuration. It is working fine and the client can connect.

Thank you very much. It was a great help.

|||Thank you Madhu for the information. Though it did not solve my problem, I find the information helpful.|||

Hi,

I am having a problem with starting the browser, I have checked the UDP port and it is certainly available.

I get this error repeated every 1 minute in the event log "The SQLBrowser is enabling SQL instance and connectivity discovery support." with a "SQLDmpr###.mdmp" dumped to C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps in a beautiful harmony with the events.

Does anyone have a clue as to what is happening here, this is the only server I have this problem with (SQL server 64bit Enterprise edition)

Many thanks

Mike

|||

Does not sound good. I'll check Watson to see if your dumps are showing up.

Check the event log to and post back with the messages from SQLBrowser service.

|||

Hey Matt, thanks for the response,

The browser service keeps repeating this error:

The SQLBrowser is enabling SQL instance and connectivity discovery support.

and this error

The SQL Server Browser service terminated unexpectedly. It has done this 45 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

If I run "sqlbrowser.exe -c" then I end up with an output like this:

C:\Program Files (x86)\Microsoft SQL Server\90\Shared>sqlbrowser -c
SQLBrowser: starting up in console mode
SQLBrowser: starting up SSRP redirection service
SQLBrowser is successfully listening on 0.0.0.0[1434]
[3608]: Waiting for next request...
[3600]: Waiting for next request...
[3616]: Waiting for next request...
[3612]: Waiting for next request...
[3608]: Received request...
[3600]: Received request...
[3608]: Waiting for next request...
SQLBrowser: starting up OLAP redirection service
[3600]: Waiting for next request...

then it crashes and leaves the dmp file.

Getting hard to see this one... there not that much that could get in the way right!? I have disabled windows firewall. Single instance is easily accessible. I had heard that KB910437 caused a conflict with the exe; have you heard of that before, so I tried removing that. no joy.

Cheers

Mike

|||

Looks like a problem with OLAP redirection dll. We host this in sqlbrowser. The dll is named msmdredir.dll and it's located in the C:\Program Files\Microsoft SQL Server\90\Shared folder. You could try as a temporary fix renaming this dll to msmdredir.dll_ but in general this looks like an invalid setup type issue.

|||

Matt,

That worked. I am amazed that it did... but it did.

How would an invalid setup have affected this? I have just run a fresh install and service packed to SP2, but this problem persisted.

I'm going to need that DLL though, this server is supposed to run analysis services and OLAP. Whatamigonnado?

Do you know what the setup validity error is?

Thanks for your help so far bud,

Great.

mike

|||

Most likely some runtime dependancy on the olap redirector dll did not get properly installed.

If you could send me one of these .mdmp files I can get this over to OLAP folks for diagnosis.

My email is mattn (at microsoft.com).

Cannot start SQL Server Browser

Hello,

I use SQL Server 2005 for multi-user access. In the Surface Area Configuration, I changed the protocol from TCP/IP to Named Pipes and restarted the service. Then I went to SQL Server Browser, stopped it and clicked on Start to restart. I am getting a message "An error occurred while performing this operation". I am not able to get the Browser started.

Any help would be greatly appreciated.

Check the Windows event log and report back with the errors listed by SQL Browser service this will help with diagnosis.|||

I checked the error log and found a few messages for SQL Browser. Here they are:

1. SQL Browser Service was unable to establish SQL instance and connectivity discovery
2. The SQL Browser service port was unavailable for listening, invalid
3. The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
4. The SQL Browser is enabling SQL instance and connectivity discovery support
5. The SQL Browser service has started
6. The SQL Browser service has shut down

|||

The key one is "The SQLBrowser service port is unavailable for listening, or invalid.".

So what happens is SQL Browser starts up and enumerates all network interfaces and attempts to bind to UDP port 1434 on each one found. If it cannot bind to any of the network interfaces, you will get the above error.

So run this from a command prompt first to locate the process id bound to UDP 1434 ->

netstat -aon -p UDP

Look for things bound to 1434, like for example PID 4736 below:

Proto Local Address Foreign Address State PID
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 1156
UDP 0.0.0.0:1025 *:* 1792
UDP 0.0.0.0:1026 *:* 1792
UDP 0.0.0.0:1027 *:* 1792
UDP 0.0.0.0:1434 *:* 4736
...

Next look up the PID in Task Manager to see what process this is. If it's a SQL Server process try shutting down all SQL Server instances and then restart SQL Browser. If it is some other process let me know what it is.

It is also possible that SQLBrowser did not find any network interfaces to bind to, for example if the computer has no NICs. Let me know if this is a NIC-less PC.

|||

check whether firewall is enabled on this machine.. check UDP port 1434 is excempted.... Refer http://msdn2.microsoft.com/en-us/library/ms165724.aspx

Madhu

|||Thank you Matt for your help. I tried the "netstat -aon -p UDP" command. The Windows 2000 Server does not seem to support the -o switch which shows the Process ID. I could only do "netstat -an -p UDP", without the "o". I can see that 1434 was listed, but do not know the process ID. How may I proceed?|||

Most likely it is another SQL Server service, do you see sqlservr.exe in the Task Manager? So go to control panel Services and stop all SQL Server services you see, then start SQL Browser. Once SQL Browser loads up it will automatically disable the other SQL Server services from binding to UDP 1434. Then you can restart the other SQL Server services. Look in Services for things like MSSQL$<Something> these are SQL Server instances.

Try running this from command prompt to find the running SQL Services (I think it might work on Windows 2000):

sc query | findstr /I "MSSQL"

Look for things like:

SERVICE_NAME: MSSQLSERVER

or

SERVICE_NAME: MSSQL$INSTANCE1

Then stop these services, start SQL Browser, then restart the SQL Services.

|||

I followed your suggestion and stopped the SQL Server services (MS SQL Server and SQL Server (SQLExpress). Then I was able to start the SQL Server Browser. Then I restarted the Database Engine Service from Surface Area Configuration. It is working fine and the client can connect.

Thank you very much. It was a great help.

|||Thank you Madhu for the information. Though it did not solve my problem, I find the information helpful.|||

Hi,

I am having a problem with starting the browser, I have checked the UDP port and it is certainly available.

I get this error repeated every 1 minute in the event log "The SQLBrowser is enabling SQL instance and connectivity discovery support." with a "SQLDmpr###.mdmp" dumped to C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps in a beautiful harmony with the events.

Does anyone have a clue as to what is happening here, this is the only server I have this problem with (SQL server 64bit Enterprise edition)

Many thanks

Mike

|||

Does not sound good. I'll check Watson to see if your dumps are showing up.

Check the event log to and post back with the messages from SQLBrowser service.

|||

Hey Matt, thanks for the response,

The browser service keeps repeating this error:

The SQLBrowser is enabling SQL instance and connectivity discovery support.

and this error

The SQL Server Browser service terminated unexpectedly. It has done this 45 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

If I run "sqlbrowser.exe -c" then I end up with an output like this:

C:\Program Files (x86)\Microsoft SQL Server\90\Shared>sqlbrowser -c
SQLBrowser: starting up in console mode
SQLBrowser: starting up SSRP redirection service
SQLBrowser is successfully listening on 0.0.0.0[1434]
[3608]: Waiting for next request...
[3600]: Waiting for next request...
[3616]: Waiting for next request...
[3612]: Waiting for next request...
[3608]: Received request...
[3600]: Received request...
[3608]: Waiting for next request...
SQLBrowser: starting up OLAP redirection service
[3600]: Waiting for next request...

then it crashes and leaves the dmp file.

Getting hard to see this one... there not that much that could get in the way right!? I have disabled windows firewall. Single instance is easily accessible. I had heard that KB910437 caused a conflict with the exe; have you heard of that before, so I tried removing that. no joy.

Cheers

Mike

|||

Looks like a problem with OLAP redirection dll. We host this in sqlbrowser. The dll is named msmdredir.dll and it's located in the C:\Program Files\Microsoft SQL Server\90\Shared folder. You could try as a temporary fix renaming this dll to msmdredir.dll_ but in general this looks like an invalid setup type issue.

|||

Matt,

That worked. I am amazed that it did... but it did.

How would an invalid setup have affected this? I have just run a fresh install and service packed to SP2, but this problem persisted.

I'm going to need that DLL though, this server is supposed to run analysis services and OLAP. Whatamigonnado?

Do you know what the setup validity error is?

Thanks for your help so far bud,

Great.

mike

|||

Most likely some runtime dependancy on the olap redirector dll did not get properly installed.

If you could send me one of these .mdmp files I can get this over to OLAP folks for diagnosis.

My email is mattn (at microsoft.com).

Saturday, February 25, 2012

Cannot start configuration manager on 1 of our active nodes

On one of our active nodes we cannot start the configuration manager but we
can start management studio.
We get the error message "Connection to target machine cannot be made in a
timely fashion". Any ideas on what causes this and how to fix?
Thanks
Is this for a Named Instance installation, on a non-standard port?
If so, then it probably works fine on the active node, but the remote node
times out?
Create a client-side alias on each node; sometimes the port resolution does
not work properly.
Are you running the SQL Browser service on each node?
Sincerely,
Anthony Thomas

"Randy" <Randy@.discussions.microsoft.com> wrote in message
news:A3FC4759-C823-400D-B9C0-651F5BA7BCD1@.microsoft.com...
> On one of our active nodes we cannot start the configuration manager but
we
> can start management studio.
> We get the error message "Connection to target machine cannot be made in a
> timely fashion". Any ideas on what causes this and how to fix?
> Thanks

Thursday, February 16, 2012

Cannot see SQL Server 2005 Services in SQL Server Configuration Manager

I cannot see any services within "SQL Server 2005 Services" in SQL Server Configuration Manager.

I am new to SQL Server 2005 and recently installed all of the SQL Server 2005 64-bit components on to a Windows 2003 64-bit server. I can create and view databases via SQL Server Management Studio. I can also start and stop the SQL Server service for the default instance via SQL Server Management Studio. But I should be able to start/stop the service via SQL Server Configuration Manager and I believe I'm supposed to use SQL Server Configuration Manager to make changes to the services.

I'm concerned that something may have become corrupted and is effected the SQL Server Configuration Manager. Any suggestions?

Thanks in advance,

Joann

I could not find any suggestions that resolved the problem directly. So I tried uninstalling and then reinstalling SQL Server 2005. I could uninstall it using Add/Remove Programs. But when I tried to reinstall it, it just hung while trying to prepare for the installation (before it even started the system configuration checks). So I ended up re-installing the Windows operating system.

Once the box was rebuilt, I was able to successfully install all of the SQL Server 2005 components. I can now properly view and modify the services within SQL Server Configuration Manager. I also no longer see the error message "library not registered" whenever I try to edit an existing maintenance plan.

Wish there had been a less destructive way to fix this problem, but rebuilding the box seemed to work.

Joann

|||

I have the same problem with a newly installed win2k3 with sql2k5.

Its kind of a big problem... because the server has been taken into production and I cannot just re-install it.

|||Hi all,

I've also encountered this problem. Freshly installed Win Server 2k3 Standard with SQL 2005 Standard + SP2, (9.0.3033). I have 2 of these servers and both have the same problem. I never realised SP2 was still in CTP but it's done now.

When trying to create / modify a Maintenance Plan locally, I get, "Library not registered", and remotely I get, "No such interface supported". When creating a plan using the wizard, it's works ok!

What's going on here?|||I have a similar problem with sql 2005 in a two node cluster. Config manager tool doesnt show me the status of analysis services and integration services. Any ideas?

Cannot see SQL Server 2005 Services in SQL Server Configuration Manager

I cannot see any services within "SQL Server 2005 Services" in SQL Server Configuration Manager.

I am new to SQL Server 2005 and recently installed all of the SQL Server 2005 64-bit components on to a Windows 2003 64-bit server. I can create and view databases via SQL Server Management Studio. I can also start and stop the SQL Server service for the default instance via SQL Server Management Studio. But I should be able to start/stop the service via SQL Server Configuration Manager and I believe I'm supposed to use SQL Server Configuration Manager to make changes to the services.

I'm concerned that something may have become corrupted and is effected the SQL Server Configuration Manager. Any suggestions?

Thanks in advance,

Joann

I could not find any suggestions that resolved the problem directly. So I tried uninstalling and then reinstalling SQL Server 2005. I could uninstall it using Add/Remove Programs. But when I tried to reinstall it, it just hung while trying to prepare for the installation (before it even started the system configuration checks). So I ended up re-installing the Windows operating system.

Once the box was rebuilt, I was able to successfully install all of the SQL Server 2005 components. I can now properly view and modify the services within SQL Server Configuration Manager. I also no longer see the error message "library not registered" whenever I try to edit an existing maintenance plan.

Wish there had been a less destructive way to fix this problem, but rebuilding the box seemed to work.

Joann

|||

I have the same problem with a newly installed win2k3 with sql2k5.

Its kind of a big problem... because the server has been taken into production and I cannot just re-install it.

|||Hi all,

I've also encountered this problem. Freshly installed Win Server 2k3 Standard with SQL 2005 Standard + SP2, (9.0.3033). I have 2 of these servers and both have the same problem. I never realised SP2 was still in CTP but it's done now.

When trying to create / modify a Maintenance Plan locally, I get, "Library not registered", and remotely I get, "No such interface supported". When creating a plan using the wizard, it's works ok!

What's going on here?
|||I have a similar problem with sql 2005 in a two node cluster. Config manager tool doesnt show me the status of analysis services and integration services. Any ideas?

Cannot see SQL Server 2005 Services in SQL Server Configuration Manager

I cannot see any services within "SQL Server 2005 Services" in SQL Server Configuration Manager.

I am new to SQL Server 2005 and recently installed all of the SQL Server 2005 64-bit components on to a Windows 2003 64-bit server. I can create and view databases via SQL Server Management Studio. I can also start and stop the SQL Server service for the default instance via SQL Server Management Studio. But I should be able to start/stop the service via SQL Server Configuration Manager and I believe I'm supposed to use SQL Server Configuration Manager to make changes to the services.

I'm concerned that something may have become corrupted and is effected the SQL Server Configuration Manager. Any suggestions?

Thanks in advance,

Joann

I could not find any suggestions that resolved the problem directly. So I tried uninstalling and then reinstalling SQL Server 2005. I could uninstall it using Add/Remove Programs. But when I tried to reinstall it, it just hung while trying to prepare for the installation (before it even started the system configuration checks). So I ended up re-installing the Windows operating system.

Once the box was rebuilt, I was able to successfully install all of the SQL Server 2005 components. I can now properly view and modify the services within SQL Server Configuration Manager. I also no longer see the error message "library not registered" whenever I try to edit an existing maintenance plan.

Wish there had been a less destructive way to fix this problem, but rebuilding the box seemed to work.

Joann

|||

I have the same problem with a newly installed win2k3 with sql2k5.

Its kind of a big problem... because the server has been taken into production and I cannot just re-install it.

|||Hi all,

I've also encountered this problem. Freshly installed Win Server 2k3 Standard with SQL 2005 Standard + SP2, (9.0.3033). I have 2 of these servers and both have the same problem. I never realised SP2 was still in CTP but it's done now.

When trying to create / modify a Maintenance Plan locally, I get, "Library not registered", and remotely I get, "No such interface supported". When creating a plan using the wizard, it's works ok!

What's going on here?|||I have a similar problem with sql 2005 in a two node cluster. Config manager tool doesnt show me the status of analysis services and integration services. Any ideas?

Cannot see SQL Server 2005 Services in SQL Server Configuration Manager

I cannot see any services within "SQL Server 2005 Services" in SQL Server Configuration Manager.

I am new to SQL Server 2005 and recently installed all of the SQL Server 2005 64-bit components on to a Windows 2003 64-bit server. I can create and view databases via SQL Server Management Studio. I can also start and stop the SQL Server service for the default instance via SQL Server Management Studio. But I should be able to start/stop the service via SQL Server Configuration Manager and I believe I'm supposed to use SQL Server Configuration Manager to make changes to the services.

I'm concerned that something may have become corrupted and is effected the SQL Server Configuration Manager. Any suggestions?

Thanks in advance,

Joann

I could not find any suggestions that resolved the problem directly. So I tried uninstalling and then reinstalling SQL Server 2005. I could uninstall it using Add/Remove Programs. But when I tried to reinstall it, it just hung while trying to prepare for the installation (before it even started the system configuration checks). So I ended up re-installing the Windows operating system.

Once the box was rebuilt, I was able to successfully install all of the SQL Server 2005 components. I can now properly view and modify the services within SQL Server Configuration Manager. I also no longer see the error message "library not registered" whenever I try to edit an existing maintenance plan.

Wish there had been a less destructive way to fix this problem, but rebuilding the box seemed to work.

Joann

|||

I have the same problem with a newly installed win2k3 with sql2k5.

Its kind of a big problem... because the server has been taken into production and I cannot just re-install it.

|||Hi all,

I've also encountered this problem. Freshly installed Win Server 2k3 Standard with SQL 2005 Standard + SP2, (9.0.3033). I have 2 of these servers and both have the same problem. I never realised SP2 was still in CTP but it's done now.

When trying to create / modify a Maintenance Plan locally, I get, "Library not registered", and remotely I get, "No such interface supported". When creating a plan using the wizard, it's works ok!

What's going on here?|||I have a similar problem with sql 2005 in a two node cluster. Config manager tool doesnt show me the status of analysis services and integration services. Any ideas?

Cannot see SQL Server 2005 Services in SQL Server Configuration Manager

I cannot see any services within "SQL Server 2005 Services" in SQL Server Configuration Manager.

I am new to SQL Server 2005 and recently installed all of the SQL Server 2005 64-bit components on to a Windows 2003 64-bit server. I can create and view databases via SQL Server Management Studio. I can also start and stop the SQL Server service for the default instance via SQL Server Management Studio. But I should be able to start/stop the service via SQL Server Configuration Manager and I believe I'm supposed to use SQL Server Configuration Manager to make changes to the services.

I'm concerned that something may have become corrupted and is effected the SQL Server Configuration Manager. Any suggestions?

Thanks in advance,

Joann

I could not find any suggestions that resolved the problem directly. So I tried uninstalling and then reinstalling SQL Server 2005. I could uninstall it using Add/Remove Programs. But when I tried to reinstall it, it just hung while trying to prepare for the installation (before it even started the system configuration checks). So I ended up re-installing the Windows operating system.

Once the box was rebuilt, I was able to successfully install all of the SQL Server 2005 components. I can now properly view and modify the services within SQL Server Configuration Manager. I also no longer see the error message "library not registered" whenever I try to edit an existing maintenance plan.

Wish there had been a less destructive way to fix this problem, but rebuilding the box seemed to work.

Joann

|||

I have the same problem with a newly installed win2k3 with sql2k5.

Its kind of a big problem... because the server has been taken into production and I cannot just re-install it.

|||Hi all,

I've also encountered this problem. Freshly installed Win Server 2k3 Standard with SQL 2005 Standard + SP2, (9.0.3033). I have 2 of these servers and both have the same problem. I never realised SP2 was still in CTP but it's done now.

When trying to create / modify a Maintenance Plan locally, I get, "Library not registered", and remotely I get, "No such interface supported". When creating a plan using the wizard, it's works ok!

What's going on here?
|||I have a similar problem with sql 2005 in a two node cluster. Config manager tool doesnt show me the status of analysis services and integration services. Any ideas?

Cannot see security certificates

Having installed a certificate from Verisign via the MMC certificate snapin
when I go to SQL Server Configuration Manager in SQL 2005 there are no
certificates visible in the drop down box. (as per
http://msdn2.microsoft.com/en-us/library/ms189067.aspx
Does anyone have experience with this? I have double checked with a
verisign tech that i have the certificates in the correct store etc.
Andrew Prior
Hi Andrew
"Andrew Prior" wrote:

> Having installed a certificate from Verisign via the MMC certificate snapin
> when I go to SQL Server Configuration Manager in SQL 2005 there are no
> certificates visible in the drop down box. (as per
> http://msdn2.microsoft.com/en-us/library/ms189067.aspx
> Does anyone have experience with this? I have double checked with a
> verisign tech that i have the certificates in the correct store etc.
> Andrew Prior
I assume that it does satisfy the certificate requirements as described in
the link you posted?
John
|||Yes, sad to say! I checked this very thorougly with Verisign, as it was my
first suspicion!
Andrew
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:8ADC2E67-9716-4BC6-B90B-1CE49DBC7838@.microsoft.com...
> Hi Andrew
> "Andrew Prior" wrote:
>
> I assume that it does satisfy the certificate requirements as described in
> the link you posted?
> John
|||Hi Andrew
"Andrew Prior" wrote:
[vbcol=seagreen]
> Yes, sad to say! I checked this very thorougly with Verisign, as it was my
> first suspicion!
> Andrew
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:8ADC2E67-9716-4BC6-B90B-1CE49DBC7838@.microsoft.com...
Apart from the fall back of cycling the box I am not sure if there is
anything else I could suggest!
John