Showing posts with label merge. Show all posts
Showing posts with label merge. Show all posts

Thursday, March 22, 2012

Error 80072F76 28635 Requested header not found

I am trying to install a SQL server 2005 database to merge with a sql mobile database on an emulator or pda.

I have installed SQL server 2005 and a copied an existing database and created the publications subscriptions that worked on another machine. As far as I can tell everything is ok with the installation. I can browse the url of the virtual directory ie.sqlcesa30.dll on the database server and from the pda emulator so I'm satisfied that part of the comms is OK.

Using the ?diagnostics feature indicates everything is OK

When I come the actually merge the databases I get error number 80072f76 (23635) with a message that the header is corrupt or missing. The odd thing is that this message refers to sql ce 2000, which is n't installed and that i'm not trying to use.

The application on the PDA that I'm using to carry out the merge worked ok on another system, I've done all the obvious things like check the database server name and ip address, the privaledges for the iusr_ and am now stuck.

Can anyone point me in the right direction or tell me what the 'header' in the error message refers to.

Thanks

Rob,

It sounds like everything is setup correctly, however your note that says "created the publications subscriptions that worked on another machine"

suggests you may be trying to synch from device/emulator after moving the publisher to a new server and you expect the subscription info

to still be valid. What I would recommend is to regenerate your snapshot and reinitialize all subscriptions in the process.

Darren

|||

Darren,

Thanks for your reply.

The other machine refered to used MS SQL 2005 to sync with a SQL mobile database using an application developeded in VS2005 .net 1 cf and then .net 2 cf.

The synchronisations work ok using those applications. Unfortuately that machine failed.

On a clean machine I reinstalled everything and manaully created the publications etc from the notes I had made and made sure everything is initialised. Its then I experienced the problems.

The really odd thing is that using the application developed in VS2005 .net1 cf I get the error reported, though on the 'old' machine this worked OK. If the app is upgraded in VS2005 to .net 2, no code changes, no changes to the database then it sysnchronises OK. Unfortuately going to .net2 is n't currently an option as this introduces additional problems which are the subject of another post. Returning to the .net 1 version I experience problems.

So, I'm stuck.

Any suggestions on what to do next or how to debug the 'header' error msg.

Thanks

|||

I'm not sure I'm entirely clear on exactly what you are doing, but I sense that you may be trying to use a CF1.0 mobile application with SQL Mobile (which you cannot do) - SQL Mobile requires CF2.0. If you must be at CF1.0 level, then you should be using SQL Server 2000 Windows CE Edition (aka SQL CE).

Darren

|||

Yep thats what I was trying to do.Though I thought I had it working previously.

Unfortunately can n't use .net 2 cf at the moment as there a some other problems with the conversion of the application.

Thanks

Error 80072F76 28635 Requested header not found

I am trying to install a SQL server 2005 database to merge with a sql mobile database on an emulator or pda.

I have installed SQL server 2005 and a copied an existing database and created the publications subscriptions that worked on another machine. As far as I can tell everything is ok with the installation. I can browse the url of the virtual directory ie.sqlcesa30.dll on the database server and from the pda emulator so I'm satisfied that part of the comms is OK.

Using the ?diagnostics feature indicates everything is OK

When I come the actually merge the databases I get error number 80072f76 (23635) with a message that the header is corrupt or missing. The odd thing is that this message refers to sql ce 2000, which is n't installed and that i'm not trying to use.

The application on the PDA that I'm using to carry out the merge worked ok on another system, I've done all the obvious things like check the database server name and ip address, the privaledges for the iusr_ and am now stuck.

Can anyone point me in the right direction or tell me what the 'header' in the error message refers to.

Thanks

Rob,

It sounds like everything is setup correctly, however your note that says "created the publications subscriptions that worked on another machine"

suggests you may be trying to synch from device/emulator after moving the publisher to a new server and you expect the subscription info

to still be valid. What I would recommend is to regenerate your snapshot and reinitialize all subscriptions in the process.

Darren

|||

Darren,

Thanks for your reply.

The other machine refered to used MS SQL 2005 to sync with a SQL mobile database using an application developeded in VS2005 .net 1 cf and then .net 2 cf.

The synchronisations work ok using those applications. Unfortuately that machine failed.

On a clean machine I reinstalled everything and manaully created the publications etc from the notes I had made and made sure everything is initialised. Its then I experienced the problems.

The really odd thing is that using the application developed in VS2005 .net1 cf I get the error reported, though on the 'old' machine this worked OK. If the app is upgraded in VS2005 to .net 2, no code changes, no changes to the database then it sysnchronises OK. Unfortuately going to .net2 is n't currently an option as this introduces additional problems which are the subject of another post. Returning to the .net 1 version I experience problems.

So, I'm stuck.

Any suggestions on what to do next or how to debug the 'header' error msg.

Thanks

|||

I'm not sure I'm entirely clear on exactly what you are doing, but I sense that you may be trying to use a CF1.0 mobile application with SQL Mobile (which you cannot do) - SQL Mobile requires CF2.0. If you must be at CF1.0 level, then you should be using SQL Server 2000 Windows CE Edition (aka SQL CE).

Darren

|||

Yep thats what I was trying to do.Though I thought I had it working previously.

Unfortunately can n't use .net 2 cf at the moment as there a some other problems with the conversion of the application.

Thanks

sql

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.

Wednesday, March 21, 2012

Error 7391

