We seem to have encountered another issue while profiling the service. One of our threads uses the JET engine to connected to an excel file on a remote machine. Our service runs under a specific account and this account has all the relevant permissions. This all works fine. However when the profiler is attached we get an error when connecting to the file.
The exception is not the most useful as it's just an "Unspecified error". I'm assuming it has something to do with permissions and the way the profiler stops and starts the service. Can you direct us in possible placed to look. We're making the assumption that when the service is restarted when the profiler is attached that it used the same account?
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at Communicator.Data.DataImport.ImportTempDB.Create() in C:\\Documents\\Visual Studio 2005\\Projects\\Communicator\\v4\\Communicator\\Data\\DataImport\\ImportTempDB.cs:line 86
at Communicator.Data.DataImport.Service.DataImporter.Import() in C:\\Documents\\Visual Studio 2005\\Projects\\Communicator\\v4\\Communicator\\Data\\DataImport\\Service\\DataImporter.cs:line 126</StackTrace>
Here is a snapshot of the stacktrace pinpointing the the calls to the OLEDB objects.