Attached is a screenshot of the error I get (I'm assuming that when I hit post, I'll get the option to upload my attachments, if not, then that will explain why this message has no attachements:

" An error occured during the retrieval of the catalogs:

Error message: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. Native error information: 14 Provider used: Microsoft OLE DB Provider for SQL Server ANSI SQL error code: 08001 "

Here's what I'm doing:

1. Downloaded the demo about an hour ago: "v 2.0.0.0 Final (May 23rd, 2007)".
2. Installed on Windows Vista Ultimate (made the batch file and ran as admin, as download page instructs). Installed with no problems.
3. Run the program (I'm told it's called the "designer").
4. File|New Project. Entered all of my information, including server name, SQL Server login (which is the sa login, btw), pw, etc...
5. Click "Connect" button and get the error.

Note the following:

1. Running LLBLGen demo on a Windows Vista Ultimate machine.
2. .NET 1.1, 2.0, 3.0 installed.
3. Ran LLBLGenPro.exe as administrator and as my regular user account (same error).
4. Server is across the internet.
5. Server is running Windows Server 2003 Web Edition.
6. DB Server is MS SQL Server 2005 Express.
7. I am NOT running SQL Server Express with a named instance... It's the default instance.
8. Using SQL Server Management Studio, I can connect all day long with the same login information and credentials... as well as my existing applications connect with no problems.
9. Asked someone else (a friend who referred me to this product) to attempt to connect to my database and he got the same error on a Windows XP Pro machine using a January build of the fully registered product. He directed me to this forum to ask for help, so "Help!"
10. I think I've followed all the posting guidelines from here: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=7721

Thanks!

What exactly do you fill in as 'server' name? An alias you created in the client-access tool for SqlServer ?

I can't reproduce it here with a sqlserver2005 box, sqlserver login etc.

The connection string used is: "Provider=SQLOLEDB;data source=" + serverName + ";UID=" + userID + ";PWD=" + password + ";initial catalog=;persist security info=False;packet size=4096"

We use OleDb for this because the OleDbConnection has a handy method to grab all catalogs easily.

I've responded in the "Help Desk" forum because of the sensitive nature of the connection information.

Thanks!

I've found out the cause of the problem: (just for reference) -> if 1434 is blocked at the firewall, be sure to define a client alias for the server, and hard-specific TCP/IP and 1433 as port.