Make sure that you are logged in during the installation with an account
(preferably a domain account, based on the preconfigured stack installer notes)
that is in the local Administrators group, and has explicit permissions to the
directories that you are installing in. Windows Server 2008 R2 is like Windows
7 (and Windows 2008 like Vista), notorious for having problems with permissions
where the logged in account can have no ability to write files or update the
registry when an installer running under that account needs to do that. Some
people report having to run the installer as an admin (right-click Run as
administrator) but that just means that you may have permission problems later,
after the install, and changing something in an AR Form may fail to update a
cfg file unless the AR Server service account has permission to write to the
file system.
On my two 7.6.03 systems upgraded from 7.5.00.006 (and the third one that is
actually upgrading Atrium Core as I write), there are four copies of the
arimportcmd.exe present (different dates but all 2010). This is on BOTH
Windows Server 2003 x64 and Windows Server 2008 R2 x64.
D:\Program Files (x86)\BMC Software\ARSystem\ arimportcmd.exe
D:\Program Files (x86)\BMC Software\ARSystem\approval\bin\ arimportcmd.exe
D:\Program Files (x86)\BMC Software\BMC Service Level Management\rik\
arimportcmd.exe
D:\Program Files (x86)\BMC Software\BMC Service Level Management\rik\upgrade\
arimportcmd.exe
Other problems with the Atrium Core installer:
On any OS – the Atrium Core installer has problems with existing records from
7.6.00 in the AIS:Global Preferences form
On the one I am doing this morning, there were already three
entries in the form from previous installs, the first with the server short
name (alias), then two more with the server FQDN, all for port 1825 and ais.
The installer refused to run until I removed the one with short name so that
the FIRST record in the form was one with the FQDN. On my 2008 R2 server on a
weird VMware host, I had to add the IP address instead of the server name when
patching Atrium 7.6.00.001 to 002, then had to add the short name (alias) when
I upgraded to 7.6.03. Basically, whatever the installer says it wants to see
(short name, FQDN, IP address) in the AIS:Global Preferences form, you have to
make the FIRST entry in that form match the value indicated, or it won’t run.
Apparently it has some sort of problem resolving the name of the server that it
is running on, and you have to provide whatever it has picked in the data.
Only one of the three servers I have upgraded from 7.5/7.6 (on 2003) has NOT
hung up on the values in the AIS:Global Preferences form.
On 2008 R2 but not 2003 server(s)
On a system where the 32-bit ARS 7.5 has been upgraded to
64-bit ARS 7.6.03, the Atrium Core installer is unable to restart the AR Server
services properly and the installation hangs.
Had to manually kill the process (kill the 32-bit ones too) in
Task Manager then restart the service before the Atrium installer could go on
The Atrium Core installer restarts the AR Server as many as 4
times during an upgrade!
This is on a VM, and is NOT in a domain due to being on a weird
private network, and had issues when installing 7.5 / 7.6, so this problem may
be isolated to this machine; it’s the only 2008 host I have left – I put my
other 2008 servers all back on 2003 because of all the permissions issues that
kept cropping up.
The Atrium Core 7.6.03 upgrade on my pre-production 2003 server just completed
successfully, so it’s time to go look at the logs.
Christopher Strauss, Ph.D.
Call Tracking Administration Manager
University of North Texas Computing & IT Center
http://itsm.unt.edu/
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Mahendra Mahalkar
Sent: Thursday, October 07, 2010 9:04 AM
To: [email protected]
Subject: CMDB 7.6.03 installation error
**
Hi All,
I installed ARS 7.6.03 successfully on Windows 2008 64 bit, MS SQL 2005, but
CMDB 7.6.03 installation is failed with rpc program not registered (ARERR 90)
in arerror.log, whenever the installer tries to import BMC%CMDB.def from
workflow directory through rik command, this error is ocurring. If I run this
command through command prompt it import the def properly but throws an error
of not finding arimportcmd.exe. Where should I find this arimportcmd.exe? So
all arx import are failing at that time. Again I import all the arx files
through Dataimport tool except cmdbroles-uid.arx as it throws an error of
required field (Application Name)could not be null. What should be correct
application name ? Also does anyone know any regisrty creation at the time of
Atrium Core installation? The same above happening for AIE installation also.
Need help.
Mahendra
_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_
