![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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 |
#3
| |||
| |||
|
|
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 |
#4
| |||
| |||
|
|
*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 |
#5
| |||
| |||
|
|
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 |
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |