New Posts New Posts RSS Feed: The installation in SQL EXPRESS 2005 succeeds but cannot connect
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

The installation in SQL EXPRESS 2005 succeeds but cannot connect
 Post Reply Post Reply
Author
  Share Topic Share Topic  Topic Search Topic Search  Topic Options Topic Options
Customer View Drop Down
Senior Member
Senior Member
Avatar
User Submitted Questions to Support

Joined: 30-May-2007
Location: United States
Posts: 260 		Post Options Post Options   Quote Customer Quote  Post ReplyReply Direct Link To This Post Topic: The installation in SQL EXPRESS 2005 succeeds but cannot connect
    Posted: 12-Jul-2007 at 11:08am
I have installed the tutorial in SQL EXPRESS 2005, but
from the OM it cannot connect to me, because from the option "Microsoft OLE DB for Provider SQL Server" it never discovers the DB nor the server.
Back to Top
IdeaBlade View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 30-May-2007
Location: United States
Posts: 346 		Post Options Post Options   Quote IdeaBlade Quote  Post ReplyReply Direct Link To This Post Posted: 12-Jul-2007 at 11:10am

 If your SQL Express installation is using a named instance you need to use "ServerName\SQLEXPRESS" for the server name.  If you're using the Data Link Properties window from the Object Mapper you can type in the server name if it's not found in the drop down list.

You can also use the SQL Native Client provider
Back to Top
jacktripper1000 View Drop Down
Newbie
Newbie


Joined: 18-Jul-2007
Posts: 4 		Post Options Post Options   Quote jacktripper1000 Quote  Post ReplyReply Direct Link To This Post Posted: 18-Jul-2007 at 8:08am
Hi, I have similar problem I think. I have used IdeaBlade devforce express in past so I am confused what's going on on my system.

I had an installation 3.4.x which was not being able to connect to the database so I upgraded to latest 3.5.2.3 but I still see the problem.

Here's what is happening. I open Visual Studio 2005 and IdeaBlade Object Mapper and try to connect to the database. In the settings I use SQL native driver, give the correct name of the SQL Server 2005 named instance MYSERVER\SQLEXPRESS and use Integrated security. Then I click test connection and it works. But when I come back to Ideablade Object Mapper, it shows me not connected and Add Classes also fails. Here's the string for your reference.

Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=IdeaBladeTutorial;Data Source=MYSERVER\SQLEXPRESS

I also tried ODBC and did a SQL trace on that and the log shows that IdeaBlade application is talking okay to ODBC (didn't see any errors) but still cannot connect.

Is there some log from Object Mapper that can tell me what's wrong?

Please help.

Jack
Back to Top
jacktripper1000 View Drop Down
Newbie
Newbie


Joined: 18-Jul-2007
Posts: 4 		Post Options Post Options   Quote jacktripper1000 Quote  Post ReplyReply Direct Link To This Post Posted: 18-Jul-2007 at 10:29am
Just a quick update, I have tried to uninstall and install this and that  is not a solution to this problem.

 
Back to Top
davidklitzke View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 14-Jun-2007
Posts: 715 		Post Options Post Options   Quote davidklitzke Quote  Post ReplyReply Direct Link To This Post Posted: 18-Jul-2007 at 1:27pm

Your problem is that there is enough connectivity to the database that you can pass the "Test Connection" test, but DevForce is not able to read the schema information from the database.  There are a number of things which can cause this problem, most of them related to database installation issues, not DevForce issues.

(1) Probably the most  common reason for this message is when you use SQL Server passwords and neglect to mark the checkbox "Allow Saving of Password".  This is almost certainly not your problem.
 
(2) Another common cause is when you don't have a "DevForce compliant" provider (e.g., you're trying to use Access).  That shouldn't be your problem, but you might just try using the OLEDB provider to see whether you have any better luck.  If the OLEDB provider works with the Object Mapper, you can then still use the Native Client provider at runtime.  Just change the connection string in the ibconfig file.
 
(3) Most of the other problems have to do with how the database was installed or configured.  Sometimes just uninstalling the database and reinstalling will fix the problem.
 
(4) The wrong version of MDAC sould cause this problem.  Go to Program Files\Common Files\System\OleDB.  Right click on oledb.dll and chose Properties and then select the Version tab.  You should be using version 2.81 or higher.
 
(5) A corrupted System DLL could cause the problem.
 
(6) The problem could be caused by a Security issue.
 

 
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down