WebI is Starting, Starting Starting (but never starts)

server administration Web Intelligence 1.x/2.x Servers
1

I agree. Not all of us have that kind of cash…

The easiest process I have found is when upgrading clear the registry of all references to BO. I know no one wants to mess with the registry but it works.

One other thing is to blow away all directories under program files. This makes sure that all programs are the latest and greatest. The install has a problem recognizing newer versions. Keep in mind don’t do this on a master install.

When doing a master install just get rid of all BIN directories. This is where all the dll and exe files get stored.

This works since I just did the 2.5.2 upgrade from 2.5.1.

Sincerely,

Tom Nather
Data Warehouse Group
Penske Logistics
email:tom.nather@penske.com

Listserv Archives (BOB member since 2002-06-25)

2

I’d like to thank everyone that responded to this. As it turned out, removing all of the registry entries (and yes, there were a lot), then reinstalling on a new partition did the trick.

I also agree with Anita below, In an ideal world, yes it would be great just to FDISK, Reinstall NT/Server and start over, but due to the cost structure of test servers, we’ll always have to find more dilligent ways to upgrade our servers because other apps are installed.

Thanks again,

Christopher J. Pohl
Mellon Financial Corporation
Corporate Information Systems Group/SED

From: Nather, Tom (CAP, PTL) [SMTP:Tom.Nather@PENSKE.COM]

I agree. Not all of us have that kind of cash…

The easiest process I have found is when upgrading clear the registry of all
references to BO. I know no one wants to mess with the registry but it works.

One other thing is to blow away all directories under program files. This makes sure that all programs are the latest and greatest. The install has a
problem recognizing newer versions. Keep in mind don’t do this on a master
install.

When doing a master install just get rid of all BIN directories. This is where all the dll and exe files get stored.

This works since I just did the 2.5.2 upgrade from 2.5.1.

Sincerely,

Tom Nather
Data Warehouse Group
Penske Logistics
email:tom.nather@penske.com

At 01:14 PM 4/14/2000 -0700, you wrote:

I would like to suggest that when upgrading a production server, it’s
best
to do a completely fresh installation on a completely different machine
with
a new, fresh installation of NT. Upgrading a production installation of
any
type of server application on Windows NT is just a bad idea, in my experience.

This would be a good idea if one has lots of machines and lots of money. We happen to have a very small user base on WebI, and we have only one machine. We had to beg to borrow an existing server for testing; since
we don’t own it, we can’t wipe it clean. And when we upgrade the production machine, we have to upgrade it in a very short period.

So the bottom line is that starting over may be practical for some folks. Figuring out upgrade workarounds may be more pragmatic for others (like us).

Regards,
Anita Craig

Listserv Archives (BOB member since 2002-06-25)

3

Here’s a few hard-learned lessons from the land of upgrades: If you don’t own your test server, it isn’t a good test server. If you have any other applications installed on your server, it isn’t a good candidate for test OR production.
It only takes 5 minutes to uninstall WebI, then another 5 minutes after the re-install/upgrade to run through the parameters and make sure your custom settings were restored. (usually they are) Deleting registry entries shouldn’t be necessary unless you just un-installed v2.5.0.
Installing a new version of WebI without UNinstalling the old one first leads to chaos and broken clusters.

If anyone has any tips or things to watch out for, let’s hear 'em! ----------
Dan Hughes HughesDS@bp.com Cleveland, Ohio, USA Business Objects Administrator for North America Phone 216-774-7435, Cell 330-573-5600, Pager 877-306-9028 The views expressed in this message are those of the author and are not those of BP Amoco plc or any of its Associated or subsidiary companies.

From: Pohl Christopher J[SMTP:pohl.cj@MELLON.COM]
Sent: Tuesday, April 18, 2000 11:34 AM

I’d like to thank everyone that responded to this. As it turned out, removing all of the registry entries (and yes, there were
a lot), then reinstalling on a new partition did the trick.

I also agree with Anita below, In an ideal world, yes it would be great just
to FDISK, Reinstall NT/Server and start over, but due to the cost structure
of test servers, we’ll always have to find more dilligent ways to upgrade our servers because other apps are installed.

Thanks again,

Christopher J. Pohl
Mellon Financial Corporation

From: Nather, Tom (CAP, PTL) [SMTP:Tom.Nather@PENSKE.COM]

I agree. Not all of us have that kind of cash…

The easiest process I have found is when upgrading clear the registry of all
references to BO. I know no one wants to mess with the registry but it works.

One other thing is to blow away all directories under program files.
This
makes sure that all programs are the latest and greatest. The install
has
a
problem recognizing newer versions. Keep in mind don’t do this on a master
install.

When doing a master install just get rid of all BIN directories. This
is
where all the dll and exe files get stored.

This works since I just did the 2.5.2 upgrade from 2.5.1.

Sincerely,

Tom Nather
Data Warehouse Group
Penske Logistics
email:tom.nather@penske.com

At 01:14 PM 4/14/2000 -0700, you wrote:

I would like to suggest that when upgrading a production server, it’s
best
to do a completely fresh installation on a completely different machine
with
a new, fresh installation of NT. Upgrading a production installation
of
any
type of server application on Windows NT is just a bad idea, in my experience.

This would be a good idea if one has lots of machines and lots of money. We happen to have a very small user base on WebI, and we have
only
one machine. We had to beg to borrow an existing server for testing; since
we don’t own it, we can’t wipe it clean. And when we upgrade the production machine, we have to upgrade it in a very short period.

So the bottom line is that starting over may be practical for some folks. Figuring out upgrade workarounds may be more pragmatic for
others
(like us).

Regards,
Anita Craig

Listserv Archives (BOB member since 2002-06-25)