Upgrade MSDS

Hi all

Intend to upgrade the TMS of 14.5 to 15.3.

Can put us directly to level?

We also intend to upgrade from 8.6 to 8, 8 VCS - can upgrade us directly?

Dev

You are right, that if someone is running TMS on the old equipment TANDBERG camera, it supports up to 14.2 TMS, which is the latest version of TMS in support of Windows 2003.

Tags: Cisco Support

Similar Questions

LAYOUT ERROR 1670 UNABLE TO LOAD THE MODULE UPGRADE MSDS 15.1.0. TO 15.3.0

I'm in TMS 15.1.0 and try to upgrade to 15.3.0...

I am connected with admin priv. Get the error failed to load the module 1670... Error code 5?

Any ideas?

VR

C

This would make sense, generally a good idea to turn any virus protection during the installation/update just in case so to avoid problems such as this, so it is the anti-virus that is causing the error.

Failure of SQL database during the upgrade (13.0.2-> 13.1.1) MSDS

Hello

Someone had problems with the TMS 13.0.2 to 13.1.1 upgrade that installation fails to put SQL server level?

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

Thank you

David

Strange, I've marked this bug as a 'visible customer' a week ago. I know that it can take a day or two before, it can actually be displayed by partners/clients, but it shouldn't take a week.

In general, mark us (at least in the world of Cisco TMS) all new bugs as a 'visible customer '. However, not all bugs old Tandberg bug tracking system have been replicated to CDETS yet, that's why you sometimes see bugs which are not visible in the Bug Toolkit.

It's the RNE for CSCtt19457:

----

Symptoms

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

2011-10 - 03T 15: 37:53 to execute SQL block 1349, starting at line 30465

2011-10 - 03T 15: 38:39 error in UpgradeDatabase unhandled

2011-10 - 03T 15: 38:39 timeout has expired. The delay before the end of the operation or the server is not responding.

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

Conditions

The issue was seen in facilities at TMS using SQL Server 2008 and occurs when the stored procedure "NET_Utility_CheckForAccessCopyPasteErrors" is installed. Installation it would normally take about one millisecond, but when this occurs, it takes more than 20 seconds.

Workaround

Upgrade SQL Server to the latest service pack and run Setup again. If the SQL code is already on the latest service pack, restart the SQL Server service.

Question about MSD + upgrade and migration applications

Hi all

I am running:

TMS 13.2

TMSPE 1.0

The two co reside on a Windows 2003 server, pointint in an external box of SQL.

We also organize TCX 2.3 on our Exchange.

Now that our server guys have * finally * installed the service pack required on the Exchange, we are ready to migrate to TMSXE but also to upgrade the TMS and TMSPE.

So we want ot go to:

TMS 14.2.1

TMSPE 1.1

TMSXE 3.1

In addition to migrate a Windows server 2008R2 TMS + TMSPE.

I know the different individual guides to upgrade as well as the dependencies between TMS and TMSPE/TMSXE versions. I'm hoping to do the upgrade and migration all in one and am hoping to get some tips on the best order to do everything.

My first question - decomission the 13.2/TMSPE server 1.1 TMS, that I can install TMS 14.2.1 and TMSPE 1.1 on the Windows Server 2008, they point to the relevant databases and allow upgrading from there? Or do I need install the new versions TMS/TMSPE on the old server, first of all, upgrade the databases and then migrate?

Second question - before all this, I run the TMSXE migration tool to extract the data 2.3 TCX, uninstall TCX of Exchange, TMS upgrades and then install TMSXE 3.0/3.1 at the end?

As all this is running on the virtual machine I'll instant just in case. Advice on the issues listed above, or general advice about these upgrades would be appreciated

Hi Nick, IMHO, I suggest you first migrate your 2.3 TCX to TMSXE 3.0.2 by this TMSXE 3.0 installation guide, and then pass the TMS and PE later.

Yes, VM snapshot backup option before any upgrade is fine.

BR, Mahesh Adithiyha

The upgrade of MXP via TMS

Having a problem to upgrade MXP BOF software Version F8.2 to F9.02 through TMS 12.6.2 (we have 200 + upgrade)

Reports of TMS 100% successful even, but the systems are not upgraded.

I tried the re-boot after upgrade, no different

Update the endpoint works Web Interface ok.

Any ideas?

Philippe

I had this problem myself.

In my case, it was due to a corrupt firmware image. Manager software TMS showed that firmware was on the server; the problem is that the file was corrupt and much smaller that it should have been. Upgrades using this inevitably failed file - even if reported as successful MSD!

