dbTalk Databases Forums  

Error 80040E35 while syncing with SQL CE

microsoft.public.sqlserver.replication microsoft.public.sqlserver.replication


Discuss Error 80040E35 while syncing with SQL CE in the microsoft.public.sqlserver.replication forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Eli Tucker
 
Posts: n/a

Default Error 80040E35 while syncing with SQL CE - 11-09-2004 , 06:52 PM






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


Reply With Quote
  #2  
Old   
Kevin Collins \(MS - SQL Mobile\)
 
Posts: n/a

Default Re: Error 80040E35 while syncing with SQL CE - 11-10-2004 , 03:08 PM






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 (AT) nerdmonkey (DOT) com> wrote

Quote:
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




Reply With Quote
  #3  
Old   
Eli Tucker
 
Posts: n/a

Default Re: Error 80040E35 while syncing with SQL CE - 11-11-2004 , 01:05 PM



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 (AT) online (DOT) microsoft.com> wrote in
message news:u87bul2xEHA.3224 (AT) TK2MSFTNGP14 (DOT) phx.gbl...
Quote:
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 (AT) nerdmonkey (DOT) com> wrote in message
news:1100047940.037822.112230 (AT) c13g2000cwb (DOT) googlegroups.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






Reply With Quote
  #4  
Old   
jrogers9
 
Posts: n/a

Default Re: Error 80040E35 while syncing with SQL CE - 11-12-2004 , 03:30 PM




Each handheld can only replicate one publication for SQLCE 2.0. The Nex
release if SQLCE is scheduled 1st Quarter of 2005 and will suppor
multupile publications per handheld.

Eli Tucker wrote:
Quote:
*Using SQL CE merge replication, we've seen the following erro
during
bi-directional sync (the upload only phase of sync, which we perform
immediately prior to the bi-directional phase, succeeds). User
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 pas
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 sam
database
instance. I believe this is permissable, but I am wondering if thi
is
not advised?
Any other help you could offer would be appreciated.

Thanks,
- Eli

-
jrogers
-----------------------------------------------------------------------
Posted via http://www.mcse.m
-----------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1212841.htm



Reply With Quote
  #5  
Old   
mrjrogers
 
Posts: n/a

Default Re: Error 80040E35 while syncing with SQL CE - 11-16-2004 , 10:39 AM



Correct me if I'm wrong but this is what you want to do with SQL C
http://msdn.microsoft.com/library/de...lplan_0e5q.asp

And this is what cant with SQL C
http://msdn.microsoft.com/library/de...tions_1ss3.asp



"Eli Tucker" wrote:

Quote:
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 (AT) online (DOT) microsoft.com> wrote in
message news:u87bul2xEHA.3224 (AT) TK2MSFTNGP14 (DOT) 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 (AT) nerdmonkey (DOT) com> wrote in message
news:1100047940.037822.112230 (AT) c13g2000cwb (DOT) googlegroups.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







Reply With Quote
  #6  
Old   
Eli Tucker
 
Posts: n/a

Default Re: Error 80040E35 while syncing with SQL CE - 01-06-2005 , 03:14 PM



What is suggested in your second link would have worked for me. If
would have saved us a huge hassle, for sure.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.