callmanager upgrade fails

Answered Question
Mar 2nd, 2010
User Badges:

guys have a cm ver 6.1(1) which wont upgrade, have tried to upgrade to a few diff vers, anyone ever seen this type of error before

Attachment: 
Correct Answer by Aaron Harrison about 7 years 3 months ago

Hi


Good to hear it's sorted out.



Thanks for the rating, BTW ;-)


Aaron

Correct Answer by David Hailey about 7 years 3 months ago

Let's back this up if you don't mind.  You say you have 6.1.1 - so first things first, what version(s) have you tried to upgrade to?  Did you experience this error on the very first attempt?  If so, what was the upgrade path?


How was this system built?  Was this a 4x to 6x upgrade build or was this a fresh 6x build?  Alternately (it could be 5x to 6x).  Give me some details and we'll try to walk this out.


Hailey


Please rate helpful posts!

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Aaron Harrison Wed, 03/03/2010 - 08:13
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hi


Looks like the failure may be time zone related - perhaps try setting your time zone to a different/equivalent one, or back to GMT temporarily whilst you upgrade?


Failing that you would need to collect full logs from RTMT - do a collect files, and grab the Install /Upgrade traces, and DB Installation service traces. Do this once for the 'active' partition, and again for the 'inactive' partition.


Regards


Aaron

mark.carroll Thu, 03/04/2010 - 01:38
User Badges:

hi

thanks, tried that but ti comes back with the same error just different time zone, I changed to GMT so its replaced Eire with GMT but error the same

Aaron Harrison Thu, 03/04/2010 - 01:55
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

OK - so that's the only error I can see on that little screen grab.


You need to do it the hard way (retrieve the logs as described, and analyse them) or raise a case with TAC.


As you've tried different versions, either all Cisco's software is broken, or you have something in your config DB that all of them don't like.


Regards


Aaron


Please rate helpful posts...

Correct Answer
David Hailey Wed, 03/10/2010 - 17:38
User Badges:
  • Purple, 4500 points or more

Let's back this up if you don't mind.  You say you have 6.1.1 - so first things first, what version(s) have you tried to upgrade to?  Did you experience this error on the very first attempt?  If so, what was the upgrade path?


How was this system built?  Was this a 4x to 6x upgrade build or was this a fresh 6x build?  Alternately (it could be 5x to 6x).  Give me some details and we'll try to walk this out.


Hailey


Please rate helpful posts!

mark.carroll Thu, 03/11/2010 - 04:08
User Badges:

actually the fix was just to change the timezone to Los_Angeles

thanks

Correct Answer
Aaron Harrison Thu, 03/11/2010 - 04:27
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hi


Good to hear it's sorted out.



Thanks for the rating, BTW ;-)


Aaron

Aaron Harrison Thu, 03/11/2010 - 04:31
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Much happier, thanks... I don't think I get paid if I don't get rated..

Actions

This Discussion