logreader is not working on 2005 db attached to 2008.

[Gene.]

Hi folks
I came accross a problem with tran. replication on db which was detached
from 2005 and attached to 2008.
Logreader was failing with:

The process could not execute 'sp_replcmds' on 'serv1\IN1'. (Source:
MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does
not exist, this type of principal cannot be impersonated, or you do not have
permission. (Source: MSSQLServer, Error number: 15517)

All agents were started with the same user which is local admin and sql
sysadmin on the same host.
When I created db's 'new' on 2008, the same exact set up started working.
Do you have any explanation to it?

Are you aware of any functional shortcomming from detaching / attaching db's
as an upgrade path?

[Paul Ibison]

Please take a look at Remus' comment in this thread:
http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.adonet/topic39210.aspx
HTH,
Paul Ibison

[Gene.]

Paul, it was genious and helpfull!

I was researching it from yesterday. I kind of suspected it was a problem,
but sid's were the same. Both servers resided on the same host. But, as I
said, it worked!
It supports very important upgrading technics.

Best regards, Gene.

Post by Paul Ibison
http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.adonet/topic39210.aspx
HTH,
Paul Ibison

[prashant mishra]

realy your artical is gre8

it is realy very help full

Post by Gene.
Hi folks
I came accross a problem with tran. replication on db which was detached
from 2005 and attached to 2008.
MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does
not exist, this type of principal cannot be impersonated, or you do not have
permission. (Source: MSSQLServer, Error number: 15517)
All agents were started with the same user which is local admin and sql
sysadmin on the same host.
When I created db's 'new' on 2008, the same exact set up started working.
Do you have any explanation to it?
Are you aware of any functional shortcomming from detaching / attaching db's
as an upgrade path?

Post by Paul Ibison
http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework.adonet/topic39210.aspx
HTH,
Paul Ibison

Post by Gene.
Paul, it was genious and helpfull!
I was researching it from yesterday. I kind of suspected it was a problem,
but sid's were the same. Both servers resided on the same host. But, as I
said, it worked!
It supports very important upgrading technics.
Best regards, Gene.
Submitted via EggHeadCafe
SharePoint Tip / Thought of the Day WebPart
http://www.eggheadcafe.com/tutorials/aspnet/14280ff8-3c9f-46bd-8214-9267e613c8ec/sharepoint-tip--thought-of-the-day-webpart.aspx

[Ben Thul]

If you're saying that the logreader agent isn't able to execute
sp_replcmds, check what permissions the account that that's set to run
under has. I'm pretty sure that it needs db_owner (though sysadmin on
the instance will obviously work, too).
--
Ben

Post by prashant mishra
realy your artical is gre8
it is realy very help full

Post by Gene.
Hi folks
I came accross a problem with tran. replication on db which was detached
from 2005 and attached to 2008.
MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help:http://help/MSSQL_REPL20011
Cannot execute as the database principal because the principal "dbo" does
not exist, this type of principal cannot be impersonated, or you do not have
permission. (Source: MSSQLServer, Error number: 15517)
All agents were started with the same user which is local admin and sql
sysadmin on the same host.
When I created db's 'new' on 2008, the same exact set up started working.
Do you have any explanation to it?
Are you aware of any functional shortcomming from detaching / attaching db's
as an upgrade path?

http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework....
HTH,
Paul Ibison

Post by Gene.
Paul, it was genious and helpfull!
I was researching it from yesterday. I kind of suspected it was a problem,
but sid's were the same. Both servers resided on the same host. But, as I
said, it worked!
It supports very important upgrading technics.
Best regards, Gene.
Submitted via EggHeadCafe
SharePoint Tip / Thought of the Day WebPart
http://www.eggheadcafe.com/tutorials/aspnet/14280ff8-3c9f-46bd-8214-9...