Voice over IP Cisco - 4.1(3) -> 5.0(4) fails

Author

4.1(3) -> 5.0(4) fails

Andre Beck

2007-02-14, 1:11 pm

Hi,

installing 5.0(4) with instant upgrade from a formerly produced DMA
backup of a 4.1(3) installation runs well almost to the end, when
it breaks with an "unrecoverable internal error". I've found that
I wasn't the first one to hit this wall, as CSCsg90581 matches my
case exactly:

Symptom:

When upgrading a 4.1.3 callmanager system to 5.0.4 it fails with
the following error:

Installation has encountered a unrecoverable internal error.
For further assistance report the following information to your support
provider.
Script "/usr/local/cm/script/5.0.4.1000-1/cm-dbl-install W1 PostInstall
5.0.4.1000-1 "4.1.3" /usr/local/cm/ /common/download/windows/
/common/log/install/install.log" exited with errors (1)

Workaround

None

Well, Ok, but no fix and no workaround? What next?

I've tried to install 5.0(4) with instant update to 5.1(1) so I might
be able to use DMA 5.1 and test whether this works, but it already
fails trying to extract the patch file. Is this supposed to work or
is there really no other path of getting to 5.1 than installing 5.0(4)
with successful DMA import and upgrading to 5.1 later on? What about
installing localization packages, are they necessary for a DMA import
that came from a localized 4.1(3) server?

TIA,
Andre.
--
The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-

Robin Inderberg

2007-02-15, 7:11 am

Hi Andre,

Do you have the install.log? =

I have had the same problem, but with a different version.

"12/13/2006 03:07:42 display_screen|Arguments: "Critial Error" "The install=
ation has encountered a unrecoverable internal error. For further assistanc=
e report the following information to your support provider.

Script "/usr/local/cm/script/5.0.4.2000-1/cm-dbl-install W1 PostInstall 5.=
0.4.2000-1 "4.1.3" /usr/local/cm/ /common/download/windows/ /common/log/ins=
tall/install.log" exited with errors (1)"

Could you send me these files,
C:\CiscoWebs\DMA\Status.htm
C:\CiscoWebs\DMA\bin\*.log
C:\Program Files\Cisco\trace\DBL\installdb*.log

And I can compare our problems, =

Best Regards/Med v=E4nliga h=E4lsningar

Robin Inderberg
robin.inderberg@candidator.se
________________________________________
_____
Telefon:=A0=A0 0322-67 10 00=A0=A0=A0 www.candidator.se
Direkt:=A0=A0=A0 0322-67 10 19=A0=A0=A0 Candidator AB
Mobil:=A0=A0=A0=A0 0733-47 10 19=A0=A0=A0 Malmgatan 15
Fax:=A0=A0=A0=A0=A0=A0 0322-67 10 99=A0=A0=A0 441 39=A0 ALINGS=C5S
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
AF=AF=AF=AF=AF=AF=AF

-----Ursprungligt meddelande-----
Fr=E5n: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.=
nether.net] F=F6r Andre Beck
Skickat: den 14 februari 2007 16:25
Till: cisco-voip@puck.nether.net
=C4mne: [cisco-voip] 4.1(3) -> 5.0(4) fails

Hi,

installing 5.0(4) with instant upgrade from a formerly produced DMA
backup of a 4.1(3) installation runs well almost to the end, when
it breaks with an "unrecoverable internal error". I've found that
I wasn't the first one to hit this wall, as CSCsg90581 matches my
case exactly:

Symptom:

When upgrading a 4.1.3 callmanager system to 5.0.4 it fails with
the following error:

Installation has encountered a unrecoverable internal error.
For further assistance report the following information to your support
provider.
Script "/usr/local/cm/script/5.0.4.1000-1/cm-dbl-install W1 PostInstall
5.0.4.1000-1 "4.1.3" /usr/local/cm/ /common/download/windows/
/common/log/install/install.log" exited with errors (1)

Workaround

None

Well, Ok, but no fix and no workaround? What next?

I've tried to install 5.0(4) with instant update to 5.1(1) so I might
be able to use DMA 5.1 and test whether this works, but it already
fails trying to extract the patch file. Is this supposed to work or
is there really no other path of getting to 5.1 than installing 5.0(4)
with successful DMA import and upgrading to 5.1 later on? What about
installing localization packages, are they necessary for a DMA import
that came from a localized 4.1(3) server?