Brief background... I have basically the same sql/db at
each of my locations and once a week I try to merge all of
the db into one corporate db. I have several queries that
are in a stored procedure that seem to be working just
fine but there is one query that just does not want to
work. I get the following messages...
INSERT INTO Invoice_MiscCharge (InvNo, MiscCharge,
UnitPrice, Qty, ExtendedPrice, WorkOrder)
SELECT Invoice_MC.InvNo, MiscCharge, UnitPrice, Qty,
ExtendedPrice, WorkOrder
FROM tmpInvoice INNER JOIN [D8J5ZH11\CASQL].
[EncompassCA].[dbo].[Invoice_MiscCharge] AS Invoice_MC
ON tmpInvoice.InvNo = Invoice_MC.InvNo
where tmpInvoice.invno=240530579
Server: Msg 8501, Level 16, State 1, Line 1
MSDTC on server 'D8J5ZH11\CASQL' is unavailable.
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed
transaction.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d01c].
If I run just the select part of the query it works just
fine but as soon as I add the insert it bombs. Even with
trying to insert just one record.
Check how to troubleshoot this error at
http://support.microsoft.com/default...b;en-us;306212 BTW, check if
your DTC service is runnin as well.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"David" <dagwin@.hotmail.com> wrote in message
news:1855201c44a5b$31568690$a501280a@.phx.gbl...
> Brief background... I have basically the same sql/db at
> each of my locations and once a week I try to merge all of
> the db into one corporate db. I have several queries that
> are in a stored procedure that seem to be working just
> fine but there is one query that just does not want to
> work. I get the following messages...
> INSERT INTO Invoice_MiscCharge (InvNo, MiscCharge,
> UnitPrice, Qty, ExtendedPrice, WorkOrder)
> SELECT Invoice_MC.InvNo, MiscCharge, UnitPrice, Qty,
> ExtendedPrice, WorkOrder
> FROM tmpInvoice INNER JOIN [D8J5ZH11\CASQL].
> [EncompassCA].[dbo].[Invoice_MiscCharge] AS Invoice_MC
> ON tmpInvoice.InvNo = Invoice_MC.InvNo
> where tmpInvoice.invno=240530579
>
> Server: Msg 8501, Level 16, State 1, Line 1
> MSDTC on server 'D8J5ZH11\CASQL' is unavailable.
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB
> provider 'SQLOLEDB' was unable to begin a distributed
> transaction.
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d01c].
> If I run just the select part of the query it works just
> fine but as soon as I add the insert it bombs. Even with
> trying to insert just one record.
|||Thank you for the reference. I am taking a look at the
page. I guess what really has me stumped is the query
that is failing is the 5th query in the list. All the
other queries run against the same server/database but the
only thing that changes are the tables.
Thank you for the information
David

>--Original Message--
>Check how to troubleshoot this error at
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;306212 BTW, check if[vbcol=seagreen]
>your DTC service is runnin as well.
>--
>Dejan Sarka, SQL Server MVP
>Associate Mentor
>Solid Quality Learning
>More than just Training
>www.SolidQualityLearning.com
>"David" <dagwin@.hotmail.com> wrote in message
>news:1855201c44a5b$31568690$a501280a@.phx.gbl...
of[vbcol=seagreen]
that[vbcol=seagreen]
with
>
>.
>

Error 7391

Brief background... I have basically the same sql/db at
each of my locations and once a week I try to merge all of
the db into one corporate db. I have several queries that
are in a stored procedure that seem to be working just
fine but there is one query that just does not want to
work. I get the following messages...
INSERT INTO Invoice_MiscCharge (InvNo, MiscCharge,
UnitPrice, Qty, ExtendedPrice, WorkOrder)
SELECT Invoice_MC.InvNo, MiscCharge, UnitPrice, Qty,
ExtendedPrice, WorkOrder
FROM tmpInvoice INNER JOIN [D8J5ZH11\CASQL].
[EncompassCA].[dbo].[Invoice_MiscCharge] AS Invoice_MC
ON tmpInvoice.InvNo = Invoice_MC.InvNo
where tmpInvoice.invno=240530579
Server: Msg 8501, Level 16, State 1, Line 1
MSDTC on server 'D8J5ZH11\CASQL' is unavailable.
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB
provider 'SQLOLEDB' was unable to begin a distributed
transaction.
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d01c].
If I run just the select part of the query it works just
fine but as soon as I add the insert it bombs. Even with
trying to insert just one record.Check how to troubleshoot this error at
http://support.microsoft.com/defaul...kb;en-us;306212 BTW, check if
your DTC service is runnin as well.
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"David" <dagwin@.hotmail.com> wrote in message
news:1855201c44a5b$31568690$a501280a@.phx
.gbl...
> Brief background... I have basically the same sql/db at
> each of my locations and once a week I try to merge all of
> the db into one corporate db. I have several queries that
> are in a stored procedure that seem to be working just
> fine but there is one query that just does not want to
> work. I get the following messages...
> INSERT INTO Invoice_MiscCharge (InvNo, MiscCharge,
> UnitPrice, Qty, ExtendedPrice, WorkOrder)
> SELECT Invoice_MC.InvNo, MiscCharge, UnitPrice, Qty,
> ExtendedPrice, WorkOrder
> FROM tmpInvoice INNER JOIN [D8J5ZH11\CASQL].
> [EncompassCA].[dbo].[Invoice_MiscCharge] AS Invoice_MC
> ON tmpInvoice.InvNo = Invoice_MC.InvNo
> where tmpInvoice.invno=240530579
>
> Server: Msg 8501, Level 16, State 1, Line 1
> MSDTC on server 'D8J5ZH11\CASQL' is unavailable.
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB
> provider 'SQLOLEDB' was unable to begin a distributed
> transaction.
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d01c].
> If I run just the select part of the query it works just
> fine but as soon as I add the insert it bombs. Even with
> trying to insert just one record.|||Thank you for the reference. I am taking a look at the
page. I guess what really has me stumped is the query
that is failing is the 5th query in the list. All the
other queries run against the same server/database but the
only thing that changes are the tables.
Thank you for the information
David

