SqlException
  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. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Source     : .Net SqlClient Data Provider

ArgumentNullException
  Value cannot be null.
Parameter name: node

Source     : System.Windows.Forms

Stack Trace:
   at System.Windows.Forms.TreeNodeCollection.AddInternal(TreeNode node, Int32 delta)
   at System.Windows.Forms.TreeNodeCollection.Add(TreeNode node)
   at MicroFour.StrataFrame.AddIns.PartialClassBuilderDialog.BuildTreeView()

I was able to fix the problem.

Alan,



Glad you fixed the problem! I have a hopefully helpful suggestion though. When you figure out what fixes the problem post the fix too. I.e. what did you do to fix this SqlException?



There are two reasons for this:



1. If you ever run into this problem again, and you've forgotten how you fixed it last time, you will have a record of what you did and you can find it easily by looking at your posts (click on your name, then you can view your posts). I've kicked myself a couple of times for not having done this.



2. There is a very good chance someone else will run into the same problem at some point. Posting the solution will help out others, saving them time, encourage them to post their fixes and maybe someday that will help you out too. Also, it helps to deepen the understanding of both .NET and the SF framework, enabling more developers to be able to answer questions, which ultimately means better/faster responses.



In any case, I'm glad you got it working!

Hi Ben,

Thanks for the suggestion. Here is how the problem was fixed:

During the installation process, the app framework installer kept erroring out on me so the StrataFrame databases were never correctly installed. So I, 1) detached the incorrectly installed databases, 2) got a back up of the databases from a co-worker whose databases were correctly installed and 3) restored the databases from the backup provided by the co-worker. Once the databases were correctly installed, the sql exception error was fixed.

I'm glad you got it working.  An incorrectly installed SF database will certainly cause all sorts of unexplained problems.

Thanks for posting the fix...I'll probably need it one day!