Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Error message when you connect to an instance of SQL Server 2005 Analysis Services: "A connection cannot be made. Ensure that the server is running."


BUG #: 410034 (SQLBUDT)

↑ Back to the top


Microsoft distributes Microsoft SQL Server 2005 fixes 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 2005 fix release.

↑ Back to the top


This article describes the following about this hotfix release:
  • The issues that are fixed by this hotfix package
  • The prerequisites for applying this hotfix package
  • Whether you must restart the computer after you apply this hotfix package
  • Whether this hotfix package is replaced by any other hotfix package
  • Whether you must make any registry changes after you apply this hotfix package
  • The files that are contained in this hotfix package

↑ Back to the top


Symptoms

When you connect to an instance of Microsoft SQL Server 2005 Analysis Services, you may receive an error message that is similar to the following:
Cannot connect to
InstanceName
A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)
When you connect to an instance of SQL Server 2005 Analysis Services from Microsoft Office Excel 2003, you may receive the following error message:
Initialization of the data source failed. Check the database server or contact your database administrator. Make sure the external database is available, and then try the operation again.
If you see this message again, create a new data source to connect to the database.

Note This article discusses one possible cause of this problem. The fix that this article describes will help only if the problem that you experience is caused by the scenario that is described in the "Cause" section.

↑ Back to the top


Cause

This problem may occur because no memory can be allocated to the new connection.

Each connection to an instance of SQL Server 2005 Analysis Services is allocated memory for cached information that relates to the connection. Some cached information is marked as non-cleanable. The memory that the non-cleanable cached information occupies is not released when memory runs low. Therefore, if new connections keep coming in, available memory is exhausted.

↑ Back to the top


Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Analysis Services installed to apply this hotfix.

Restart information

You do not have to restart the computer after you apply this hotfix. However, this hotfix stops and then restarts the Analysis Services service. If you have configured SQL Server 2005 Analysis Services for HTTP access, you have to stop Microsoft Internet Information Services (IIS) and then restart it after the installation is finished. If you have installed SQL Server 2005 Analysis Services as a named instance, you must stop the SQL Server Browser service because the Msmdredir.dll component of the SQL Server Browser service is updated when you apply this hotfix.

Registry information

You do not have to change the registry after you apply this hotfix.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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.
SQL Server 2005 Analysis Services, 32-bit version
File nameFile versionFile sizeDateTimePlatform
Msmdlocal.dll9.0.1518.015,585,49621-Jan-200601:11x86
Msmdpump.dll9.0.1518.03,913,43221-Jan-200601:11x86
Msmdredir.dll9.0.1518.03,927,25621-Jan-200601:11x86
Msmdsrv.exe9.0.1518.014,564,05621-Jan-200601:11x86
Msmgdsrv.dll9.0.1518.05,935,32021-Jan-200601:11x86
Msolap90.dll9.0.1518.04,204,76021-Jan-200601:11x86
SQL Server 2005 Analysis Services, 64-bit version
File nameFile versionFile sizeDateTimePlatform
Msmdlocal.dll9.0.1518.030,011,60821-Jan-200605:15x64
Msmdpump.dll9.0.1518.04,957,40021-Jan-200605:14x64
Msmdredir.dll9.0.1518.04,831,96021-Jan-200605:14x64
Msmdsrv.exe9.0.1518.029,336,28021-Jan-200605:15x64
Msmgdsrv.dll9.0.1518.08,909,52821-Jan-200605:14x64
Msolap90.dll9.0.1518.05,667,03221-Jan-200605:14x64
SQL Server 2005 Analysis Services, Itanium architecture version
File nameFile versionFile sizeDateTimePlatform
Msmdlocal.dll9.0.1518.048,416,98421-Jan-200604:30IA-64
Msmdpump.dll9.0.1518.06,527,70421-Jan-200604:31IA-64
Msmdredir.dll9.0.1518.06,072,53621-Jan-200604:31IA-64
Msmdsrv.exe9.0.1518.047,449,81621-Jan-200604:32IA-64
Msmgdsrv.dll9.0.1518.012,842,20021-Jan-200604:31IA-64
Msolap90.dll9.0.1518.07,686,36020-Jan-200612:31IA-64

↑ Back to the top


Status

Microsoft 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 2005 Service Pack 1.

↑ Back to the top


More Information

For more information about how to connect to an instance of SQL Server 2005 Analysis Services from Office Excel 2003, visit the following Microsoft Web site: For more 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 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbpubtypekc, kbexpertiseadvanced, kbsqlserv2005fix, kbfix, kbsql2005sp1fix, kbsql2005as, kbsql2005presp1fix, kb, kbsql2005olapsp1fix, kbautohotfix, kbsql2005bi

↑ Back to the top

Article Info
Article ID : 912017
Revision : 3
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 229