Eternal 'Enable Pending' on SQL2005

Hi!

I have this problem... im kinda new to sql2005, and im responsible for creating some notification services.

Ive done a lot of tutorials, books and samples and every time, when i reach the step of enabling the instance, i get this...

Generator-Enable Pending

Distributor-Enable Pending

Even doing the Microsoft's Notification Services Tutorial.

Ive tried everything I could figure, registering the instance with a user with every permission there could be... doing this local or on a client... and ive been 2 weeks stuck here...

Any tip or clue will be thankfull.

M.Eng.Leandro Melendez

Have you started the Windows Service for the instance? If you enable an instance when the service hasn't been started, it'll report a status of pending.

HTH...

|||

Well, i thought that i should start the windows service after enabling the instance... but ive tried also that, ive already tried to start it from the 'SQL Server MAngment Studio' and from 'Services' and both of them give me this message:

TITLE: System.ServiceProcess
Cannot start service NS$Tutorial on computer 'CROSS-AIPZ'.

ADDITIONAL INFORMATION:

The service did not respond to the start or control request in a timely fashion

Any clue what does this means?

|||

That's usually a permissions problem. Check to make sure that the service account has the appropriate permissions in the NS databases.

HTH...

|||Ive tried to give the user the permissions that the tutorial says, also ive tried to give the user every permission i could imagine... and nothing.... do you know what permissions i must give? maybe the tutorial is missing some one|||

Generally speaking, you want to make the login account used by the NS$InstanceName service (either window or SQL Server) a member of the NSRunService database role.

Check out this page in BOL for more detail.

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/5a70a24c-25cf-4b77-a3a3-1cdf696d9262.htm

HTH...

Joe

|||

Here's another BOL link that may help, too.

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/sqlntsv9/html/c20ece76-eca0-463d-a226-ba8e93c9fcb9.htm

Joe

|||

Yeah, i did that and everything i could...

After many searches ive found a comment saying that everything worked after reinstalling sql server 2005...

I did it, ununstall and install... and guess what... it just worked smoothly... any idea why does this happends?

Aniway thanks all

|||

Ouch! That's a pretty drastic step! Glad it worked and thanks for posting the solution.

Haven't had that problem before (thank goodness), so no...no idea what's going on there.

Joe

Establish log dhipping db in sql2005

Hi all
I have db on my log shipping server as standby\readonly and my transaction log
was out of sync, I would like to make full bak from the source server and
restore
on log shipping server but when I right click the db in sql manager studio
the RESTORE database option DIM out. I can do this with sql 2000 to
reestablish
db when my transaction log was out of sync but look like I can't do this
with sql 2005. Have i missed any thing here?
Please help
Thanks in advancedfrank
Personally I have not played yet with it on SQL Server 2005 , but can you
issue BACKUP/RESTORE in the query builder instead of SSMS?
"frank" <frank@.discussions.microsoft.com> wrote in message
news:752AC215-1833-4B97-B57C-2E52C646D6BF@.microsoft.com...
> Hi all
> I have db on my log shipping server as standby\readonly and my transaction
> log
> was out of sync, I would like to make full bak from the source server and
> restore
> on log shipping server but when I right click the db in sql manager studio
> the RESTORE database option DIM out. I can do this with sql 2000 to
> reestablish
> db when my transaction log was out of sync but look like I can't do this
> with sql 2005. Have i missed any thing here?
> Please help
> Thanks in advanced

Establish log dhipping db in sql2005

Hi all
I have db on my log shipping server as standby\readonly and my transaction log
was out of sync, I would like to make full bak from the source server and
restore
on log shipping server but when I right click the db in sql manager studio
the RESTORE database option DIM out. I can do this with sql 2000 to
reestablish
db when my transaction log was out of sync but look like I can't do this
with sql 2005. Have i missed any thing here?
Please help
Thanks in advanced
frank
Personally I have not played yet with it on SQL Server 2005 , but can you
issue BACKUP/RESTORE in the query builder instead of SSMS?
"frank" <frank@.discussions.microsoft.com> wrote in message
news:752AC215-1833-4B97-B57C-2E52C646D6BF@.microsoft.com...
> Hi all
> I have db on my log shipping server as standby\readonly and my transaction
> log
> was out of sync, I would like to make full bak from the source server and
> restore
> on log shipping server but when I right click the db in sql manager studio
> the RESTORE database option DIM out. I can do this with sql 2000 to
> reestablish
> db when my transaction log was out of sync but look like I can't do this
> with sql 2005. Have i missed any thing here?
> Please help
> Thanks in advanced