>--Original Message--
>Check how to troubleshoot this error at
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;306212 BTW, check if
>your DTC service is runnin as well.
>--
>Dejan Sarka, SQL Server MVP
>Associate Mentor
>Solid Quality Learning
>More than just Training
>www.SolidQualityLearning.com
>"David" <dagwin@.hotmail.com> wrote in message
> news:1855201c44a5b$31568690$a501280a@.phx
.gbl...
of[vbcol=seagreen]
that[vbcol=seagreen]
with[vbcol=seagreen]
>
>.
>sql

Monday, March 19, 2012

error 7102

I have merge replication setup on SQL 2000. I am getting
the following error during when the snapshot runs:
Error: 7102, Severity: 20, State: 7
SQL Server Internal Error. Text manager cannot continue
with current statement..
The only KB article I can find does not seem to be
relevent.
Anyone have any idea? Thanks!
Dave
Dave,
interesting - I've never heard of this error before, apart from with SQL 7.0
(http://support.microsoft.com/default...;EN-US;q246775).
A workaround in this case was to lock down the table (HOLDLOCK), but my
understanding is that the table is locked down in the snapshot creation for
merge, (unlike transactional where there is an option for concurrent
snapshot generation). You could try generating the snapshot when noone else
is on the system just to verify if it is a concurrency issue. Alternatively,
as this is apparently a new error, and assuming you have sp3 on the
publisher, distributor and subscriber, I'd consider raising this issue with
PSS.
Regards,
Paul Ibison
|||Thanks Paul,
That is kind of what I was expecting. I am the only user
connected to the database. I even tried to remove the
publication both in Enterprise manager and through the
query analyzer and I get the same error. This database
is really a copy of the original and could easily be
recreated if I could just get rid of everything.
Dave
>--Original Message--
>Dave,
>interesting - I've never heard of this error before,
apart from with SQL 7.0
>(http://support.microsoft.com/default.aspx?scid=kb;EN-
US;q246775).
>A workaround in this case was to lock down the table
(HOLDLOCK), but my
>understanding is that the table is locked down in the
snapshot creation for
>merge, (unlike transactional where there is an option
for concurrent
>snapshot generation). You could try generating the
snapshot when noone else
>is on the system just to verify if it is a concurrency
issue. Alternatively,
>as this is apparently a new error, and assuming you have
sp3 on the
>publisher, distributor and subscriber, I'd consider
raising this issue with
>PSS.
>Regards,
>Paul Ibison
>
>.
>

Sunday, March 11, 2012

ERROR 605, SEVERITY 21

Hi,
I found error in the SERVER(subscriber in merge replication) windows event
viewer the error is regarding a particular database(out of 15).
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/23/2005
Time: 12:32:26 AM
User: N/A
Computer: DTDPMS
Description:
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
object 'PatientAlerts', not to object 'chargepostingprocs'.
Data:
0000: 5d 02 00 00 15 00 00 00 ]......
0008: 07 00 00 00 44 00 54 00 ...D.T.
0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
0018: 00 00 06 00 00 00 43 00 .....C.
0020: 45 00 52 00 45 00 53 00 E.R.E.S.
0028: 00 00 ..
can u help me.
What is the reason for this message?
How can I resolve this?
Thanks,
Sourahttp://www.mssqlcity.com/FAQ/Trouble/er605.htm
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"SouRa" <SouRa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||The first thing should be to check the db integrity using "dbcc checkdb".
AMB
"SouRa" wrote:
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>

ERROR 605, SEVERITY 21

Hi,
I found error in the SERVER(subscriber in merge replication) windows event
viewer the error is regarding a particular database(out of 15).
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/23/2005
Time: 12:32:26 AM
User: N/A
Computer: DTDPMS
Description:
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
object 'PatientAlerts', not to object 'chargepostingprocs'.
Data:
0000: 5d 02 00 00 15 00 00 00 ]......
0008: 07 00 00 00 44 00 54 00 ...D.T.
0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
0018: 00 00 06 00 00 00 43 00 .....C.
0020: 45 00 52 00 45 00 53 00 E.R.E.S.
0028: 00 00 ..
can u help me.
What is the reason for this message?
How can I resolve this?
Thanks,
Sourahttp://www.mssqlcity.com/FAQ/Trouble/er605.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"SouRa" <SouRa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||The first thing should be to check the db integrity using "dbcc checkdb".
AMB
"SouRa" wrote:

> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>|||http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>

ERROR 605, SEVERITY 21

Hi,
I found error in the SERVER(subscriber in merge replication) windows event
viewer the error is regarding a particular database(out of 15).
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 6/23/2005
Time: 12:32:26 AM
User: N/A
Computer: DTDPMS
Description:
Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
object 'PatientAlerts', not to object 'chargepostingprocs'.
Data:
0000: 5d 02 00 00 15 00 00 00 ]......
0008: 07 00 00 00 44 00 54 00 ...D.T.
0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
0018: 00 00 06 00 00 00 43 00 .....C.
0020: 45 00 52 00 45 00 53 00 E.R.E.S.
0028: 00 00 ..
can u help me.
What is the reason for this message?
How can I resolve this?
Thanks,
Soura
http://www.mssqlcity.com/FAQ/Trouble/er605.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"SouRa" <SouRa@.discussions.microsoft.com> schrieb im Newsbeitrag
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>
|||The first thing should be to check the db integrity using "dbcc checkdb".
AMB
"SouRa" wrote:

> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>
|||http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"SouRa" <SouRa@.discussions.microsoft.com> wrote in message
news:3A2EC9C8-06D3-4BC7-85BF-22A732A35B6C@.microsoft.com...
> Hi,
> I found error in the SERVER(subscriber in merge replication) windows event
> viewer the error is regarding a particular database(out of 15).
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 6/23/2005
> Time: 12:32:26 AM
> User: N/A
> Computer: DTDPMS
> Description:
> Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:98036) in database 'CERES' belongs to
> object 'PatientAlerts', not to object 'chargepostingprocs'.
> Data:
> 0000: 5d 02 00 00 15 00 00 00 ]......
> 0008: 07 00 00 00 44 00 54 00 ...D.T.
> 0010: 44 00 50 00 4d 00 53 00 D.P.M.S.
> 0018: 00 00 06 00 00 00 43 00 .....C.
> 0020: 45 00 52 00 45 00 53 00 E.R.E.S.
> 0028: 00 00 ..
> can u help me.
> What is the reason for this message?
> How can I resolve this?
> Thanks,
> Soura
>

Friday, March 9, 2012

ERROR 515: while creating a merge replication publication

I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
|||Since I'm not sure "what that is/ why I need it", I guess I'd have to say no. When I attempt to create the publication, I get the following messages:
SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated.
Adding a new column will:
Cause INSERT statements without column lists to fail
Increase the size of the table
Increase the time required to generate the first snapshot
SQL Server will add a uniqueidentifier column with a unique index and the ROWGUIDCOL property to each of the following tables.
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblControl]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
[dbo].[tblReportParameters]
[dbo].[tblUsers]
AND
It is strongly recommendeds that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity range management is enabled for an article, SQL Server automatically adds the NOT FOR REPLICATION option to the IDENTITY column.
The following published tables, for which automatic identity range management has not been enabled, contain IDENTITY columns without the NOT FOR REPLICATION option:
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
SQL Server automatically adds what I need, right?
Thanks,
Chris McKenzie
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OGF4$2koEHA.1088@.TK2MSFTNGP09.phx.gbl...
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
|||There is a bug if you have a composite primary key which may generate the error message you are seeing.
The best way to check for this is to open up Enterprise Manager, connect to your publisher, expand your publication database and click on the tables folder. For each table you are replication right click on it and select design table. Look for icons to the left of columns which have a key on them. This is your primary key. If more than one column has the key icon on per table you have a composite primary key. You will have to talk to your developers or the vendor who created the database about changing the composite primary key.
You might also want to open a support incident with Microsoft on this on how to proceed.
Regarding the informational messages EM is throwing up.
Cause insert statements without column lists to fail.
If your application issues queries like this
insert into tablename1
select * from tablename2
you may get an application failure unless the GUID column (used to track changes in merge replication) is added to both tables. You will have to consult your developers or the vendor to confirm this is not happening. Or you can replicated every table using merge replication.
Regarding the changing size of the table - merge replication adds a GUID column of 16 bytes. This may cause very slight performance degradation on heavily utilized systems, and may make wide tables exceed the 8k maximum width of a table. Unless your tables are wide you should not have to worry about it.
Regarding the guid column - you should not have to worry about this as it almost always is not problematic. It will cause the snapshot creation time to increase especially on very large tables.
Regarding the identity column. As a good practice you should manually change your identity columns to not for replication. To make this change right click on your tables and select design table. Give focus to your identity columns and in the drop down box in the lower portion of the dialog change identity(YES) to Identity (NOT FOR REPLICATION).
HTH
"Chris McKenzie" <taganov@.charter.net> wrote in message news:ObSMlFloEHA.3900@.TK2MSFTNGP10.phx.gbl...
Since I'm not sure "what that is/ why I need it", I guess I'd have to say no. When I attempt to create the publication, I get the following messages:
SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated.
Adding a new column will:
Cause INSERT statements without column lists to fail
Increase the size of the table
Increase the time required to generate the first snapshot
SQL Server will add a uniqueidentifier column with a unique index and the ROWGUIDCOL property to each of the following tables.
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblControl]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
[dbo].[tblReportParameters]
[dbo].[tblUsers]
AND
It is strongly recommendeds that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity range management is enabled for an article, SQL Server automatically adds the NOT FOR REPLICATION option to the IDENTITY column.
The following published tables, for which automatic identity range management has not been enabled, contain IDENTITY columns without the NOT FOR REPLICATION option:
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
SQL Server automatically adds what I need, right?
Thanks,
Chris McKenzie
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OGF4$2koEHA.1088@.TK2MSFTNGP09.phx.gbl...
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
|||HI Hilary,
I know what you mean by a composite primary key now. I don't use those normally, so I was a little thrown by terminology, lol. As far as manipulating the database goes, I have sole discretion over that.
I did as you suggested and manually changed my IDENTITY PRIMARY KEY columns to PRIMARY KEY IDENTITY NOT FOR REPLICATION.
Every table in the databas has one and only one PRIMARY KEY column now, and they are all created as IDENTITY NOT FOR REPLICATION. STill, when I try to create the new publication article, I get the same error.
Thanks for your help, and please let me know if you have any other ideas.
Chris
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ePBmXploEHA.1308@.TK2MSFTNGP14.phx.gbl...
There is a bug if you have a composite primary key which may generate the error message you are seeing.
The best way to check for this is to open up Enterprise Manager, connect to your publisher, expand your publication database and click on the tables folder. For each table you are replication right click on it and select design table. Look for icons to the left of columns which have a key on them. This is your primary key. If more than one column has the key icon on per table you have a composite primary key. You will have to talk to your developers or the vendor who created the database about changing the composite primary key.
You might also want to open a support incident with Microsoft on this on how to proceed.
Regarding the informational messages EM is throwing up.
Cause insert statements without column lists to fail.
If your application issues queries like this
insert into tablename1
select * from tablename2
you may get an application failure unless the GUID column (used to track changes in merge replication) is added to both tables. You will have to consult your developers or the vendor to confirm this is not happening. Or you can replicated every table using merge replication.
Regarding the changing size of the table - merge replication adds a GUID column of 16 bytes. This may cause very slight performance degradation on heavily utilized systems, and may make wide tables exceed the 8k maximum width of a table. Unless your tables are wide you should not have to worry about it.
Regarding the guid column - you should not have to worry about this as it almost always is not problematic. It will cause the snapshot creation time to increase especially on very large tables.
Regarding the identity column. As a good practice you should manually change your identity columns to not for replication. To make this change right click on your tables and select design table. Give focus to your identity columns and in the drop down box in the lower portion of the dialog change identity(YES) to Identity (NOT FOR REPLICATION).
HTH
"Chris McKenzie" <taganov@.charter.net> wrote in message news:ObSMlFloEHA.3900@.TK2MSFTNGP10.phx.gbl...
Since I'm not sure "what that is/ why I need it", I guess I'd have to say no. When I attempt to create the publication, I get the following messages:
SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated.
Adding a new column will:
Cause INSERT statements without column lists to fail
Increase the size of the table
Increase the time required to generate the first snapshot
SQL Server will add a uniqueidentifier column with a unique index and the ROWGUIDCOL property to each of the following tables.
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblControl]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
[dbo].[tblReportParameters]
[dbo].[tblUsers]
AND
It is strongly recommendeds that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity range management is enabled for an article, SQL Server automatically adds the NOT FOR REPLICATION option to the IDENTITY column.
The following published tables, for which automatic identity range management has not been enabled, contain IDENTITY columns without the NOT FOR REPLICATION option:
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
SQL Server automatically adds what I need, right?
Thanks,
Chris McKenzie
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OGF4$2koEHA.1088@.TK2MSFTNGP09.phx.gbl...
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
|||I am afraid I don't. I did a search on your problem and found some matches indicating it might be a bug.
Can you call PSS on this one?
"Chris McKenzie" <taganov@.charter.net> wrote in message news:%23dZ6$EmoEHA.3668@.TK2MSFTNGP15.phx.gbl...
HI Hilary,
I know what you mean by a composite primary key now. I don't use those normally, so I was a little thrown by terminology, lol. As far as manipulating the database goes, I have sole discretion over that.
I did as you suggested and manually changed my IDENTITY PRIMARY KEY columns to PRIMARY KEY IDENTITY NOT FOR REPLICATION.
Every table in the databas has one and only one PRIMARY KEY column now, and they are all created as IDENTITY NOT FOR REPLICATION. STill, when I try to create the new publication article, I get the same error.
Thanks for your help, and please let me know if you have any other ideas.
Chris
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ePBmXploEHA.1308@.TK2MSFTNGP14.phx.gbl...
There is a bug if you have a composite primary key which may generate the error message you are seeing.
The best way to check for this is to open up Enterprise Manager, connect to your publisher, expand your publication database and click on the tables folder. For each table you are replication right click on it and select design table. Look for icons to the left of columns which have a key on them. This is your primary key. If more than one column has the key icon on per table you have a composite primary key. You will have to talk to your developers or the vendor who created the database about changing the composite primary key.
You might also want to open a support incident with Microsoft on this on how to proceed.
Regarding the informational messages EM is throwing up.
Cause insert statements without column lists to fail.
If your application issues queries like this
insert into tablename1
select * from tablename2
you may get an application failure unless the GUID column (used to track changes in merge replication) is added to both tables. You will have to consult your developers or the vendor to confirm this is not happening. Or you can replicated every table using merge replication.
Regarding the changing size of the table - merge replication adds a GUID column of 16 bytes. This may cause very slight performance degradation on heavily utilized systems, and may make wide tables exceed the 8k maximum width of a table. Unless your tables are wide you should not have to worry about it.
Regarding the guid column - you should not have to worry about this as it almost always is not problematic. It will cause the snapshot creation time to increase especially on very large tables.
Regarding the identity column. As a good practice you should manually change your identity columns to not for replication. To make this change right click on your tables and select design table. Give focus to your identity columns and in the drop down box in the lower portion of the dialog change identity(YES) to Identity (NOT FOR REPLICATION).
HTH
"Chris McKenzie" <taganov@.charter.net> wrote in message news:ObSMlFloEHA.3900@.TK2MSFTNGP10.phx.gbl...
Since I'm not sure "what that is/ why I need it", I guess I'd have to say no. When I attempt to create the publication, I get the following messages:
SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated.
Adding a new column will:
Cause INSERT statements without column lists to fail
Increase the size of the table
Increase the time required to generate the first snapshot
SQL Server will add a uniqueidentifier column with a unique index and the ROWGUIDCOL property to each of the following tables.
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblControl]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
[dbo].[tblReportParameters]
[dbo].[tblUsers]
AND
It is strongly recommendeds that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity range management is enabled for an article, SQL Server automatically adds the NOT FOR REPLICATION option to the IDENTITY column.
The following published tables, for which automatic identity range management has not been enabled, contain IDENTITY columns without the NOT FOR REPLICATION option:
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
SQL Server automatically adds what I need, right?
Thanks,
Chris McKenzie
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OGF4$2koEHA.1088@.TK2MSFTNGP09.phx.gbl...
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris
|||I'm going to try reinstalling SQL Server and see if that takes care of it. I've tried the same operation on other installations and it works.
Chris
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:unrh$fmoEHA.3792@.TK2MSFTNGP11.phx.gbl...
I am afraid I don't. I did a search on your problem and found some matches indicating it might be a bug.
Can you call PSS on this one?
"Chris McKenzie" <taganov@.charter.net> wrote in message news:%23dZ6$EmoEHA.3668@.TK2MSFTNGP15.phx.gbl...
HI Hilary,
I know what you mean by a composite primary key now. I don't use those normally, so I was a little thrown by terminology, lol. As far as manipulating the database goes, I have sole discretion over that.
I did as you suggested and manually changed my IDENTITY PRIMARY KEY columns to PRIMARY KEY IDENTITY NOT FOR REPLICATION.
Every table in the databas has one and only one PRIMARY KEY column now, and they are all created as IDENTITY NOT FOR REPLICATION. STill, when I try to create the new publication article, I get the same error.
Thanks for your help, and please let me know if you have any other ideas.
Chris
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:ePBmXploEHA.1308@.TK2MSFTNGP14.phx.gbl...
There is a bug if you have a composite primary key which may generate the error message you are seeing.
The best way to check for this is to open up Enterprise Manager, connect to your publisher, expand your publication database and click on the tables folder. For each table you are replication right click on it and select design table. Look for icons to the left of columns which have a key on them. This is your primary key. If more than one column has the key icon on per table you have a composite primary key. You will have to talk to your developers or the vendor who created the database about changing the composite primary key.
You might also want to open a support incident with Microsoft on this on how to proceed.
Regarding the informational messages EM is throwing up.
Cause insert statements without column lists to fail.
If your application issues queries like this
insert into tablename1
select * from tablename2
you may get an application failure unless the GUID column (used to track changes in merge replication) is added to both tables. You will have to consult your developers or the vendor to confirm this is not happening. Or you can replicated every table using merge replication.
Regarding the changing size of the table - merge replication adds a GUID column of 16 bytes. This may cause very slight performance degradation on heavily utilized systems, and may make wide tables exceed the 8k maximum width of a table. Unless your tables are wide you should not have to worry about it.
Regarding the guid column - you should not have to worry about this as it almost always is not problematic. It will cause the snapshot creation time to increase especially on very large tables.
Regarding the identity column. As a good practice you should manually change your identity columns to not for replication. To make this change right click on your tables and select design table. Give focus to your identity columns and in the drop down box in the lower portion of the dialog change identity(YES) to Identity (NOT FOR REPLICATION).
HTH
"Chris McKenzie" <taganov@.charter.net> wrote in message news:ObSMlFloEHA.3900@.TK2MSFTNGP10.phx.gbl...
Since I'm not sure "what that is/ why I need it", I guess I'd have to say no. When I attempt to create the publication, I get the following messages:
SQL Server requires that all merge articles contain a uniqueidentifier column with a unique index and the ROWGUIDCOL property. SQL Server will add a uniqueidentifier column to published tables that do not have one when the first snapshot is generated.
Adding a new column will:
Cause INSERT statements without column lists to fail
Increase the size of the table
Increase the time required to generate the first snapshot
SQL Server will add a uniqueidentifier column with a unique index and the ROWGUIDCOL property to each of the following tables.
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblControl]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
[dbo].[tblReportParameters]
[dbo].[tblUsers]
AND
It is strongly recommendeds that all replicated IDENTITY columns use the NOT FOR REPLICATION option. When automatic identity range management is enabled for an article, SQL Server automatically adds the NOT FOR REPLICATION option to the IDENTITY column.
The following published tables, for which automatic identity range management has not been enabled, contain IDENTITY columns without the NOT FOR REPLICATION option:
[dbo].[tblActivity]
[dbo].[tblAssetPayable]
[dbo].[tblClass]
[dbo].[tblGLJournal]
[dbo].[tblItemClasses]
[dbo].[tblItemMaster]
[dbo].[tblItemVendors]
[dbo].[tblPicture]
SQL Server automatically adds what I need, right?
Thanks,
Chris McKenzie
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:OGF4$2koEHA.1088@.TK2MSFTNGP09.phx.gbl...
do you have a composite primary key?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Chris McKenzie" <taganov@.charter.net> wrote in message news:e6fdwpkoEHA.1776@.TK2MSFTNGP14.phx.gbl...
I've been trying to work through the example listed at http://www.databasejournal.com/featu...le.php/1438231 but I keep getting the following error when I try to create the pubs_article publication:
SQL Server Enterprise Manager could not create publication 'pubs_article' from database 'pubs.'
Error 515: Cannot insert the value NULL into column 'step_name', table 'msdb.dbo.sysjobsteps'. column does not allow nulls. INSERT failed.
Any ideas?
Chris

