StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Trial install Sample Console doesn't work because of SQLExpress connection

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Edhy Rijo — Wed, 26 Aug 2015 12:54:15 GMT

Hi Darrell,

Since you are using Windows 8.1, try opening VS as "Administrator", then test to see if that fixes the issue.

Trial install Sample Console doesn't work because of SQLExpress connection

Michael Niemann — Wed, 26 Aug 2015 12:54:15 GMT

I just installed the trial edition, and the installation went fine (XP and Vista on the same PC).

However, they both have the same problem... I am unable to execute the Sample applications from the Sample Console because there is a problem connecting to the database. Note: This is in spite of installing the StrataFrame and StrataFrameSample databases (.mdf files) in SQLExpress... which is running as a service.

Any help would be appreciated.

Regards, Mike Niemann

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Darrell Praytor — Wed, 26 Aug 2015 12:41:17 GMT

It appears to be correct. It is the same I use when I test connected using Visual Studio and it allows me access to the Strataframe sample database. I'm using windows 8.1 and SQLEXPRESS 2014 if that makes a difference. I tried both local\sqlexpress and mycomputername\sqlexpress. On the top level (BOMapper on Project level) it acts like both connect fine. Then when I move to CustomersBO to configure it, as soon as I try to select a source it gives me the error if I"ve selected SQL server.

RE: Trial install Sample Console doesn't work because of SQLExpress connection

StrataFrame Team — Wed, 26 Aug 2015 11:57:55 GMT

When you view the properties on a project node in the BOMapper, there is a list of connection strings at the bottom. Those are the connection strings that are used unless the connection string is overriden on the configuration for the individual BO (in the properties of the BO in the BOMapper). Check those connection strings; it sounds like the "SQL Server Connection String" in the project properties is off.

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Darrell Praytor — Wed, 26 Aug 2015 11:44:39 GMT

My problem happens on the next step. I connect to my SQLEXPRESS server fine. But when I configure CustomersBO and try to select a table using the SQL Server selection, I get a Business Object Mapper Error ID 3 - An error occurred while attempting to open the data source with the connection string ....etc. Exception - Cannot open database xx requested by the login. Login Failed for user 'yyyy'. When I change selection to DDT, I can access the sample tables just fine. I can also access them thru the SQLEXPRESS management console. Not sure why it is refusing my login when selecting SQL server.

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Trent L. Taylor — Sun, 29 Jun 2008 12:40:11 GMT

Great! Glad you got it going!!! :)

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Michael Niemann — Sun, 29 Jun 2008 12:25:18 GMT

[quote][b]Trent L. Taylor (06/29/2008)[/b][hr]Mike,

You might try one of the following when entering the server name.

You can also try this in the case the TCP/IP is turned on:

[codesnippet]localhost\SQLEXPRESS[/codesnippet]

One of these should more than likely work.[/quote]

Trent, I had enable all the communication protocols when I first encountered the problem... and the above suggestion worked just fine. Thank you very much.

Regards, Mike Niemann

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Trent L. Taylor — Sun, 29 Jun 2008 11:21:05 GMT

Mike,

You might try one of the following when entering the server name. Unless you manually changed the default settings you will have an instance name and TCP/IP will be turned off. So you will want to enter a server name like this:

[codesnippet]MyComputerName\SQLEXPRESS[/codesnippet]

You can also try this in the case the TCP/IP is turned on:

[codesnippet]localhost\SQLEXPRESS[/codesnippet]

Finally, if you installed SQL Server as the default instance, then you can omit the SQLEXPRESS instance name (this is not as likely if you did not do this intentionally):

[codesnippet]MyComputerName[/codesnippet]

or (if TCP/IP is enabled)

[codesnippet]localhost[/codesnippet]

One of these should more than likely work.

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Michael Niemann — Sun, 29 Jun 2008 09:05:40 GMT

Trent,

Thank you for the weekend reply!

I believe the problem must be related to my configuration (home network) and SQLExpress. The error I get is "unable to authenticate server". Note: I do see the "Database Connection Wizard"... that is not the problem.

Using "SQL Server Management Express" I can see that both the StrataFrame database, and the StrataFrameSamples database are available... and I can see the data in the Sample database. So as far as SQLExpress is concerned things are fine.

Unfortunately I am new to SQL Server, and I believe the issue is there (with connectivity or authorization). I will see what I can find on MSDN.

Thanks again for your assistance, and I will post here what the problem was to help the next person who travels this path.

Regards, Mike Niemann

RE: Trial install Sample Console doesn't work because of SQLExpress connection

Trent L. Taylor — Sat, 28 Jun 2008 23:45:54 GMT

This just sounds like an SQL connection problem. All of the samples (that talk to a database) attempt to connect to a StrataFrameSample database. So if this database was installed during the installation process (it is an option) then you just need to direct the connection to that database. If you do not even get a prompt asking you for the connection to the database, then more than likely when you first entered or selected the connection it was either the wrong connection or has moved...and thus an error may occur. So what you will want to do in that case is just manually remove the AppKeys.Dat and Connections.Dat (this is the easiest way to explain your options here versus going another route).

For Vista

Open the C:\ProgramData\MicroFour\ConnectionData folder
Delete the Appkeys.dat and Connections.dat files
Attempt to launch another SF sample. You should then be prompted for the connection information again.
If the appropriate server containing the StrataFrameSample database was entered, then you should be good to go.

For Windows XP

Same as above other that the path is c:\Documents and Settings\All Users\Application Data\MicroFour\CoonnectionData (this is at least a close approximation off of the top of my head :) )