Take a look on your server in your software repository location (most often

C:\Program Files\TANDBERG\TMS\wwwTMS\Public\data\SOFTWARE) and see if the file looks suspiciously small (or something else). You can manually copy the file to that location.

TMS upgrade, the OS and DB Migration

Hello

We currently use TMS 12.6.1 on Server 2003 with SQL 2005, but we intend to move to 13.2 TMS on Server 2008 with SQL 2008. I can't find a specific documentation on the management of OS and DB updates just in place upgrades to MSDS.

Are the steps below for a migration to that action plan we aim the right?

-New server made available with SQL2008 (same host, same IP address, but obviously disconnected name)

-Move tmsng database from the old server to new server.

-Install the TMS 12.6.1 on the new server by selecting a custom installation and specifying the existing database.

-Perform to upgrade in place on the new server to 13.2 TMS.

-Disconnect the old server, connect to the new server.

Thank you

Mark

Hello

Yes these steps only seems that you don't need to install 12.6.1. Once the database is moved to the new server, you can install 13.2.1. The installation program will detect the 12.6.1 data bases and update accordingly.

Also remember that when you upgraded, check the settings in MSD since a large part of the old server settings will reside in the database. But you will notice...

Good luck.

/ Magnus

Sent by Cisco Support technique iPhone App

TMS 14.1 upgrade error

Hey all,.

I was running MSD 14.1 Beta (yes I am part of the EFT) with PE and everything worked fine. I decided to upgrade to final v14.1 TMS today and now TMS will not talk about PE more.

I see the following over and over again in the log file - error message tmsagentproxy.txt:

2012-12-19 10:13:41, 397 [7] WARN Tandberg.TMS.Framework.Proxy.ReverseProxy - lack of demand: http://localhost:8788 / dr/groups/id/b8e3d61c-8567-477b-921b-2cbbe8c181a3

2012-12-19 10:13:41, 397 [7] ERROR Tandberg.TMS.Framework.Proxy.ReverseProxy -.

System.Net.WebException: The remote server returned an error: (503) server unavailable.

to System.Net.HttpWebRequest.GetResponse)

at Tandberg.TMS.Framework.Proxy.ReverseProxy.ProcessRequest (HttpContext httpContext, dictionary 2 proxyRequestHeaders)

The TMSAgent service runs & so is the TMSPE service. Help, please

Thank you

Justin

Ok

I think I got this one. In this case you see this error because the fact that you named on. You should verify that the named pipes are disabled and TCP ip is enabled (it must be enabled as a Protocol as well (there are two places to enable TCP/IP in SQL Setup))

The surest way to success is to download the patch:

http://www.Microsoft.com/en-US/Download/details.aspx?ID=963

Discover this error here:

Windows Server if using the Protocol of pipes for SQL database connection, the following security

Windows Server updates/patches are required:

n Windows Server 2003: http://support.microsoft.com/kb/958687

n Windows Server 2008 R2: http://support.microsoft.com/kb/2194664 and

http://support.Microsoft.com/kb/2194664

Note that the default connection protocol is TCP/IP. If this Protocol is used, no patches are

Mandatory.

What I lived, is that even if you enable TCP/IP only and not using named pipes, I always got this error. More secure is to install the hotfix, restart and you should have a moment of "this is" hehe (I hope).

/ Magnus

Upgrade behind firewall settings against TMS

Hello

We have hundreds of endpoints at home on the Internet. (E20, 1700MXP, EX etc.). All are now in need of a software upgrade.

I know TMS connection could not be established for the endpoints behind the firewall.

Thus, we have planned for the upgrade manually.

But I still want to check, is it a way automate this either through the software upgrade option MSDS or any other option.

Any practical solution is appreciated.

Best regards / / Rio

From what I remember, because TMS does not have direct access to the endpoints to trigger the upgrade. TMS tells endpoints at the start when they contact TMS if they have an update on hold, indicating then endpoints to start to download the update and install it. If endpoints are configured in the connection settings in MSD to be behind the firewall, that TMS won't know if you are planning of these units go through a software update, it will delay the schedule until it receives feedback from start from the endpoint to initiate the upgrade process.

The upgrade of control VCS v7.2.2 to 8.1

Happy new year!

I saw the 8.1 release notes

"Before you upgrade to X 8 or later, if you use Agent TMS (legacy mode) for commissioning you must first migrate from Extension Cisco TelePresence Management Suite Provisioning"

In our VCS, I have the alarm - "Configuration warning - VCS runs in a legacy of the Agent mode TMS;" It is recommended to switch your system to use another mode.