Error 515

I get this error during Merge replication
" Cannot insert the value NULL into column 'nicknames', table
'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT fails. "
Can anyone help
Did you register your publisher or subscriber using an IP address? There
have been reports in the past that this can cause this problem.
Hilary Cotter
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
"Sesha" <Sesha@.discussions.microsoft.com> wrote in message
news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> I get this error during Merge replication
> " Cannot insert the value NULL into column 'nicknames', table
> 'REP_Sub.dbo.MSmerge_genhistory'; column does not allow nulls. INSERT
fails. "
> Can anyone help
|||Sesha,
You must check @.@.servername on the SUBSCRIBER. This will probably return a
NULL.
Select * from sysservers
This will give you a list of local/linked/remote servers on that box. If you
returned NULL above, it's because the server has gotten confused about not
having a local named server (SRVID=0) to put in the nickname table.
If you don't have a SRVID=0 and your servername does exist in the list then
do the following:
SP_dropserver 'Servername'
go
Sp_Addserver 'Servername','local'
If it doesn't exist and you don't have SRVID=0 then just do the Add.
That should sort you out.
Good luck.
"Hilary Cotter" wrote:

> Did you register your publisher or subscriber using an IP address? There
> have been reports in the past that this can cause this problem.
> --
> Hilary Cotter
> 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
> "Sesha" <Sesha@.discussions.microsoft.com> wrote in message
> news:87EB3D3B-913F-4B6B-8FC7-471517A0F444@.microsoft.com...
> fails. "
>
>

