Re: Logreader access violation



Hi,

Just a quick update on this problem. I applied SP4 and that has resolved the
problem.

Thanks


"sqlnewbie" wrote:

Hi Hillary,

Thanks for your time on this. I did post the contents of the
ReplExceptLogRdr.log in me initial post. It was located in the C:\Program
Files\Microsoft SQL Server\MSSQL\LOG folder. Is this the same log you are
referring to? I am not sure what you mean by (IIRC).

I wasn't sure if this was a bug so I haven't applied any patches.

Is this a user rights problem? That is the user running the SQL Server agent
has insufficient rights, because the user I created has Admin rights for
Windows and System Admin rights for SQL Server.

Thanks,
SQLNEwbie

"Hilary Cotter" wrote:

I get these from time to time. Did you check ReplExceptLogRdr.log IIRC it
will be found in windows\system32

Also does this apply?

http://support.microsoft.com/kb/872843/EN-US/

--
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



"sqlnewbie" <sqlnewbie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5CCC218-2858-42BD-97BE-6C0B3AB1054E@xxxxxxxxxxxxxxxx
Hi everyone,

I am setting up Transaction Replication on a MSSQL 2000 8.0.194.
Everything
was going fine until the log reader stopped with a "An access violation
occurred" error.

I tried setting up a publication on another test database on the same
server
to make sure the problem was not with the database it self and encountered
the same error.

In the ReplExceptLogRdr.log I am getting the following error:

Microsoft SQL Server Replication: Exception Stack Dump

*******************************************************

Computer type is AT/AT COMPATIBLE.
Bios Version is DELL - 1
Phoenix ROM BIOS PLUS Version 1.10 A10Current local time is Fri Apr 13
15:16:41 2007
4 Intel x86 level 15, 2392 Mhz processor(s).
Windows NT 5.2 Build 3790 CSD .
MemoryLoad 62% TotalPhys 2047 MB
AvailPhys 1481 MB TotalPageFile 4095 MB

*******************************************************

An exception was caught
in LOGREAD.EXE

* Exception Address = 00000001
* Exception Code = c0000005
*
*******************************************************

Module Name Return Address Location
[No Module Info] 003678f0 00000001
[No Module Info] 0040abd5 003678f0
logread 0040dec9 0040abd5
logread 0040aa5c 0040dec9
logread 77e4f38c 0040aa5c
kernel32 00000000 TerminateThread + 113

I have tested setting up replication using the same database on the users
reporting server and everything went fine. I have tried giving the folder
that contains the Distributor database and logfile access to "Everyone".

The Event Viewer show the following error and information:

[SQLSERVERAgent Error]
Microsoft SQL Server Replication : The LOGREAD.EXE executable is
terminating
abnormally because it hit an exception. Exception Code c0000005. Check
file
ReplExceptLogRdr.log for details.

[Information]
SubSystem Message - Job 'CL-SQL-CLUAT-1'
(0x7A865965F727AB4CA60CC19D5A5EEEA8), step 2 - An access violation
occurred.

I tried changing the Logreaders agents verbose level to 3, but nothing
extra
appeared in the sqlserver log.

Before I set up replication I had to change the logon the sqlserver agent
was running from the system account to a windows user with Admin rights.
The
user also has sql server admin rights.

I am kind of stuck now as I don't know what else I can do to further
investigate the problem.

Any help would really be appreciated.
Thanks,
SQLNewbie



.



Relevant Pages

  • Re: Logreader access violation
    ... Windows and System Admin rights for SQL Server. ... Microsoft SQL Server Replication: Exception Stack Dump ...
    (microsoft.public.sqlserver.replication)
  • Re: ASP.NET 2.0 - a newbie question
    ... the exception can be identified using the exception stack trace below. ... established connection failed because connected host has failed to ... connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& ... Microsoft SQL Server? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Authentication problem continued
    ... This is the exception I get if on my test box if I haven't run ... I have a SQL Server login established now and I can log in on my ... SQL Server is configured for Windows Authentication only and not ... I'm still having trouble getting my app to authenticate correctly. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Implementation of Replication en SQL SERVER 2K
    ... Hilary Cotter ... Looking for a SQL Server replication book? ... "Alvaro Rebolledo" wrote in ... >> Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)
  • Re: UPDATE Statements May be Replicated as DELETE/INSERT Pairs
    ... how about you make the fk's and all constraints Not For Replication? ... Looking for a SQL Server replication book? ... Looking for a FAQ on Indexing Services/SQL FTS ...
    (microsoft.public.sqlserver.replication)