Database.VB

SimpleCSLA posted on Friday, June 01, 2007

In Project Tracker, could someone please explain why the code never stops on the line:

Return ConnectionStrings("Security").ConnectionString

yet I still get an error that says:
An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

If CSLA isn't trying to get the connection string, why am i getting a message that appears as though it has hit and failed to retrieve data from SQL Server?

I'm using Remoting, so this might be over most people's heads.  It's sure way over mine.

ajj3085 replied on Friday, June 01, 2007

I'm not sure where exactly that line of code is within the example, but I would guess its because VS is attached to the ptracker.exe process but not the relevent remoting server process (one of the IIS processes).

Does your web.config have the proper connection information?  Does the server have access to the Sql Server instance?

SimpleCSLA replied on Thursday, June 07, 2007

It took a while, but I finally figured out the problem, my IIS Directory Security setting was checked for "Allow IIS to Control Password".  After unchecking the box 'voila' Remoting worked perfectly.

My code never stopped on Database.VB because it never got there.  CSLA first said use remoting and never could open the channel, so I only got a generic 401 unauthorized error.