Distribution Agent fails with Access Violation

I have a SQL Server 2000 installation on Windows 2000 Server, last night I
updated this server with SQL SP4. The install was successful but after the
installation one of my Publications failed with Data Transformation (DTS)
Failed.
In the Event log I have the following error.
Microsoft SQL Server Replication: The DISTRIB.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005.
Check file ReplExceptDist.log for details
This log file does not exist on the Server.
I have traced the problem to a particular article in the publication. If I
Reinitilize this one application with a snapshot it is successful.
Any suggestions would be helpful at this point
Thanks
Janet
I think that this log should be in %windir%\system32
I have seen these events as well.Sometimes it is that the data is not in the
correct form and the distrib agent will fault, but on the next run will work
fine. Query your data to determine if this could account for the problem.
What happens if you restart your agent? Does the error clear?
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
"Janet" <Janet@.discussions.microsoft.com> wrote in message
news:BC4CCE66-3860-4558-B8BD-1AD6A6D99BD2@.microsoft.com...
> I have a SQL Server 2000 installation on Windows 2000 Server, last night I
> updated this server with SQL SP4. The install was successful but after
the
> installation one of my Publications failed with Data Transformation (DTS)
> Failed.
> In the Event log I have the following error.
> Microsoft SQL Server Replication: The DISTRIB.EXE executable is
terminating
> abnormally because it hit an exception. Exception Code c0000005.
> Check file ReplExceptDist.log for details
> This log file does not exist on the Server.
> I have traced the problem to a particular article in the publication. If I
> Reinitilize this one application with a snapshot it is successful.
> Any suggestions would be helpful at this point
> Thanks
> Janet
|||Log file is not in the system32 we have searched the entire machine for it.
I have checked the data and that looks fine, and the DTS should be ok too
because the Snapshot uses it and works. I have also restarted the SQL Agent
This article has been working now for a couple of months and started to fail
the moment SQL came back up after the SP4 install.
The other thing to note is that now whenever a distrubtion agent fails (for
other publications not just this one) the SPID doesn't seem to clear properly
and when the agent runs again it fails saying that the agent is already
running.
"Hilary Cotter" wrote:

> I think that this log should be in %windir%\system32
> I have seen these events as well.Sometimes it is that the data is not in the
> correct form and the distrib agent will fault, but on the next run will work
> fine. Query your data to determine if this could account for the problem.
> What happens if you restart your agent? Does the error clear?
> --
> 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
> "Janet" <Janet@.discussions.microsoft.com> wrote in message
> news:BC4CCE66-3860-4558-B8BD-1AD6A6D99BD2@.microsoft.com...
> the
> terminating
>
>
|||Hi Janet, i write from Italy, i have the same problem.
Have you resolved the problem.
I don' t know more what to make.
Thanks
"Janet" wrote:
[vbcol=seagreen]
> Log file is not in the system32 we have searched the entire machine for it.
> I have checked the data and that looks fine, and the DTS should be ok too
> because the Snapshot uses it and works. I have also restarted the SQL Agent
> This article has been working now for a couple of months and started to fail
> the moment SQL came back up after the SP4 install.
> The other thing to note is that now whenever a distrubtion agent fails (for
> other publications not just this one) the SPID doesn't seem to clear properly
> and when the agent runs again it fails saying that the agent is already
> running.
> "Hilary Cotter" wrote:
|||Same problem, but only on non DTS publications sharing distribution agent.
Sorry, Janet, no answer. Hope somebody find it soon.
Rafa