Re: Connection Forcibly Closed

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



This will most likely be an NTLM authentication issue. With a Win Forms
app, the client connects directly to the AS server. In a Web Forms app,
the browser connects to the web server, which connects to the AS server.
If Kerberos is not setup, the web server cannot pass the client
credentials on to the web server and will use it's own credentials to
connect to AS (in the case of Win2003 I think this will be the "NETWORK
SERVICE" credentials)

Your 3 options are:

1) You either need to set up the application pool in IIS to run as one
fixed domain user account that has access to the cubes.

2) If you have enterprise edition you can specify a username/password in
the connection string.

3) You could set up Kerberos so that the credentials are passed from the
client to the AS server.

Mosha has some articles on enabling Kerberos on AS2k and AS2k5
AS2k - http://www.mosha.com/msolap/articles/enablingdelegation.htm
AS2k5 - http://www.mosha.com/msolap/articles/kerberos_delegation.htm

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1C581251-F918-47B3-93AB-FCBF0CED266F@xxxxxxxxxxxxx>,
AlexandreValente@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> I have an AS 2005 that we can access with a simple connection string from a
> C# Windows Form application. However, when we try to access the same server
> from a Web application on the same client machine, we get this error: "An
> existing connection was forcibly closed by the remote host."
>
> The connection string is just "Data Source=MyServer; Initial Catalog=MyDb;".
> It doesn't appear to be a network or client installation issue, since it
> works perfectly on a Form application. The server ist a Windows 2003 Std SP1
> and the client is a Windows XP SP2.
>
> Any clues on what could be happening?
>
> Alexandre Valente
>

.



Relevant Pages

  • RE: Using kerberosSecurity Throws Security Exception
    ... I am experiencing this error while trying to use a Windows XP client ... application to access a web service located on a W2k3 server. ... client app on the server, ... > Account with a Custom Principal Name using SetSPN.exe utility. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Questions about Remoting, objects, threading. lease lifetime and object cleanup, and a couple of
    ... so long as the Client app is ... always refering to the same server object. ... it sets its ClassOne object to nothing and goes away. ... >>The client app at some point is going to become an ASP.Net app also. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Remoting or windows service
    ... Thanks for writing up such a decent overview of the remoting dev process ... the client and the server. ... > 2) Implement this class in the server app and say that it can be accessed ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
  • Re: Schannel and Session Renegotiation
    ... Schannel does not support the server sending app ... We are discussing the option of providing support for the client blowing off ...
    (microsoft.public.platformsdk.security)