Showing posts with label node. Show all posts
Showing posts with label node. Show all posts

Wednesday, March 7, 2012

Cannot start SQLBrowser

Hi all,

Have a sql 2005 x64 sp2 2 node a/p cluster setup.

On both nodes it's not possible to start sqlbrowser service.

Compared registry and configuration on a 2nd equal system found no differences :-(

In eventlog I get:

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Warning: The configuration of the SQL instance MSSQLSERVER is not valid.

Error: The SQLBrowser service was unable to establish SQL instance and connectivity discovery. Data: 0000: 08 00 00 00

Info: The SQLBrowser is enabling SQL instance and connectivity discovery support.

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Info: The SQLBrowser service has started.

Info: The SQLBrowser service has shutdown.

Any help is highly appreciated.

TIA

acki

Hi,

Is your sql server browser service starting with a domain service accout?

|||

Yes, it's a domain account

Currently it is not into local admin group, but adding does not help.

|||

OK,

I tried to start sqlbroswer.exe manualy (sqlbrowser.exe -c) and getting the following output:

SQLBrowser: starting up in console mode

SQLBrowser: starting up SSRP redirection service

SQLBrowser is successfully listening on 0.0.0.0[1434]

SQLBrowser: failed starting SSRP redirection services -- shutting down.

Does this make someone flashing a light ?

TIA

Dan

|||

I am facing the same issue. Does anyone found a sloution for this problem?

Thanks

-Vikas

|||I've got the same problem...I've found a way to start SQLBrowser.

1. Bring offline SQL group(s) with Cluster Administrator
2. Delete on both cluster nodes these keys under Wow6432Node:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1]
and eventually
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.2]
if you have two instances.
3. Start SQLBrowser on both cluster nodes.
4. Bring online SQL group(s)

Anyway it's not a great solution everytime you bring online SQL Server service these keys under Wow6432Node are recreated and SQLBrowser doesn't start.

Hope it helps...

Alessandro

Cannot start SQLBrowser

Hi all,

Have a sql 2005 x64 sp2 2 node a/p cluster setup.

On both nodes it's not possible to start sqlbrowser service.

Compared registry and configuration on a 2nd equal system found no differences :-(

In eventlog I get:

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Warning: The configuration of the SQL instance MSSQLSERVER is not valid.

Error: The SQLBrowser service was unable to establish SQL instance and connectivity discovery. Data: 0000: 08 00 00 00

Info: The SQLBrowser is enabling SQL instance and connectivity discovery support.

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Info: The SQLBrowser service has started.

Info: The SQLBrowser service has shutdown.

Any help is highly appreciated.

TIA

acki

Hi,

Is your sql server browser service starting with a domain service accout?

|||

Yes, it's a domain account

Currently it is not into local admin group, but adding does not help.

|||

OK,

I tried to start sqlbroswer.exe manualy (sqlbrowser.exe -c) and getting the following output:

SQLBrowser: starting up in console mode

SQLBrowser: starting up SSRP redirection service

SQLBrowser is successfully listening on 0.0.0.0[1434]

SQLBrowser: failed starting SSRP redirection services -- shutting down.

Does this make someone flashing a light ?

TIA

Dan

|||

I am facing the same issue. Does anyone found a sloution for this problem?

Thanks

-Vikas

|||I've got the same problem...I've found a way to start SQLBrowser.

1. Bring offline SQL group(s) with Cluster Administrator
2. Delete on both cluster nodes these keys under Wow6432Node:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1]
and eventually
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.2]
if you have two instances.
3. Start SQLBrowser on both cluster nodes.
4. Bring online SQL group(s)

Anyway it's not a great solution everytime you bring online SQL Server service these keys under Wow6432Node are recreated and SQLBrowser doesn't start.

Hope it helps...

Alessandro

Cannot start SQLBrowser

Hi all,

Have a sql 2005 x64 sp2 2 node a/p cluster setup.

On both nodes it's not possible to start sqlbrowser service.

Compared registry and configuration on a 2nd equal system found no differences :-(

In eventlog I get:

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Warning: The configuration of the SQL instance MSSQLSERVER is not valid.

Error: The SQLBrowser service was unable to establish SQL instance and connectivity discovery. Data: 0000: 08 00 00 00

Info: The SQLBrowser is enabling SQL instance and connectivity discovery support.

Warning: The configuration of the SQL instance MSSQLServer is not valid.

Info: The SQLBrowser service has started.

Info: The SQLBrowser service has shutdown.

Any help is highly appreciated.

TIA

acki

Hi,

Is your sql server browser service starting with a domain service accout?

|||

Yes, it's a domain account

Currently it is not into local admin group, but adding does not help.

|||

OK,

I tried to start sqlbroswer.exe manualy (sqlbrowser.exe -c) and getting the following output:

SQLBrowser: starting up in console mode

SQLBrowser: starting up SSRP redirection service

SQLBrowser is successfully listening on 0.0.0.0[1434]

SQLBrowser: failed starting SSRP redirection services -- shutting down.

Does this make someone flashing a light ?

TIA

Dan

|||

I am facing the same issue. Does anyone found a sloution for this problem?

Thanks

-Vikas

|||I've got the same problem...I've found a way to start SQLBrowser.

1. Bring offline SQL group(s) with Cluster Administrator
2. Delete on both cluster nodes these keys under Wow6432Node:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1]
and eventually
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.2]
if you have two instances.
3. Start SQLBrowser on both cluster nodes.
4. Bring online SQL group(s)

Anyway it's not a great solution everytime you bring online SQL Server service these keys under Wow6432Node are recreated and SQLBrowser doesn't start.

Hope it helps...

Alessandro

Saturday, February 25, 2012

Cannot start Log Reader Agent and Snapshot Agent

I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.

For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).

This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"

Any ideas?

Also this domain account is a member of

SQLServer2005MSSQLUsers$ServerName$MSSQLSERVER

SQLServer2005MSAgentUser$ServerName$MSSQLSERVER


open the properties of each job and change the owner to sa and it should work fine.|||I tried it. No luck...it gives the same error message