Splinters

I dont think OTM supports SP4, try moving back to SP3 and see if that resolves the issue.

Splinters

gwebster

Nortel released an advisory (PAA-2003-0398-Global) last November which outlines support of OTM 1.2, 2.0, 2.01 with Windows 2000 Service Pack 4. It specifically has workarounds for the what appears to be installation issue which you are experiencing. Note that OTM 2.1 fully supports Windows 2000 Service Pack 4.

Machivelli

The first problem you’re having is, NOT READING THE DOCUMENTATION. It clearly states that the version of OTM you’re running is supported on SP3 and below. As with all software, if it doesn’t clearly state that it runs on a certain SP, then it more than likely won’t. Now if you’re serious about installing OTM, the first thing you need to do is back out SP4. Once that’s done re-install (if you’ve already done it) MDAC 2.8. Restart the PC. Install OTM, apply any patches you need. Restart again. Reapply SP4, and you’re good to go. The issue with SP4 is ONLY with the installation. M$ loves to make changes on the fly that interrupt other applications, especially during their installation phase.

Oh and since you’re pissed at Nortel about their software, remember this. Nortel is a VOICE company (been around since 1895 BTW), not a Software company. Trust me, I have my Bachelors in Comp Sci and used to work for them. NOBODY and I mean nobody can keep up with M$ and their daily hotfixes that modify key components. All you can hope to do is react in a timely manor. And no Nortel is usually not one of the groups that hits that target. Cisco has the same problems when it comes to dealing with M$. But hay don’t let me stop you from going with Cisco, they do have cool looking phones. Features and services are seriously lacking, but like I said at least the phones look cool.

Side note – Don’t take the CAPS as me being pissed or yelling. Just stressing a point, a point that 85% of all my calls while I was with ETAS had in common. If I had a dollar for every time a customer or Distributor Tech told me the Documentation was still in it’s cellophane wrapping when I asked them if they had review it, I’d be up there with Bill Gates.

dixiedogger

I must agree on a few points cisco is no better at working with MS than nortel and in general any microsoft product sucks for a telecom operating system. I wish nortel never tried to migrate their mail and call center stuff to it. Meridian mail was rock solid and so was max. I know they were needing updated but did that have to mean going to MS. I did notice the lateset version of Unity express (cisco's vm) is on linux. I hope that is the start of a trend,

telecom116

It won't be if SCO has anything to do with it.

aldon

Geez, relax Machi. Just because Nortel software stinks doesn't mean you need to get bent out of shape. I did read the documentation, and it does NOT say service Pack 3 or less. It just says service pack 3, not greater, not less. I assumed it listed SP 3 because that was most current at time of release. There are other parts of the documentation that specifically say to get the latest hotfixes from windows upfdate site. Nortel needs to write their code so it is not so OS dependent. Our company runs over 500 applications, and we hotfix servers all the time without problems. If you were one of the programmers, then it's your fault that Call Pilot 1.07 and Symposium clients couldn't run with any stability on the same partition of a machine, and it's your fault that Nortel's two flagship products couldn't even communicate. We had to keep buying MerMail modules so that Symposium could do give IVR. Ridiculous. You're right, Nortel is a phone company, and should concentrate on that. I have never seen any telecom app run well on M$, including Cisco. Fortunately for Nortel, I think their CSE call server runs on vxworks.

Machivelli

Better late than never ..


NO I wasn’t a programmer at Nortel, I was ETAS. 3rd level support for MAT/OTM, Remote Office and a host of other apps. So don’t go off blaming me for the way the apps work. As for that, again Nortel is a VOICE company, not a software company. Most everything they have has been purchased or licensed from 3 party vendors. A piss poor model when it comes to support, compatibility (your comm problems with Nortel Apps) or trying to keep up with M$. Take OTM for example, it’s a collection of modules from up to three different companies (more like 2 now). The thing that gets me bent out of shape is the shear level of Ignorance that exists out there. Now granted most of that is do to idiot distributors that don’t bother educating either their staff or their customers. When I was at ETAS I would spend most of my time running damage control by educating end users as the “Real” way things worked with the software and why it was so important to follow installation manuals. Would it be M$ fault if you tried to install Windows XP on an old 486 DX 66 PC with 8 Megs of RAM? Of Course not, the manual tells you exactly what you need to do to install the software successfully.

Oh and your comment about “Running” applications and hot fixing them all the time. The key word is “Running”. Once OTM is “Running” you can hot fix it without problems. It’s the “Installing” that causes problems. Problems that those other 500 applications would more than likely experience if you tried to install them on an SP they were not designed for. Not making software OS dependent? So you’re saying they should develop for Windows, Linux and the others all at the same time? If so you have no clue as to the development cycle of software, and the resources (Money) this would require.

Oh and it Mach … Machi … that’s just wrong!

And I wasn’t bent out of shape; I have to have a 2616 sitting in front of me to get bent out of shape. That way I have something to pound with my fist …

Pip

Ran into the same problem one month ago when migrating OTM 2.0 from a Win2K Server with SP4. The initial installation on the old server was done with SP3 as base. Later version 4 was installed and everything was functioning Ok.

The new server was already installed with SP4 and so this is where the MSI detection for version 2.0 fails. You keep on installing and booting and …

Solution for this problem is upgrading your MSI version before installing OTM.
Latest version of the Windows Installer is 3.0.3790.2538 and can be downloaded from
http://www.microsoft.com/downloads/d...DisplayLang=en