I know that this problem has already been fixed in SQL Server 2005 SP 1 for
AS 2005 cubes, however it still exists for AS 2000 cubes. When connecting to
such cubes using different internet internet browsers (or a different default
language in IE) the connection errors occur sometimes. The exception message
is "A connection cannot be made. Ensure that the server is running." The
stack trace looks like this:

Microsoft.AnalysisServices.AdomdClient.XmlaClient. GetTcpClient(ConnectionInfo connectionInfo)
Microsoft.AnalysisServices.AdomdClient.XmlaClient. OpenTcpConnection(ConnectionInfo connectionInfo)
Microsoft.AnalysisServices.AdomdClient.XmlaClient. Connect(ConnectionInfo
connectionInfo, Boolean beginSession)
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider
.Microsoft.AnalysisServices.AdomdClient.AdomdConne ction.IXmlaClientProviderEx.ConnectXmla()
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.ConnectToXMLA(Boolean
createSession, Boolean isHTTP)
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.Open()

Is there any work-around for this? Does Microsoft have any intention to fix
this any time soon? This is a show stopper for applications that need to
support both AS 2000 and AS 2005 cubes.

Stan

Can you please describe your scenario in more depth? This must be limited to
something specific about your scenario or environment -- otherwise there
would have been other users running into this...

Are you saying it happens sometimes but not always for the same
users/environment?

Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/Sho...ID=83&SiteID=1

This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

"Stan Kondrat" <StanKondrat (AT) discussions (DOT) microsoft.com> wrote

I'm using XP PRO machine for development. I have both SQL Server 2000 and SQL
Server 2005 installed. SQL Server 2000 is installed as the default instance,
SQL Server 2005 is installed as the named instance. I have no problem
accessing AS 2005 cubes (server=localhost\sql2005). Initially I can also
access AS 2000 cubes (server=localhost), but if I change the default language
in IE (e.g. from English to French) all AS 2000 connections fail. This
happens consistently.

Trying different browsers (Netscape, Firefox) causes occasional failures.

"Akshai Mirchandani [MS]" wrote:

hello Stan,

to help better understand the issue, could you please do the following:
in problematic scenario [i.e. connecting to AS2000 with changed default
language in IE]
- add ConnectTo=8.0 to the connection string;
- wrap up the connection.Open() call into something like the following and
post the output:
try

{

// code here

}

catch (Exception e)

{

Exception ex = e;

while (ex != null)

{

Debug.WriteLine("========Exception================ ");

Debug.WriteLine("Type: " + ex.GetType().FullName);

Debug.WriteLine("Message: " + ex.Message);

Debug.WriteLine("Stack :" + ex.StackTrace);



AdomdErrorResponseException errResponse = ex as

AdomdErrorResponseException;

AdomdConnectionException conException = ex as

AdomdConnectionException;



if (errResponse != null)

{

foreach (AdomdError r in errResponse.Errors)

{

Debug.WriteLine("::::ERROR::::");

Debug.WriteLine("code: " +

r.ErrorCode.ToString());

Debug.WriteLine("msg: " + r.Message);

}

}

else if (conException != null)

{

Debug.WriteLine("ExceptionCause:" +

conException.ExceptionCause.ToString());

}

ex = ex.InnerException;

}

} // catch


thanks a lot,
-- mary
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Stan Kondrat" <StanKondrat (AT) discussions (DOT) microsoft.com> wrote

Hello Mary,

Here is the output you requested. I should also mention that our web
application matches the Culture and UI Culture to the browsers default
language.

After switching the default IE language from English to French:

========Exception================
Type: Microsoft.AnalysisServices.AdomdClient.AdomdConnec tionException
Message: Impossible d'établir une connexion. Vérifiez que le serveur
fonctionne.
Stack : at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. GetTcpClient(ConnectionInfo
connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. OpenTcpConnection(ConnectionInfo connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. Connect(ConnectionInfo
connectionInfo, Boolean beginSession)
at

Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.AdomdConne

ction.IXmlaClientProviderEx.ConnectXmla()
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.ConnectToXMLA(Boolean
createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.Open()
... (our part)


After restarting IIS Admin service (or Visual Studio 2005 in case of the
debugger) the French browser connects to the cube.

After switching the default IE language back from French to English:

========Exception================
Type: Microsoft.AnalysisServices.AdomdClient.AdomdConnec tionException
Message: A connection cannot be made. Ensure that the server is running.
Stack : at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. GetTcpClient(ConnectionInfo
connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. OpenTcpConnection(ConnectionInfo connectionInfo)
at
Microsoft.AnalysisServices.AdomdClient.XmlaClient. Connect(ConnectionInfo
connectionInfo, Boolean beginSession)
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.AdomdConnection.IXmlaClientProviderEx .ConnectXmla()
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.ConnectToXMLA(Boolean
createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.Open()
... (our part)

Let me know if more information is required.

Thanks,
Stan

"Mary Potapova [MS]" wrote:

Hello Mary,

In the output generated in my previous message I forgot to add
"ConnectTo=8.0" to the connection string.

After doing that the debug output looks a bit different and is identical in
both cases of language switch (the exception message is always in English).

========Exception================
Type: Microsoft.AnalysisServices.AdomdClient.AdomdErrorR esponseException
Message: The LCID or Compare String flags have already been set by an
existing connection. They cannot be changed.
Stack : at

Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.XmlaClientProvider.Microsoft.AnalysisServices .AdomdClient.AdomdConne

ction.IXmlaClientProviderEx.ConnectIXmla()
at
Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.ConnectToIXMLA(Boolean
createSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnec tion.Open()
... (our part)

Is there any relationship between this problem and this one
(http://support.microsoft.com/kb/912017/) fixed in SQL Server 2005 SP 1?

Stan

"Stan Kondrat" wrote:

We also use "MDX Compatibility=2" in the connection string to handle ragged
hierarchies.

Stan

"Stan Kondrat" wrote:

hello Stan,

from this info, it looks like you might be hitting the msolap8 limitation.
[when connecting to AS2000 adomd.net eventually (through ixmla) delegates to
msolap8.]
msolap8 doesn't allow usage of different LCIDs in the same process, and also
by default, adomd.net 90 uses CultureInfo.CurrentCulture to supply the lcid.
i think this would explain the error you are getting when switching the
language.
if acceptable, i think one way to go about this is to explicetly specify an
LCID in the connection string, so that to make sure it does not change in
case the default language gets re-set.

hope this explains,
-- mary
--
This posting is provided "AS IS" with no warranties, and confers no rights.
--
"Stan Kondrat" <StanKondrat (AT) discussions (DOT) microsoft.com> wrote