Problem Description:

I am installing SAP Web Application Server 6.20 on the SAPDB Database
version 7.30.  Upon completing the installation, I started installing
the BASIS Support Packages in order to patch the system to the most
current support pack.  When installing support pack number 14 the SAP
system froze and stopped processing the transaction.  Normally I could
open a new session and run a particular transaction that would allow
me to cancel the frozen operation; however when I tried to open
another session (with the SAP front-end gui) and log in, the system
completely froze and went into a "dialog queue standstill".  The
server itself is not frozen and can be shut down and restarted, but
the SAP system will not get past the "yellow" state and start up into
"green", even after stopping and starting the SAP system several times
using the Microsoft Management Console.  I can not log in through the
front-end while the system is in this state.

--------------------------------------------
Troubleshooting techniques that I have tried:

(1) I tried to update SAP DB with the latest patch set that has been
released.  When trying to update the database, I recieved an error and
the upgrade process cancels "abnormally".  The error is as follows:

-24988,ERR_SQL: sql error
500,Message not available

When I searched for notes relating to this error on the SAP Service
Marketplace I found one that looked promising.  It said the following:

?The data that the DBMServer uses to check the user data of the users
'control' and 'superdba' is entered in the
<IndepDataPath>/config/<SID>.cfg file. If this file does not contain
any entries, the database cannot reach the status 'WARM'.?

I tried following the solution that was provided, however it did not
work.  During the process (which involves logging into the database
through command prompt) I received and error saying that the database
was not started.  I cannot figure out how to start the database.

(2)   I created a developer trace for the "work processes" in my SAP
System.  All of the work processes are ending after about 30 seconds
with one error.  The MMC says that they never fully started.  The
error that I am receiving according to the developer trace is as
follows:

*** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   672]
*** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event
BEFORE_DUMP failed [thxxtool3.c  238]
Entering ThSetStatError
Entering ThReadDetachMode
call ThrShutDown (1)...
***LOG Q02=> wp_halt, WPStop (Workproc 0 880) [dpnttool.c   356]

I searched the SAP Service Marketplace for a note relating to the
error and found three notes that look very similar to the problem that
I am having (only as far as the database update is concerned, not the
dialog queue standstill).  Two of the notes described adding the
database to the Windows environment variables; however they were
geared towards a system running Oracle, not SAP DB.  I have not tried
adding anything extra to the environment variable list, except for my
JAVA_HOME which was done before the installation.  I suppose that I
could try adding a few SAPDB directories to my environment variables
list, however I do not know what format is needed, and what name to
give the environment variable; as it's different from the name that
would be given to an Oracle environment variable.

The other note that I found mentioned upgrading the SAP system kernal.
 I tried this and there was no difference.  I think that the kernal is
not supposed to be updated until a certain support pack has already
been loaded into the system, and this can only be done through the
front-end, so I'm a bit stuck.  That may be why the kernal update did
not work.

--------------------------------------------
What I need:

I need for the SAP system to start up into ?green? state.  I need to
be able to log into the system from the front-end gui in order to make
the system productive.

--------------------------------------------
What I would like:

I would like to find out why the problem is happening, and a good
method of preventing the problem in the future.

Thank you very much for looking at my question.