Re: Schema Extend Failure Upgrading from v3.1.3 to v4.02
As a follow-up, we re-ran the Schema Expansion about 30 minutes later from a Terminal Services window (to capture logs) and, to our surprise, it ran successfully. We are puzzled as to what may have caused this to work suddenly. We suspect it is either the fact that more time had passed since the last system restart from the previous upgrade step OR it was because we ran it from Terminal Services. TAC is still reviewing both successful and failed logs but we were able to complete our upgrade after getting past this issue.
Also note that we are utilizing Digital Networking between 2 Unity servers in production which may be a factor as we did not encounter this issue in our Lab test upgrades.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...