Need help - desperate

Hi,
I am contacting you all for your help in solving a problem with
transactional replication in SQL server 2005. The setup is as follows:
One publisher and three subscribers - all are SQL 2005
Distributor database is in the same server as the publisher database.
I had set it up and it was working fine. unfortunately, the publisher
database was reloaded when I was on vacation. Now the replication is broken.
I have tried the following
Dropped the subscription.
There was no publication to be dropped. so I dropped the database, recreated
it and loaded it with a copy from production. Recreated the publication.
Recreated the subscription. When I insert data into the tables, they are not
getting replicated. The subscription status shows "The concurrent snapshot
to publication <publication name> is not available because it has not been
fully generated or the log reader agent is not running to activate it. etc'.
Can you please guide me as to how to fix this issue. Your help and advise
will be very highly appreciated.
Thanking you in anticipation,
Yoga
Hi Yoga
You contacted me privately via email yesterday about this problem. I emailed
you a response and it bounced due to ip restrictions. I then replied again
via a diferent email address and did not hear back from you. Here is the
response I emailed to you.
This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
yoga_r@.sbcglobal.net
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 8): 550 5.0.0 flpi096.sbcis.sbc.com Access
Denied. To request removal, send the complete error message, including your
ip addresses, in an E-mail to removeme@.sbc.sbcglobal.net
-- Original message --
Received: by 10.82.153.5 with SMTP id a5mr1813673bue.1165352214286;
Tue, 05 Dec 2006 12:56:54 -0800 (PST)
Received: by 10.82.161.10 with HTTP; Tue, 5 Dec 2006 12:56:54 -0800 (PST)
Message-ID: <10c19b1b0612051256y724d2bdfw4dddd9c10a12c8cd@.mail .gmail.com>
Date: Tue, 5 Dec 2006 15:56:54 -0500
From: "Hilary Cotter" <hilary.cotter@.gmail.com>
To: Yoga <yoga_r@.sbcglobal.net>
Subject: Re: Need your help
In-Reply-To: <028e01c718ac$2da491f0$a302810a@.ipsoft.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <028e01c718ac$2da491f0$a302810a@.ipsoft.net>
wow! you sure have a mess on your hands there.
I am not sure where you are now. I think it would be best to drop the
publication and subscriptions and make sure the jobs are gone as well.
You'll have to look in the jobs folder for them.
Then try to restore the database again and try again, this time with
new publication names.
If this doesn't work use sp_replicationdboption
'databasename','publish','true'
Good luck
Hilary
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:%23$Ng2VWGHHA.3976@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I am contacting you all for your help in solving a problem with
> transactional replication in SQL server 2005. The setup is as follows:
> One publisher and three subscribers - all are SQL 2005
> Distributor database is in the same server as the publisher database.
> I had set it up and it was working fine. unfortunately, the publisher
> database was reloaded when I was on vacation. Now the replication is
> broken. I have tried the following
> Dropped the subscription.
> There was no publication to be dropped. so I dropped the database,
> recreated it and loaded it with a copy from production. Recreated the
> publication. Recreated the subscription. When I insert data into the
> tables, they are not getting replicated. The subscription status shows
> "The concurrent snapshot to publication <publication name> is not
> available because it has not been fully generated or the log reader agent
> is not running to activate it. etc'. Can you please guide me as to how to
> fix this issue. Your help and advise will be very highly appreciated.
> Thanking you in anticipation,
> Yoga
>
|||Hi Hilary,
Thanks a lot for the reply. I did what you asked me to do. I made sure that
there were no jobs running with this database name. Still I am not able to
get this to work. Just to make sure, I created a temporary database, created
1 table with primary key, created publication, created subscription and
walla, the replication is working for this database. Bur the actual database
is still refusing to co-operate. Any help will be much appreciated.
Yoga
408-441-5313
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eeplQbWGHHA.3952@.TK2MSFTNGP02.phx.gbl...
> Hi Yoga
> You contacted me privately via email yesterday about this problem. I
> emailed you a response and it bounced due to ip restrictions. I then
> replied again via a diferent email address and did not hear back from you.
> Here is the response I emailed to you.
> This is an automatically generated Delivery Status Notification
> Delivery to the following recipient failed permanently:
> yoga_r@.sbcglobal.net
> Technical details of permanent failure:
> PERM_FAILURE: SMTP Error (state 8): 550 5.0.0 flpi096.sbcis.sbc.com Access
> Denied. To request removal, send the complete error message, including
> your ip addresses, in an E-mail to removeme@.sbc.sbcglobal.net
> -- Original message --
> Received: by 10.82.153.5 with SMTP id a5mr1813673bue.1165352214286;
> Tue, 05 Dec 2006 12:56:54 -0800 (PST)
> Received: by 10.82.161.10 with HTTP; Tue, 5 Dec 2006 12:56:54 -0800 (PST)
> Message-ID: <10c19b1b0612051256y724d2bdfw4dddd9c10a12c8cd@.mail .gmail.com>
> Date: Tue, 5 Dec 2006 15:56:54 -0500
> From: "Hilary Cotter" <hilary.cotter@.gmail.com>
> To: Yoga <yoga_r@.sbcglobal.net>
> Subject: Re: Need your help
> In-Reply-To: <028e01c718ac$2da491f0$a302810a@.ipsoft.net>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> References: <028e01c718ac$2da491f0$a302810a@.ipsoft.net>
>
> wow! you sure have a mess on your hands there.
> I am not sure where you are now. I think it would be best to drop the
> publication and subscriptions and make sure the jobs are gone as well.
> You'll have to look in the jobs folder for them.
> Then try to restore the database again and try again, this time with
> new publication names.
> If this doesn't work use sp_replicationdboption
> 'databasename','publish','true'
> Good luck
> Hilary
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
> news:%23$Ng2VWGHHA.3976@.TK2MSFTNGP05.phx.gbl...
>
|||My mistake I meant for you to try this.
sp_replicationdboption 'databasename','publish','False'
Then run your publication and subscription scripts and try again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:OMOu1eWGHHA.4112@.TK2MSFTNGP04.phx.gbl...
> Hi Hilary,
> Thanks a lot for the reply. I did what you asked me to do. I made sure
> that there were no jobs running with this database name. Still I am not
> able to get this to work. Just to make sure, I created a temporary
> database, created 1 table with primary key, created publication, created
> subscription and walla, the replication is working for this database. Bur
> the actual database is still refusing to co-operate. Any help will be much
> appreciated.
> Yoga
> 408-441-5313
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eeplQbWGHHA.3952@.TK2MSFTNGP02.phx.gbl...
>
|||Hi Hilary,
I executed the command and recreated the publication and subscription. But
the subscription view detail window still shows the same message "The
concurrent snapshot for publication <publication name> is not available
because it has not been fully generated or the Log Reader Agent is not
running to activate it. If generation of the concurrent snapshot was
interrupted, the Snapshot Agent for the publication m" I made sure that the
snapshot was 100% complete before I created the subscription. I also see
that the logread.exe is running. I am literally against the wall.
Yoga
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ubVJCkXGHHA.420@.TK2MSFTNGP02.phx.gbl...
> My mistake I meant for you to try this.
> sp_replicationdboption 'databasename','publish','False'
>
> Then run your publication and subscription scripts and try again.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
> news:OMOu1eWGHHA.4112@.TK2MSFTNGP04.phx.gbl...
>
|||I have tried to use push subscription and it did not work either. Any help
will be much appreciated.
Thank you,
Yoga
"Yoganarasimha Prasad" <yogakiran@.gmail.com> wrote in message
news:uKCXbaYGHHA.3976@.TK2MSFTNGP05.phx.gbl...
> Hi Hilary,
> I executed the command and recreated the publication and subscription. But
> the subscription view detail window still shows the same message "The
> concurrent snapshot for publication <publication name> is not available
> because it has not been fully generated or the Log Reader Agent is not
> running to activate it. If generation of the concurrent snapshot was
> interrupted, the Snapshot Agent for the publication m" I made sure that
> the snapshot was 100% complete before I created the subscription. I also
> see that the logread.exe is running. I am literally against the wall.
> Yoga
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ubVJCkXGHHA.420@.TK2MSFTNGP02.phx.gbl...
>
|||Have you tried sp_removedbrepication?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
sql