User profile for Nigel Morse

There is a issue number SB-3735 created for this (sorry - been meaning to post this for a while now!) / comments

There is a issue number SB-3735 created for this (sorry - been meaning to post this for a while now!)

0 votes

Hi - This issue wasn't fixed in 5.4 so sorry if you've been led to believe it was. The issue (number SB-3421) is currently assigned to me and I'm hoping we can fix this in the next version - though I can't say for sure yet I'm afraid. / comments

Hi - This issue wasn't fixed in 5.4 so sorry if you've been led to believe it was. The issue (number SB-3421) is currently assigned to me and I'm hoping we can fix this in the next version - thoug...

0 votes

Thanks - I have them now. The problem here is very different so I've passed the logs to the current response team who are investigating a similar issue to the one you seem to have. thanks / comments

Thanks - I have them now. The problem here is very different so I've passed the logs to the current response team who are investigating a similar issue to the one you seem to have. thanks

0 votes

If you email support they should be able to sort out an ftp transfer you. / comments

If you email support they should be able to sort out an ftp transfer you.

0 votes

Ah - in which case it may be a different problem. Could you send the alert repository logs to support@red-gate.com (and reference this thread in your email so they know to send it to me - thanks) / comments

Ah - in which case it may be a different problem. Could you send the alert repository logs to support@red-gate.com (and reference this thread in your email so they know to send it to me - thanks)

0 votes

If you're seeing the same stack trace in the logs then the only fix available now is the hotfix from Microsoft that I mentioned in my last post here. / comments

If you're seeing the same stack trace in the logs then the only fix available now is the hotfix from Microsoft that I mentioned in my last post here.

0 votes

Ok - the logs came through. Because they were so big the ones for the time when it was rebooted had been deleted, however the ones that were left showed the problem. There's a bug in the Microsoft SQL connection stuff for which there is a fix on here http://support.microsoft.com/kb/948176. Sadly it seems to be an on-request fix rather than a download, however they do say it would be in the next service pack (though if that is shipped yet I can't tell - The list of fixes for .NET 2.0 SP1 doesn't list this fix (http://support.microsoft.com/kb/945757/)) It seems that once this error occurs it keeps recurring so the only way is to restart the repository and hope it doesn't happen again. However we'll try and make a case to reproduce it here and then hopefully we can try and put a workaround in to fix, or at least detect this happening and take action. I'll add it to our issue tracking system in the meantime. EDIT: So that people searching for this error the stack trace in the log that shows this is like 06:26:00.616|Error |AlertRepository |28 |SqlServerUpMonitor : Failed to get information from SQL Server <servername> (code 0)|System.IndexOutOfRangeException: Index was outside the bounds of the array. at SNINativeMethodWrapper.SNIOpenEx(ConsumerInfo consumerInfo, String constring, IntPtr& pConn, Boolean fInitSec, Byte[] sspiBuffer, Byte[] instanceName, Boolean fOverrideCache, Boolean fSync) at System.Data.SqlClient.SNIHandle..ctor(ConsumerInfo myInfo, String serverName, Boolean integratedSecurity, Byte[] serverUserName, Boolean ignoreSniOpenTimeout, Int32 timeout, Byte[]& instanceName, Boolean flushCache, Boolean fSync) at System.Data.SqlClient.TdsParserStateObject.CreatePhysicalSNIHandle(String serverName, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Byte[]& instanceName, Boolean integratedSecurity, Byte[] serverUserName, Boolean flushCache, Boolean async) 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 g.a(String ) at l.GetConnection() at aw.a(V ) at az.a() at az.RunNow() / comments

Ok - the logs came through. Because they were so big the ones for the time when it was rebooted had been deleted, however the ones that were left showed the problem. There's a bug in the Microsoft ...

0 votes

Hi Really sorry you've had this problem - I'm not sure what's happened... i've not hear of this before at least. Could you please answer the following first: - When you reinstalled did you have to reactivate or did the servers just come back as activated? - Did you try just restarting the alert repository service before reinstalling? Also if you could gather the logs from the Alert Repository machine (in documents and settings/all users/application data/red gate/logs/....) and then send them to support@red-gate.com (and put a link to this forum post in so they know to send the files to me) that would be great - thanks. / comments

Hi Really sorry you've had this problem - I'm not sure what's happened... i've not hear of this before at least. Could you please answer the following first: - When you reinstalled did you have to ...

0 votes

Thanks. I suspect that just restarting the service would have worked as well in that case - but obviously it shouldn't happen in the first place. I'll take a look at the logs and see what I can glean. / comments

Thanks. I suspect that just restarting the service would have worked as well in that case - but obviously it shouldn't happen in the first place. I'll take a look at the logs and see what I can gl...

0 votes

Hi, Glad you're liking it so far [image] I'm afraid there's no way to do currently - but I will add it to the lost of feature requests. / comments

Hi, Glad you're liking it so far I'm afraid there's no way to do currently - but I will add it to the lost of feature requests.

0 votes

How can we help you today?

Nigel Morse

Comments