[cisco-voip] Upgrade CCM 3.3(3)->3.3(4) fails

[Dietmar]

Upgrade assistant 3.3.4c did not find a fault and completed successfully. I 
will check the given directories for logfiles tomorrow.


Thanks for your help
  Dietmar


> Before too much troubleshooting have you run the Upgrade Assistant to
> make sure system is ready for upgrade?
> http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr-33
>
> If yes, then we really need to get a look at the log files to see why
> upgrade failed.
>
> 1. C:\*.log
> 2. C:\*.txt
> 3. C:\Winnt\sti*.*
> 4. C:\dcdsrvr\log\*.*
> 5. C:\Install\DBInstall\*.*
> 6. C:\Program Files\Common Files\Cisco\Logs\*.*
>
> /Wes
>
> On Apr 9, 2006, at 5:29 AM, Dietmar wrote:
>
> I have tried the direct upgrade last week but it failed, too. My next
> trial
> was the "step by step upgrade".
>
> The log of the installer looks like this:
> 04/08/2006 19:10:09.294(W) "C:\CCMTmp\CCM\Setup.exe" -s -f1"C:\CCM
> \CCM\CCM_Pub.iss" -f2"C:\Program Files\Common Files\Cisco\Logs
> \CCM.log" -SMS
> 04/08/2006 19:10:09.294(W) Calling CreateProcessWithLogonW()
> 04/08/2006 19:10:09.310(W) Successfully launched EXE
> 04/08/2006 19:10:09.310(W) Waiting for process to exit
> 04/08/2006 19:15:44.303(W) Process exited
> 04/08/2006 19:15:44.396(W) Return code: 0
> 04/08/2006 19:15:44.428(W) Stopping "seclogon" service
> 04/08/2006 19:15:46.553(W) Return Code: [0]
> 04/08/2006 19:15:46.553(W) Disabling "seclogon" service
> 04/08/2006 19:15:46.553(W) Return Code: [0]
> 04/08/2006 19:15:46.553(W) <-- MSICreateProcessWithLogon()
> Action 19:15:46: MSICheckForCCMFailure.
> 04/08/2006 19:15:46.568(W) -->MSICheckForCCMFailure()
> 04/08/2006 19:15:46.568(W) Opened registry key
> 04/08/2006 19:15:46.568(W) Retrieved status of CallManager install
> 04/08/2006 19:15:46.568(W) 1
> 04/08/2006 19:15:46.568(W) CallManager install failed
> 04/08/2006 19:15:46.568(W) Notifying user of failure
> Failure occured during the Cisco CallManager installation. Please
> look at the
> Cisco CallManager installation log files for details.  Aborting Cisco
> CallManager install.
> 04/08/2006 19:15:52.881(W) <--MSICheckForCCMFailure()
> Action ended 19:15:52 InstallFinalize. Return value 3.
> Action 19:15:52: Rollback. Rolling back action:
> Action ended 19:15:52: INSTALL. Return value 3.
>
> And the last entry in CCMDBSetup.log:
> 4-8-2006 19:15:12 Migrating data from CCM0300 to CCM0301 database...
>
> I hope to find the reason in C:\Install\DBInstall tomorrow. If not, I
> really
> don't know what to do next...
>
>
> Dietmar
>
> > why wouldn't you just install 4.1(3) on the new server? maybe i'm
> > missing
> > something, but that's what we were planning on doing. but maybe that's
> > gonna change. do you have 4.1(3) install media? ----- Original Message
> > -----
> >   From: Dietmar
> >   To: cisco-voip at puck.nether.net
> >   Sent: Saturday, April 08, 2006 3:59 PM
> >   Subject: [cisco-voip] Upgrade CCM 3.3(3)->3.3(4) fails
> >
> >
> >   Hi,
> >
> >   I want to upgrade CCM from 3.3(3)sr4 to 4.1(3) with hardware
> > replacement.
> > What I tried is the following:
> >
> >   Old hardware:
> >   - Install BARS 4.0.9 and do backup
> >
> >   New hardware:
> >   - Install OS 2000.4.1a (on HP DL320-G3)
> >   - Install 2000.4.1sr5
> >   - Install CCM 3.3(3)
> >   - Install CCM 3.3(3)sr4a
> >   - Install BARS 4.0.9 and do restore
> >
> >   Up to this point, everything is okay and 3.3(3) is running without
> > problems.
> >
> >   Unfortunately, the next upgrade with ciscocm-ffu.3-3-4.exe fails.
> > Last
> > line of CCMDBSetup.log:
> >   4-8-2006 19:15:12 Migrating data from CCM0300 to CCM0301 database...
> >
> >   Is my upgrade procedure okay? Where can I get more information
> > about the
> >   reason why the upgrade failed?
> >
> >
> >   Thanks,
> >     Dietmar
> >
> >   --
> >   E-Mail: db7td at gmx.de
> >   _______________________________________________
> >   cisco-voip mailing list
> >   cisco-voip at puck.nether.net
> >   https://puck.nether.net/mailman/listinfo/cisco-voip

-- 
E-Mail: db7td at gmx.de