RE: Security Patch Woes

From: Rich Cowley (rcowley@irsc.com)
Date: 05/21/02 

From:     Rich Cowley <rcowley@irsc.com>
Date: Tue, 21 May 2002 09:27:11 -0700

No, I don't believe this was a case of a "file in use" on the EXE; all
SQL services were stopped at the time, and I was able to copy the new
version into the Binn directory with no problems. (Found no
"sqlservr.1", either...)

The exact message? "The procedure entry point
FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsScheduler@@W4UmsSchedulerA
lgorithms @@K@Z could not be located in the dynamic link library
UMS.DLL." For the record, UMS.DLL is dated 8/6/2000 2:51PM, and reads
v2000.80.194.0.

One of the servers experiencing this problem held only a default
instance of SQL Server; the other held two named instances (one I
invented, and one loaded by the DotNet SDK). Is the DotNet SDK instance
(or any named instances, for that matter) a factor in this problem?

Thanks for your help!

Rich Cowley
rcowley@irsc.com

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!