Wednesday, March 7, 2012

Error 3726

Hi all,
I am encountering a similar problem to Tom's. I am trying to do a merge repl
with sql 2005 on both ends. I have a decent size db of 1.2 gb. I had the
replication working ok before. But due to some updates I had to apply to a
program , I had to break replication. When get the snapshot made and the try
to sync I get: "The schema script "xxx.sch" could not be propagated to the
subscriber." Upon further digging in the logs I see that I too am getting the
3726 saying "Could not drop object 'dbo.xxx' because it is referenced by a
FOREIGN KEY constraint."
I remember getting this error before and I had re-created the publication a
few times and was somehow able to get it to work. I am not able to get it to
work now. Any insight would be greatly appreciated.
Thanks
"Tom" wrote:

> I am doing a snapshot replication between SQL server 200 and SQLexpress.
> When I sync I get the following error:
> Could not drop object 'Events' because it is referenced by a FOREIGN KEY
> constraint..
> I went into the "Events" table and removed all the foreign keys, but the
> error persists. Also, the database is being used for simple queries and no
> data input.
> Any insight would be appreciated.
> Tom
>
>
>
I answered this in your other post, but I believe Tom's case was different -
certainly the description is distinct in that he mentions he removed the FK
constraints. It might be that he removed them on the publisher! In this case
he does has the same issue and will need to drop them on the subscriber
before the table is dropped eg via a pre-snapshot script.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Friday, February 24, 2012

