Hi, I have confired some transactional replication with puss subscrition
between servers running sql server 2000 sp3. The replication works fine,
but yesterday after the publication/distribution was restared the log
reader agent of each publication reports this error:
The process could not execute 'sp_msadd_repl_commands27hp'
on publishername
Do somebody know how could I resolve the problem.
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Please try increasing theLogReader's QueryTimeout parameter.
Also it might be interesting to check the view msdistribution_status to see
how many commands are in the pipeline.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Friday, March 30, 2012
Problems with transactional replication without making a snapshot
I try to configure replication between 2 SQL Server 2000 servers with another
SQL Server 2000 machine configured as the distributor. (All with SP3)
I initialize the replication with 'subscribers already has the data schema
en the data'
and I use pull subscription.
When I have finished the replication setup the next error occurred on the
Distribution agent:
Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__0169315C'. Cannot
insert duplicate key in object '#00750D23'.
I've disabled the whole replication and reboot the servers but the error
still appears.
What could be the reason of the problem I’ve defined?
have a look at this kb article:
http://support.microsoft.com/default...b;en-us;813494
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Marijn" <Marijn@.discussions.microsoft.com> wrote in message
news:AE46BE44-3E53-4CD2-ADF4-9D01EE86BDF3@.microsoft.com...
>I try to configure replication between 2 SQL Server 2000 servers with
>another
> SQL Server 2000 machine configured as the distributor. (All with SP3)
> I initialize the replication with 'subscribers already has the data schema
> en the data'
> and I use pull subscription.
> When I have finished the replication setup the next error occurred on the
> Distribution agent:
> Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__0169315C'.
> Cannot
> insert duplicate key in object '#00750D23'.
> I've disabled the whole replication and reboot the servers but the error
> still appears.
> What could be the reason of the problem I've defined?
>
>
SQL Server 2000 machine configured as the distributor. (All with SP3)
I initialize the replication with 'subscribers already has the data schema
en the data'
and I use pull subscription.
When I have finished the replication setup the next error occurred on the
Distribution agent:
Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__0169315C'. Cannot
insert duplicate key in object '#00750D23'.
I've disabled the whole replication and reboot the servers but the error
still appears.
What could be the reason of the problem I’ve defined?
have a look at this kb article:
http://support.microsoft.com/default...b;en-us;813494
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Marijn" <Marijn@.discussions.microsoft.com> wrote in message
news:AE46BE44-3E53-4CD2-ADF4-9D01EE86BDF3@.microsoft.com...
>I try to configure replication between 2 SQL Server 2000 servers with
>another
> SQL Server 2000 machine configured as the distributor. (All with SP3)
> I initialize the replication with 'subscribers already has the data schema
> en the data'
> and I use pull subscription.
> When I have finished the replication setup the next error occurred on the
> Distribution agent:
> Violation of PRIMARY KEY constraint 'PK__@.snapshot_seqnos__0169315C'.
> Cannot
> insert duplicate key in object '#00750D23'.
> I've disabled the whole replication and reboot the servers but the error
> still appears.
> What could be the reason of the problem I've defined?
>
>
Problems with transactional replication
I got transactional replication between two servers , two identical database
(one publusher and one subscriber, distributor is on publisher server),
everything works clear however a few days ago i got on
Replication Monitor --> Publishers --> MyServerName failed icon snapshot
agent, now on path above i have two publication one that i buil transactional
with 3 agents, and one snapshot i don't know how it created.
Also when i trying to remove it i got the following message description
couldn't retrive information about publication, ... .... ... publication
name not found in the TransPublication collection.
Any ideas ? TNX
Message posted via http://www.droptable.com
You have inconsistent meta data in your distribution database. The best way
to fix this is unfortunately to start carefully editing the metadata tables.
Sometimes it is better to live with these phantom messages.
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
"akej via droptable.com" <forum@.droptable.com> wrote in message
news:507682708C7A4@.droptable.com...
> I got transactional replication between two servers , two identical
database
> (one publusher and one subscriber, distributor is on publisher server),
> everything works clear however a few days ago i got on
> Replication Monitor --> Publishers --> MyServerName failed icon
snapshot
> agent, now on path above i have two publication one that i buil
transactional
> with 3 agents, and one snapshot i don't know how it created.
> Also when i trying to remove it i got the following message description
> couldn't retrive information about publication, ... .... ... publication
> name not found in the TransPublication collection.
>
> Any ideas ? TNX
> --
> Message posted via http://www.droptable.com
|||>carefully editing the metadata tables
I don't really understande what does it mean, can u explain me plz?
Message posted via http://www.droptable.com
|||somebody can help me with problem that i experiance
Message posted via http://www.droptable.com
(one publusher and one subscriber, distributor is on publisher server),
everything works clear however a few days ago i got on
Replication Monitor --> Publishers --> MyServerName failed icon snapshot
agent, now on path above i have two publication one that i buil transactional
with 3 agents, and one snapshot i don't know how it created.
Also when i trying to remove it i got the following message description
couldn't retrive information about publication, ... .... ... publication
name not found in the TransPublication collection.
Any ideas ? TNX
Message posted via http://www.droptable.com
You have inconsistent meta data in your distribution database. The best way
to fix this is unfortunately to start carefully editing the metadata tables.
Sometimes it is better to live with these phantom messages.
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
"akej via droptable.com" <forum@.droptable.com> wrote in message
news:507682708C7A4@.droptable.com...
> I got transactional replication between two servers , two identical
database
> (one publusher and one subscriber, distributor is on publisher server),
> everything works clear however a few days ago i got on
> Replication Monitor --> Publishers --> MyServerName failed icon
snapshot
> agent, now on path above i have two publication one that i buil
transactional
> with 3 agents, and one snapshot i don't know how it created.
> Also when i trying to remove it i got the following message description
> couldn't retrive information about publication, ... .... ... publication
> name not found in the TransPublication collection.
>
> Any ideas ? TNX
> --
> Message posted via http://www.droptable.com
|||>carefully editing the metadata tables
I don't really understande what does it mean, can u explain me plz?
Message posted via http://www.droptable.com
|||somebody can help me with problem that i experiance
Message posted via http://www.droptable.com
Wednesday, March 28, 2012
Problems with sql server 2005 linked servers
I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
I have set up several linked servers to our AS400 and they work
correctly as long as I am connected to the database as "sa" via Sql
Server security.
For example I can run queries against the AS400 tables with no problem.
If I connect to the database using Windows Authentication and try to
run the exact same query I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "HiTOLEDB400"
for linked server "AS400".
My Windows login is setup the same as the "sa" login as far as I can
tell.What is the configuration for the security mappings on the
linked server?
-Sue
On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>I have set up several linked servers to our AS400 and they work
>correctly as long as I am connected to the database as "sa" via Sql
>Server security.
>For example I can run queries against the AS400 tables with no problem.
>If I connect to the database using Windows Authentication and try to
>run the exact same query I get the following error:
>Msg 7399, Level 16, State 1, Line 1
>The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>error. Access denied.
>Msg 7350, Level 16, State 2, Line 1
>Cannot get the column information from OLE DB provider "HiTOLEDB400"
>for linked server "AS400".
>
>My Windows login is setup the same as the "sa" login as far as I can
>tell.|||The linked server is set to use an as400 userid/password for every
connection.
Sue Hoegemeier wrote:[vbcol=seagreen]
> What is the configuration for the security mappings on the
> linked server?
> -Sue
> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
> wrote:
>|||Okay...the first thing you'd want to try is to make sure you
have Allow In Process option enabled for the provider.
That may not do it though. The other thing to try after that
would be to enable delegation for the Windows domain
account.
-Sue
On 14 Sep 2006 12:42:22 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
[vbcol=seagreen]
>The linked server is set to use an as400 userid/password for every
>connection.
>Sue Hoegemeier wrote:
I have set up several linked servers to our AS400 and they work
correctly as long as I am connected to the database as "sa" via Sql
Server security.
For example I can run queries against the AS400 tables with no problem.
If I connect to the database using Windows Authentication and try to
run the exact same query I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "HiTOLEDB400"
for linked server "AS400".
My Windows login is setup the same as the "sa" login as far as I can
tell.What is the configuration for the security mappings on the
linked server?
-Sue
On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>I have set up several linked servers to our AS400 and they work
>correctly as long as I am connected to the database as "sa" via Sql
>Server security.
>For example I can run queries against the AS400 tables with no problem.
>If I connect to the database using Windows Authentication and try to
>run the exact same query I get the following error:
>Msg 7399, Level 16, State 1, Line 1
>The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>error. Access denied.
>Msg 7350, Level 16, State 2, Line 1
>Cannot get the column information from OLE DB provider "HiTOLEDB400"
>for linked server "AS400".
>
>My Windows login is setup the same as the "sa" login as far as I can
>tell.|||The linked server is set to use an as400 userid/password for every
connection.
Sue Hoegemeier wrote:[vbcol=seagreen]
> What is the configuration for the security mappings on the
> linked server?
> -Sue
> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
> wrote:
>|||Okay...the first thing you'd want to try is to make sure you
have Allow In Process option enabled for the provider.
That may not do it though. The other thing to try after that
would be to enable delegation for the Windows domain
account.
-Sue
On 14 Sep 2006 12:42:22 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
[vbcol=seagreen]
>The linked server is set to use an as400 userid/password for every
>connection.
>Sue Hoegemeier wrote:
Problems with sql server 2005 linked servers
I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
I have set up several linked servers to our AS400 and they work
correctly as long as I am connected to the database as "sa" via Sql
Server security.
For example I can run queries against the AS400 tables with no problem.
If I connect to the database using Windows Authentication and try to
run the exact same query I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "HiTOLEDB400"
for linked server "AS400".
My Windows login is setup the same as the "sa" login as far as I can
tell.What is the configuration for the security mappings on the
linked server?
-Sue
On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>I have set up several linked servers to our AS400 and they work
>correctly as long as I am connected to the database as "sa" via Sql
>Server security.
>For example I can run queries against the AS400 tables with no problem.
>If I connect to the database using Windows Authentication and try to
>run the exact same query I get the following error:
>Msg 7399, Level 16, State 1, Line 1
>The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>error. Access denied.
>Msg 7350, Level 16, State 2, Line 1
>Cannot get the column information from OLE DB provider "HiTOLEDB400"
>for linked server "AS400".
>
>My Windows login is setup the same as the "sa" login as far as I can
>tell.|||The linked server is set to use an as400 userid/password for every
connection.
Sue Hoegemeier wrote:
> What is the configuration for the security mappings on the
> linked server?
> -Sue
> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
> wrote:
> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
> >I have set up several linked servers to our AS400 and they work
> >correctly as long as I am connected to the database as "sa" via Sql
> >Server security.
> >For example I can run queries against the AS400 tables with no problem.
> >If I connect to the database using Windows Authentication and try to
> >run the exact same query I get the following error:
> >
> >Msg 7399, Level 16, State 1, Line 1
> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
> >error. Access denied.
> >Msg 7350, Level 16, State 2, Line 1
> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
> >for linked server "AS400".
> >
> >
> >My Windows login is setup the same as the "sa" login as far as I can
> >tell.|||Okay...the first thing you'd want to try is to make sure you
have Allow In Process option enabled for the provider.
That may not do it though. The other thing to try after that
would be to enable delegation for the Windows domain
account.
-Sue
On 14 Sep 2006 12:42:22 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>The linked server is set to use an as400 userid/password for every
>connection.
>Sue Hoegemeier wrote:
>> What is the configuration for the security mappings on the
>> linked server?
>> -Sue
>> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
>> wrote:
>> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>> >I have set up several linked servers to our AS400 and they work
>> >correctly as long as I am connected to the database as "sa" via Sql
>> >Server security.
>> >For example I can run queries against the AS400 tables with no problem.
>> >If I connect to the database using Windows Authentication and try to
>> >run the exact same query I get the following error:
>> >
>> >Msg 7399, Level 16, State 1, Line 1
>> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>> >error. Access denied.
>> >Msg 7350, Level 16, State 2, Line 1
>> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
>> >for linked server "AS400".
>> >
>> >
>> >My Windows login is setup the same as the "sa" login as far as I can
>> >tell.
I have set up several linked servers to our AS400 and they work
correctly as long as I am connected to the database as "sa" via Sql
Server security.
For example I can run queries against the AS400 tables with no problem.
If I connect to the database using Windows Authentication and try to
run the exact same query I get the following error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
error. Access denied.
Msg 7350, Level 16, State 2, Line 1
Cannot get the column information from OLE DB provider "HiTOLEDB400"
for linked server "AS400".
My Windows login is setup the same as the "sa" login as far as I can
tell.What is the configuration for the security mappings on the
linked server?
-Sue
On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>I have set up several linked servers to our AS400 and they work
>correctly as long as I am connected to the database as "sa" via Sql
>Server security.
>For example I can run queries against the AS400 tables with no problem.
>If I connect to the database using Windows Authentication and try to
>run the exact same query I get the following error:
>Msg 7399, Level 16, State 1, Line 1
>The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>error. Access denied.
>Msg 7350, Level 16, State 2, Line 1
>Cannot get the column information from OLE DB provider "HiTOLEDB400"
>for linked server "AS400".
>
>My Windows login is setup the same as the "sa" login as far as I can
>tell.|||The linked server is set to use an as400 userid/password for every
connection.
Sue Hoegemeier wrote:
> What is the configuration for the security mappings on the
> linked server?
> -Sue
> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
> wrote:
> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
> >I have set up several linked servers to our AS400 and they work
> >correctly as long as I am connected to the database as "sa" via Sql
> >Server security.
> >For example I can run queries against the AS400 tables with no problem.
> >If I connect to the database using Windows Authentication and try to
> >run the exact same query I get the following error:
> >
> >Msg 7399, Level 16, State 1, Line 1
> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
> >error. Access denied.
> >Msg 7350, Level 16, State 2, Line 1
> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
> >for linked server "AS400".
> >
> >
> >My Windows login is setup the same as the "sa" login as far as I can
> >tell.|||Okay...the first thing you'd want to try is to make sure you
have Allow In Process option enabled for the provider.
That may not do it though. The other thing to try after that
would be to enable delegation for the Windows domain
account.
-Sue
On 14 Sep 2006 12:42:22 -0700, "EagleGT" <a016691@.gmail.com>
wrote:
>The linked server is set to use an as400 userid/password for every
>connection.
>Sue Hoegemeier wrote:
>> What is the configuration for the security mappings on the
>> linked server?
>> -Sue
>> On 12 Sep 2006 13:17:32 -0700, "EagleGT" <a016691@.gmail.com>
>> wrote:
>> >I have just installed Sql Server 2005 SP1 on Windows 2003 SP1
>> >I have set up several linked servers to our AS400 and they work
>> >correctly as long as I am connected to the database as "sa" via Sql
>> >Server security.
>> >For example I can run queries against the AS400 tables with no problem.
>> >If I connect to the database using Windows Authentication and try to
>> >run the exact same query I get the following error:
>> >
>> >Msg 7399, Level 16, State 1, Line 1
>> >The OLE DB provider "HiTOLEDB400" for linked server "AS400" reported an
>> >error. Access denied.
>> >Msg 7350, Level 16, State 2, Line 1
>> >Cannot get the column information from OLE DB provider "HiTOLEDB400"
>> >for linked server "AS400".
>> >
>> >
>> >My Windows login is setup the same as the "sa" login as far as I can
>> >tell.
Monday, March 26, 2012
Problems with SP and NULL values.
Hi friends.
I have two servers, one with SQL 7.0 SP4 (Production server) and the
development server with SQL 2000 SP3.
One developer tells me that in the development server the store procedures
he creates permits the NULL output. On the production server, he says that
the SP migrated, does not permit a NULL output.
Is this true? how can i check this?
Thanks all.Output *parameters* may be NULL. *RETURN values* must be a non-NULL integer,
although this is handled as a warning rather than an error in 2000. May have
been different in 7.0, I don't recall. Don't try to return a NULL RETURN
value.
You use SQL2000 as a dev box for a 7.0 production server?! Good luck! ;-)
David Portas
SQL Server MVP
--|||Thanks David, the developer has corrected the scripts and now all is working
fine.
I dont unterstand why the developers have migrated to SQL 2000 without
permission, i am new to the company, so my next task will be migrate the SQl
7.
Thanks again.
I have two servers, one with SQL 7.0 SP4 (Production server) and the
development server with SQL 2000 SP3.
One developer tells me that in the development server the store procedures
he creates permits the NULL output. On the production server, he says that
the SP migrated, does not permit a NULL output.
Is this true? how can i check this?
Thanks all.Output *parameters* may be NULL. *RETURN values* must be a non-NULL integer,
although this is handled as a warning rather than an error in 2000. May have
been different in 7.0, I don't recall. Don't try to return a NULL RETURN
value.
You use SQL2000 as a dev box for a 7.0 production server?! Good luck! ;-)
David Portas
SQL Server MVP
--|||Thanks David, the developer has corrected the scripts and now all is working
fine.
I dont unterstand why the developers have migrated to SQL 2000 without
permission, i am new to the company, so my next task will be migrate the SQl
7.
Thanks again.
Problems with services not starting
We have a number of 6.5 servers on Windows NT and recently the AT jobs used
to start the services simply fail to run; they simply don't kick-in.
It is as if the internal Windows scheduler isn't running and as such the job
s don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) s
ervice not being started which would mean that any tasks / jobs not being ru
n.
There is nothing in the Event logs or anywhere else.
something that I don't believe is a coincidence: we are currently in the pro
cess of a domain migration to Windows 2000 and we are in a situation where s
ome of our 6.5 servers have not been migrated to the new domain and are on t
he old Windows NT domain. T
wo 6.5 server that have been migrated to the new Windows 2000 domain do not
exhibit these problems.
Any ideas as to were I could look for this would be greatly appreciated.
Peter ApostolakopoulosPeter,
I thing you have better chance to get good suggestion in a NT/Windows forum
for this. It is probably something
with the scheduler service, possibly related to the service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to sta
rt the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don'
t run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which wo
uld mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process o
f a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have no
t been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated
to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos|||Good idea Tibor.
Thanks,
Peter Apostolakopoulos
to start the services simply fail to run; they simply don't kick-in.
It is as if the internal Windows scheduler isn't running and as such the job
s don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) s
ervice not being started which would mean that any tasks / jobs not being ru
n.
There is nothing in the Event logs or anywhere else.
something that I don't believe is a coincidence: we are currently in the pro
cess of a domain migration to Windows 2000 and we are in a situation where s
ome of our 6.5 servers have not been migrated to the new domain and are on t
he old Windows NT domain. T
wo 6.5 server that have been migrated to the new Windows 2000 domain do not
exhibit these problems.
Any ideas as to were I could look for this would be greatly appreciated.
Peter ApostolakopoulosPeter,
I thing you have better chance to get good suggestion in a NT/Windows forum
for this. It is probably something
with the scheduler service, possibly related to the service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to sta
rt the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don'
t run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which wo
uld mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process o
f a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have no
t been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated
to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos|||Good idea Tibor.
Thanks,
Peter Apostolakopoulos
Problems with services not starting
We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply fail to run; they simply don't kick-in
It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not being run
There is nothing in the Event logs or anywhere else
something that I don't believe is a coincidence: we are currently in the process of a domain migration to Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do not exhibit these problems
Any ideas as to were I could look for this would be greatly appreciated
Peter ApostolakopoulosPeter,
I thing you have better chance to get good suggestion in a NT/Windows forum for this. It is probably something
with the scheduler service, possibly related to the service account.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process of a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos|||Good idea Tibor
Thanks
Peter Apostolakopoulos
It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not being run
There is nothing in the Event logs or anywhere else
something that I don't believe is a coincidence: we are currently in the process of a domain migration to Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do not exhibit these problems
Any ideas as to were I could look for this would be greatly appreciated
Peter ApostolakopoulosPeter,
I thing you have better chance to get good suggestion in a NT/Windows forum for this. It is probably something
with the scheduler service, possibly related to the service account.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process of a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos|||Good idea Tibor
Thanks
Peter Apostolakopoulos
Problems with services not starting
We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply fail to run; they simply don't kick-in.
It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not being run.
There is nothing in the Event logs or anywhere else.
something that I don't believe is a coincidence: we are currently in the process of a domain migration to Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain and are on the old Windows NT domain. T
wo 6.5 server that have been migrated to the new Windows 2000 domain do not exhibit these problems.
Any ideas as to were I could look for this would be greatly appreciated.
Peter Apostolakopoulos
Peter,
I thing you have better chance to get good suggestion in a NT/Windows forum for this. It is probably something
with the scheduler service, possibly related to the service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process of a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos
|||Good idea Tibor.
Thanks,
Peter Apostolakopoulos
sql
It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not being run.
There is nothing in the Event logs or anywhere else.
something that I don't believe is a coincidence: we are currently in the process of a domain migration to Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain and are on the old Windows NT domain. T
wo 6.5 server that have been migrated to the new Windows 2000 domain do not exhibit these problems.
Any ideas as to were I could look for this would be greatly appreciated.
Peter Apostolakopoulos
Peter,
I thing you have better chance to get good suggestion in a NT/Windows forum for this. It is probably something
with the scheduler service, possibly related to the service account.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Peter Apostolakopoulos" <apostolp@.britannic.co.uk> wrote in message
news:6C55044B-35C1-40A5-86C1-B11698950444@.microsoft.com...
> We have a number of 6.5 servers on Windows NT and recently the AT jobs used to start the services simply
fail to run; they simply don't kick-in.
> It is as if the internal Windows scheduler isn't running and as such the jobs don't run. It would be similar
to the SQLExecutive (or SQLServer Agent ) service not being started which would mean that any tasks / jobs not
being run.
> There is nothing in the Event logs or anywhere else.
> something that I don't believe is a coincidence: we are currently in the process of a domain migration to
Windows 2000 and we are in a situation where some of our 6.5 servers have not been migrated to the new domain
and are on the old Windows NT domain. Two 6.5 server that have been migrated to the new Windows 2000 domain do
not exhibit these problems.
> Any ideas as to were I could look for this would be greatly appreciated.
> Peter Apostolakopoulos
|||Good idea Tibor.
Thanks,
Peter Apostolakopoulos
sql
Wednesday, March 21, 2012
Problems with OraOLEDB.Oracle
Good day everyone....
I have installed the OraOLEDB.Oracle Provider on 3 different servers, and have made a link server on all three.
On two of the machines, I am successful in retrieving data from the Oracle database. But, on the third machine, I receive this error:
Server: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "employee_prod" reported an error. The provider did not give any information about the error.
Server: Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod".
On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it.
I have also uninstalled/installed serveral times.
All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition.
Does anyone have any suggestions?
Found the solution.... "Allow inprocess" has to be checked in the provider options.|||hi can you please send me the steps on how to stepup a connection to Oracle Database throught SQL Database.
I have created a linked server, but i keep getting an error message
OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN" returned message "ORA-12154: TNS:could not resolve the connect identifier specified".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN".
My tns string is Prooracle and the database is oracle and the Schema is HR
appreciate your help
|||I had the same symtoms and did the re install etc. The item was checked and I unchecked it and it now works. Something to do with triggering a change in settings ?
|||It works, thanks. by unchecking the "Allow inprocess" option.|||I spent some time to find the option. From SQL Server Management Studio-->Server Objects-->Linked Servers-->Providers-->MSDAORA, right click select properties.Problems with OraOLEDB.Oracle
Good day everyone....
I have installed the OraOLEDB.Oracle Provider on 3 different servers, and have made a link server on all three.
On two of the machines, I am successful in retrieving data from the Oracle database. But, on the third machine, I receive this error:
Server: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "employee_prod" reported an error. The provider did not give any information about the error.
Server: Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod".
On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it.
I have also uninstalled/installed serveral times.
All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition.
Does anyone have any suggestions?
Found the solution.... "Allow inprocess" has to be checked in the provider options.|||hi can you please send me the steps on how to stepup a connection to Oracle Database throught SQL Database.
I have created a linked server, but i keep getting an error message
OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN" returned message "ORA-12154: TNS:could not resolve the connect identifier specified".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN".
My tns string is Prooracle and the database is oracle and the Schema is HR
appreciate your help
|||I had the same symtoms and did the re install etc. The item was checked and I unchecked it and it now works. Something to do with triggering a change in settings ?
|||It works, thanks. by unchecking the "Allow inprocess" option.|||I spent some time to find the option. From SQL Server Management Studio-->Server Objects-->Linked Servers-->Providers-->MSDAORA, right click select properties.Problems with OraOLEDB.Oracle
Good day everyone....
I have installed the OraOLEDB.Oracle Provider on 3 different servers, and have made a link server on all three.
On two of the machines, I am successful in retrieving data from the Oracle database. But, on the third machine, I receive this error:
Server: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "employee_prod" reported an error. The provider did not give any information about the error.
Server: Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod".
On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it.
I have also uninstalled/installed serveral times.
All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition.
Does anyone have any suggestions?
Found the solution.... "Allow inprocess" has to be checked in the provider options.|||hi can you please send me the steps on how to stepup a connection to Oracle Database throught SQL Database.
I have created a linked server, but i keep getting an error message
OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN" returned message "ORA-12154: TNS:could not resolve the connect identifier specified".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN".
My tns string is Prooracle and the database is oracle and the Schema is HR
appreciate your help
|||I had the same symtoms and did the re install etc. The item was checked and I unchecked it and it now works. Something to do with triggering a change in settings ?
|||It works, thanks. by unchecking the "Allow inprocess" option.|||I spent some time to find the option. From SQL Server Management Studio-->Server Objects-->Linked Servers-->Providers-->MSDAORA, right click select properties.Problems with OraOLEDB.Oracle
Good day everyone....
I have installed the OraOLEDB.Oracle Provider on 3 different servers, and have made a link server on all three.
On two of the machines, I am successful in retrieving data from the Oracle database. But, on the third machine, I receive this error:
Server: Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "OraOLEDB.Oracle" for linked server "employee_prod" reported an error. The provider did not give any information about the error.
Server: Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "tims2_prod".
On the machine which is generating the error, I can use SQL*Plus to connect to the remote database. I can also connect to the database using the "ODBC Data Source Administrator" when I create a system DSN. It would appear that the driver is installed and working correctly, but SQL Server can not access it.
I have also uninstalled/installed serveral times.
All of our servers are running W2003 Standard X64 with SQL Server 2005 Standard 64-bit Edition.
Does anyone have any suggestions?
Found the solution.... "Allow inprocess" has to be checked in the provider options.|||hi can you please send me the steps on how to stepup a connection to Oracle Database throught SQL Database.
I have created a linked server, but i keep getting an error message
OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN" returned message "ORA-12154: TNS:could not resolve the connect identifier specified".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "DBCONN".
My tns string is Prooracle and the database is oracle and the Schema is HR
appreciate your help
|||I had the same symtoms and did the re install etc. The item was checked and I unchecked it and it now works. Something to do with triggering a change in settings ?
|||It works, thanks. by unchecking the "Allow inprocess" option.|||I spent some time to find the option. From SQL Server Management Studio-->Server Objects-->Linked Servers-->Providers-->MSDAORA, right click select properties.sqlTuesday, March 20, 2012
problems with MSX account
Hello i tried to configure my servers to multi-server admon, but when i'm
defining the MSX account
appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
the account is member of sysadmin role in server and the sql server agent is
asociated with the account
thank
FabricioThis means that you have not configured an account on the MSX server
correctly. EM tries to validate it by logging in. Please check the SP3
readme for creating such an account. Make sure the account is member of
TargetServersRole (msdb).
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Fabricio E. Gil" <fgil@.calpia.com.sv> wrote in message
news:OWVl91DiDHA.2460@.TK2MSFTNGP09.phx.gbl...
> Hello i tried to configure my servers to multi-server admon, but when i'm
> defining the MSX account
> appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
> ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
> the account is member of sysadmin role in server and the sql server agent
is
> asociated with the account
> thank
> Fabricio
>|||Thank u! it works
"Michiel Wories [MS]" <mwories@.online.microsoft.com> wrote in message
news:3f7b14ea$1@.news.microsoft.com...
> This means that you have not configured an account on the MSX server
> correctly. EM tries to validate it by logging in. Please check the SP3
> readme for creating such an account. Make sure the account is member of
> TargetServersRole (msdb).
> --
> Michiel Wories, SQL Server PM
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --
> "Fabricio E. Gil" <fgil@.calpia.com.sv> wrote in message
> news:OWVl91DiDHA.2460@.TK2MSFTNGP09.phx.gbl...
> > Hello i tried to configure my servers to multi-server admon, but when
i'm
> > defining the MSX account
> > appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
> > ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
> >
> > the account is member of sysadmin role in server and the sql server
agent
> is
> > asociated with the account
> >
> > thank
> >
> > Fabricio
> >
> >
>
defining the MSX account
appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
the account is member of sysadmin role in server and the sql server agent is
asociated with the account
thank
FabricioThis means that you have not configured an account on the MSX server
correctly. EM tries to validate it by logging in. Please check the SP3
readme for creating such an account. Make sure the account is member of
TargetServersRole (msdb).
--
Michiel Wories, SQL Server PM
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Fabricio E. Gil" <fgil@.calpia.com.sv> wrote in message
news:OWVl91DiDHA.2460@.TK2MSFTNGP09.phx.gbl...
> Hello i tried to configure my servers to multi-server admon, but when i'm
> defining the MSX account
> appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
> ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
> the account is member of sysadmin role in server and the sql server agent
is
> asociated with the account
> thank
> Fabricio
>|||Thank u! it works
"Michiel Wories [MS]" <mwories@.online.microsoft.com> wrote in message
news:3f7b14ea$1@.news.microsoft.com...
> This means that you have not configured an account on the MSX server
> correctly. EM tries to validate it by logging in. Please check the SP3
> readme for creating such an account. Make sure the account is member of
> TargetServersRole (msdb).
> --
> Michiel Wories, SQL Server PM
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --
> "Fabricio E. Gil" <fgil@.calpia.com.sv> wrote in message
> news:OWVl91DiDHA.2460@.TK2MSFTNGP09.phx.gbl...
> > Hello i tried to configure my servers to multi-server admon, but when
i'm
> > defining the MSX account
> > appear the next message THE ACCOUNT "DOMAIN\account" IS NOT A VALID MSX
> > ACCOUNT, CONTACT THE MSX ADMINISTRATOR TO GET MSX ACCOUNT INFORMATION.
> >
> > the account is member of sysadmin role in server and the sql server
agent
> is
> > asociated with the account
> >
> > thank
> >
> > Fabricio
> >
> >
>
problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',
@.LockMode = 'Exclusive',
@.LockOwner = 'Session',
@.LockTimeout = 0,
@.DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
anyone?|||Looks to me like the upgrade did not happen correctly on the subscriber machine.
Can you check the upgrade log for any failures?
Also would dropping the subscriber db and recreating the subscription help?
If you create a new database and subscriber, do you still see the same error?
|||Thanks for the reply
however the error with the database role occured at the publisher/distributor and not the subscriber
have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors
also, both instances did not report any errors during upgrade
any other ideas why this might happen?
thanks
|||We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.
Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.
Any ideas would be gratefully received.
|||Sorry. The publisher is version 9..3054.|||Im having this problem as well, anybody mange to solve it?problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',
@.LockMode = 'Exclusive',
@.LockOwner = 'Session',
@.LockTimeout = 0,
@.DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
anyone?|||Looks to me like the upgrade did not happen correctly on the subscriber machine.
Can you check the upgrade log for any failures?
Also would dropping the subscriber db and recreating the subscription help?
If you create a new database and subscriber, do you still see the same error?
|||Thanks for the reply
however the error with the database role occured at the publisher/distributor and not the subscriber
have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors
also, both instances did not report any errors during upgrade
any other ideas why this might happen?
thanks
|||We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.
Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.
Any ideas would be gratefully received.
|||Sorry. The publisher is version 9..3054.problems with merge rep after upgrading from sql server 2000 sp3a to sql server 2005 build 2153
Hi,
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403)
Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207)
Get help: http://help/207
2)
Command attempted:
{call sp_MSensure_single_instance (N'Merge Agent Name', 4)}
Error messages:
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368)
Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036)
Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @.retcode = -1 and thus cannot obtain exclusive lock on resource
EXEC @.retcode = sys.sp_getapplock @.Resource = 'Merge Agent Name',
@.LockMode = 'Exclusive',
@.LockOwner = 'Session',
@.LockTimeout = 0,
@.DbPrincipal = 'MSmerge_PAL_role'
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
can anyone help?
Thanks
anyone?|||Looks to me like the upgrade did not happen correctly on the subscriber machine.
Can you check the upgrade log for any failures?
Also would dropping the subscriber db and recreating the subscription help?
If you create a new database and subscriber, do you still see the same error?
|||Thanks for the reply
however the error with the database role occured at the publisher/distributor and not the subscriber
have went back to check the installation logs for both the publisher/distributor and the subscriber and didn't find any errors
also, both instances did not report any errors during upgrade
any other ideas why this might happen?
thanks
|||We have the same error under similar circumstances. We upgraded a data from an SQL Server 2000 SP4 machine to a new machine of the same name running SQL Server 2005 (9.0.1399). Prior to the upgrade I dropped all subscriptions for this database from the publisher (SQL Server 2005 9.0.) and then copied the MDF and LDF files to the new server and attached them.
Snapshot and Transactional replication run fine, but Merge replication does not run at all. As per the original messenger I have tried to initialize the subscriptions, delete the subscriptions and re-create them, and nothing is working.
Any ideas would be gratefully received.
|||Sorry. The publisher is version 9..3054.|||Im having this problem as well, anybody mange to solve it?Problems with Linked servers between sql 2000 and sql 2005
Dear all
I have created linked server object between a sql 2000 and sql 2005 database. i have the latest mdacs installed and all the services enabled on both sides.
But when i try and run a sql statement on the sql 2000 side i get this error:
[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.
If i try and run a sql statment on the sql server 2005 side the procedure works.
Has anyone experienced the same problem?Any advice?
Thank you so much for the help.
Dan
What is the SQL Statement that works/doesn't work?
Do any other queries work on the SQL 2000 server when executed from the SQL 2005 server?
|||Also, if you can you post:
1 - Any errors that you see in the error log
2 - The commands that you used to create the linked server
3 - What type of authentication are you using? Integrated auth?
You may also want to take a look at this blog posting: http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx. It's describes the scenario using sql2k5 servers but there is a lot of info that applies to sql2k as well.
Thanks,
Il-Sung.
|||The select statement i used is just a simple one:
Select * from MyLink.MyDatabase.dbo.Table1
This is working now. It had to do with the way sql server 05 was setup.
But i have a different problem.
When i place the select statement in a simple insert trigger that has nothing in except for the select statement the trigger just blocks and does not execute. It stalls to a lock. The trigger is placed on a table at the sql 2000 server.
Any suggestions as to why this might not work?
Sincerely
Dan
|||Hi, Dan
This indicates your insert trigger fails to execute, normally, due to the rwo to be inserted did not pass all constraints check such as primary keys, unique indeex, foregin keys, etc...
Hence, I suggest you take a look at your table schema and double check. If you still face problem, please post your question to SQL Engine forumn where experts can help you very quick.
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1
Good Luck!
Ming.
Problems with Linked servers between sql 2000 and sql 2005
Dear all
I have created linked server object between a sql 2000 and sql 2005 database. i have the latest mdacs installed and all the services enabled on both sides.
But when i try and run a sql statement on the sql 2000 side i get this error:
[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.
If i try and run a sql statment on the sql server 2005 side the procedure works.
Has anyone experienced the same problem?Any advice?
Thank you so much for the help.
Dan
What is the SQL Statement that works/doesn't work?
Do any other queries work on the SQL 2000 server when executed from the SQL 2005 server?
|||Also, if you can you post:
1 - Any errors that you see in the error log
2 - The commands that you used to create the linked server
3 - What type of authentication are you using? Integrated auth?
You may also want to take a look at this blog posting: http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx. It's describes the scenario using sql2k5 servers but there is a lot of info that applies to sql2k as well.
Thanks,
Il-Sung.
|||The select statement i used is just a simple one:
Select * from MyLink.MyDatabase.dbo.Table1
This is working now. It had to do with the way sql server 05 was setup.
But i have a different problem.
When i place the select statement in a simple insert trigger that has nothing in except for the select statement the trigger just blocks and does not execute. It stalls to a lock. The trigger is placed on a table at the sql 2000 server.
Any suggestions as to why this might not work?
Sincerely
Dan
|||Hi, Dan
This indicates your insert trigger fails to execute, normally, due to the rwo to be inserted did not pass all constraints check such as primary keys, unique indeex, foregin keys, etc...
Hence, I suggest you take a look at your table schema and double check. If you still face problem, please post your question to SQL Engine forumn where experts can help you very quick.
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1
Good Luck!
Ming.
Problems with Linked servers between sql 2000 and sql 2005
Dear all
I have created linked server object between a sql 2000 and sql 2005 database. i have the latest mdacs installed and all the services enabled on both sides.
But when i try and run a sql statement on the sql 2000 side i get this error:
[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.
If i try and run a sql statment on the sql server 2005 side the procedure works.
Has anyone experienced the same problem?Any advice?
Thank you so much for the help.
Dan
What is the SQL Statement that works/doesn't work?
Do any other queries work on the SQL 2000 server when executed from the SQL 2005 server?
|||Also, if you can you post:
1 - Any errors that you see in the error log
2 - The commands that you used to create the linked server
3 - What type of authentication are you using? Integrated auth?
You may also want to take a look at this blog posting: http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx. It's describes the scenario using sql2k5 servers but there is a lot of info that applies to sql2k as well.
Thanks,
Il-Sung.
|||The select statement i used is just a simple one:
Select * from MyLink.MyDatabase.dbo.Table1
This is working now. It had to do with the way sql server 05 was setup.
But i have a different problem.
When i place the select statement in a simple insert trigger that has nothing in except for the select statement the trigger just blocks and does not execute. It stalls to a lock. The trigger is placed on a table at the sql 2000 server.
Any suggestions as to why this might not work?
Sincerely
Dan
|||Hi, Dan
This indicates your insert trigger fails to execute, normally, due to the rwo to be inserted did not pass all constraints check such as primary keys, unique indeex, foregin keys, etc...
Hence, I suggest you take a look at your table schema and double check. If you still face problem, please post your question to SQL Engine forumn where experts can help you very quick.
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1
Good Luck!
Ming.
Subscribe to:
Posts (Atom)