Missing system stored procedures

I developed a Pocket PC app that uses merge replication in an isolated
development environment. It worked fine. The I moved to the operational
environment. Synchronization fails with error 2812, "Could not find stored
procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows that
in the development environment, that stored procedure exists, but it does not
exist on the operational SQL Server. (The total sp count on the development
server is 969, on the operational server 930, so other sp's are also
missing). I disabled replication on the operational server and then
reconfigured it, but that didn't help.
The operational SQL Server is SQL Server 2000 Standard Edition running sp3a.
Any ideas why those sp's didn't get created, and how to fix this problem?
There's a message thread out there that suggests that xp_cmdshell is needed
to properly create some replication-related sp's. Is it possible that
xp_cmdshell is missing or disabled? However, when I configure the server for
replication, I don't get any error messages.
You need to reapply the sp. This problem has been observed before.
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
"PGallez" <PGallez@.discussions.microsoft.com> wrote in message
news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> I developed a Pocket PC app that uses merge replication in an isolated
> development environment. It worked fine. The I moved to the operational
> environment. Synchronization fails with error 2812, "Could not find stored
> procedure 'sp_MSgetmakegenerationapplock'". A little investigation shows
that
> in the development environment, that stored procedure exists, but it does
not
> exist on the operational SQL Server. (The total sp count on the
development
> server is 969, on the operational server 930, so other sp's are also
> missing). I disabled replication on the operational server and then
> reconfigured it, but that didn't help.
> The operational SQL Server is SQL Server 2000 Standard Edition running
sp3a.
> Any ideas why those sp's didn't get created, and how to fix this problem?
> There's a message thread out there that suggests that xp_cmdshell is
needed
> to properly create some replication-related sp's. Is it possible that
> xp_cmdshell is missing or disabled? However, when I configure the server
for
> replication, I don't get any error messages.
|||Thanks much, I'll give that a try.
"Hilary Cotter" wrote:

> You need to reapply the sp. This problem has been observed before.
> --
> 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
> "PGallez" <PGallez@.discussions.microsoft.com> wrote in message
> news:8A112E32-D0BB-4FB5-9A51-B62BBAFBAB01@.microsoft.com...
> that
> not
> development
> sp3a.
> needed
> for
>
>