Error DB upgrade

Published 9 years ago

Hi,

When I have upgraded version 11.7.6.0 to 12.0.2.0 I've got error.

SqlException - Either the parameter @objname is ambiguous or the claimed @objtype (INDEX) is wrong.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.
Caution: Changing any part of an object name could break scripts and stored procedures.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.ExecuteNonQuery(String sql, IDbTransaction dbTransaction, IDbDataParameter[] parameters, Int32 commandTimeout)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.ExecuteScript(String script, IDbTransaction dbTransaction)
at Devolutions.RemoteDesktopManager.Business.DatabaseUpgradeAction.Execute(DatabaseConnectionDataSource dataSource)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.Upgrade(Boolean silent, LogMessageDelegate logMessage)

All Comments (8)

Stéfane Lavergne

Published 9 years ago

Please send us you DB schema. File -> Data Sources -> Upgrade (tab) -> Email Schema to Support

Stéfane Lavergne

Stéfane Lavergne

Published 9 years ago

Have you moved your database using a third-party tool or SSMS? You are missing all indexes and triggers. We usually see this with clients using third-party tools to manage their database.

Do you have a backup of your database?

Bringing your database schema back to a usable state is possible but not a trivial task at this point.

Best regards,

Stéfane Lavergne

GBialy

Published 9 years ago

I have found solution.
I've generated script because on production environment I don't have permissions to restore and my SQL version is 2014 Express on production is 2008 R2.
When I generate script i forget about trigger and indexes.

After recreating upgrade has finished successfully.

Thanks for help and sorry for my mistake.

Regards,
Grzegorz

Stéfane Lavergne

Published 9 years ago

Perfect, thank you for the update. Let me know if you need any more assistance.

Best regards,

Stéfane Lavergne

GBialy

Published 9 years ago

Thanks in this topic no but I've question.
Has application possibility to transfer data or synchronize between different data sources?

Jeff Dagenais

Published 9 years ago

Hello,

Do you want to transfer data from one data source to another? If yes, you would need to do an export/import of your sessions.

For more details, please consult https://help.remotedesktopmanager.com/tipsandtricks_data_migration.htm

Best regards,

Jeff Dagenais

GBialy

Published 9 years ago

But documentation is not exportable.
That is reason creating SQL scripts.

I also tried export/import option but my session through Linux gateway stop working. Something happens witch Kepass credentials and pkk key imported to Key agent.

Now I've known how to generate scrips after this experience.

Stéfane Lavergne

Published 9 years ago

Your best bet to get a "pure-copy" of the database would be to either:
- full backup & restore, make sure this doesn't affect your production backup strategy
- detach/attach : https://msdn.microsoft.com/en-CA/library/ms187858.aspx (copy the files instead of moving them)

In both cases you will need to "fix" your SQL Server logins.

if the logins don't exist, create them then in RDM -> Administration -> Users -> select all user -> "Fix SQL Login" (hit the hammer)

Best regards,

Stéfane Lavergne