Internet merge replication. Need to detach to move to a new box. Deleted
all the publication, now when I try to disable it as the publisher. I tried
to run sp_removedbreplication 'db_name' and get the same message.
Any thoughts?
Thanks
After lots more reading and searching, I found low memory could cause this.
I added another 512 to the box, and it worked.
"SteveInBeloit" wrote:
> Internet merge replication. Need to detach to move to a new box. Deleted
> all the publication, now when I try to disable it as the publisher. I tried
> to run sp_removedbreplication 'db_name' and get the same message.
> Any thoughts?
> Thanks
|||I would have bounced the server and then tried this - this is abnormal.
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
"SteveInBeloit" <SteveInBeloit@.discussions.microsoft.com> wrote in message
news:17E5CBD0-5D2A-444A-97BD-4629B2AE3559@.microsoft.com...[vbcol=seagreen]
> After lots more reading and searching, I found low memory could cause
> this.
> I added another 512 to the box, and it worked.
>
> "SteveInBeloit" wrote:
Showing posts with label disable. Show all posts
Showing posts with label disable. Show all posts
Monday, March 19, 2012
Can't disable publishing
I have a server work as publisher and distributor for a database and another
remote server work as subscriber. The remote server downed and reformatted
due to system failure. We setup another remote server with different name.
But when I tried to disable publishing/ delete and recreate subscription at
publisher/distributor server, i received the following error:
The server has been disconnected. Please reconnect it and perform this
action again.
How should i fixed it?
Thank you.
In article <E87D093B-0F0D-4601-9D00-
6988821C47DB@.microsoft.com>, Clarin@.discussions.microsoft.com
says...
> I have a server work as publisher and distributor for a database and another
> remote server work as subscriber. The remote server downed and reformatted
> due to system failure. We setup another remote server with different name.
> But when I tried to disable publishing/ delete and recreate subscription at
> publisher/distributor server, i received the following error:
> The server has been disconnected. Please reconnect it and perform this
> action again.
> How should i fixed it?
> Thank you.
I have had this problem twice. You can do the sp that paul
said to do, but for it work you need to reboot the
publisher. I kept running it, and kept receiving the same
error you were getting. We finally rebooted the publisher
and stopped getting the error.
You can also set a fake subscriber with the same
name/db/tables as the old one (just no data in them), and
then delete it. That worked for us also.
remote server work as subscriber. The remote server downed and reformatted
due to system failure. We setup another remote server with different name.
But when I tried to disable publishing/ delete and recreate subscription at
publisher/distributor server, i received the following error:
The server has been disconnected. Please reconnect it and perform this
action again.
How should i fixed it?
Thank you.
In article <E87D093B-0F0D-4601-9D00-
6988821C47DB@.microsoft.com>, Clarin@.discussions.microsoft.com
says...
> I have a server work as publisher and distributor for a database and another
> remote server work as subscriber. The remote server downed and reformatted
> due to system failure. We setup another remote server with different name.
> But when I tried to disable publishing/ delete and recreate subscription at
> publisher/distributor server, i received the following error:
> The server has been disconnected. Please reconnect it and perform this
> action again.
> How should i fixed it?
> Thank you.
I have had this problem twice. You can do the sp that paul
said to do, but for it work you need to reboot the
publisher. I kept running it, and kept receiving the same
error you were getting. We finally rebooted the publisher
and stopped getting the error.
You can also set a fake subscriber with the same
name/db/tables as the old one (just no data in them), and
then delete it. That worked for us also.
Can't disable publishing
SQL Server will not allow me to disable publishing; it just gets hung up and freezes. I have tried using the wizard in Enterprise Manager and I have also tried running sp_dropsubscription and sp_droppublication in Query Analyzer. I found Hilary's past p
ost on a similar problem that says to run the following code (below). What does this code do? I was wondering if it would help my problem. Or what if I just changed replInfo = 0? I just want to disable the publication. Thank you.
CREATE TABLE [MSdistributiondbs] (
[name] [sysname] NOT NULL ,
[min_distretention] [int] NOT NULL ,
[max_distretention] [int] NOT NULL ,
[history_retention] [int] NOT NULL
) ON [PRIMARY]
GO
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> CREATE TABLE [MSdistributiondbs] (
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
|||I stopped the Log Reader agent and tried to drop the publication again, and it worked. Thank you so much.
-- Hilary Cotter wrote: --
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
ost on a similar problem that says to run the following code (below). What does this code do? I was wondering if it would help my problem. Or what if I just changed replInfo = 0? I just want to disable the publication. Thank you.
CREATE TABLE [MSdistributiondbs] (
[name] [sysname] NOT NULL ,
[min_distretention] [int] NOT NULL ,
[max_distretention] [int] NOT NULL ,
[history_retention] [int] NOT NULL
) ON [PRIMARY]
GO
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> CREATE TABLE [MSdistributiondbs] (
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
|||I stopped the Log Reader agent and tried to drop the publication again, and it worked. Thank you so much.
-- Hilary Cotter wrote: --
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
can't disable a job in sql2k
Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/defaul...kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/defaul...b;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...[v
bcol=seagreen]
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedul
e)
> that originated from an MSX server.the job was not saved.
> Thanks
>[/vbcol]
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/defaul...kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/defaul...b;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...[v
bcol=seagreen]
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedul
e)
> that originated from an MSX server.the job was not saved.
> Thanks
>[/vbcol]
can't disable a job in sql2k
Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
Thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>
|||Thats an easy one:
http://support.microsoft.com/default...b;en-us;281642
HTH, jens Suessmeyer.
|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default...;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>
|||In addition to the other posts:
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
Thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>
|||Thats an easy one:
http://support.microsoft.com/default...b;en-us;281642
HTH, jens Suessmeyer.
|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default...;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>
|||In addition to the other posts:
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>
can't disable a job in sql2k
Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I have a job in sql2k box. After the box network name changed. I can't do
>> any modification to that job anymore.
>> It says, error 14274 can't update, add or delete a job(or steps or
>> schedule) that originated from an MSX server.the job was not saved.
>> Thanks
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I have a job in sql2k box. After the box network name changed. I can't do
>> any modification to that job anymore.
>> It says, error 14274 can't update, add or delete a job(or steps or
>> schedule) that originated from an MSX server.the job was not saved.
>> Thanks
>|||In addition to the other posts:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>
Subscribe to:
Posts (Atom)