Error 28562 and Error 28037

Hi to All,
I have a Merge Replication on SQL2005 SP1 running on a Microsoft
Server 2003 SP1.
My Subscribers are 60 Handhelds.

>From time to time when Handhelds try to Synch, we get Error 28562 on
some of them
and its usually resolved by warm booting the Handheld and then Re-
Synch.
I dont know if this solution is just luck or if the error indicates a
handheld memory issue.
This error usually Occurs when the Subscriber has a lot of deletions
to process.
My first Question is ,why from time to time the subscriber has large
numbers of rows to delete and why
this error appears.
Now from time to time again i get a 28037 Error witch again the
Resolving of it is to Re-Synch.
Can somebody Please explain this Error?
Thanks
Savvas Christodoulou
P.S If I put SQL2005 SP2 and MS2003 SP2 will this issues continue?
I believe these errors indicate problems in establishing connection to the
IIS of your server.
read this :
[url]http://www.kbalertz.com/842907/Server.client.programs.connect.computers.running.W indows.aspx[/url]
maybe it will help you...
r
<savvaschr@.nodalsoft.com.cy> wrote in message
news:1174977871.162264.63080@.p15g2000hsd.googlegro ups.com...
> Hi to All,
> I have a Merge Replication on SQL2005 SP1 running on a Microsoft
> Server 2003 SP1.
> My Subscribers are 60 Handhelds.
> some of them
> and its usually resolved by warm booting the Handheld and then Re-
> Synch.
> I dont know if this solution is just luck or if the error indicates a
> handheld memory issue.
> This error usually Occurs when the Subscriber has a lot of deletions
> to process.
> My first Question is ,why from time to time the subscriber has large
> numbers of rows to delete and why
> this error appears.
> Now from time to time again i get a 28037 Error witch again the
> Resolving of it is to Re-Synch.
> Can somebody Please explain this Error?
> Thanks
> Savvas Christodoulou
> P.S If I put SQL2005 SP2 and MS2003 SP2 will this issues continue?
>
|||If the problem is on Establishing connection with IIS then why all
other Handhelds can establish is via GPRS and only 1 or 2 per day
cannot do it and they have to Re-Synch?
And I also have to mension that in replication monitor I can see the
failure attemp of Synchronization, if there is a problem with the
connection there is no link to the server and the attemp to synch
never reatch the Server.
Any Other ideas?

Error 2812 Could not Find Store Procedure dbo.MSmerge_expand_sp_A2F.......

Hi i am running SQL 2005 and i have a merge replication.
Sudently when i am trying to insert a new record on a table i am
getting this Error.
Error 2812 Could not Find Store Procedure
dbo.MSmerge_expand_sp_A2F......
Can anyone help please
Thanks
Savvas Christodoulou
Sounds like this proc is missing. Can you locate it on other subscribers? If
so copy it here.
Normally when you get errors like this your replication metadata is
inconsistent and it is best solved by regenerating and redistributing the
snapshot.
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
<savvaschr@.nodalsoft.com.cy> wrote in message
news:1163094573.683827.298500@.m73g2000cwd.googlegr oups.com...
> Hi i am running SQL 2005 and i have a merge replication.
> Sudently when i am trying to insert a new record on a table i am
> getting this Error.
> Error 2812 Could not Find Store Procedure
> dbo.MSmerge_expand_sp_A2F......
> Can anyone help please
> Thanks
> Savvas Christodoulou
>

Friday, February 17, 2012

Error -2147024809 An error has occured on the computer running IIS

I am sync. for the first time (Merge Replication using SQL 2005 and Mobile) and this error keeps poping up on the emulator. I am tring out the tutorial. :) boss on my butt.

Does anyone have any ideas or a solution to this...your help is WELL APPRECIATED ...

Error code: -2147024809

zo

1. Can I assume the merge emulator run for merge sync on SQL mobile device?

2. Does the error popup on every sync or from time to time?

