Re: SSAS with an Instance name
- From: "Akshai Mirchandani [MS]" <akshaim@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 21 Jun 2006 11:54:32 -0700
The error appears to indicate that the service isn't running on the expected
port... My guess would be that for some reason your msmdpump.ini isn't being
loaded at all and it is using the default values.
Unfortunately this type of issue isn't very easy to solve remotely... You
could try to use FileMon to see if the ISAPI DLL tries to load msmdpump.ini
(and from the correct location).
I would also highly recommend moving the server to SP1 -- there were several
issues fixed related to HTTP and Pump connectivity (although nothing that
sounds like your scenario).
Thanks,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=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.
"Jorge" <Jorge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8746F2DA-5E0B-4F02-88B9-920BB30C9EB6@xxxxxxxxxxxxxxxx
Thanks Akshai for the help,,, but it's not working on the development
machine
(Windows XP, SSAS 2005 no Service Pack), these are the facts:
- We are able to connect to the named instance from Excel without passing
any userid or password (we have assigned permissions to everyone in the
development machine)
- When using the named instance (and configured properly the msmdpump.ini
file) the Profiler doesn't detect any events (not even a SessionStart or
LogInFailure) and the web service returns the message: "No connection
could
be made because the target machine actively refused it. ." (with two dots
at
the ending)
- If we rename the instance to be the default instance (and configured
properly the msmdpump.ini file) the XMLA is returned and the Profiler
detects
all the events.
"Akshai Mirchandani [MS]" wrote:
This should work. How are you trying to connect to it?
Apparently the ISAPI DLL (msmdpump.dll) is for some reason unable to open
a
connection to the named instance. You should verify that OLE DB is able
to
connect to the named instance (e.g. try to use Excel on that machine to
connect to that server).
It could also be a permissions problem somehow -- you can try to run
Profiler against the server and see if it shows an event indicating a
failure to logon...
HTH,
Akshai
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=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.
"Jorge" <Jorge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EB665BB6-1568-479B-B774-78FB429D00C3@xxxxxxxxxxxxxxxx
I have configured HTTP to access the SSAS server and it is working fine
with
the default instance, but I need to query a named instances
(local\sql2k5),
so I change did the following:
1. instance name to SQL2K5
2. changed the msmdpump.ini, the ServerName to: wsdti\sql2k5
But we are getting this error:
The following system error occurred: No connection could be made
because
the
target machine actively refused it. .
Thanks,
Jorge
"Akshai Mirchandani [MS]" wrote:
The XMLA SDK 1.1 is only supported against AS 2000.
AS 2005 natively supports XMLA. For AS 2005 you should just configure
HTTP
access to the server using instructions here:
http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
Thanks,
Akshai
--
--
Try out the MSDN Forums for Analysis Services at:
http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=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.
"Jorge" <Jorge@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BEF007B4-4B9B-4566-B4B6-6DC2FC5720D8@xxxxxxxxxxxxxxxx
Hi, we are using a SSAS with a named instance (SQL2K5) and just
configured
XMLA 1.1, but it brings an error: Datasource Local Analysis Server
not
found
where "Local Analysis Server" is the DataSourceName and my
<DataSourceInfo>Provider=MSOLAP.2;Data
Source=mypc\sqk2k5</DataSourceInfo>
Is there a problem with the named instance?
Thanks,
.
- References:
- Re: SSAS with an Instance name
- From: Akshai Mirchandani [MS]
- Re: SSAS with an Instance name
- From: Akshai Mirchandani [MS]
- Re: SSAS with an Instance name
- From: Jorge
- Re: SSAS with an Instance name
- Prev by Date: Re: SSAS with an Instance name
- Next by Date: Listing "Attribute Hierarchy" "Display Folders" with XMLA
- Previous by thread: Re: SSAS with an Instance name
- Next by thread: Listing "Attribute Hierarchy" "Display Folders" with XMLA
- Index(es):
Relevant Pages
|
Loading