 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Replication / July 2006Following error seen in Distribution agent history
Transaction replication with read only subscriber. Publisher - SQL server 2000 Subscriber - SQL server 2000 entrp Following err noticed in Distribution agent history The process could not execute '{call sp_MSget_subscription_guid(4)}' on 'xxxx'. xxxx - netbios name of publisher What this error means? How to debug this issue? everything workng fine except for above problem? thanks in advance Please can you give some more info - is the error reproducible on restart of the distribution agent? Do you have the latest service pack (sp4) on all publisher and distributor? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com Infact I have noticed distribution agent hung up bcoz of this error.Publisher & distributor in one server & has sp4. Can you let me know why this error comes up ? & how to resolve ? > Please can you give some more info - is the error reproducible on restart of > the distribution agent? > Do you have the latest service pack (sp4) on all publisher and distributor? > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com yes the eror is reprod on restart of distrib agent. Pull sub configured on subscriber.Distribution db on Publisher but distrib agent configured to run at subscriber. both server have sp4. > Infact I have noticed distribution agent hung up bcoz of this error.Publisher > & distributor in one server & has sp4. [quoted text clipped - 5 lines] > > Cheers, > > Paul Ibison SQL Server MVP, www.replicationanswers.com Deni - did this used to work beforehand, or is it an initialization error? I'm wondering if the issue is a permissions one. Just for the moment, can you set the domain user that the pull agent runs as (sql server agent on subscriber) to be the same as that used on the publisher and this'll tell us for sure if it is permissions-related. BTW I'm assuming that the sql server agent on the publisher runs under a domain user that is a sysadmin on the publisher. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com Paul : it used to work before. both servers are in one nt domain & connect over wan link. there is no permision chnages.also confirmng that the sql & sqlagent services on both servers running under a common domain user & this domain user is sysadmin on both servers. can u let me know more what the issue could be ? > Deni - did this used to work beforehand, or is it an initialization error? > I'm wondering if the issue is a permissions one. Just for the moment, can [quoted text clipped - 5 lines] > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com OK - pretty obscure this. Anyway, please try running this script and let's see if this sheds any light on it: use distribution go exec sp_helptext 'sp_MSget_subscription_guid' go select a1.subscription_guid from MSdistribution_agents a1 where -- for non anonymous agents ((a1.virtual_agent_id is null and a1.id = 4) or ( -- for anonymous agents a1.id = (select virtual_agent_id from MSdistribution_agents a2 where a2.id = 4)) -- virtual account ) Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com Paul : outpt of exec sp_helptext 'sp_MSget_subscription_guid' is select a1.subscription_guid from MSdistribution_agents a1 where -- for non anonymous agents ((a1.virtual_agent_id is null and a1.id = @agent_id) or ( -- for anonymous agents a1.id = (select virtual_agent_id from MSdistribution_agents a2 where a2.id = @agent_id)) -- virtual account ) > OK - pretty obscure this. Anyway, please try running this script and let's > see if this sheds any light on it: [quoted text clipped - 17 lines] > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com And what about the second bit in the previous post - effectively running sp_MSget_subscription_guid(4) in the distribution database directly. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com For below query : select a1.subscription_guid > from MSdistribution_agents a1 > where [quoted text clipped - 4 lines] > a2.id = 4)) -- virtual account > ) the output is : 0xC5C2C994FACA734F89E61996A1A6FB93 Paul : kindli give some insight about what this issue is. > And what about the second bit in the previous post - effectively running > sp_MSget_subscription_guid(4) in the distribution database directly. > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com Deni, to be honest I'm almost out of ideas. To summarise, the synchronization is using an account in the sysadmin group so permissions can't be an issue. Running the procedure locally is fine so the proc exists in a good state. Perhaps something is wrong in the connectivity between the 2 servers? Can you set up successfully any other publications (independant agent) between the 2 servers? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com Paul : Thnks for support im confused.How to debug the issue ? has someone else seem this problem before ? May be Hillary has some solution. > Deni, > to be honest I'm almost out of ideas. To summarise, the synchronization is [quoted text clipped - 5 lines] > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com How about the last part of my posting? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com Ok i will try that out & get back. Can you let me know when and what pupose is sp_MSget_subscription_guid used for ? > How about the last part of my posting? > Cheers, > Paul Ibison SQL Server MVP, www.replicationanswers.com Deni, I'm surmising here, but I think it returns a GUID which relates MSsubscriptions to MSreplication_subscriptions records. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.