Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Thanks for the quick answer - I think you are right, it is simply a coincidence / timing issue. I simply disabled the "multiprotocol" network library for now which should fix it otherwise I'll try the article you included. Thanks. One other thing - how fast should I expect CVSNT to execute commands on my client machine (XP Pro) when talking to our server using sspi over our LAN? I'm using the Tortoise CVS shell and it seems to take several seconds for each command to execute - is that normal? Are other protocols (like pserver) faster? -- Allan Williams "Tony Hoyle" <tmh at nodomain.org> wrote in message news:c37vt3$5nl$1 at paris.nodomain.org... > Al Williams wrote: > > > I installed CVSNT v2.0.34 (standard install) onto a fully patched NT4 > > SP6a server running MS SQLServer 7.0. CVSNT works fine, but now I get > > the following event 17052 crash in SQL's ssmsrp70.dll (ListenOn RPC Net > > library v7.00.961) on every reboot: > > I run sqlserver with cvsnt all the time (need it for my paid work...) so there's > no reason why it wouldn't work. > > cvsnt doesn't go anywhere near the RPC libraries. All it does is install a standard > service and open a TCP/IP port... there's nothing to go wrong really. > > > Turning off the CVS services didn't help and as I indicated the only > > thing I installed was CVSNT when this problem started to show up. If > > anyone has any other ideas post back. > > > If the cvs services are disabled there's zero impact on the system, so it sounds like it's just > a coincidence. > > Try http://support.microsoft.com/default.aspx?scid=kb;en-us;160871 > > From the KB it sounds like a timing problem... if RPC hasn't started before SQLServer then > SQLServer barfs. It's possible that the startup time is slightly longer with the extra service > and it's triggered the problem. > > Tony