Thursday, March 22, 2012
error 8198
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisR
right click on your agent and make the agent owner sa. Restart your job.
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
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>
|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> 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
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> 8198:
> same
>
error 8198
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisRright click on your agent and make the agent owner sa. Restart your job.
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
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> 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
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> 8198:
> same
>sql
error 8198
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisR
right click on your agent and make the agent owner sa. Restart your job.
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
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>
|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> 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
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> 8198:
> same
>
error 8198
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisRright click on your agent and make the agent owner sa. Restart your job.
--
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
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> 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
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
>> sql2k sp3
>> win2k sp4
>> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
>> Could not obtain information about Windows NT group/ user 'domain/
>> user'".
>> I read this:
>> http://support.microsoft.com/?kbid=834124
>> But both boxes are in the same domain and the same subnet. Both use the
> same
>> domain admin account for SQL Server and the Agent accounts.
>> I also read this:
>> http://support.microsoft.com/?kbid=838460
>> But Im not about to install sp4 Beta on anything.
>> Is there anything else I can do?
>> TIA, ChrisR
>>
>
Error 8102:cannot update identity column
Thanks.Check out this MSDN Article:Replication: Managing Identity Values.
Terri|||Thanks for the reply, I already read this article and it solves the problem but creates another. The article does describe how to increment the Identity column on the subscriber, but it will not match the value on the publisher because you must set the ID column ranges in seperate blocks. Server P 1-1000 Server S 1001-2000 When 1 is used on P, it insert 1001 on S.
Here's what I'm doing and maybe there is another way to do it.
I have two servers running my application, 1 exposed to the Internet for client access and one for my Intranet. I need an exact replica of my database on the Internet server that is being updated periodically from my Intranet server. I am installing clustered servers soon but I need to have an interim solution in place until then. The publically exposed server is also to act as a backup in the event that my Intranet server goes down.
The database is currently being replicated between the servers, but the Identity columns on the subscriber are not set, so if we had to switch to it I would have to define the ID columns in my tables for my application to work properly.
Would it be okay to point my Internet servers WEB.CONFIG data connection string to the Intranet server and just allow the replication to continue as is, and if I do have an outage direct my Intranet traffic to the Internet server, change the conn string in the WEB.CONFIG and define the ID columns?
Thanks in advance.|||Is your Internet server then serving as a warm standby? Is it then basically a read-only version of the database on your Intranet server??
If so, I can telll you that we usetransaction log shipping to keep a warm standby of our database on a different server.
Otherwise, I'm sorry, replication is out of my league. We had used replication for a short while until we found out that it did not meet our needs (due in part to the IDENTITY column situation). With some research and effort we might have gotten replication to work, but log shipping was exactly right for us.
Terri
PS, if you haven't seen it, you might consider this article:Architecting Replication with Identity Columns
|||Transaction logs would work if I had the Enterprise version of SQL, but I won't have it for a few more months, at which point I am installing clustered servers. I think for the time being I am going to go with allowing it to replicate with no ID columns set on the subscriber. I only have 5, so if there was a problem I could just set the ID columns on the subscriber and then change my DB Connection in my WEB.CONFIG to point to it. This is however a temporary solution.
Thanks, I found your info most helpful.
error 8102:cannot update identity column
I have 2 SQL Servers 2000 enterprise version. I setup a transactional replication between them. There is a table using identity feature and set to not for replication. On the server A as publication, B as Subscriber. I created table in B manually and set the name conflict in article default to keep existing data. When it replicates at the first time, everything is fine, but if there is some data added to the table in Server A, the replication fails, saying cannot update indentity column.
I read about something on add Set Identity on/off thing. But I dont know which SP I should add this to. Please help. As detail as possible. Thanks.There is a bug in the Managed Range Identity system. In Merge Replication I have found that while creating a publication using range identities it will work only the first time. Changing settings such as Publisher range or subscriber range does not have an effect. Also, deleting the subscriptions and publications DOES NOT remove the constraints from the affected subscriber tables. Also, the entry for the database in the replication distribution DB table MSrepl_identity_range does not get deleted and therefore the next time the publication is run it will not take the correct settings. In order to successfully recreate the subscription you must delete the row(s) from the afore mentioned table and remove all constraints manually. Only then will it work. If the constraints are not removed the subscriber will show the identity range as used up and will demand a re-sync, and the re-sync will have no effect.
Applies to SQL Server 2000 All SPs
You MUST delete all publications on the affected database and subscriptions first, then run SP_RemoveDBReplication DBName on the publisher and subscribers first then follow the steps above. You can sp_help to see what constraints are on the tables.|||I am sorry, if I undertsand you correctly what you are saying is that I cannot have a replication set up for identity enabled table?|||Originally posted by cobraeyez
I am sorry, if I undertsand you correctly what you are saying is that I cannot have a replication set up for identity enabled table?
no, you can set it up. Just keep in mind that there is a bug in SQL Server relating to the identitiy managing subsystem. What you want to do is delete the pub, subscriptions, drop the Check Constraints on all the subscription tables, find the Identity_Range table in the Replication Distribution database and delete all entries for the database that you are working on. Then recreate the publication and subcription and you will be fine.|||hey. thanks that SP_RemoveDBReplication thing works. :)|||ok, maybe I speak too quick, I think the insert works, but the update doesn't . If I modify a record in the publisher the replication failed again.
And what I did for fix the insert record is remove the publications and subscriptions and ran that RemoveReplication command on the DBs, there is no records in MSrepl_indentity_range table for me to delete.|||ok. The article containing the identitiy field is not set to range identitiy. When you set up the publication you need to click the "..." button to the right of the article name, then click the "Identity Range" tab. Enter your values and click OK to start the Identitiy Ranging.|||thanks, you mean the table article property button (...) right? In there, there is no Identity Range Tab. There are 3 tabs in it. General, Command, Snapshot.|||You will only have that tab on articles that have an identitiy column. Are you sure the article has an Identitiy?|||yes, and I am using sql 2000, identity is enabled and set not for replication|||You've got much of suggestions to the question, but I hope this MSDN Link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) also gives you much insight to resolve.
HTH|||I had a similar problem and it was because I had triggers and DRI on the same table
Error 8102: Cannot Update Identity Column
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.Originally posted by da_i256
Hi,
I'd set up Transactional Replication btw 2 servers running on MSSQL 2000.
However, from time to time, I encounter Error 8102. I try to reinitialise the subscription but failed. After I delete the current subscription and PUSH a new one, it will works fine again.
I'm curious why this is happening as I'd already set all the tables (articles) in the subscriber to "YES, not_for_replication".
Any idea?
Thanks.
check this thread:
http://dbforums.com/arch/7/2003/5/779346|||thanks, harshal_in...
then link did provide some insights into the matter.
anyone else got any idea?
thanks.|||Have you gone thru the MSDN link (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlpro01/html/sql01d4.asp) referred in the above post, it must have resolved with the workaround mentioned.|||Thanks guys...
the problem solved... :>sql
Error 8102, Cannot update identity
I have setup unidirectional transaction replication between two SQL2k
servers. On the subscription database I have set the PK as (Indentity not
for Replication).
I can insert and delete records on the publisher and they get replicated
without any errors, but on the updates I get an error.
The issue I belieive is with the generated sp_MSupd stored procedure. For
some reason it is tring to execute the first block even if the logic is
false.
Can someone please advise how to get around this issue.
Thanks
This problem is caused by updating the PK. You have to look at exactly what
the application which is modifying the data on the publisher is doing.
For some applications (including ones using the .net DataGrid component),
any update of any column in a table results in the update of all columns.
This is translated as a delete followed by an insert.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"mm" <postto@.news.com> wrote in message
news:%23lUTk14mEHA.1296@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have setup unidirectional transaction replication between two SQL2k
> servers. On the subscription database I have set the PK as (Indentity not
> for Replication).
> I can insert and delete records on the publisher and they get replicated
> without any errors, but on the updates I get an error.
> The issue I belieive is with the generated sp_MSupd stored procedure. For
> some reason it is tring to execute the first block even if the logic is
> false.
> Can someone please advise how to get around this issue.
> Thanks
>
>
Error 80040E35 while syncing with SQL CE
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:
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
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.
Monday, March 19, 2012
error 7102
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
>
>.
>
Error 627:Cannot use SAVE TRANSACTION within a distributed transac
SQL Server 2000 Enterprise Edition
Server Pack 3a
Server Edition is Windows 2000 Advanced Server
Replication Type is Transactional
I am trying to drop a publication. I am getting the error:
Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
This error also is generated when trying to drop the individual subscription.
Can anyone provide insight as to what could be causing this error?
Thank you in advance.
Robert M.Check the "remote proc trans" value from sp_configure. If it's 1, you need
to change it to 0.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> Information:
> SQL Server 2000 Enterprise Edition
> Server Pack 3a
> Server Edition is Windows 2000 Advanced Server
> Replication Type is Transactional
> I am trying to drop a publication. I am getting the error:
> Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> This error also is generated when trying to drop the individual
subscription.
> Can anyone provide insight as to what could be causing this error?
> Thank you in advance.
> Robert M.
>|||I am assuming that the 'remote proc trans' setting needs to be set to zero on
the publisher (i have separate servers for distributor/publisher/subscriber).
Thanks...Robert M.
"Richard Ding" wrote:
> Check the "remote proc trans" value from sp_configure. If it's 1, you need
> to change it to 0.
>
> "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > Information:
> > SQL Server 2000 Enterprise Edition
> > Server Pack 3a
> > Server Edition is Windows 2000 Advanced Server
> > Replication Type is Transactional
> >
> > I am trying to drop a publication. I am getting the error:
> > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> >
> > This error also is generated when trying to drop the individual
> subscription.
> >
> > Can anyone provide insight as to what could be causing this error?
> >
> > Thank you in advance.
> >
> > Robert M.
> >
> >
>
>|||Actually, I believe it should be set to 0 on the subscriber. No need to
touch the values on publisher or distributor.
"Robert M." <RobertM@.discussions.microsoft.com> wrote in message
news:4A56EC3F-0537-441C-990E-0C7D43BD972C@.microsoft.com...
> I am assuming that the 'remote proc trans' setting needs to be set to zero
on
> the publisher (i have separate servers for
distributor/publisher/subscriber).
> Thanks...Robert M.
> "Richard Ding" wrote:
> > Check the "remote proc trans" value from sp_configure. If it's 1, you
need
> > to change it to 0.
> >
> >
> > "Robert M." <RobertM@.discussions.microsoft.com> wrote in message
> > news:28E165FE-67B2-44F1-98DC-1F2CB3EA0B7E@.microsoft.com...
> > > Information:
> > > SQL Server 2000 Enterprise Edition
> > > Server Pack 3a
> > > Server Edition is Windows 2000 Advanced Server
> > > Replication Type is Transactional
> > >
> > > I am trying to drop a publication. I am getting the error:
> > > Error 627:Cannot use SAVE TRANSACTION within a distributed transaction
> > >
> > > This error also is generated when trying to drop the individual
> > subscription.
> > >
> > > Can anyone provide insight as to what could be causing this error?
> > >
> > > Thank you in advance.
> > >
> > > Robert M.
> > >
> > >
> >
> >
> >
Sunday, March 11, 2012
ERROR 605, SEVERITY 21
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
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
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
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
" 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. "
>
>
Error 50007: xp_execresultset: unable to get a bound connection back to server
I have just resinstalled my server and restored the backup of my database. I am now trying to re-setup replication and I get the above error. The server configuiration:
Win2k3
SQL Server 2000 SP4
Replication: Distributor & Publisher (intended Push Publisher)
Snapshot
Subscriber: Remote server
I have looked around the web for similar problems and resolutions but mine still does not want to work. I have completely removed the replication as per the information on this article: http://support.microsoft.com/kb/324401 but still cannot get it working.
I did not backup the distribution db, master or msdb - only the main database I want to replicate.
Any advice?
Thanx
Dave
From http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
You get this error when you have not set up your administrative link
password correctly. Either uncheck this option or ensure that when you
configure your publisher you enter the correct one.
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
"Dave" <nospam@.developmentnow.com> wrote in message
news:2ae92f81-6f29-41d1-ba10-e7841b355fbb@.developmentnow.com...
> Hi,
> I have just resinstalled my server and restored the backup of my database.
> I am now trying to re-setup replication and I get the above error. The
> server configuiration:
> Win2k3
> SQL Server 2000 SP4
> Replication: Distributor & Publisher (intended Push Publisher)
> Snapshot
> Subscriber: Remote server
> I have looked around the web for similar problems and resolutions but mine
> still does not want to work. I have completely removed the replication as
> per the information on this article:
> http://support.microsoft.com/kb/324401 but still cannot get it working.
> I did not backup the distribution db, master or msdb - only the main
> database I want to replicate.
> Any advice?
> Thanx
> Dave
> From
> http://www.developmentnow.com/g/114_0_0_0_0_0/sql-server-replication.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
|||Hi,
Thanx for the information. I have managed to get it to work again by creating a new username and password for the distribution agents to use. Initially it was set to impersonate the service account (which is a domain account that the SQL Services use). I would have thought that this would be sufficient. I even gave this account sysadmin privledges.
Also, when I first setup the replication it worked without having to change any usernames and/or passwords. Was the problem because I recovered from a backup?
Thanx
Dave
From http://www.developmentnow.com/g/114_2007_7_0_0_995269/Error-50007-xp-execresultset-unable-to-get-a-bound-connection-back-to-server.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
|||Its hard to say what caused the problem, but I am glad you have solved it.
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
"Dave" <nospam@.developmentnow.com> wrote in message
news:2258406d-86c6-4c5e-87e2-1283b7f9b4e6@.developmentnow.com...
> Hi,
> Thanx for the information. I have managed to get it to work again by
> creating a new username and password for the distribution agents to use.
> Initially it was set to impersonate the service account (which is a domain
> account that the SQL Services use). I would have thought that this would
> be sufficient. I even gave this account sysadmin privledges.
> Also, when I first setup the replication it worked without having to
> change any usernames and/or passwords. Was the problem because I recovered
> from a backup?
> Thanx
> Dave
> From
> http://www.developmentnow.com/g/114_2007_7_0_0_995269/Error-50007-xp-execresultset-unable-to-get-a-bound-connection-back-to-server.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
Wednesday, March 7, 2012
Error 3724 : Cannot delete database
I wanted to delete some databases used for replication. When I
tried to delete them above error message was displayed. I used the the
following SPs and then deleted the databases :
sp_dboption 'databasename', 'published' , 'false'
go
sp_dboption 'databasename', 'merge publish' , 'false'
go
However one database still did not get deleted and displayed the
above error. I then tried changing the Category field to 0 for the database
in "sysdatabases" table of master. ODBC Error was displayed containing the
message "You do not have enough rights to alter a system database".
Can someone tell me how to solve this problem.
Thanks and Regards,
Harshad
Hi,
Try Tools --> Replication --> Configure
Publishing,Subscribers,Distribution --> Publication database --> Disable the
appropriate database
Then try dropping the database.
Hope this helps.
"Harshad Phadnis" wrote:
> Hi,
> I wanted to delete some databases used for replication. When I
> tried to delete them above error message was displayed. I used the the
> following SPs and then deleted the databases :
> sp_dboption 'databasename', 'published' , 'false'
> go
> sp_dboption 'databasename', 'merge publish' , 'false'
> go
>
> However one database still did not get deleted and displayed the
> above error. I then tried changing the Category field to 0 for the database
> in "sysdatabases" table of master. ODBC Error was displayed containing the
> message "You do not have enough rights to alter a system database".
> Can someone tell me how to solve this problem.
> Thanks and Regards,
> Harshad
Friday, February 24, 2012
Error 28562 and Error 28037
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.......
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
>