I guess this VCS was used with an MSD, but now we do not have a.

How can I get rid of this alarm and upgrade to 8.1 VCS?

I found that this configuration is the config FindMe, but we have no option to FindMe key now and he is not active.

I hope that I have explained the problem as clear as possible.

Best regards

Kiril

You can do a factory reset after you be logged in as root, however, he will wipe away everything, including details of intellectual property.

Your best option is to contact TAC, explain what you want to do and what has kept the data you need and ask them to arrange a re-flash to the system via USB key. (In your case, it seems that you can simply remove the key from the commissioning, however, you should also check that the details of external management have been erased.)

Edit: See your last post it looks a lot like a factory reset is in order, it will recreate the image on the system and clean the database as well, but like I said above, contact TAC for a re-USB flash file.

/Jens

Please note the answers and score the questions as "answered" as appropriate.

Upgrading from 2.3.1 to 3.02 with TMS 14.1.1 TMSXE

Hi all

I ahev a general questions about the Migration of TMSXE 2.3.1 to 3.02 with Exchange 2003.

Is there something to do? or might be a risk that I am loose all my calendar on the Exchange entry?

It is also possible to upgrade to 3.02 in way tracking:

1 detach the room (on 2003) mailbox-> is no longer to synchronize the calendar in the TMS

2 uninstall the TMSXE 2.3.1

3. now I'm clearly all booking resource on MSDS

4. move / convert mailboxes to room mailbox to Exchange 2010

5. installation TMSXE 3.02

6. installation and configuration TMSXE 3.02 as New Installation

7 configure the VC system with the associated mailbox room (Exchange 2010)

Now the existing calendar entry are synchronously with TMS should beo OK.

Any input appreciated for my questions.

Best regards

Georg

Hello

performing migration of 2.3.1 is possible and the process must be documented in the installation guide for TMSXE:

http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/tmsxe/Install_Guide/Cisco_TMSXE_install_guide_3-0.PDF

/ Magnus

Upgrade TMS from 14.5 to 15

Hi all

Do we need to run scripts (such as mensioned in the release notes for TMS 14.6.X) or any other manipulation of data or controls to be performed on the TMSNG database before the upgrade of TMS version 14.5 to TMS version 15.0) for deployment on a large scale of MSDS.

Intend to upgrade to version 15.0 of Cisco TelePresence Management Suite.

Endpoints in TMS lol = approximately 4700

DB size 50000 MB

Currect version 14, 5

Apprecitae comments

Deva

I recently made this upgrade (from 14.5.0 15.0). Any additional scripts should be executed before the upgrade.

Only thing to note is the CSCuv40676bug. You may need to purge some data from your database and turn off the automatic update of the controls manually.

Wayne
--
Remember the frequency responses and mark your question as answered as appropriate.

Upgradeing TMS using TMSPE

What is the process of upgrading of TMS which currently uses the TMSPE? I know with TMS Agent Legacy, you had to Devil replication with VCS, but I'm not familiar with TMSPE at the moment and how to upgrade of MSDS.

Simply upgrade the tms regularly according to the documentation. No need to turn off the mark.

/ Magnus

Sent by Cisco Support technique iPhone App

No CDR MCU logs on MSDS

Hey cisco-ster!

I have 2 simple questions about interoperability TMS (14.3.2).

(1) when it comes to Reporting-call detail Records-MCU, I couldn't see all the folders on the chart.

Even if the MCU is properly registered on MCU (4.1), the records do not show on this page. Also, I could see the proceedings of each saved settings.

(2) with the logs of packet loss on the MSDS report category, I couldn't see newspapers of the MXP endpoint C-series (TC6).

I missed some configuration? or both work as designed?

I'd appreciate a response to this topic!

Thank you
```
Kjetil Ree wrote:
Paul Changwon Choi wrote:
1) When it comes to Reporting-Call Detail Records-MCU, I couldn't see any records on the graph.
Even though the MCU is correctly registered on MCU(4.1), the records don't show in that page. Also I could see the records of every registered endpoints.
MCU software 4.1 is quite old (2010?), so we haven't tested it systematically with TMS 14.3.2. Would upgrading to 4.4 be an option?
```
I've done some research more and asynchronous bridge of TMS CDR mechanism requires MCU 4.2 and later. I highly recommend upgrading your software MCU.

If upgrading is not an option, check that the receiver of the feedback is set that correctly on the MCU and then create a network trace to watch how TMS responds to feedback. TMS always responds with a 200 OK? Whatever it be recorded in the log-web - TMS public.txt?

