Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > microsoft.public.sqlserver.replication > #3
| Newsgroups | microsoft.public.sqlserver.replication |
|---|---|
| Date | 2017-08-07 04:10 -0700 |
| References | <O1iziqObIHA.4712@TK2MSFTNGP04.phx.gbl> |
| Message-ID | <6bb3faf8-4599-4936-83a9-7f3da2607037@googlegroups.com> (permalink) |
| Subject | Re: Subscriber updatable transactional error. |
| From | marian.nasry.azmy@gmail.com |
i have same error , anyone can help me On Monday, February 11, 2008 at 10:13:57 PM UTC+2, Edwin Smith wrote: > Well I have this working one way now but I still can't get updates from the > subscriber to work. > > I started out with immediate updating but that setting would not let me > login to my application, probably because the login process needed to update > the database which was failing. The application was reporting a password > error but this is a sample database and no password is required. The > password issue is most likely due to a general exception handler catching > all SQL errors and is a red herring. > > I switched the Subscriber to Queued updating mode and this let my > application run but the updates still don't work. > > I look at the Replication monitor which has a useless help link and reports: > > Failed while applying queued message to publisher (Source: MSSQL_REPL, Error > number: MSSQL_REPL36046) > > The SQL error log contains this over and over: > > 02/11/2008 13:33:10,spid62,Unknown,Replication-Replication Transaction Queue > Reader Subsystem: agent [JGPIOLA\CREATIVESOLUTION].6 failed. Queue Reader > aborting > 02/11/2008 13:33:10,spid62,Unknown,Error: 14151<c/> Severity: 18<c/> State: > 1. > > Hopefully this will be the last problem. > > Thank you. > > Edwin
Back to microsoft.public.sqlserver.replication | Previous | Next | Find similar
Re: Subscriber updatable transactional error. marian.nasry.azmy@gmail.com - 2017-08-07 04:10 -0700
csiph-web