Establish log dhipping db in sql2005

Hi all
I have db on my log shipping server as standby\readonly and my transaction l
og
was out of sync, I would like to make full bak from the source server and
restore
on log shipping server but when I right click the db in sql manager studio
the RESTORE database option DIM out. I can do this with sql 2000 to
reestablish
db when my transaction log was out of sync but look like I can't do this
with sql 2005. Have i missed any thing here?
Please help
Thanks in advancedfrank
Personally I have not played yet with it on SQL Server 2005 , but can you
issue BACKUP/RESTORE in the query builder instead of SSMS?
"frank" <frank@.discussions.microsoft.com> wrote in message
news:752AC215-1833-4B97-B57C-2E52C646D6BF@.microsoft.com...
> Hi all
> I have db on my log shipping server as standby\readonly and my transaction
> log
> was out of sync, I would like to make full bak from the source server and
> restore
> on log shipping server but when I right click the db in sql manager studio
> the RESTORE database option DIM out. I can do this with sql 2000 to
> reestablish
> db when my transaction log was out of sync but look like I can't do this
> with sql 2005. Have i missed any thing here?
> Please help
> Thanks in advanced

Errors with combined use of transactional and merge replication - SQL2005

I am investigating the feasibility of a configuration with 3 databases on SQL2005

DB_A is an OLTP database and serves up transactional publication pub_txn - with updateable subscriptions

DB_B is a subscriber database which subscribes to pub_txn

DB_B is also a publisher which serves up merge publication pub_merge

DB_C is a subscriber database which pulls pub_merge

===============================

Updates on DB_A are successfully replicated to DB_B

Howvever, when DB_C pulls updates, it doesn't find the update sent to DB_B

===============================

Updates on DB_B are successfully replicated to both DB_A and DB_C

===============================

Updates on DB_C initially failed with the error

Msg 916, Level 14, State 1, Procedure trg_MSsync_upd_course_type, Line 0
The server principal "repllinkproxy" is not able to access the database
"DB_C" under the current security context.

I then changed the login repllinkproxy to be a db_owner in DB_C

I now get the error

Msg 208, Level 16, State 1, Procedure sp_check_sync_trigger, Line 23
Invalid object name 'dbo.MSreplication_objects'.

=================================

I have three questions as a result
1) Is there anything fundamentally wrong with what I am trying to achieve?

2) Why is update on DB_A not reaching DB_C

3) Why can't I update DB_C?

Any suggestions gratefully received

aero1

Just to clarify - I am replicating the same table between all the databases - without any filtering|||quick question - in which order did you create the publications/subscriptions? For the tran pub, are you using immediate updating subscriber, or queue updating subscriber?|||

Setup order was:

1) Transactional publication

2) Transactional subscription (immediate updating)

3) Merge publication

4) Merge subscription

|||

Some progress:

I have got rid of the errors on updating DB_C

- My initial setup was unrepresentative with all the databases, DB_A, DB_B and DB_C on the same server

- I dropped and recreated the whole setup with DB_C on a separate machine - which is more representative of what I am ultimately trying to achieve

- There were then no errors when attempting to update DB_C

However, updates on DB_A don't reach DB_C and updates on DB_C don't reach DB_A.

Updates on DB_B reach DB_A and DB_C OK

|||

Hi aero1, republishing is not supported when using updatable subscriptions, this is documented in SQL 2005 Books Online topic "Updatable Subscriptions for Transactional Replication". Your best bet is to implement Peer-to-Peer instead of updatable subscriptions.

|||

Hi Greg

Thanks - I am investigating peer to peer

aero1

|||

Hello *,

I have a problem very similar to this post, so I don’t open a new thread. The only different think is I use transactional publication WITHOUT updateable subscriptions.

I can cascade n SQL Servers 2005 and every update, insert and delete command change every beneath Database (already described by aero1). Because the end-users work with mobile clients the last Replication must be from type Merge. When I change some data on the top level server these changes comes only to the last transactional subscriber:

Example:

ServerA.DBA ===TR==>ServerB.DBB==TR==>ServerC.DBC==MR==>MobileDB

When I change a datarow on DBB the changes are available on DBC but not on MobileDB (after pull the data from there).

I hope someone can help me

Regards

Markus

|||

You need to set this article property to true: published_in_tran_pub

See the articles below and that should solve your problem of merge subscribers not receiving the data changes. However note that if you make updates at the merge subscribers, they will not flow all the way to the Tran root publisher and can cause non-convergence.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl_11et.asp

