UMS.DLL failure

[Bethany Holliday]

Hi All,

We have SQL Server 2000 (sp3), running on Win2k Server. Yesterday, mid
morning, during normal processing (selecting data .. loading data ..
etc) the sql server service suddenly shut down and would not start
again. We received several messages but the 2 most consistent messages
were that 1) the ums.dll could not be loaded and 2) the services failed
to start in a timely fashion.
IN the event log, the only thing of interest was this:

Application popup: sqlservr.exe - Entry Point Not Found : The procedure
entry point
?FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsSch eduler@@W4UmsScheduler
Algorithms@@@Z could not be located in the dynamic link library UMS.DLL.

I am at a complete loss. I did create a new instance of sql Server and
reattached all of my databases to the new instance - but, of course, now
the question being posed to me is "what happened?" I have no idea and
am wondering if anyone has experienced this before or has any insight
they might be able to share.

Any information would be greatly appreciated! Thanks!
Bethany Holliday
IU, KSOB
Indiana Business Research Center

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

[Simon Hayes]

"Bethany Holliday" <bh******@iupui.edu> wrote in message
news:41**********************@news.newsgroups.ws.. .

Hi All,

We have SQL Server 2000 (sp3), running on Win2k Server. Yesterday, mid
morning, during normal processing (selecting data .. loading data ..
etc) the sql server service suddenly shut down and would not start
again. We received several messages but the 2 most consistent messages
were that 1) the ums.dll could not be loaded and 2) the services failed
to start in a timely fashion.
IN the event log, the only thing of interest was this:

Application popup: sqlservr.exe - Entry Point Not Found : The procedure
entry point
?FindNextAvailable@UmsSchedulerQueue@@QAEPAVUmsSch eduler@@W4UmsScheduler
Algorithms@@@Z could not be located in the dynamic link library UMS.DLL.

I am at a complete loss. I did create a new instance of sql Server and
reattached all of my databases to the new instance - but, of course, now
the question being posed to me is "what happened?" I have no idea and
am wondering if anyone has experienced this before or has any insight
they might be able to share.

Any information would be greatly appreciated! Thanks!
Bethany Holliday
IU, KSOB
Indiana Business Research Center

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

This KB article mentions that error, although in a very different
environment:

http://support.microsoft.com/default...b;en-us;306034

Looking at the "Cause" section of the article, perhaps something happened on
the server like a failed servicepack or hotfix installation? But I'm just
guessing, and I have no real idea, so if you're concerned about it happening
again, you might want to consider calling PSS, although if you've already
reinstalled then it might be tough to find a resolution.

Simon