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." (912017)
The information in this article applies to:
- Microsoft SQL Server 2005 Analysis Services
BUG #: 410034 (SQLBUDT)
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. 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
SYMPTOMSWhen 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. CAUSEThis 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.RESOLUTIONService 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 informationPrerequisitesYou must have SQL Server 2005 Analysis Services installed to apply
this hotfix. Restart informationYou 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 informationYou do not have to change the registry 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 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 |
| Msmdlocal.dll | 9.0.1518.0 | 15,585,496 | 21-Jan-2006 | 01:11 | x86 | | Msmdpump.dll | 9.0.1518.0 | 3,913,432 | 21-Jan-2006 | 01:11 | x86 | | Msmdredir.dll | 9.0.1518.0 | 3,927,256 | 21-Jan-2006 | 01:11 | x86 | | Msmdsrv.exe | 9.0.1518.0 | 14,564,056 | 21-Jan-2006 | 01:11 | x86 | | Msmgdsrv.dll | 9.0.1518.0 | 5,935,320 | 21-Jan-2006 | 01:11 | x86 | | Msolap90.dll | 9.0.1518.0 | 4,204,760 | 21-Jan-2006 | 01:11 | x86 |
SQL Server 2005 Analysis Services, 64-bit version |
| Msmdlocal.dll | 9.0.1518.0 | 30,011,608 | 21-Jan-2006 | 05:15 | x64 | | Msmdpump.dll | 9.0.1518.0 | 4,957,400 | 21-Jan-2006 | 05:14 | x64 | | Msmdredir.dll | 9.0.1518.0 | 4,831,960 | 21-Jan-2006 | 05:14 | x64 | | Msmdsrv.exe | 9.0.1518.0 | 29,336,280 | 21-Jan-2006 | 05:15 | x64 | | Msmgdsrv.dll | 9.0.1518.0 | 8,909,528 | 21-Jan-2006 | 05:14 | x64 | | Msolap90.dll | 9.0.1518.0 | 5,667,032 | 21-Jan-2006 | 05:14 | x64 |
SQL Server 2005 Analysis Services, Itanium architecture version |
| Msmdlocal.dll | 9.0.1518.0 | 48,416,984 | 21-Jan-2006 | 04:30 | IA-64 | | Msmdpump.dll | 9.0.1518.0 | 6,527,704 | 21-Jan-2006 | 04:31 | IA-64 | | Msmdredir.dll | 9.0.1518.0 | 6,072,536 | 21-Jan-2006 | 04:31 | IA-64 | | Msmdsrv.exe | 9.0.1518.0 | 47,449,816 | 21-Jan-2006 | 04:32 | IA-64 | | Msmgdsrv.dll | 9.0.1518.0 | 12,842,200 | 21-Jan-2006 | 04:31 | IA-64 | | Msolap90.dll | 9.0.1518.0 | 7,686,360 | 20-Jan-2006 | 12:31 | IA-64 |
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 2005 Service Pack 1.
| Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
|---|
| Keywords: | kbsql2005olapsp1fix kbsql2005sp1fix kbsql2005presp1fix kbsql2005as kbsql2005bi kbfix KBSQLServ2005fix kbExpertiseAdvanced kbHotfixServer kbQFE kbpubtypekc KB912017 kbAudDeveloper kbAudITPRO |
|---|
|