TIA,
Andre.
-- =

The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Andre Beck

2007-02-15, 7:11 am

Hi Robin,

On Thu, Feb 15, 2007 at 08:18:56AM +0100, Robin Inderberg wrote:
> =

> Do you have the install.log? =

Yep, saved that to an USB stick and groked it up and down without seeing
much that would explain the issues.

> I have had the same problem, but with a different version.
> =

> "12/13/2006 03:07:42 display_screen|Arguments: "Critial Error" "The insta=
llation has encountered a unrecoverable internal error. For further assista=
nce report the following information to your support provider.
> =

> Script "/usr/local/cm/script/5.0.4.2000-1/cm-dbl-install W1 PostInstall =
5.0.4.2000-1 "4.1.3" /usr/local/cm/ /common/download/windows/ /common/log/i=
nstall/install.log" exited with errors (1)"

Aah. The "good" thing about that is now I'm sure it will also happen with
5.0(4a) and all my tries to get the 5.0(4) upgraded to 5.0(4a) before
the DMA load will be in vain...
=

> Could you send me these files,
> C:\CiscoWebs\DMA\Status.htm
> C:\CiscoWebs\DMA\bin\*.log
> C:\Program Files\Cisco\trace\DBL\installdb*.log
> =

> And I can compare our problems, =

I don't have files from the Windows install anymore (blown away) and I
wouldn't like to send the install.log around as it contains weakly
obfuscated passwords which happen to be in use here (not that I wouldn't
trust you, but I'm even in doubt whether I would want to send this file
to TAC, the same way I'm in doubt with IOS password "encryption"). But
let's talk about what in this file or in the DMA might be of interest.
=

First, I had a verification warning during DMA (after I finally came to
the verification phase, I had to use kill.exe on the database service
that hung in "Stopping" state), it was about the description field of
the personal directory containing an umlaut ("Pers=F6nliches Telefonbuch").
It didn't read like it would be a real problem and so I continued. If
you had a similar warning, I'd try to reinstall 4.1(3), eliminate that
warning and DMA again but given that this takes a day of work (mostly
spent waiting, but nonetheless) I'd like to have confidence in the
character set issue beeing involved.

Second, let's have a closer look to the log starting at

02/12/2007 15:06:44 IPM| begin-of-session "Database Installation", 1 items=
|<LVL::Info>
02/12/2007 15:06:44 IPM| ipmDoTimedCommand: cmd=3D"/usr/local/cm/script/=
5.0.4.1000-1/cm-dbl-install W1 PostInstall 5.0.4.1000-1 "4.1.3" /usr/local=
/cm/ /common/download/windows/ /common/log/install/install.log", est(sec)=
=3D2400, max(sec)=3D120
00|<LVL::Debug>
02/12/2007 15:06:44 IPM| begin-of-work: [cmd=3D"/usr/local/cm/script/5.0=
..4.1000-1/cm-dbl-install W1 PostInstall 5.0.4.1000-1 "4.1.3" /usr/local/cm=
/ /common/download/windows/ /common/log/install/install.log"]|<LVL::Info>
02/12/2007 15:06:44 IPM-Child|execlp(/tmp/.ipmJrkOXw) for cmd "/usr/local/c=
m/script/5.0.4.1000-1/cm-dbl-install W1 PostInstall 5.0.4.1000-1 "4.1.3" /=
usr/local/cm/ /common/download/windows/ /common/log/install/install.log"|<L=
VL::Debug>

It's not that much, so I'll include it here:

02/12/2007 15:16:01 IPM|(CAPTURE) Inside doInstallPost...|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Verifying SDI directory [/var/log/active/=
cm/trace/dbl/sdi]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) chown database.ccmbase /var/log/active/cm=
/trace/dbl/sdi|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) chmod 775 /var/log/active/cm/trace/dbl/sd=
i|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside setupPreferences...|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside dbllib.py getDBName(0)...|<LVL::De=
bug>
02/12/2007 15:16:01 IPM|(CAPTURE) Fresh on PUB, hence dbname is defaulted t=
o [ccm0500v0000]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) dbname so far [ccm0500v0000]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) final dbname is [ccm0500v0000]|<LVL::Debu=
g>
02/12/2007 15:16:01 IPM|(CAPTURE) Updating prefs [/usr/local/cm/conf/dbl/pr=
efs.xml]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside getHostName() ....|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside getHostName() ....|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside getHostName() ....|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Updating prefs [/usr/local/cm/conf/dbl/sd=
i/prefs.xml]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Updating prefs [/usr/local/cm/conf/dbnoti=
fy/sdi/prefs.xml]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Updating prefs [/usr/local/conf/cisco_dat=
abase_layer_monitor/output/prefs.xml]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside getPublisherFromInstallPrefs...|<L=
VL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) (odbc setup moved to dbl init)|<LVL::Debu=
g>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside fixSQLLibPaths....|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside fixSQLLibPaths....|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside doInstallPost_installDB ...|<LVL::=
Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside installdb ...|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside dbllib.py getDBName(0)...|<LVL::De=
bug>
02/12/2007 15:16:01 IPM|(CAPTURE) Fresh on PUB, hence dbname is defaulted t=
o [ccm0500v0000]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) dbname so far [ccm0500v0000]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) final dbname is [ccm0500v0000]|<LVL::Debu=
g>
02/12/2007 15:16:01 IPM|(CAPTURE) Start DBMS|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) su -c 'if [ -f /usr/local/cm/db/informix/=
local/ids.env ]; then source /usr/local/cm/db/informix/local/ids.env; fi ; =
oninit' - informix|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) IDSWillStart...ok|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Using port [54320]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/dbf=
uncs.sql.pathed.sql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/mak=
edb.sql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_super /usr/local/cm/db/csv|=
<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) installCsv: rc=3D1|<LVL::Debug>
^^^^
^^^^
It's not obvious, but this might mean a return code of 1, an error. However,
the process continues without much fuzz:

02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_super /usr/local/cm/db/csv/=
newinstall/ApplicationUserDirGroupMap.csv|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_super /usr/local/cm/db/csv/=
newinstall/LDAPFilter.csv|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_super /usr/local/cm/db/csv/=
products|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) xml DSN=3Dccm_super /usr/local/cm/db/xml/=
xml|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) catalog DSN=3Dccm_super AlarmCatalog /usr=
/local/cm/db/xml/alarmcatalog|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) catalog DSN=3Dccm_super TraceCatalog /usr=
/local/cm/db/xml/tracecatalog|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) creating ccmw1 using /usr/local/cm/db/cre=
ate_ccmw1.sql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccmw1 /usr/local/cm/db/create_ccmw1.s=
ql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) installSchema DSN=3Dccm_w1 /usr/local/cm/=
db/exported|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_w1 /usr/local/cm/db/exporte=
d|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) installSchema DSN=3Dccm_w1 /usr/local/cm/=
db/csv/directory|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_w1 /usr/local/cm/db/csv/dir=
ectory|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccmw1 /usr/local/cm/db/sql/dbl/migrat=
ion/conv4to5_auto_fix.sql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Update Statistics DSN=3Dccm_w1|<LVL::Debu=
g>
02/12/2007 15:16:01 IPM|(CAPTURE) Convert Database 4 to 5: DSN=3Dccm_w1 to =
DSN=3Dccm_super|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) UpdateLoadInfo: DSN=3Dccm_super file:/usr=
/local/cm/db/loadinfo/loadinfo.txt|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/dbl=
_common|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/dbl=
|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/dbl=
_gen|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/dbl=
_trig|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/sql/ccm=
|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) sql ccm0500v0000 /usr/local/cm/db/informi=
x/ertools/checksum/checksum.sql|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Cleanup Dblcnqueue DSN=3Dccm_super|<LVL::=
Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Update Statistics DSN=3Dccm_super|<LVL::D=
ebug>
02/12/2007 15:16:01 IPM|(CAPTURE) Failure 1|<LVL::Debug>
^^^^^^^^^

Whoops. The first clear sign of a problem.

Theres just this following:

02/12/2007 15:16:01 IPM|(CAPTURE) /usr/local/cm/bin/dbl start --safe --nopr=
eflight|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) rm -f /tmp/*.txt /tmp/*.log /tmp/*.err /t=
mp/psqlx /tmp/*.bin /tmp/af* /tmp/shmem*|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) Inside getPublisherFromPrefs...|<LVL::Deb=
ug>
02/12/2007 15:16:01 IPM|(CAPTURE) su -l informix -s /bin/sh -c 'source /usr=
/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/l=
ocal/ids.env ; /usr/local/cm/bin/installdb -p 54320 -f W1 /usr/local/cm /co=
mmon/download/windows 5.0.4.1000-1 4.1.3 installdb_w1.log'|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) cm-dbl-install [1]|<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) rc=3D1|<LVL::Debug>
^^^^
Seems my return code theory applies.

02/12/2007 15:16:01 IPM| end-of-work: [cmd=3D"/usr/local/cm/script/5.0.4=
..1000-1/cm-dbl-install W1 PostInstall 5.0.4.1000-1 "4.1.3" /usr/local/cm/ =
/common/download/windows/ /common/log/install/install.log"]|<LVL::Info>
02/12/2007 15:16:01 IPM|Child's return-status =3D 0x00000100|<LVL::Debug>
02/12/2007 15:16:01 IPM|Internal Error, File:ipm.c:1858, Function: ipmDoTim=
edCommand(), Script "/usr/local/cm/script/5.0.4.1000-1/cm-dbl-install W1 P=
ostInstall 5.0.4.1000-1 "4.1.3" /usr/local/cm/ /common/download/windows/ /c=
ommon/log/insta
ll/install.log" exited with errors (1)|<LVL::Critical>
02/12/2007 15:16:03 IPM| end-of-session "Database Installation": 559.280 s=
ecs.|<LVL::Info>
02/12/2007 15:16:03 IPM|Close progress meter ""|<LVL::Info>
02/12/2007 15:16:03 post_install.sh|check_for_critical_error, found /common=
/log/install/critical.log, exiting|<LVL::Error>
02/12/2007 15:16:03 display_screen|Arguments: "Critial Error" "The installa=
tion has encountered a unrecoverable internal error. For further assistance=
report the following information to your support provider.

Script "/usr/local/cm/script/5.0.4.1000-1/cm-dbl-install W1 PostInstall 5.=
0.4.1000-1 "4.1.3" /usr/local/cm/ /common/download/windows/ /common/log/ins=
tall/install.log" exited with errors (1)

The system will now halt.

So it seems the real location of the error is in the import of the CSV
exported DMA data to the database:

02/12/2007 15:16:01 IPM|(CAPTURE) csv DSN=3Dccm_super /usr/local/cm/db/csv|=
<LVL::Debug>
02/12/2007 15:16:01 IPM|(CAPTURE) installCsv: rc=3D1|<LVL::Debug>

Is it the same for you? The strange point is that /usr/local/cm/db/csv
obviously is a directory and the above might not be an error at all,
as the installation continues to import CSVs from below this directory
later...

TIA,
Andre.
-- =

The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-

Andre Beck

2007-02-15, 7:11 am

Re Robin,

On Thu, Feb 15, 2007 at 10:11:41AM +0100, Andre Beck wrote:[vbcol=seagreen]
> On Thu, Feb 15, 2007 at 08:18:56AM +0100, Robin Inderberg wrote:

Argh, silly me. I just found the /var/log/active/cm/trace/dbl/sdi
directory within the error dump tar, and within it, installdb_w1.log.err
seems to be what went wrong in the import. Everything in there is
related to an MGCP gateway which I don't even use any longer, so I'll
rehop over 4.1(3), eliminating this gateway (and the umlaut) and retry
the DMA. I'll let the list know of what I find out.

BTW, error lines look like:

02/12/2007 15:08:17.733 installdb|*ERROR* Error executing "Insert into GatewayLayout ( enum, tkProduct, lev1Header, lev2Header, slotPosition, tkMGCPSlotModule, tkMGCPVic, endPointFormatString ) values (30269, 30013, 'Module in Slot 1', 'Subunit', 1, 18,
34, 'S[slot]/DS1-[port]' )": [Informix][Informix ODBC Driver][Informix]Missing key in referenced table for referential constraint (informix.tk_gatewaylayout_tkproduct).|

Thanks for pointing me in the right direction, I'm getting a better feeling
of beeing able to overcome this catch22.

Andre.
--
The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-

Ryan O'Connell

2007-06-23, 1:11 pm

Did you ever get this fixed, having a similar problem upgrading from 4.1(3)=
to 5.1.1b

06/19/2007 18:02:14 post_install.sh|check_for_critical_error, error found w=
ith return code 127, exiting|<LVL::Error>
06/19/2007 18:02:14 display_screen|Arguments: "Critical Error" "The install=
ation has encountered a serious internal error. The system will be halted.

-----Original Message-----
From: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.ne=
ther.net] On Behalf Of Robin Inderberg
Sent: Thursday, February 15, 2007 12:19 AM
To: Andre Beck; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] 4.1(3) -> 5.0(4) fails

Hi Andre,

Do you have the install.log? =

I have had the same problem, but with a different version.

"12/13/2006 03:07:42 display_screen|Arguments: "Critial Error" "The install=
ation has encountered a unrecoverable internal error. For further assistanc=
e report the following information to your support provider.

Script "/usr/local/cm/script/5.0.4.2000-1/cm-dbl-install W1 PostInstall 5.=
0.4.2000-1 "4.1.3" /usr/local/cm/ /common/download/windows/ /common/log/ins=
tall/install.log" exited with errors (1)"

Could you send me these files,
C:\CiscoWebs\DMA\Status.htm
C:\CiscoWebs\DMA\bin\*.log
C:\Program Files\Cisco\trace\DBL\installdb*.log

And I can compare our problems, =

Best Regards/Med v=E4nliga h=E4lsningar

Robin Inderberg
robin.inderberg@candidator.se
________________________________________
_____
Telefon:=A0=A0 0322-67 10 00=A0=A0=A0 www.candidator.se
Direkt:=A0=A0=A0 0322-67 10 19=A0=A0=A0 Candidator AB
Mobil:=A0=A0=A0=A0 0733-47 10 19=A0=A0=A0 Malmgatan 15
Fax:=A0=A0=A0=A0=A0=A0 0322-67 10 99=A0=A0=A0 441 39=A0 ALINGS=C5S
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=AF=
AF=AF=AF=AF=AF=AF=AF

-----Ursprungligt meddelande-----
Fr=E5n: cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.=
nether.net] F=F6r Andre Beck
Skickat: den 14 februari 2007 16:25
Till: cisco-voip@puck.nether.net
=C4mne: [cisco-voip] 4.1(3) -> 5.0(4) fails

Hi,

installing 5.0(4) with instant upgrade from a formerly produced DMA
backup of a 4.1(3) installation runs well almost to the end, when
it breaks with an "unrecoverable internal error". I've found that
I wasn't the first one to hit this wall, as CSCsg90581 matches my
case exactly:

Symptom:

When upgrading a 4.1.3 callmanager system to 5.0.4 it fails with
the following error:

Installation has encountered a unrecoverable internal error.
For further assistance report the following information to your support
provider.
Script "/usr/local/cm/script/5.0.4.1000-1/cm-dbl-install W1 PostInstall
5.0.4.1000-1 "4.1.3" /usr/local/cm/ /common/download/windows/
/common/log/install/install.log" exited with errors (1)

Workaround

None

Well, Ok, but no fix and no workaround? What next?

I've tried to install 5.0(4) with instant update to 5.1(1) so I might
be able to use DMA 5.1 and test whether this works, but it already
fails trying to extract the patch file. Is this supposed to work or
is there really no other path of getting to 5.1 than installing 5.0(4)
with successful DMA import and upgrading to 5.1 later on? What about
installing localization packages, are they necessary for a DMA import
that came from a localized 4.1(3) server?

TIA,
Andre.
-- =

The _S_anta _C_laus _O_peration
or "how to turn a complete illusion into a neverending money source"

-> Andre Beck +++ ABP-RIPE +++ IBH Prof. Dr. Horn GmbH, Dresden <-
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Attention:

Privileged/Confidential Information may be contained in this message. Disc=
losure to any person other than the named recipient is unauthorized. If yo=
u are not the intended recipient, please delete all copies of this informat=
ion and kindly notify the sender by reply email. Opinions, conclusions and=
other information in this message that do not relate to the official busin=
ess of UNIS LUMIN Inc. shall be understood as neither given nor endorsed by=
it. UNIS LUMIN Inc. and any of its subsidiaries reserve the right to moni=
tor all e-mail communications through its networks. Thank you.