Catalog service is starting and stopping again


My Catalog service does not run properly on Vista - I start it and it enters stopped state after some seconds. No exceptions... hm?!
Any idea?
I am running MSE with SQLServer Express (followed all installation instructions, hopefully) and my OS is Vista 32bit with all latest patches.


RalfKremer wrote Nov 13, 2007 at 11:13 AM

I had the same problem and resolved it with some small configuration changes.

Open the file Microsoft.MSE.Repository.Service.exe.config in the folder C:\Program Files\Microsoft Managed Services Engine (or for you in Germany c:\Programme\Microsoft Managed Services Engine). Search for the element DBConnString (line 9) and change the Source key that it works with you local SQL Express edition.

It should looks similar to this:
<DBConnString>Initial Catalog=MSE6DB;Data Source=localhost\SQLEXPRESS;MultipleActiveResultSets=True;Integrated Security=SSPI</DBConnString>

williamo wrote Nov 13, 2007 at 10:26 PM

If that doesn't solve your problem, see if anythign is showing up in the event log for the Catalog Service. That should tell you what error it is encountering as it is trying to start.

ChristianWeyer wrote Nov 15, 2007 at 10:44 PM

I already did that change, thx Ralf.

The exception (I didn't know there is an extra event log for MSE, sorry):

Attempt to start MSE6 Service Catalog failed: 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)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.MSE.Repository.Service.WCFCatalogSvcHost.RegisterForEvents(DBEvents dbEvent)
at Microsoft.MSE.Repository.Service.WCFCatalogSvcHost.StartService()

at Microsoft.MSE.Repository.Service.WCFCatalogSvcSvc.OnStart(String[] args)

My SqlExpress is configured for both TCP and NP... strange.

cpmadrid wrote Nov 16, 2007 at 12:45 PM

Can you connect to your SQL Express instance from Visual Studio or the Management Studio?

ChristianWeyer wrote Nov 16, 2007 at 2:01 PM

Yes, SqlExpress just works fine for me besides for MSE.

cpmadrid wrote Nov 17, 2007 at 6:06 PM

I'll contact you directly, so I get more detailed debugging information.

wrote Nov 24, 2007 at 9:59 PM

wrote Aug 26, 2010 at 8:49 PM

wrote Feb 14, 2013 at 7:08 PM

wrote May 16, 2013 at 9:11 AM

wrote May 16, 2013 at 9:11 AM

wrote Jun 14, 2013 at 7:07 AM