cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2417
Views
0
Helpful
10
Replies

SQL database failure during TMS upgrade (13.0.2 -> 13.1.1)

dlongworth
Beginner
Beginner

Hi

Has anyone had any issues with upgrading TMS from 13.0.2 to 13.1.1 whereby the installation fails to upgrade the SQL server?

My server is now at the stage where I can't install the upgrade or re-install v13.0.2.

Thanks

David

1 Accepted Solution

Accepted Solutions

Strange, I marked that bug as "customer viewable" a week ago. I know that it may take a day or two before it actually can be viewed by partners/customers, but it shouldn't take a week.

In general, we (at least in the Cisco TMS world) mark all new bugs as "customer viewable". However, not all bugs from the old Tandberg bug tracking system have been replicated to CDETS yet, so that's why you sometimes see bugs that aren't viewable in the Bug Toolkit.

This is the RNE for CSCtt19457:

----

Symptoms

Upgrading Cisco TMS to version 13.1 or 13.1.1 fails. The Databaselog.txt file shows a timeout in SQL Server:

2011-10-03T15:37:53 Executing SQL Block 1349, starting at line 30465

2011-10-03T15:38:39 Unhandled Error in UpgradeDatabase

2011-10-03T15:38:39 Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

2011-10-03T15:38:39    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Conditions

The issue has been seen in TMS installations using SQL Server 2008, and happens when the stored procedure "NET_Utility_CheckForAccessCopyPasteErrors" is installed. Installing it would normally take about a millisecond, but when this issue happens, it takes more than 20 seconds.

Workaround

Upgrade the SQL Server to the latest service pack and re-run the installer. If the SQL already is on the latest service pack, restart the SQL Server service.

View solution in original post

10 Replies 10

Martin Koch
Advocate
Advocate

Hi!

For the next time and all the others havent done a TMS upgrade, I can strongly recomend running

TMS on a proper virutal enviroment. Upfront an update I do a snapshot and if something would go wrong

you can easyly revert to the old version.

In addition, always have a SQL and the OpenDS backup availalbe, and this not only for the update,

also during normal operation.

With the SQL backup the installer asks you to do it should be quite easy to bring up a 13.0.2 version.

Just take that file and the opends provisioning db backup on the existing or a fresh installed server,

remove TMS, fix the SQL server, reinstall TMS, load the OpenDS backup if needed and there you go.

If you are stuck, its a production TMS and you have a valid service contract I would contact my

Cisco partner and open a TAC case for it.

Please remember to rate helpful responses and identify

Good points Martin but, and as you know, the TMS installer doesn't even touch the SQL, i.e. note the last part of his sentence:

"...installation fails to upgrade the SQL server?"

The installer will upgrade the database (of course) but it won't (and never has) upgrade the type of SQL version being used.

IAWs, if you have TMS installed using SQL Server 2005 Express and although new initial installations (note the word new and initial) starting in TMS 13.0 now utilizes SQL Server 2008 Express, TMS will not upgrade the SQL version. It will utilize what's there, i.e. that being SQL Server 2005 Express in this case.

If you want to upgrade the SQL version that TMS utilizes, then that's a complete different story

So has anyone had an issue of TMS failing to upgrade the SQL database?

Or will I have to rebuild?

Thanks for your help

David

I opened a TAC case.

There is an issue when using SQL 2008.

Reference TMS defect CSCts75316 in the Cisco Bug Tool Kit. This may just be your problem. Can you also provide me with your TAC case reference number so that I can follow up with TAC appropriately.

Cheers,

Dale

Dale,

Does thi bug have to do with a table being named incorrectly and the upgrading looking for that table and failing?  I tried running it through the bug kit but I get the following:

CSCts75316 Bug Details
Dear valued Cisco Bug Toolkit customer, the bug ID CSCts75316 you searched contains proprietary information that cannot be disclosed at this time; therefore, we are unable to display the bug details. Please note it is our policy to make all externally-facing bugs available in Bug Toolkit to best assist our customers. As a result, the system administrators have been automatically alerted to the problem.

While we are working to resolve this issue, we invite you to reach out to the experts on the Bug Toolkit Support Community. You may find answers there to your Bug Toolkit questions, or post your feedback on our forum as well. Thank you.

Note: Some product enhancement requests and documentation bugs may not be available in Bug Toolkit.

Would you be able to email me the bug information?

Thanks,

Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

CSCts75316 is something unrelated; it must be a typo. Maybe Dale meant CSCtt19457 ?

-Kjetil

Yup, that's the one, my apologies...copy and paste error

Thanks Kjetil!

Hmm, still not very helpful though

CSCtt19457 Bug Details
We apologize, but the information contained within bug ID CSCtt19457 is currently under review for publishing on Bug Toolkit. The information will be available soon (typically within one or two business days). The publishing team has been automatically alerted to expedite the review of this bug. Please add this bug to your watch group, so you will be notified when the bug is made available to you. Thank you.

Just out of curiosity, why would any 'bug' be restricted from peoples viewing?  Would it not save countless calls and wasted time for both the customer & Cisco to reveal all known bugs & issues at this moment in time?  Just asking

Thanks,

Justin

Thank you,
Justin Ferello
Technical Support Specialist, ScanSource KBZ

Strange, I marked that bug as "customer viewable" a week ago. I know that it may take a day or two before it actually can be viewed by partners/customers, but it shouldn't take a week.

In general, we (at least in the Cisco TMS world) mark all new bugs as "customer viewable". However, not all bugs from the old Tandberg bug tracking system have been replicated to CDETS yet, so that's why you sometimes see bugs that aren't viewable in the Bug Toolkit.

This is the RNE for CSCtt19457:

----

Symptoms

Upgrading Cisco TMS to version 13.1 or 13.1.1 fails. The Databaselog.txt file shows a timeout in SQL Server:

2011-10-03T15:37:53 Executing SQL Block 1349, starting at line 30465

2011-10-03T15:38:39 Unhandled Error in UpgradeDatabase

2011-10-03T15:38:39 Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

2011-10-03T15:38:39    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

Conditions

The issue has been seen in TMS installations using SQL Server 2008, and happens when the stored procedure "NET_Utility_CheckForAccessCopyPasteErrors" is installed. Installing it would normally take about a millisecond, but when this issue happens, it takes more than 20 seconds.

Workaround

Upgrade the SQL Server to the latest service pack and re-run the installer. If the SQL already is on the latest service pack, restart the SQL Server service.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers