Re: 401:Unauthorized Connection Puzzler

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Akshai Mirchandani [MS] (akshaim_at_online.microsoft.com)
Date: 10/04/04 

Date: Mon, 4 Oct 2004 12:00:01 -0700

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?

Relevant Pages

  • Re: .Net packaging/wrapper application?
    ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Unnown process... 5eplorer.exe
    ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings. ... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ...
    (microsoft.public.win2000.general)
  • Re: WinSxS, functional under 2k ?
    ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
    (microsoft.public.win2000.general)
  • Re: Determine name and path of dropped object?
    ... MDE I would really suggest the use of external DLL to hold the subclassing ... windows after loading the Microsoft Office Visual Basic Editor, ... Public Declare Sub DragAcceptFiles Lib "shell32.dll" _ ...
    (microsoft.public.access.modulesdaovba)
  • Re: .Net packaging/wrapper application?
    ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. ... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ...
    (microsoft.public.dotnet.framework.aspnet)