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.




Unable to view System Log

web-app

Hello,

I recently upgraded from Gemini 3.5 to v3.6.0 Build (2543).  We are running on SQL Server 2005.  Recently I noticed that email notifications were not being sent (althought the test notification button works).  So, I went to check for errors in the System Log.  I get the following error when attempting to view the log:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

This log worked in the past.  What troubleshooting tips can you provide?  Do you need additional information?

Once this is resolved, i will look int the email notification problem.  Is it possible the two problems are related?

Thanks,

Jason

 

 
Jason109
· 1 		Jason109
Wednesday, March 3, 2010, 7:04:39 PM
Replies (2)
helpful
0
not helpful

Please make sure that you have used the new web.config file and that the connection string is set properly:

 <connectionStrings>
<add name="Gemini" connectionString="Server=localhost; Initial Catalog=GeminiLive; uid=sa; pwd=gemini"/> </connectionStrings>

  <session-factory>
   <property name="connection.connectionstringname">Gemini</property>
   <property name="connection.driverclass">NHibernate.Driver.SqlClientDriver</property>
   <property name="dialect">NHibernate.Dialect.MsSql2005Dialect</property>
   <property name="proxyfactory.factoryclass">NHibernate.ByteCode.Castle.ProxyFactoryFactory, NHibernate.ByteCode.Castle</property>

This should solve both issues.
Saar Cohen
· 5000 		Saar Cohen
Wednesday, March 3, 2010, 7:33:45 PM
helpful
0
not helpful

Argh.  That was it.

I checked this file previously, however, I failed to notice the second connection string listed under the 'session-factory' node.  After updating that second connection string, all was well.

Thank you for the quick response.
Jason109
· 1 		Jason109
Wednesday, March 3, 2010, 8:03:45 PM