Thanks.

|||

I have talked with one of the experts and the error number -2147024809 stands for invalid arguments.

Can you check the parameters again on the sync object? Did you see any exception message also?

Thanks.

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

|||

Sorry for the late reply...The parameters for the sync object (based on the sample in msdn) are correct. At first I thought it was a permission problem. I went through the debug process and the error comes up on the emulator when the code gets to repl.syncronize, then the exception is thrown giving the error above. Here is the code:

Sub Sync()
Dim repl As New SqlCeReplication()

repl.InternetUrl = "http://localhost/SQLMobile/sqlcesa30.dll"
repl.Publisher = "REALTORBUSINESS\JONES_SQL"
repl.PublisherDatabase = "SQLMobile"
repl.PublisherSecurityMode = SecurityType.NTAuthentication
repl.Publication = "SQLMobile"
repl.Subscriber = "SQLMobile"
repl.SubscriberConnectionString = "Data Source='" + filename + "';Max Database Size=128;Default Lock Escalation =100;"
Try
repl.AddSubscription(AddOption.CreateDatabase)
repl.Synchronize()
Catch err As SqlCeException
DisplaySQLCEErrors(err)
End Try

End Sub

Public Sub DisplaySQLCEErrors(ByVal ex As SqlCeException)

Dim errorCollection As SqlCeErrorCollection = ex.Errors
Dim bld As New StringBuilder()
Dim inner As Exception = ex.InnerException
Dim err As SqlCeError

For Each err In errorCollection

bld.Append(ControlChars.Lf + " Error Code: " + err.HResult.ToString())
bld.Append(ControlChars.Lf + " Message : " + err.Message)
bld.Append(ControlChars.Lf + " Minor Err.: " + err.NativeError.ToString())
bld.Append(ControlChars.Lf + " Source : " + err.Source)

Dim numPar As Integer
For Each numPar In err.NumericErrorParameters
If (numPar <> 0) Then
bld.Append(ControlChars.Lf + " Num. Par. : " + numPar.ToString())
End If
Next numPar
Dim errPar As String
For Each errPar In err.ErrorParameters
If (errPar <> String.Empty) Then
bld.Append(ControlChars.Lf + " Err. Par. : " + errPar)
End If
Next errPar

MessageBox.Show(bld.ToString(), "SQL Mobile Error")

Next err

I am going to try straight to the device, emulator might be screwed. Let me know what you find out ... got to figure this out one way or another, I have a project depending on it.

Appreciate everything and everyone ... Thank you.

|||

See what error message in the runtime you have captured.

Thanks.

|||

The error codes from the runtime is as follows:

Error Code: -2147024809

Message: An error has occured on the computer running IIS. Try restarting the IIS Server. (Tried several times)

Minor Error: 28022

Source: Microsoft SQL Server 2005 Mobile Edition

|||

Did you run the above code on the CE device? If true then I am wondering repl.InternetUrl = "http://localhost/SQLMobile/sqlcesa30.dll" might be the cause. Can you try to use the IIS machine name instead of "localhost"?

Thanks.

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

|||

No, I haven't ran it on the CE device. I am using the emulator first, I figure if it woks there it should work anywhere else...but, I will change the URL and see what happens.

Let you know in a minute.

|||I'm pretty sure you need to use HTTPS as well, HTTP should fail with a graceful error msg.|||I had the same error number in a custom build Powerpoint wizard when

you failed to enter a filename of a background picture for the front

page.

In general is seems to indicate a wrong or invalid parameter in a system call.

Complete error message was:

"Err. -2147024809-

Description: The specified file wasn't found."

Wednesday, February 15, 2012

Error 208: Invalid object name 'sysextendedarticlesview'

hi,
for maintainance tasks (converting database from SQL_Latin to Latin_General)
we scripted a working merge replication and removed it with Enterprise
Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
Now, when trying to reinstall the replication (via script or EM), the
publication seems to be installed ok, snapshot passed without error. But the
setup of a new subscription fails with the following error message (raw
translation from german message):
Error 208: Invalid object name 'sysextendedarticlesview'.
(Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
Prozedur sp_addmergesubscription, Zeile 325
Ungltiger Objektname 'sysextendedarticlesview'.)
This view indeed cannot be found on one of the participating servers, but on
a different set of servers, where the same kind of replication is still
running, this view can't be found either.
Any help / suggestions would we appreciated.
TIA
Frank Linde
find a server/database that has this view on. In EM, right click on the view
and select copy. Then connect to the database you are having this problem
using EM. select tools, Query Analyzer and then hit ctrl v.
Then run this script. You may encounter more missing object problems but
they can be solved in the same way.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"A.Hoff" <z100@.gmx.org> wrote in message
news:cbk6a5$j6m$01$1@.news.t-online.com...
> hi,
> for maintainance tasks (converting database from SQL_Latin to
Latin_General)
> we scripted a working merge replication and removed it with Enterprise
> Manager (3 servers, 1 database, SQL 2000 SP3 on all 3 Servers).
> Now, when trying to reinstall the replication (via script or EM), the
> publication seems to be installed ok, snapshot passed without error. But
the
> setup of a new subscription fails with the following error message (raw
> translation from german message):
> Error 208: Invalid object name 'sysextendedarticlesview'.
> (Original Errormessage: Server: Nachr.-Nr. 208, Schweregrad 16, Status 1,
> Prozedur sp_addmergesubscription, Zeile 325
> Ungltiger Objektname 'sysextendedarticlesview'.)
> This view indeed cannot be found on one of the participating servers, but
on
> a different set of servers, where the same kind of replication is still
> running, this view can't be found either.
> Any help / suggestions would we appreciated.
> TIA
> Frank Linde
>