http://msdn2.microsoft.com/en-us/library/ms152559.aspx

|||

The issues that I had only involved 2 databases communicating with transactional replication - with merge subscribers hanging off one of these

For this scenario, bidirectional transactional replication seems to work well - but customisation of the replication stored procs is needed to handle conflicts.

Markus appears to have 3 databases communicating with transactional replication. I am not sure whether a chain of 3 bidirectionally replicating databases would work, but I can't think of any reason why it shouldn't. If it did then the merge changes would flow back to the root tran publisher.

Note that peer to peer wouldn't work in my scenario because the updates could not be partitioned suitably

Errors with combined use of transactional and merge replication - SQL2005

I am investigating the feasibility of a configuration with 3 databases on SQL2005

DB_A is an OLTP database and serves up transactional publication pub_txn - with updateable subscriptions

DB_B is a subscriber database which subscribes to pub_txn

DB_B is also a publisher which serves up merge publication pub_merge

DB_C is a subscriber database which pulls pub_merge

===============================

Updates on DB_A are successfully replicated to DB_B

Howvever, when DB_C pulls updates, it doesn't find the update sent to DB_B

===============================

Updates on DB_B are successfully replicated to both DB_A and DB_C

===============================

Updates on DB_C initially failed with the error

Msg 916, Level 14, State 1, Procedure trg_MSsync_upd_course_type, Line 0
The server principal "repllinkproxy" is not able to access the database
"DB_C" under the current security context.

I then changed the login repllinkproxy to be a db_owner in DB_C

I now get the error

Msg 208, Level 16, State 1, Procedure sp_check_sync_trigger, Line 23
Invalid object name 'dbo.MSreplication_objects'.

=================================

I have three questions as a result
1) Is there anything fundamentally wrong with what I am trying to achieve?

2) Why is update on DB_A not reaching DB_C

3) Why can't I update DB_C?

Any suggestions gratefully received

aero1

Just to clarify - I am replicating the same table between all the databases - without any filtering|||quick question - in which order did you create the publications/subscriptions? For the tran pub, are you using immediate updating subscriber, or queue updating subscriber?|||

Setup order was:

1) Transactional publication

2) Transactional subscription (immediate updating)

3) Merge publication

4) Merge subscription

|||

Some progress:

I have got rid of the errors on updating DB_C

- My initial setup was unrepresentative with all the databases, DB_A, DB_B and DB_C on the same server

- I dropped and recreated the whole setup with DB_C on a separate machine - which is more representative of what I am ultimately trying to achieve

- There were then no errors when attempting to update DB_C

However, updates on DB_A don't reach DB_C and updates on DB_C don't reach DB_A.

Updates on DB_B reach DB_A and DB_C OK

|||

Hi aero1, republishing is not supported when using updatable subscriptions, this is documented in SQL 2005 Books Online topic "Updatable Subscriptions for Transactional Replication". Your best bet is to implement Peer-to-Peer instead of updatable subscriptions.

|||

Hi Greg

Thanks - I am investigating peer to peer

aero1

|||

Hello *,

I have a problem very similar to this post, so I don’t open a new thread. The only different think is I use transactional publication WITHOUT updateable subscriptions.

I can cascade n SQL Servers 2005 and every update, insert and delete command change every beneath Database (already described by aero1). Because the end-users work with mobile clients the last Replication must be from type Merge. When I change some data on the top level server these changes comes only to the last transactional subscriber:

Example:

ServerA.DBA ===TR==>ServerB.DBB==TR==>ServerC.DBC==MR==>MobileDB

When I change a datarow on DBB the changes are available on DBC but not on MobileDB (after pull the data from there).

I hope someone can help me

Regards

Markus

|||

You need to set this article property to true: published_in_tran_pub

See the articles below and that should solve your problem of merge subscribers not receiving the data changes. However note that if you make updates at the merge subscribers, they will not flow all the way to the Tran root publisher and can cause non-convergence.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_repl_11et.asp

http://msdn2.microsoft.com/en-us/library/ms152559.aspx

|||

The issues that I had only involved 2 databases communicating with transactional replication - with merge subscribers hanging off one of these

For this scenario, bidirectional transactional replication seems to work well - but customisation of the replication stored procs is needed to handle conflicts.

Markus appears to have 3 databases communicating with transactional replication. I am not sure whether a chain of 3 bidirectionally replicating databases would work, but I can't think of any reason why it shouldn't. If it did then the merge changes would flow back to the root tran publisher.

Note that peer to peer wouldn't work in my scenario because the updates could not be partitioned suitably