Kjetil-

TMS must be upgraded before TMSXE?

Hi team,

I don't know if I should post this question here, but I'm running MSD 14.4.0 and TMSXE 4.0 and want to update both. I want to upgrade the 14.6.2 TMS and the TMSXE to 4.1, can someone tell me what I should be upgraded first. I took a glance at the following link and it shows that the TMSXE should be the first. I'm what some confused because the other told me that the TMS must be first of all, if someone can check, thanks. P14

http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/TMS...

Hello

According to the TMSXE deployment guide (page 24)

http://www.Cisco.com/c/dam/en/us/TD/docs/Telepresence/infrastructure/TMS...

You must also pass to the required version of the Cisco MSDS before beginning any installation or upgrade of Cisco TMSXE.

Manish

-Does the rate of useful messages-

upgrade 11i - step: apply the latest patches of product (required)

Hello

I'm in the process of upgrading 11.5.9 (DB 9.2.0.4) to 12.1.1 (DB 10.2.0.5).

As part of the upgrade steps in the document entitled * "Oracle® E-Business Suite Upgrade Guide Release 11i to 12.1.1 Ref. / E16342-04 / August 2010" *, I was directed to apply the last product rivierra. Chapter 3, article 5.

I downloaded the latest version of the Oracle patchsets.sh and it ran with the following parameters:

patchsets.sh connect = apps / < apps_password > available = metalink

This tool has generated a bunch of reports including one called "Report.txt" and "Report_R12.txt".

Many of these patches should I download and ask to be able to continue the update?

An excerpt from "Report.txt":

=============================================================================
        Report Generated: Fri Sep 16 15:34:12 EDT 2011               Tool Version:  4.52
  Patchsets List Updated: Sep 15 22:30
              Machine/OS: Linux xxxxxxxxxxxxxxxxxxxx 2.6.9-101.ELlargesmp #1 SMP Fri May 27 19:07:07 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
                  Domain: 
         applptch Source: Patch.csv
   Version from APPLPTCH: 12.1.1
                Database: PROD
       Limited Report to: APPLFULL and APPLSHAR products
                APPLFULL: AK ALR AP AR AS AX AZ BNE CE CHV EC ECX EDR FA FND FRM FV GHR GL GMS HZ IBY ICX IGI IGW ITG JTF JTM PA PER PN PO PQH PSA PSB PSP RG SSP 
                APPLSHAR: AD AMV ASO AU BEN BOM CRP CS CUA DT ENG FF INV MFG MRP ONT PAY QA QP SHT WIP XLA 
         Pseudo Products:  ADO AHL AME AML AMS AMW ASF ASG ASL ASN ASP AST BIC BIL BIM BIS BIV BIX BPA BSC CAC CCT CDR CLA CLE CLJ CLL CLN CN CSC CSD CSE CSF CSI CSK CSL CSM CSP CSR CSZ CTB CUG CZ DDD DDR DNA DOM DPP EAM EDW EGO ENI EWS FEM FII FLM FPA FTE FTP FUN FWK GCS GHG GMA GMD GME GMF GMI GML GMO GMP GR HCP HCT HRI HXT IA IBC IBE IBU IBW IEB IEC IEM IEO IES IEU IEX IGP IGR IGS IMC INL IPA IPM IRC ISC ITA ITM IZU JA JAI JE JG JL JMF JTA JTH JTO JTT JTY LNS MSC MSD MSE MSO MSR MST MTH MWA OAM OCM OE OIE OIR OKC OKE OKI OKL OKS OKX OPI OTA OWF OZF PFT PJB PJC PJF PJI PJL PJM PJR PJT PMI POA POM PON POS PQP PRP PV QOT QPR QRM RCI RLM RRS TXK UMX VEA WMS WPS WSH WSM XDO XDP XLE XNB XNP XTR ZPB ZX
              Written By: Oracle Support, SSANDREW
                 WARNING: DOWNLOAD CHANGING NOVEMBER 3rd, 2006
         Program Updates: ftp://ftp.oracle.com/support/outgoing/PATCHSET_COMPARE_TOOL
      Download Patchsets: Go to link below or click on Patches
     http://metalink.oracle.com/metalink/plsql/dis_download.startup
=============================================================================

