LogScan in progress

Hello,
We have a mixed replication environment with SQL Server transactional
replication and Datamirror replication (with DB2). Yesterday we upgraded to
SQL Server 2005 and the transactional replication does not work.
The log reader message is "Logscan in progress. Approximately 4254920 log
records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
Watcher tells that all subscriptions are uninitialized. But actually, I have
not subscription to initialize (there are Datamirror). And, in any case, I
cannot reinitialize the subscription because the initial synchronization was
made manually.
Now, all pending changes are in the transaction log of the publisher database.
What can I do? Is to drop and recreate the publication the only way to solve
this issue?
Thank you in advanced,
qwalgrande
You need to contact DataMirror to learn how to make their product work with
SQL Server 2005.
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
"qwalgrande" <qwalgrande*nospam*@.yahoo.es> wrote in message
news:19C4184F-C544-43A3-B6AD-74E170047129@.microsoft.com...
> Hello,
> We have a mixed replication environment with SQL Server transactional
> replication and Datamirror replication (with DB2). Yesterday we upgraded
> to
> SQL Server 2005 and the transactional replication does not work.
> The log reader message is "Logscan in progress. Approximately 4254920 log
> records scanned in pass # 1, elapsed time 7620 (ms).". The Subscription
> Watcher tells that all subscriptions are uninitialized. But actually, I
> have
> not subscription to initialize (there are Datamirror). And, in any case, I
> cannot reinitialize the subscription because the initial synchronization
> was
> made manually.
> Now, all pending changes are in the transaction log of the publisher
> database.
> What can I do? Is to drop and recreate the publication the only way to
> solve
> this issue?
> Thank you in advanced,
> --
> qwalgrande

Logins from SQL7 to SQL2000

We are upgraded our vendor software (Jenzabar EX) from SQL7 to SQL2000. In the process, we are also moving the databases to a new server. Everything seemed to go fine until we tried to log on to one of Jenzabar EX modules. We have tried several differe
nt things, including the sp_change_users (which failed because of the @.action clause). We've tried running that huge script included in the Knowledge Base article. We also have tried using the transfer login wizard. Which, report success, but the login
s still do not work.
Could we have possibly missed a step somewhere? Is there something else we can try? I sure would greatly appreciate any advice or assistance.
Thanks!
Karma
What is the exact problem you are having when you login from this
application?
Rand
This posting is provided "as is" with no warranties and confers no rights.

Logins from SQL7 to SQL2000

We are upgraded our vendor software (Jenzabar EX) from SQL7 to SQL2000. In
the process, we are also moving the databases to a new server. Everything s
eemed to go fine until we tried to log on to one of Jenzabar EX modules. We
have tried several differe
nt things, including the sp_change_users (which failed because of the @.actio
n clause). We've tried running that huge script included in the Knowledge B
ase article. We also have tried using the transfer login wizard. Which, re
port success, but the login
s still do not work.
Could we have possibly missed a step somewhere? Is there something else we
can try? I sure would greatly appreciate any advice or assistance.
Thanks!
KarmaWhat is the exact problem you are having when you login from this
application?
Rand
This posting is provided "as is" with no warranties and confers no rights.