Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Error configuring the SQL database

web-app

Error configuring the SQL database.
SQL Server does not exist or access is denied.

I am attempting at installing Gemini and I keep getting this error. I'm trying to install it with SQL Server Express and the database named Gemini.

Here is the connectin string from my web.config file. Are there any known issues of Gemini running with SQL Server Express? I wouldn't think there would be but I can't seem to find out where the error is being thrown.

    <nhibernate>
        <!-- The SQL Server dialect (Gemini supports "MsSql2000Dialect" or "MsSql7Dialect") -->
        <add key="hibernate.dialect" value="NHibernate.Dialect.MsSql2000Dialect"/>
        <!-- The SQL Server database connection string -->
        <add key="hibernate.connection.connectionstring" value="data source=127.0.0.1;initial catalog=Gemini;user id=sa;password=sa"/>
        <!-- Misc -->
        <add key="hibernate.connection.provider" value="NHibernate.Connection.DriverConnectionProvider"/>
        <add key="hibernate.connection.driverclass" value="NHibernate.Driver.SqlClientDriver"/>
    </nhibernate>
deaner
· 1 		deaner
Friday, February 16, 2007, 5:37:25 AM
Replies (8)
helpful
0
not helpful

Please make sure you set the server name (data source), database (initial catalog) and user name and password.
Saar Cohen
· 5000 		Saar Cohen
Friday, February 16, 2007, 10:29:45 AM
helpful
0
not helpful

Ok, I've double checked the connection in the web config but now I keep getting this error message. I've attempted to troubleshoot it and already enable Named Pipes in the SQL Server Configuration Manager, added the users and checked the firewall but keep getting this error. 

Does anyone have any suggestions as to what else I should check?

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
deaner
· 1 		deaner
Tuesday, February 20, 2007, 6:37:35 AM
helpful
0
not helpful

Try enabling TCP.


Saar Cohen
· 5000 		Saar Cohen
Tuesday, February 20, 2007, 7:53:17 AM
helpful
0
not helpful

I have seen this sort of error before with SQL Express databases.  You may need to connect with the format:

machine_name\sqlexpress

(change the sqlexpress if you didn't install it with this default name).

Kevin
kevinw
· 1 		kevinw
Tuesday, February 20, 2007, 11:26:57 AM
helpful
0
not helpful

Ok, Thanks alot. Changing the adding the servername\sqlexpress seemed to help. Now I am getting this error.

Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection.



I did some research and changed the authentication method and enabled Named Pipes but it is still throwing that error.

Any suggestions?


deaner
· 1 		deaner
Wednesday, February 21, 2007, 10:01:35 AM
helpful
0
not helpful

You need to enable SQL authentication. You can do this using SQL Server Management Studio.

Right click on the server and select the security option, select SQL and windows authentication mode in Server authentication.
Mark Wing
· 9108 		Mark Wing
Wednesday, February 21, 2007, 10:59:06 AM
helpful
0
not helpful

^ I've already done that and I can't seem to see why I am still getting the error message. I've also added the SQL Service Patches.

I am usually pretty good at troubleshooting these kinds of problems myself but I am having very little luck finding documentation similar to my problems online.

I was hoping to avoid reinstalling everything but it looks like I'm running out of options.

I've tried to reset the sa password but SQL Server managment throws an exception everytime.

Any other suggestions would be most appreciated.


deaner
· 1 		deaner
Thursday, February 22, 2007, 4:00:38 AM
helpful
0
not helpful

Try creating a new SQL login and made it a dbo to the gemini database and use that login information in the web.config.

Also, try using the computername instead of 127.0.0.1
SystemIdleProcess
· 1 		SystemIdleProcess
Thursday, February 22, 2007, 5:52:22 PM