Invalid instance invalid connection when refreshing catalog

Posts   
 
    
GregCSharp
User
Posts: 45
Joined: 18-Nov-2013
# Posted on: 18-Nov-2013 18:14:34   

Hello,

I use LLBLGen Pro 2.6 final. I got the software installed on my machine as well as the project I started to work on. So I try to refresh the catalog.

I get stuck on "retrieving schema 'db_accessAdmin'" till I get the error [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection.

I use Microsoft SQL Server 2008 R2 and connect with DB credentials

Here is what I did so far according to previous posts: - opened ports 1433 1434 and other ports needed according to http://blogs.msdn.com/b/jorgepc/archive/2009/08/25/open-firewall-ports-for-sql-server-the-easy-way.aspx - the UAC is at its lowest level - re installed LLBL Gen - ran LLBL Gen as an admin

So I am running out of ideas.

Can anyone help me please? Thank you

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 18-Nov-2013 20:34:42   

Did you add the port number to the connection string?

Similar post: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=19435

GregCSharp
User
Posts: 45
Joined: 18-Nov-2013
# Posted on: 18-Nov-2013 21:05:41   

Could you explain this step a little bit more?

Where do I add the port to SQL Express?

Thank you

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 18-Nov-2013 21:23:55   

In LLBLGen Pro Designer, when you connect to the database, you write the server name (SQLExpress was just an example), all you need to do is to add the port.

In the following format SERVER_NAME, port_no.

example: SQLServer, 1434

GregCSharp
User
Posts: 45
Joined: 18-Nov-2013
# Posted on: 18-Nov-2013 21:35:38   

I got it, I was trying port 1234...

It worked with 1433.

Now I would like to know is it specific to SQL Express? Another developer gave me the procedure to follow and he only specifies the server IP address without any port.

Thank you anyways

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 19-Nov-2013 07:14:51   

If you are running more than one instance on your server, this might be the cause.

However, this is more likely the answer: http://support.microsoft.com/kb/318432

David Elizondo | LLBLGen Support Team