Help! Trans log is growing and Log Reader can't connect

I have a SQL 2000 box with latest service pack as a publisher and
distributor. The log reader agent is not able to connect and as a result the
transaction log is growing.
On the other hand, there is a connection to the distrubtion database and it
appears to be an orphan connection from the log reader agent. I have killed
the orphan connection several times but that has not resolved the issue.
Following is the error I am getting:
SPID 30: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
I believe if I can kill the connection, I will be able to start the log
reader agent successfully. I had the exact same issue yesterday and rebooting
the server did the trick. It is a production box so I can't afford to reboot
everyday like this.
What happens when you do a sp_repltrans in publisher database? You need to
set up a verboselevel to 2 and see what kind of output you get in output
file. That would be the start.
"Adam" wrote:

> I have a SQL 2000 box with latest service pack as a publisher and
> distributor. The log reader agent is not able to connect and as a result the
> transaction log is growing.
> On the other hand, there is a connection to the distrubtion database and it
> appears to be an orphan connection from the log reader agent. I have killed
> the orphan connection several times but that has not resolved the issue.
> Following is the error I am getting:
> SPID 30: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> I believe if I can kill the connection, I will be able to start the log
> reader agent successfully. I had the exact same issue yesterday and rebooting
> the server did the trick. It is a production box so I can't afford to reboot
> everyday like this.
>
|||it probably is a phantom. See if you can start up the log reader agent
again.
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
"Adam" <Adam@.discussions.microsoft.com> wrote in message
news:C47F8C71-4D3A-4823-84AE-1948DAFAF850@.microsoft.com...
>I have a SQL 2000 box with latest service pack as a publisher and
> distributor. The log reader agent is not able to connect and as a result
> the
> transaction log is growing.
> On the other hand, there is a connection to the distrubtion database and
> it
> appears to be an orphan connection from the log reader agent. I have
> killed
> the orphan connection several times but that has not resolved the issue.
> Following is the error I am getting:
> SPID 30: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> I believe if I can kill the connection, I will be able to start the log
> reader agent successfully. I had the exact same issue yesterday and
> rebooting
> the server did the trick. It is a production box so I can't afford to
> reboot
> everyday like this.
>

HELP! Please Server Crash

I have had a piece of hardware fail (motherboard died),
and I don't have a back up of the entire SQL Box. What I
do have is all the files, master, tempdb, etc etc... in
the directory on the hard drive they were on. They are
fine.
I can't get SQL to run on another box tho, and there is a
humongous amount of jobs, and dts' that I need from there.
The data is fine, but is there a way to get this server
to run on another box?
I am in desparate need.
THank you
SvenInstall SQL Server on the new box .If you remember the paths for the install
,set it up in that fashion. Once completed, stop the SQL server service and
if you remember the exact path names/locations of your data files and log
files , you could restore all those files exactly in the same location
before you start the SQL Server instance on the other box. Give that a try..
"Sven Hansen" <shansen@.westjet.com> wrote in message
news:00c001c3c914$177c3210$a001280a@.phx.gbl...
> I have had a piece of hardware fail (motherboard died),
> and I don't have a back up of the entire SQL Box. What I
> do have is all the files, master, tempdb, etc etc... in
> the directory on the hard drive they were on. They are
> fine.
> I can't get SQL to run on another box tho, and there is a
> humongous amount of jobs, and dts' that I need from there.
> The data is fine, but is there a way to get this server
> to run on another box?
> I am in desparate need.
> THank you
> Sven
>|||After you install SQL , then stop the services and copy all of the files
back. You would then have to use sp_attach_db to attach the non-system
databases..
THe copying over of master, model , tempdb and msdb may or may not work...
The very least thing is that you MUST use the same collation that was
originally used...
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Sven Hansen" <shansen@.westjet.com> wrote in message
news:00c001c3c914$177c3210$a001280a@.phx.gbl...
> I have had a piece of hardware fail (motherboard died),
> and I don't have a back up of the entire SQL Box. What I
> do have is all the files, master, tempdb, etc etc... in
> the directory on the hard drive they were on. They are
> fine.
> I can't get SQL to run on another box tho, and there is a
> humongous amount of jobs, and dts' that I need from there.
> The data is fine, but is there a way to get this server
> to run on another box?
> I am in desparate need.
> THank you
> Sven
>sql