Applied Patchsets that Match ARU:
FAMILY PACKS
Prod      Patchset             Bug     RELEASED Release Status      Distribution
=======================================================================================
atg_pf    R12.ATG_PF.A.1      5907545 07/04/15 23:44:46 Checkin Released     Not_Distributed                            
atg_pf    R12.ATG_PF.A.2      5917344 07/07/13 05:48:57 Checkin Released     Not_Distributed                            
atg_pf    R12.ATG_PF.A.3      6077669 07/10/14 21:48:17 Checkin Released     Not_Distributed                            
atg_pf    R12.ATG_PF.A        4461237 07/01/18 17:08:25 Checkin Released     Not_Distributed                            
atg_pf    R12.ATG_PF.A.4      6272680 08/01/13 09:10:12 Checkin Released     By_Metalink                                
atg_pf    R12.ATG_PF.B.1      7307198 09/04/07 22:45:29 Checkin Released     Not_Distributed                            
.
.
.

APPLIED PATCHSETS
Prod      Patchset             Bug     RELEASED Release Status      Distribution
=======================================================================================
ado       R12.ADO.B.1         7460276 09/04/07 22:19:25 Checkin Released     Not_Distributed                            
ado       R12.ADO.B           6867824 08/08/11 22:59:18 Checkin Released     Not_Distributed                            
ad        R12.AD.A.1          5905728 07/04/13 13:11:10 Checkin Released     Not_Distributed                            
ad        R12.AD.A.2          6014659 07/07/13 05:30:06 Checkin Released     Not_Distributed                            
ad        R12.AD.A.3          6272715 07/10/14 17:33:24 Checkin Released     Not_Distributed                            
ad        R12.AD.A            4502962 07/01/18 17:08:25 Checkin Released     By_Metalink                                
ad        R12.AD.A.4          6510214 08/01/13 07:38:00 Checkin Released     By_Metalink                                
.
.
.

The Most Recent Release Family Packs on Metalink(Not Included Above) are: 
=======================================================================================
atg_pf    R12.ATG_PF.A.6      7237006 08/11/05 20:30:52 Checkin Released     By_Metalink                                
atg_pf    R12.ATG_PF.B.2      7651091 09/12/16 08:03:30 Checkin Released     By_Metalink                                
atg_pf    R12.ATG_PF.B.3      8919491 10/07/08 01:40:33 Checkin Released     By_Metalink                                
cc_pf     R12.CC_PF.A.6       7291073 08/11/06 03:57:36 Checkin Released     By_Metalink                                
cc_pf     R12.CC_PF.B.2       8522000 09/12/17 01:08:48 Checkin Released     By_Metalink                                
.
.
.

The Most Recent Release Patchsets on Metalink(Not Included Above) are: 
=======================================================================================
ad        R12.AD.A.6          7305220 08/11/05 11:14:22 Checkin Released     By_Metalink                                
ad        R12.AD.B.2          8502056 09/12/16 06:44:40 Checkin Released     By_Metalink                                
ad        R12.AD.B.3          9239089 10/07/07 14:22:15 Checkin Released     By_Metalink                                
cdr       R12.CDR.A          10161040 11/05/11 08:39:23 Checkin Released     By_Metalink                                
cla       R12.CLA.B           8506229 09/06/30 23:13:11 Checkin Released     By_Metalink                                
.
.
.

Base Patchset List for 12.1.1 included below: 
=============================================================================
7461070 - R12.AD.B.1 ad 10-APR-09 Checkin Released By_Metalink 
6665350 - R12.AD.B ad 13-AUG-08 Checkin Released Not_Distributed 
7458155 - R12.AD.B.1 ad 08-APR-09 Checkin Released Not_Distributed

Thank you
Sinan

Sinan,

I guess I'm not sure if families and patchsets packs can be substitutes for each other.

Sorry, but I'm really confused with your answers.

You're talking about what a family pack?

What patchsets you speak?

For both, please mention the name of patch and number.

Is there a document MOS you can direct me to learn more about these two types of patches?

See the links following/documents.

Note: the 457566,1 - patch FAQ for version 11i Oracle Applications
Note: the 459156,1 - patch FAQ for release 12 Oracle Applications
Note: the 174436,1 - patch FAQ Oracle Applications

Maintain all Documentation Oracle Applications
http://www.Oracle.com/technology/documentation/applications.html

Products and families and Versions - Oh, my!
http://blogs.Oracle.com/stevenChan/2009/04/products_and_families_and_vers.html

And finally, I will then need to apply all the packs families and patchsets listed as two sections in the report above (completely at the top)?

Depends, you can find some of the patchsets included in family packs and in this case, you do not have to apply it-when you find the number of patch via MOS, it must list all patches which include this fix.

Thank you
Hussein

Upgrade MSDS

Similar Questions

Maybe you are looking for