Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Some problems upgrading from 2.4.0.120 to 2.4.6

Due to so many issues (e.g. telophony service terminating unexpectedly) with older versions of Unity and CM we forced to upgrade Unity from 2.4.0.120 to 2.4.6, AvCiscoTSP 1.0.0.21 to 1.0.0.28 and CM from 3.02d to 3.08. (That made for one helluva of a stressful Saturday but I digress). <br><br>We started with the call managers and that went without a hitch. Then we had to tackle Unity. Based on a past experience upgrading from 2.3 to 2.4 where the server got trashed the day before it was to go into production, I had alot of trepidation about upgrading Unity. Anyway, we proceeded to slap in the disk and ran setup.exe. We chose intalling/upgrading unity and entered our license key etc. Everything was humming along fine until we were prompted" "Do you want to a)Create a new Unity server b)Install Unity into an existing site." There was a note along with that explaining that if you chose to install Unity into an existing site this was for simple failover. None of the previous questions had caused me any hesitation but this one did. I knew that we did not need simple failove because this is the only Unity server we currently have so I chose "install new server". In retrospect this was the wrong move. I should have got on the horn to TAC. Anyway the setup proceeded and seemed to be going fine until a window popped up "setup could not configure default settings do you wish to continue and configure these setting manually" That is when I got really angry becasue I thought for sure that Unity just got trashed either from the upgrade process or some wrong choice I made. At this point I did call TAC and spoke to Alex. He din't understand why I was prompted to Create a unity server or add it to an existing site. He was afraid I had chosen to do a complete install of Unity. There was nothing to do but to complete the installation and reboot Unity. That was 10 minutes of pure anxiety but hallelujah, Unity came up and all of our subscribers were still there!!!!!! We installed the new AvCiscoTSP and made some test calls and Unity worked fine. However, we discovered that when we tried to retrieve the message, all of our subcriber passwords got changed and we could not figure out to what. That seems to be the only thing that happened during the upgrade. We used your bulk edit utility and set all the passwords to blank and set Unity to prompt users for a new password at their next login. I am going to try and do this upgrade again in the lab and see if I get the same installation prompts again. but here are my points;<br><br>a)if you are upgrading: the installation prompts could be made clearer, especially, where it asks about creating a Unity server or joining a Unity server to an existing site.<br><br>b)the passwords getting changed/corrupted could be a possible bug.<br><br><br>Thanks,<br><br>Vince <br><br>

4 REPLIES
Anonymous
N/A

Re: Some problems upgrading from 2.4.0.120 to 2.4.6

First off, you did do exactly the right thing by creating a new location. You only join a location if there’s another Unity server in the Exchange site that you want to “mirror” in a simple fail over scenario. If you had picked “join an existing location” the next thing you would have been asked to do is pick a location from the directory. This would have come up empty since you don’t have any other Unity servers already installed into that site… in other words, you wouldn’t have gotten too far.

However, this means you were doing a new install! You only get this option when a new installation is going on and not an upgrade. I’m very puzzled as to why the setup chose to do a new install instead of an upgrade. This is also why your database configuration failed… you already HAD a database configured so it saw all the objects it was trying to create in the directory and bailed out. This is ALSO why your passwords are not workable… the password format changed between 2.4.5 and 2.4.6 and unless the migration server is run (done only during an upgrade) they are not reformatted to the new method. 2.4.6 can’t read the old format.

I have no idea how this could happen… the setup process checks the registry and then the hard drive to see if there’s a Unity server already installed. For whatever reason that check must have failed and it went into new install mode…

Can you send us the TEMPU.LOG file created by the setup program to the TAC folks? I’d definitely like it attached to a ticket so we can look into why that happened. I’ve done several upgrades from 2.4.0 and 2.4.5 and have never had this issue. That’s kinda scary…


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

Anonymous
N/A

Re: Some problems upgrading from 2.4.0.120 to 2.4.6

I opened case B234227 and uploaded the TEMPU.LOG file. It has been open over 24 hours and is still not assigned, so I cannot tell you which engineer has it.

Thanks,

Vince

Anonymous
N/A

Re: Some problems upgrading from 2.4.0.120 to 2.4.6

Actually, it is assigned... we're not on DDTS yet so we're having to do things kinda manual for the moment. We're looking at it...


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

New Member

Re: Some problems upgrading from 2.4.0.120 to 2.4.6

Ok. Good.

97
Views
0
Helpful
4
Replies