Professional Documents
Culture Documents
TG0004en_Ed02
TG0004en_Ed02
02
The troubleshooting guide of "OmniPCX Enterprise PC Installer" application is used to identify the
installation environment and the operating troubles of the software.
1
OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION
CONTENTS
1. PC INSTALLER APPLICATION........................................................3
2. HISTORY......................................................................................3
3. INTRODUCTION ..........................................................................3
1. PC INSTALLER APPLICATION
In order to troubleshoot PC Installer application problems, reading of the "Call Server Installation" in
the technical documentation available on Alcatel Business Partner Web Site
(www.businesspartner.alcatel.com) and on CDROM with the reference 3BH 19918 FR and EN is
highly recommended.
2. HISTORY
Edition 01 : Creation of the Troubleshooting Guide.
Edition 02 : Upgrades with PC Installer v2.17.
3. INTRODUCTION
The troubleshooting guide of "OmniPCX Enterprise PC Installer" application is used to identify the
installation environment and the operating troubles of the software.
Click on OK and validate the automatic start of "Computer Browser" windows service at the end of
software installation; refer to § 5.1.1.
An error message appears when the "OmniPCX Enterprise PC Installer" application starts:
This event can cause a TFTP misfunctioning (timeout) when installing an Appliance Server type of
Call Server on Windows NT4/ 2000/ XP.
Solution
Enable the automatic start and start the "Computer Browser" Windows service.
An error message appears when the "OmniPCX Enterprise PC Installer" application starts:
This event can cause a FTP misfunctioning (timeout) when carrying out a standard installation of a
Call Server.
Solution
• Uninstall, re-install then start a first time the "OmniPCX Enterprise PC Installer" application as
local administrator (and not in a domain).
An error message appears when the "OmniPCX Enterprise PC Installer" application starts:
This event can occur when using two network boards causing a conflict for the application (e.g. a
PCI avm fritz! network board and pcmcia ISDN modem board, or standard IP board and a Wireless
LAN board) and involves the blocking of the application.
Solution
• In network interfaces, disable the board which causes the conflict (e.g. the pcmcia modem or
the Wireless LAN board).
IP address determination
============================
*RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,TOIPRcv,R
cvTO,TOIPRcv,RcvTO,TOIPRcv........
server-name "PC-Install";
option host-name "OXE_1";
filename "/bootp/linux/5.0/alize/startup.txt";
option vendor-encapsulated-options "SD:/dhs3mgr/e1601.fr";
server-name "PC-Install";
option host-name "OXE_1";
Solution
Manage only one IP address in a same sub-network in Advanced TCP/IP settings.
Solution
Check that the PC Server can be reached from Call Server: Launch a ping command from Call
Server on IP address of PC Server.
If the ping failed, check the Ethernet cable (see section 5.1.2.1) et IP addresses of the Call Server
and PC.
Start the "OmniPCX Enterprise PC Installer" application. In the field Installation type, select
the type of installation to Call handling or patch only.
The patch installation on the Call Server is done with swinst and "OmniPCX Enterprise PC Installer"
application.
Use Expert menu/Deliveries installation menu of swinst.
Name the patch with the repertory name on PC server:
For example: /dhs3mgr/f16023g
The installation of the binaries will modify the current installed version
Please, confirm the installation of a new version (y/n, default y):
Check the patch loading with swinst on the V24 configuration port of the Call Server.
NOTE
Loading progress is visible on the "OmniPCX Enterprise PC Installer" application.