Logreader access violation

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: DTS Exception loading BI Accelerator data
    ... Manager if you have a support contract. ... Make sure you've updated both SQL Server RDBMS and Analysis Services to SP3 ... > exception at 0x015f20bf in dtsrun.exe: 0xc00000005: Access violation ... > The access violation occurs on the first call instruction. ...
    (microsoft.public.sqlserver.datawarehouse)
  • Re: Transactional replication from SQL Server 2005 to SQL Server 7 - how?
    ... SQL Server 7.0 from the SQL2005 management tools but I would encourage to ... primary keys are replicated as unique indexes if you ... configure replication using the SQL2000 Enterprise Manager. ... If you plan to reinitialize your SQL2000->SQL2005 subscription in the ...
    (microsoft.public.sqlserver.replication)
  • Re: High Availability
    ... also does failover. ... Async replication is real-time, as opposed to the scheduled Log Shipping ... > Note that one of the considerations for the active/passive GEO Cluster is ... > SQL Server 2000 High Availability Series ...
    (microsoft.public.sqlserver.clustering)
  • Re: Snapshot Creation
    ... Director of Text Mining and Database Strategy ... Looking for a SQL Server replication book? ... The Microsoft AD account under which the Snapshot agent (and other ...
    (microsoft.public.sqlserver.replication)
  • Re: QUEUE READER - A FREQUENT PROBLEM!
    ... "Hilary Cotter" wrote: ... Looking for a SQL Server replication book? ... queue table and the same transaction coldn't be inserted at the ...
    (microsoft.public.sqlserver.replication)
Loading