We currently have a pull transactional subscription running from a remote 'PublicationServer' in another country to our local server.
After restarting our fire wall we get the following error message:
"The process could not execute '{call sp_MSget_subscription_guid(16)}' on 'PublicationServer'."
This message is followed by another error message: "Another distribution agent for the subscription(s) is running.", although nothing was changed to the configuration and no SQL processes were started or restarted.
When we restart the distribution job manually it runs as if nothing happened.
Does anyone know what exactly caused the failure, and how to prevent it ?
PhilipQuit restarting your firewall ?
I really don't have a good answer for this question. Sometimes after an unexpected failure, the simplest answer is just to manually restart what won't start automagically.
-PatP
Friday, March 9, 2012
Replication - sp_MSget_subscription_guid impossible
Labels:
country,
database,
local,
microsoft,
mysql,
oracle,
publicationserver,
pull,
remote,
replication,
running,
server,
sp_msget_subscription_guid,
sql,
subscription,
transactional
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment