A little Advise Please!

From: Duane Arnold (notme@notme.com)
Date: 01/04/03 

From: "Duane Arnold" <notme@notme.com>
Date: Sat, 04 Jan 2003 21:53:51 GMT

The situation is the following:

1) The production Dual 1 Ghz with 1 Gig ram Win 2k Com++ Transaction sever
is down.
2) The development team *test* machine 400 MHz with 256 mb of ram has got
the load.
3) The company has waited 7 years to get this business application up and
running
4) The application has been in production with limited usage two to three
months
5) Middle part of November 2002, team finds out that application was never
in a Transaction mode using the Com++ server.
6) Team gets n-tier application into transaction mode and realizes that the
production 800 MHz with 256 mb machine is not going to cut it.
7) The team has been doing some tweaking with application sub levels Com++
and SQL Server
8) Found that DCOM permissions needed to be set Permission error 70 -- one
sub components exposed this.
9) The application pushout has pushed MDAC 2.6 over top of 2.5 at that Com++
severe and Office 2000 components have been pushed out over Office 97, 97
being the production standards and the Permission error 70 is back on the
entire application and sometimes you get the error and sometimes you don't.
10) Pointing to that Gig Com++ server Pushout person and Systems guy can't
find the problem.
11) Monday after next, the plug is being pulled on the Notrix/Domino
application, which has been inquiry mode only.
12) I don't know somewhere around 10 to 15 thousand users are going to come
at it.

My boss tells me on this past Friday "Duane I need you to get this
application up and running".

I need you to come in Monday with a game plan and procedures to not allow
this to happen again with the development team and work with the System
personnel on "how to secure the production environment" and what to do about
getting a decent backup to the Com++ server.

The two guys are very good who are chasing down this problem that has been
going for week and they have not found it.

I know that Office 2000 has to come out of the application.

The System guy is reluctant to whack the machine unless there is no other
choice. He tells me that may not fix the problem.

A hard decision has to be made by Wednesday, if it's not up and running by
then.

Any advise on trying to locate the problem?
Any advise on finding some documentation on procedures?

All advise is welcomed!

BTW as all this *** was coming down, I was on vacation!

Duane :) 

--
The protection of the machine is a process and is not a given!
Quantcast