On Mar 14, 12:45 pm, "Hilary Cotter" <hilary.cot...@gmail.com> wrote:
> The status event is the best way to monitor progress of your sync.
>
> Merge replication does put schema and application locks on your tables,
> including the sysmergerarticles table - this is probably what you are
> seeing.
> --
> Hilary Cotter
>
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
>
> "Mar72Vin" <mar72...@gmail.com> wrote in message
>
> news:1173826362.218126.53350@l75g2000hse.googlegroups.com...
>
> > Hi All,
> > I have previously posted in the MSDN forums with no responses, so any
> > hints on this would be greatly appreciated.
>
> > I am replicating an SQL2005 express machine to SQL2005 standard
> > edition server using merge replication.
>
> > I have a simple VB application using ADO polling msMerge_history at
> > the subscriber every second so that i can show the end user the
> > progress of the replication.
>
> > When the subscription first subscribes and after the initial snapshot
> > is applied replication downloads all changes from the server that have
> > been changed since the snapshot was created.
>
> > Towards the end of this download faze the VB polling application fails
> > with "Cannot open database "DBName" requested by the login. The login
> > failed."
>
> > This connection fails 4 or 5 times and then normal polling resumes.
> > The scary thing is that sometimes when the polling connection fails
> > the merge replication does not complete and if i check
> > msMerge_Sessions the "runstatus" is stuck at 3 (InProgress).
>
> > 1) Is the reason the ADO polling connection fails because of some sort
> > of lock between replication and reading the system tables?
> > 2) Is replication getting stuck because of locks?
> > 3) What can i do to get around this?
>
> > cheers,
> > Tim

"Mar72Vin" <mar72vin@gmail.com> wrote in message
news:1173826362.218126.53350@l75g2000hse.googlegroups.com...
> Hi All,
> I have previously posted in the MSDN forums with no responses, so any
> hints on this would be greatly appreciated.
>
> I am replicating an SQL2005 express machine to SQL2005 standard
> edition server using merge replication.
>
> I have a simple VB application using ADO polling msMerge_history at
> the subscriber every second so that i can show the end user the
> progress of the replication.
>
> When the subscription first subscribes and after the initial snapshot
> is applied replication downloads all changes from the server that have
> been changed since the snapshot was created.
>
> Towards the end of this download faze the VB polling application fails
> with "Cannot open database "DBName" requested by the login. The login
> failed."
>
> This connection fails 4 or 5 times and then normal polling resumes.
> The scary thing is that sometimes when the polling connection fails
> the merge replication does not complete and if i check
> msMerge_Sessions the "runstatus" is stuck at 3 (InProgress).
>
> 1) Is the reason the ADO polling connection fails because of some sort
> of lock between replication and reading the system tables?
> 2) Is replication getting stuck because of locks?
> 3) What can i do to get around this?
>
> cheers,
> Tim
>

"Mar72Vin" <mar72vin@gmail.com> wrote in message
news:1173852824.327599.170440@n59g2000hsh.googlegroups.com...
> Looks like i have been barking up the wrong tree. The connections from
> the ado application are not causing this error.
>
> I ran replmerg.exe and captured the results (see below), It looks like
> replication is trying to use the SYSTEM login at some point to access
> the database and it does not have access.
>
> The SQL2005Express instance is running under the system account, I
> can't see why it should have troubles connecting to this database.
>
> Any Ideas?
>
> cheers,
> Tim
>
>
> 2007-03-14 04:56:34.347 Connecting to Subscriber 'BARNEYXP\MDSZINC'
> 2007-03-14 04:56:34.347 Connecting to OLE DB Subscriber at datasource:
> 'BARNEYXP\MDSZINC', location: '', catalog: 'MDS200703146',
> providerstring: '' using provider 'SQLNCLI'
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:AGENT
> Source: BARNEYXP\MDSZINC
> Number: 20052
> Message: The process could not access database 'MDS200703146' on
> server 'BARNEYXP\MDSZINC'.
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:SQLSERVER
> Source: BARNEYXP\MDSZINC
> Number: 4060
> Message: Cannot open database "MDS200703146" requested by the login.
> The login failed.
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:SQLSERVER
> Source: BARNEYXP\MDSZINC
> Number: 18456
> Message: Login failed for user 'NT AUTHORITY\SYSTEM'.
>