Article ID: 883656 - Last Review: November 21, 2006 - Revision: 3.3 The MSSQLServerOLAPService service may stop and then restart when you incrementally update dimensions in Analysis ServicesMicrosoft SQL Server 2000 fixes are distributed as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. On This PageArticle ContentsSUMMARYThis article describes the following about this hotfix release:
IntroductionWhen you incrementally update dimensions in Microsoft SQL Server 2000 Service Pack 3 (SP3) Analysis Services, the MSSQLServerOLAPService service may stop and then restart. If you browse the data, the CPU utilization may increase to capacity and you receive the following error message: Event 117 "Unexpected Fatal Error Occurred, attempting to restart server. For a list of previous hotfixes, see the "Microsoft SQL Server 2000 Post-Service Pack 3 or Microsoft SQL Server 2000 Post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article: 290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack
RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack
Hotfix informationPrerequisitesYou must install SQL Server 2000 SP3 before you apply this hotfix.Restart informationYou do not have to restart your computer after you apply this hotfix.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name -------------------------------------------------------------- 20-Aug-2004 14:45 8.0.971.0 221,760 Msmdcb80.dll 20-Aug-2004 14:45 8.0.0.971 4,063,808 Msmddo80.dll 20-Aug-2004 14:45 8.0.971.0 1,036,864 Msmdgd80.dll 20-Aug-2004 14:45 8.0.971.0 172,608 Msmdpump.dll 20-Aug-2004 14:04 8.0.971.0 446,524 Msmdsgn.rll 20-Aug-2004 14:45 8.0.0.971 9,642,564 Msmdsgn80.dll 20-Aug-2004 14:45 8.0.971.0 2,089,552 Msolap80.dll 20-Aug-2004 13:34 8.0.971.0 213,068 Msolap80.rll STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4. REFERENCES
For additional information about the naming schema for Microsoft SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
