Re: A connection cannot be made. Ensure that the server is running.
From: Marco Liedekerken (nospam_at_hotmail.com)
Date: 05/19/04
- Next message: Zach Wells: "Re: Can't connect using ADOMD.NET"
- Previous message: Marco Liedekerken: "Re: A connection cannot be made. Ensure that the server is running."
- In reply to: Marco Liedekerken: "Re: A connection cannot be made. Ensure that the server is running."
- Next in thread: T.K. Anand [MSFT]: "Re: A connection cannot be made. Ensure that the server is running."
- Reply: T.K. Anand [MSFT]: "Re: A connection cannot be made. Ensure that the server is running."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 19 May 2004 10:55:19 +0200
Also solved this one myself by looking in the next post after my post.
Adding "ConnectTo=8.0;" to the connectionstring did the trick.
By the way the performance I get with the final release is not good. Now I
have to look at why this is the case.
Marco
"Marco Liedekerken" <nospam@hotmail.com> wrote in message
news:OzK0kNXPEHA.3300@TK2MSFTNGP09.phx.gbl...
> I am using the final release not the Beta of ADOMD.NET.
>
> Any Ideas?
>
> Marco
>
>
> "Akshai Mirchandani [MS]" <akshaim@online.microsoft.com> wrote in message
> news:40aa8347$1@news.microsoft.com...
> > If you are using the Beta of ADOMD.NET connecting to AS2000 then this
will
> > not work -- with the beta you can only connect to AS2k using the XMLA
SDK
> > 1.1 on the middle tier. Your connection string would then look like:
> > Data Source=http://server/xmla/msxisapi.dll
> >
> > With the RTM of ADOMD.NET you can do what you are trying but in the beta
> > this was not implemented.
> >
> > HTH,
> > Akshai
> > --
> > 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.
> >
> > "Marco Liedekerken" <nospam@hotmail.com> wrote in message
> > news:uzBpPzNPEHA.268@TK2MSFTNGP11.phx.gbl...
> > > Hi,
> > >
> > > I get this exception message when I try to Open the connection with
the
> > > following connectionstring:
> > >
> > > "Data source=DRSERVER;initial catalog=Ontwikkel;integrated
> > > security=SSPI;Connect Timeout=0;Client Cache Size=0;Auto Synch
> > Period=0;MDX
> > > Unique Name Style=1;MDX Compatibility=2;Large Level
> Threshold=10;Execution
> > > Location=2;Default Isolation Mode=1;Provider=msolap;Persist Security
> > > Info=False;Location=DRSERVER;"
> > >
> > > The server is running so do you know what the problem is? Is there
some
> > > property which is set wrong?
> > >
> > > Thanks, Marco (hope to have the ADOMD.NET final release working in
some
> > > days)
> > >
> > >
> >
> >
>
>
- Next message: Zach Wells: "Re: Can't connect using ADOMD.NET"
- Previous message: Marco Liedekerken: "Re: A connection cannot be made. Ensure that the server is running."
- In reply to: Marco Liedekerken: "Re: A connection cannot be made. Ensure that the server is running."
- Next in thread: T.K. Anand [MSFT]: "Re: A connection cannot be made. Ensure that the server is running."
- Reply: T.K. Anand [MSFT]: "Re: A connection cannot be made. Ensure that the server is running."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|