Re: 401:Unauthorized Connection Puzzler
From: Rob Conery (RobConery_at_discussions.microsoft.com)
Date: 10/11/04
- Previous message: Akshai Mirchandani [MS]: "Re: ADMD.net connection problem"
- In reply to: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Next in thread: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Reply: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 11 Oct 2004 13:09:06 -0700
I should have thought of asking you this before, but both of the machines i
am trying to set this up on are setup as Domain Controllers (don't ask me
why, but the hosting company thought it would be fun to make them DCs). I
have had lots of trouble putting applications on DCs - could this be it?
"Akshai Mirchandani [MS]" wrote:
> I'd suggest the following:
>
> - check the IIS access log -- it might give a hint about where the problem
> is.
> - if that doesn't help, you can try to use FileMon and RegMon utilities
> (available from sysinternals.com) to see what activity is failing for the
> IIS process.
> - make sure the entire installation folder has Read permissions for
> "Everyone"
>
> By the way, have you installed MSXML4? I don't see why it would cause an
> Unauthorized error, but you never know...
>
> Thanks,
> 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.
>
> "Rob Conery" <RobConery@discussions.microsoft.com> wrote in message
> news:3D0B3FF1-23B9-4E17-A021-F6E4E9D98F52@microsoft.com...
> > I just set this up and it doesn't seem to help - i still get the 401. I
> made
> > sure to restart IIS as well.
> >
> > The one difference between this machine and our development machine (which
> > works fine) is that AD is setup differently, with 2 separate user group
> > schemas. I don't think this should have any bearing as i am able to access
> > the cube remotely using http:// (with msolap.asp); so my credentials are
> > being passed properly. Might there be an issue that way? This is a
> killer...
> >
> > "Akshai Mirchandani [MS]" wrote:
> >
> > > Did you try to allow the POST operation on the .dll type? I don't know
> what
> > > it is on Windows 2003 off-hand, but on Windows XP you can add a mapping
> in
> > > the Configuration properties of the virtual directory. Create a mapping
> of
> > > ".dll" to the msxisapi.dll file and explicitly allow the POST operation.
> > >
> > > 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.
> > >
> > > "Rob Conery" <RobConery@discussions.microsoft.com> wrote in message
> > > news:788A1833-E78F-4A11-9091-5B86AB881941@microsoft.com...
> > > > This is the 5th time i have installed XML SDK as well as the Grape
> City
> > > > control; each time has been interesting to say the least, but i did
> manage
> > > to
> > > > get it to work each time (on windows2k and 2003); this one's killin me
> > > > though...
> > > >
> > > > I have win2003 enterprise server, SQL 2000 and Analysis Enterprise
> with
> > > SP3a
> > > >
> > > > This time, however, i am completely stumped. Here's what i did:
> > > > 1) Install SDK
> > > > 2) Add the virtual directory
> > > > 3) Add the ISAPI dll to Allowed Extensions
> > > > 4) Selected "Allow all unknown ISAPI extentions" just to be sure
> > > > 5) Browsed to http://localhost/xmla/msxisapi.dll and received the XML
> > > notice
> > > > nicely ("expects a POST...").
> > > >
> > > > So i know the dll is loading properly; what i can't figure out is why
> i am
> > > > getting an "unauthorized" connection error (401 request failed,
> > > unauthorized).
> > > >
> > > > This happens before the discover event is even fired and appears to be
> a
> > > > SOAP issue. When i try to connect using the MDX sample app from a
> remote
> > > > machine (using http://ipaddress/xmla/msxisapi.dl with MSOLAP.2) it
> won't
> > > > allow the connection saying the same thing (unauthorized).
> > > >
> > > > When i use the BI control to try and connect i get the same error -
> 401
> > > > Unauthorized
> > > >
> > > > When i try to connect locally, on the server itself, using the same
> MDX
> > > > sample app method i get "Server Error"; however i can connect to the
> cube
> > > > just fine if i just specify the name (not using http/SOAP).
> > > >
> > > > In addition, i can use the old school msolap.asp connection over http
> to
> > > > connect Excel to the cube, so i don't think it's rights or role
> > > restrictions
> > > > on the cube.
> > > >
> > > > I have tried every combination of Allow Anonymous on/off, Digest,
> etc - no
> > > > luck.
> > > >
> > > > Is there anything i missed?
> > >
> > >
> > >
>
>
>
- Previous message: Akshai Mirchandani [MS]: "Re: ADMD.net connection problem"
- In reply to: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Next in thread: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Reply: Akshai Mirchandani [MS]: "Re: 401:Unauthorized Connection Puzzler"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|