Groups | Blog | Home
all groups > sql server replication > june 2006 >

sql server replication : Trying to track down the cause of a distributor failure.



Bill Wunder
6/28/2006 2:07:01 PM
I'm very new on the project here. We had a transactional replication machine
fail over night with the following event log message.

SQLSERVERAGENT - " Microsoft SQL Server Replication :
The C:_Program Files_Microsoft SQL Server_80_COM_distrib.exe executable is
terminating abnormally because it hit an exception. Exception Code
c0000005. Check file ReplExcept.log for details.

We have looked high and low to identify a problem. Hardware, software,
network. Everything seems fine. Would need to understand the failure and take
all necessary stpes to prevent it in the future. One issue I cannot explain
is the whereabouts of the ReplExcept.log file the message points us to. It is
nowhere to be found on the box. Where should this file be and is there
something different we should be doing to bring it into existence?

Any other suggestions about what this failure may be are greatly appreciated.

Thanks
--
Hilary Cotter
6/28/2006 9:53:08 PM
Hi Bill

It dumps in the windows temp directory - %windir%\temp.

It is possible that no log file is being generated. I have seen this sort of
error when there is bad data, ie binary data in text columns. You might want
to enable debugging so it launches a debugger so you can track it more
closely.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

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



[quoted text, click to view]

petery NO[at]SPAM online.microsoft.com (
6/29/2006 5:13:22 AM
Hello Bill,

Thank you for using Microsoft MSDN newsgroup.

This is "access violation" ( c0000005) issue of distribution agent process
on distributor. It is possible that ReplExcept.log was not created when the
AV occured or captured by the proper error handling components. To find out
the root cause of this issue we may need to analyze memory dumps, this work
has to be done by contacting Microsoft Product Support Services. Therefore,
we probably will not be able to resolve the issue through the newsgroups.
I recommend that you open a Support incident with Microsoft Product Support
Services so that a dedicated Support Professional can assist with this
case. If you need any help in this regard, please let me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp


Also, I saw similar issue was resolved by installing latest MDAC on the
server. If you have OS is Win2000, you could try to install Mdac 2.8 sp1 to
test the sitaution:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=78CA
C895-EFC2-4F8E-A9E0-3A1AFBD5922E

If it is Win2003, latest mdac for this OS is included in SP1, you could
reinstall it by following method:

Go to %windir%\inf\ folder

Right click mdac.inf->Install, you may prompt to insert Win2003 SP1 setup
CD, please insert the CD or direct them to the proper setup folder of SP1

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================



This posting is provided "AS IS" with no warranties, and confers no rights.

AddThis Social Bookmark Button