First off... EXCELLENT job with this framework, packaging & everything about it.

I have sucessfully installed this a number of times (testing) and have been successful with SQL 2005 Express on my local machine, local IIS.   Now, however, I'm trying to install this on my company's intranet.  I have a web server WEB01 and a MS sql server 2000 SQL01. 

I work with SQL Server daily, so I know it pretty well.  I created the login/user, assigned necessary permissions, etc.  Then tested the connection from my workstation successfully.  Then, made the necessary changes and installations on the 2 servers.  Yet, I always receive the "cannot connect to the database, check your connection string. " 

I have since taken an existing mojoportal running on my workstation, changed webconfig to point to the new db server, and it doesn't connect. 

I ran SQL Profiler on the sql server but I don't even see a connection attempt??

Any ideas?

Sql server is set for both Windows & SQL authentication.  I've successfully tested connecting from QA and SQL2005CTP.

I wasn't using user.config simply because i wasn't sure what/how much info should be in there, although I did read that it would take precedence.

A local db works with the following connection string

server=WS17\SQLEXPRESS;UID=mojo;PWD=M0jo;database=mojo

Simply changing it to:

server=SQL01;UID=mojo;PWD=M0jo;database=mojo

Is there any additional debugging I can turn on? As I said, I've turned SQL Profiler on to trace SQL on my db  server, but I don't even see the connection attempts.

Also, in web.config there is a section titled <connectionstrings> with an item key LocalSqlServer.  What is this used for?

I forgot to mention: this is version 2.2.3.6.  I've used both the download and TortoiseSVN.

Thanks for the help!

On another note: I've looked at DNN & Rainbow and like your project the best.  I also use CodeSmity and do a lot of n-tier/oop development for financial services & consulting.  I really want to have everything setup so I can build my own modules for addition, but I'm having some minor troubles with that also.  Once I get this resolved, I'll follow up on that a little bit more.

Chris

Joe,

I eliminated the other webserver and I am just using IIS on my XP workstation, so I am positive that it can connect to the DB server.  Also, the db server has connections from other systems.  I verified that by connecting from my workstation to the DB server with QA - connected both via Named Pipes and TCP/IP.

However, I get strange (and different) errors for both connections.

named pipes just says: "Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

but TCP/IP says: (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)

I know that it looks like the server isn't allowing connections, but as I said, I have tested it with QA.  The currentlog.config contains a number of entries for: "mojoPortal.Business.WebHelpers.CacheHelper [(null)] - Error trying to obtain siteSettings"

Thoughts?

I'm familiar with QA & SQL2005CTP... when you connect to a server, you can specify Windows or SQL Auth.  I'm selecting SQL Auth with the user/password. 

I will go through and double-check everything again and also setup a simple test site (not mojo) to verify that I can connect to the db from asp.net on my local machine.

The local install (sql2005express) has worked a number of times & I've seen you've already fixed issues with the script to work with sql2000. 

I'll start a new thread if I can get it to connect.  However, I'm about to start a new thread in the developer forums because I really want to understand how to set it up properly (i've had some issues already).  I really want to get that set so I can add my own modules (not for contribution yet, but for proprietary services). 

Thanks!!!