[cisco-voip] CCM on Non-MCS

Mon Dec 11 12:12:44 EST 2006

Yes, but you could have a problem with a few corrupted files on the CD...
The CCM4.1(2) distribution was known to be finicky about CD quality.

Then again, this could be a hardware fault on your PC (bad drive, etc...)

I would try the install on VMWare... use ISOs for the CDs...

Jonathan

On 12/11/06, ian.2.warburton at bt.com <ian.2.warburton at bt.com> wrote:
>
>  Jonathan
>
> I did consider that, but the log file showed such a definite statement
> about the call manager failure, where as the Database seems to have
> completed successfully,
>
> regards
>
> Ian
>
>  ------------------------------
> *From:* Jonathan Charles [mailto:jonvoip at gmail.com]
> *Sent:* 11 December 2006 16:59
> *To:* Warburton,I,Ian,JPGRFX C
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] CCM on Non-MCS
>
> Without the registry hack, the CCM installation would barely start, let
> alone get to the second CD.
>
> I think you have a media problem... something isn't happy about the CDs
> you are using...
>
>
>
> Jonathan
>
> On 12/11/06, ian.2.warburton at bt.com <ian.2.warburton at bt.com> wrote:
> >
> >  Guys
> >
> > Wondered if you could help. I am trying to install Call Manager 4.1(2)on
> > a non-MCS machine. I have made the following registry hacks:
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Model]
> > "Hardware"="MCS7835"
> > "Memory"="512"
> > "Speed"="1000"
> > "@"=""
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems\Spirian]
> >
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Spirian\System Info\OS Image]
> > "Version"="2000.2.7"
> >
> > I then installed the 2000.2.7 upgrade and then ran the setup program.
> > Everything looked okay until half way through the second disk, it suddenly
> > bombed out and failed. When I looked at the log file I saw the following
> > output:
> >
> > Action 11:27:24: MSICheckForDCDFailure.
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    Function Started
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    Opened registry key
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    Retrieved status of DCD
> > install
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    0
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    Cisco Directory install
> > succeed
> > 11:27:26: MSIApi.cpp: MSICheckForDCDFailure:    Function Ended
> > Action 11:27:26: InstallODBC. Installing ODBC components
> > Action 11:27:26: StartServices. Starting services
> > Action 11:27:26: MSICreateProcessWithLogon_CCM_PubFresh. Installing
> > Cisco CallManager
> > 12/11/2006 11:27:27.496(W) --> MSICreateProcessWithLogon()
> > 12/11/2006 11:27:27.506(W) GetComputerName computername: WARBNET-9714624
> > 12/11/2006 11:27:27.506(W) Initializing data buffer
> > 12/11/2006 11:27:27.506(W) Retrieving "CustomActionData" property
> > 12/11/2006 11:27:27.506(W) Parsing string into tokens
> > 12/11/2006 11:27:27.506(W) Password: <Hidden>
> > 12/11/2006 11:27:27.516(W) Program : "C:\CCMTmp\CCM\Setup.exe"
> > 12/11/2006 11:27:27.516(W) Params  : -s -f1"C:\CCMTmp\CCM\CCM_Pub.iss"
> > -f2"C:\Program Files\Common Files\Cisco\Logs\CCM.log" -SMS
> >
> > 12/11/2006 11:27:27.516(W) Connecting to SCM
> > 12/11/2006 11:27:27.516(W) Return code: [0]
> > 12/11/2006 11:27:27.516(W) Enabling "seclogon" service
> > 12/11/2006 11:27:28.587(W) Return code: [0]
> > 12/11/2006 11:27:28.587(W) Starting "seclogon" service
> > 12/11/2006 11:27:28.597(W) Return code: [0]
> > 12/11/2006 11:27:43.599(W) Setting startup parameters for EXE
> > 12/11/2006 11:27:43.599(W) Creating command-line string for launching
> > EXE
> > 12/11/2006 11:27:43.599(W) "C:\CCMTmp\CCM\Setup.exe" -s
> > -f1"C:\CCMTmp\CCM\CCM_Pub.iss" -f2"C:\Program Files\Common
> > Files\Cisco\Logs\CCM.log" -SMS
> >
> > 12/11/2006 11:27:43.599(W) Calling CreateProcessWithLogonW()
> > 12/11/2006 11:27:43.709(W) Successfully launched EXE
> > 12/11/2006 11:27:43.709(W) Waiting for process to exit
> > 12/11/2006 11:28:48.933(W) Return code: 0
> > 12/11/2006 11:28:49.043(W) Stopping "seclogon" service
> > 12/11/2006 11:28:51.076(W) Return Code: [0]
> > 12/11/2006 11:28:51.076(W) Disabling "seclogon" service
> > 12/11/2006 11:28:52.218(W) Return Code: [0]
> > 12/11/2006 11:28:52.218(W) <-- MSICreateProcessWithLogon()
> > Action 11:28:52: MSICheckForCCMFailure.
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    Function Started
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    Opened registry key
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    Retrieved status of
> > CallManager install
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    1
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    CallManager install
> > failed.
> > 11:28:54: MSIApi.cpp: MSICheckForCCMFailure:    Message displayed:
> > Failure occured during the Cisco CallManager installation.
> >
> > Please look at the Cisco CallManager installation log files for details.
> > Aborting Cisco CallManager install.
> > 11:30:32: MSIApi.cpp: MSICheckForCCMFailure:    Function Ended
> > Action ended 11:30:32: InstallFinalize. Return value 3.
> > Action 11:30:32: Rollback. Rolling back action:
> > Action ended 11:30:33: INSTALL. Return value 3.
> >
> > I'm not sure however what this relates to. Any help would be appreciated
> >
> > Thanks
> >
> > Ian
> >
> > Ian Warburton CCNP CCIP I Technical Design Authority I BT Global
> > Services I Tel: +44 (0) 7918 039242
> > I E: ian.2.warburton at bt.com I  ***<<****www.bt.com/globalservices** >>*
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061211/f9fab156/attachment-0001.html 