How can we help you today? How can we help you today?
Andrew Hodge
Activity overview Badges (0) Posts (41) Comments (43)

Comments

Sort by recent activity
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 _23._1(String , Object ) at _16._1(Server , ConnectionInformation ) at RedGate.SQLBackup.Engine.Server.OpenConnection() / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL Backup fails to connect on first start
System.IndexOutOfRangeException: Index was outside the bounds of the array. at SNINativeMethodWrapper.SNIOpenEx(ConsumerInfo consumerInfo, String constring, IntPtr& pConn, Boolean fInitSec, Byte[] ...
0 votes
Just experienced this issue as well. Is the fixed version listed here supported? / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Backup Logs [*] throws errors with databases in SIMPLE mode
Just experienced this issue as well. Is the fixed version listed here supported?
0 votes
Thanks for the prompt reply Pete. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Backup shows as completed successfully but actually failed
Thanks for the prompt reply Pete.
0 votes
Thanks Jason I have been in contact with support with call ref F0005120 and provided the following extra info, but have not had any feedback for a while now. I tested the saving of templates on another server which we have SQLBackup running on and found that the template does save correctly. I see the template information gets saved into the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\(LOCAL). The server I am experiencing an issue with is configured differently as it is using a 3rd party product (PolyServe) to provide a type of clustering for SQL Server instances. This software basically virtualises the SQL Server instance. When it does this it changes the server name in the SQL Server serverproperty value. So the servers NETBIOS name is MEDPOL1 but SQL Server serverproperty is set to MEDSQLVM01. The instance is then attached to this virtual server ie MEDSQLVM01\INSTA When I save a template on this server nothing is getting created in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\. It stays totally blank even though the job states that the template was saved successfully which is slighty confusing. I think it might be our 3rd party software causing this issue with the templates not being saved. The other thing that is different between this server and the one I successfully saved the template on is that it is Windows Server 2003 x64 edition. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Templates not available
Thanks Jason I have been in contact with support with call ref F0005120 and provided the following extra info, but have not had any feedback for a while now. I tested the saving of templates on ano...
0 votes
For completeness the resolution to this issue is that the account that backup is running under requires permissions to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsand not the user account running the GUI. If it does not have permissions it will still display as the template saving successfully even though it fails. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. Templates not available
For completeness the resolution to this issue is that the account that backup is running under requires permissions to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSetting...
0 votes
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. Data Compare 10.2 issue with SQL Server 2000 databases
Just to update this thread v10.2.0.885 released on August 6th appears to have resolved this issue
0 votes
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die. Please can I have a link to the previous version. Many Thanks / comments
  1. Community
  2. SQL Data Compare Previous Versions
  3. Data Compare 10.2 issue with SQL Server 2000 databases
No worries, glad you guys are still supporting 2000. Trying to get rid of our 2000 instances but 1 or 2 just wont die. Please can I have a link to the previous version. Many Thanks
0 votes
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation. / comments
  1. Community
  2. SQL Monitor Previous Versions
  3. Clock Skew alert issue
Will cross reference the clock skew alert times with the performance on the server and see if there is any correlation.
0 votes
Just did some more testing. When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct. The bug only appears to be when having the overwrite database radio button selected. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL backup 6.5 Ability to choose "existing database file bug
Just did some more testing. When I select the create new database radio button the drop down (orginal database data directory) works correctly ie the paths and filenames are correct. The bug only a...
0 votes
I agree with David When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location). [image] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Setup\SQLDataRoot] =E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL This appears to be missing the final folder \DATA. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\DefaultLog] F:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA When chossing original database directory it should be Database file locations from the database being overwritten. / comments
  1. Community
  2. SQL Backup Previous Versions
  3. SQL backup 6.5 Ability to choose "existing database file bug
I agree with David When selecting SQL Server Data Directory it should default to the SQL Server settings (specifically it should pick up the log location). [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi...
0 votes
Total activity
107
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
23