Microsoft Knowledge Base Email Alertz

KBAlertz.com: (814853) - When you run an application that uses SQL Server CE replication, the application may fail and you receive the following error message: 29045: Initializing SQL Server Reconciler has failed.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 814853 - Last Review: January 3, 2007 - Revision: 1.7

SQL Server CE Replication application fails with error message 29045

SYMPTOMS

When you run an application that uses SQL Server CE replication, the application may fail and you receive the following error message:

29045: Initializing SQL Server Reconciler has failed.

CAUSE

The DLL file that corresponds to the SQL Server CE Replication provider is not registered on the computer where SQL Server CE Server Tools is installed.

RESOLUTION

To resolve the problem, register the SQL Server CE Replication Provider DLL on the computer where SQL Server CE Server Tools is installed. To do so, follow these steps:
  1. Open a command prompt.
  2. Run the following command:

    regsvr32 "Full path of DLL file"
Note Here is the list of the DLL file names that correspond to the SQL Server Replication provider in SQL Server CE 1.0, SQL Server CE 1.1,SQL Server CE 2.0:
  • Sscerp10.dll for SQL Server 2000 Windows CE Edition 1.0
  • Sscerp10.dll for SQL Server 2000 Windows CE Edition 1.1
  • Sscerp20.dll for SQL Server 2000 Windows CE Edition 2.0

REFERENCES

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
279123  (http://kbalertz.com/Feedback.aspx?kbNumber=279123/EN-US/ ) FIX: SQL Server 2000 Uninstallation May Break SQL Server CE Replication

APPLIES TO
  • Microsoft SQL Server 2000 Windows CE Edition 2.0
  • Microsoft SQL Server 2000 Windows CE Edition 1.1
  • Microsoft SQL Server 2000 Windows CE Edition
Keywords: 
kbregistry kbdll kberrmsg kbprb KB814853
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Anonymous User Reported as Irrelevant  
Written: 3/14/2006 1:13 AM
The application may fail with the following error message: 'A request to send data to the computer running IIS has filed.' Please help me to solve this error..

Anonymous User Reported as Irrelevant  
Written: 4/25/2006 3:51 AM
I don't think so! Registering mentioned dll is not always the solution to the problem. I have several replications and some of them work always, some of the sometime, some of them never. The message after failed replication is all the time the same.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please