Error 80040E35 while syncing with SQL CE

Using SQL CE merge replication, we've seen the following error during
bi-directional sync (the upload only phase of sync, which we perform
immediately prior to the bi-directional phase, succeeds). Users have
sync'd successfully before this error occurs.
-Error Code: 80040E35
Message :
NativeErr.: 28574
Source : Microsoft SQL Server 2000 Windows CE Edition
Num. Par. : 897
-Error Code: 80040E35
Message :
NativeErr.: 0
Source : Microsoft SQL Server 2000 Windows CE Edition
Err. Par. 0: s_GenIdx;
The closest error description that I can find for 80040E35 is
"DB_E_NOINDEX 80040E35 The specified index does not exist in the
current data source or does not apply to the specified table."
What could be causing this?
The only reference to this problem that I found was in a past message
in this newsgroup:
http://tinyurl.com/6c6gz
That message seems to have gone unanswered.
We recently added a second publication that points to the same database
instance. I believe this is permissable, but I am wondering if this is
not advised?
Any other help you could offer would be appreciated.
Thanks,
- Eli
You are getting an internal error. You need to call Microsoft Product
Support for them to get a repro of this issue. The support call will be
free because you have hit an internal error.
You can have multiple publications access the same database. That is a
typical scenario and is fully supported.
"Eli Tucker" <eli-news@.nerdmonkey.com> wrote in message
news:1100047940.037822.112230@.c13g2000cwb.googlegr oups.com...
> Using SQL CE merge replication, we've seen the following error during
> bi-directional sync (the upload only phase of sync, which we perform
> immediately prior to the bi-directional phase, succeeds). Users have
> sync'd successfully before this error occurs.
> -Error Code: 80040E35
> Message :
> NativeErr.: 28574
> Source : Microsoft SQL Server 2000 Windows CE Edition
> Num. Par. : 897
> -Error Code: 80040E35
> Message :
> NativeErr.: 0
> Source : Microsoft SQL Server 2000 Windows CE Edition
> Err. Par. 0: s_GenIdx;
> The closest error description that I can find for 80040E35 is
> "DB_E_NOINDEX 80040E35 The specified index does not exist in the
> current data source or does not apply to the specified table."
> What could be causing this?
> The only reference to this problem that I found was in a past message
> in this newsgroup:
> http://tinyurl.com/6c6gz
> That message seems to have gone unanswered.
> We recently added a second publication that points to the same database
> instance. I believe this is permissable, but I am wondering if this is
> not advised?
> Any other help you could offer would be appreciated.
> Thanks,
> - Eli
>
|||Hi Kevin. The error was the result of reinitializing the publication. It
would be nice if the error was more detailed and included some description
of the cause of the problem.
What's more frightening is that the upload-only portion of the sync
successfully runs, reporting that no new rows were uploaded. This is
misleading -- new information may exist in the SQL CE database and will not
be uploaded.
- Eli
PS- As a followup, is it possible to undo the re-initialization of a
publication?
"Kevin Collins (MS - SQL Mobile)" <kevincol@.online.microsoft.com> wrote in
message news:u87bul2xEHA.3224@.TK2MSFTNGP14.phx.gbl...
> You are getting an internal error. You need to call Microsoft Product
> Support for them to get a repro of this issue. The support call will be
> free because you have hit an internal error.
> You can have multiple publications access the same database. That is a
> typical scenario and is fully supported.
>
> "Eli Tucker" <eli-news@.nerdmonkey.com> wrote in message
> news:1100047940.037822.112230@.c13g2000cwb.googlegr oups.com...
>
|||Each handheld can only replicate one publication for SQLCE 2.0. The Next release if SQLCE is scheduled 1st Quarter of 2005 and will support multupile publications per handheld.

Quote:

Originally posted by Eli Tucker
Using SQL CE merge replication, we've seen the following error during
bi-directional sync (the upload only phase of sync, which we perform
immediately prior to the bi-directional phase, succeeds). Users have
sync'd successfully before this error occurs.
-Error Code: 80040E35
Message :
NativeErr.: 28574
Source : Microsoft SQL Server 2000 Windows CE Edition
Num. Par. : 897
-Error Code: 80040E35
Message :
NativeErr.: 0
Source : Microsoft SQL Server 2000 Windows CE Edition
Err. Par. 0: s_GenIdx;
The closest error description that I can find for 80040E35 is
"DB_E_NOINDEX 80040E35 The specified index does not exist in the
current data source or does not apply to the specified table."
What could be causing this?
The only reference to this problem that I found was in a past message
in this newsgroup:
http://tinyurl.com/6c6gz
That message seems to have gone unanswered.
We recently added a second publication that points to the same database
instance. I believe this is permissable, but I am wondering if this is
not advised?
Any other help you could offer would be appreciated.
Thanks,
- Eli

|||Correct me if I'm wrong but this is what you want to do with SQL CE
http://msdn.microsoft.com/library/de...lplan_0e5q.asp
And this is what cant with SQL CE
http://msdn.microsoft.com/library/de...tions_1ss3.asp
"Eli Tucker" wrote:

> Hi Kevin. The error was the result of reinitializing the publication. It
> would be nice if the error was more detailed and included some description
> of the cause of the problem.
> What's more frightening is that the upload-only portion of the sync
> successfully runs, reporting that no new rows were uploaded. This is
> misleading -- new information may exist in the SQL CE database and will not
> be uploaded.
> - Eli
> PS- As a followup, is it possible to undo the re-initialization of a
> publication?
> "Kevin Collins (MS - SQL Mobile)" <kevincol@.online.microsoft.com> wrote in
> message news:u87bul2xEHA.3224@.TK2MSFTNGP14.phx.gbl...
>
>
|||What is suggested in your second link would have worked for me. If
would have saved us a huge hassle, for sure.