I had inconsistent behavior with that... probably back on patch 001.  I am 
testing with 003 now, and will have to test some different scenarios to see if 
it will do a better job of spot maintenance.

The other "exciting feature" I hit (patch 003) was that if you select overwrite 
database (there was an old ARSystem db on the remote SQL Server), the installer 
issued a drop command for the database (normal behavior), and then issued a 
drop command for the domain\user account that I had entered as the SQL Server 
account (Windows authentication to SQL Server), and then it was no longer able 
to connect to the SQL Server using that account (DUH!) to create the new 
ARSystem db.  Support hasn't been able to explain that bizarre behavior yet, 
but it is definitely fatal to your installation.

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:arsl...@arslist.org] On Behalf Of Guillaume Rheault
Sent: Thursday, October 29, 2009 12:39 PM
To: arslist@ARSLIST.ORG
Subject: Re: ARS 7.5 Installer

**

Can't you only select the Email engine, so that is the only thing that gets 
installed?

Guillaume

-----Original Message-----
From: Action Request System discussion list(ARSList) on behalf of strauss
Sent: Thu 10/29/09 1:16 PM
To: arslist@ARSLIST.ORG
Subject: ARS 7.5 Installer

<RANT>

Is it just me, or are any of you having problems with the new ARS 7.5 
monolithic installer?  It is an all or nothing kind of approach that makes 
upgrades and repairs a lot more hazardous and unreliable since you can no 
longer work on just the one problem service (AREmail is the primary culprit 
here) without running an install against the entire ARS system.  In 7.1 and 
earlier we have always had trouble with the AREmail module - it is one of the 
services that seldom upgraded correctly, usually losing its ability to connect 
to MAPI properly and requiring you to uninstall it, wipe all traces of it from 
the file system and registry, and reinstall it.  I haven't figured out any way 
to do that with the monolithic suite installer without "touching" the entire 
installation.  Someone somewhere must have thought that a single suite 
installer would be simpler to work with, but in practice it makes a nightmare 
out of troubleshooting and reinstalling a particular problem service (and 
AREMail after 4.x has always been a "problem" service - witness the open issue 
I have had with our production AREmail system crashing on 7.1 since June 2008, 
still unresolved).  It also means that any run of the installer takes WAY 
longer since you have to go through every dialog even though 90% are irrelevant 
to what you want to do, and reenter passwords all along the way for things you 
didn't need to work on, or now they will STOP working.  The suite installer 
might make sense for a new install of a fresh system - ONCE.  After that, you 
still need individual service uninstall-reinstall capability.

Part of my frustration is from trying to troubleshoot two 7.5 systems, one 
upgraded from 7.1 and one a fresh install, neither of which can successfully 
run the AREmail service and send out mail.

The same complaint applies when working on a web server, but you are generally 
in a more limited environment with only mid-tier and flashboards installed.  
Upgrading the 7.x mid-tier by installer historically trashes your integration 
to crystal reports, making it necessary to uninstall it and install a fresh 
instance in order to get it working again.  The monolithic installer gets in 
the way here too, just not as much (and not as high-risk) because only mid-tier 
and flashboards are typically on the web server.

</RANT>

BTW, the 7.5 installer still prompts for account, password, and domain for 
Email like it always did (5.x, 6.x, 7.0, 7.1), but no longer concatenates 
domain\account to use when creating the Remedy Email Engine service (so it 
fails to do so in our environment).   You have to enter the account in the form 
domain\account in order for the service to get installed - the field for domain 
is now ignored by the installer.  I have reported it as a new 7.5-specific 
defect.

Christopher Strauss, Ph.D.
Call Tracking Administration Manager
University of North Texas Computing & IT Center
http://itsm.unt.edu/

TRYING to achieve environment:
ITSM 7.6.00 (Incident, Problem, Change Management);
Remedy Knowledge Mgmt 7.5.00.001; Service Level Mgmt 7.5.00.001 AIE 7.5.00.003
Kinetic Request 4.4.1, Survey Lite 4.4.1, Calendar Lite 1.2+;
on AR Server, Approval, Assignment, Mid-Tier, and Flashboards 7.5.00.003
on: Win2K8 R2 Ent x64 / SQL Server 2008 x64 Sp1

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
_Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

Reply via email to