SAP system is not started during the downtime phase MAIN_NEW

Problem:
------------

We are upgrading to ECC6.0 EHP5 from ECC 6.0 EHP3
I have completed the pre-processing stage successfully. Then I started
the Downtime phase.But after some time in the pahase
MAIN_NEWBAS/STARTSAP_NBAS it gives the below error :
CURRENTPHASE MAIN_NEWBAS/STARTSAP_NBAS
...started at 20120212103622
..times self: 0.030000/0.030000 usr/sys, children 7.170000/3.630000
usr/sys.
..finished at 20120212103654 with status NO SYSTEM START.
# Error message set: 'Process 'startsap' exited with 1,
see '/sapcd/EHP5_Upg/EHPI/abap/log/SAPehpi.ECO' for details
System start failed'
...begin dialogue at 20120212103654

Analysis:
----------------

I checked the log in the work directory and error logs are as follows
sendbox:jepadm 121> pwd
/usr/sap/JEP/ASCS00/work
sendbox:jepadm 122> cat sapstartsrv.log
---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 0, release: "700"
---------------------------------------------------
pid 368814
Sun Feb 12 11:11:13 2012
No halib defined => HA support disabled
Initializing SAPControl Webservice
SapSSLInit failed => https support disabled
Starting WebService thread
Webservice thread started, listening on port 50013
sendbox:jepadm 123>

sendbox:jepadm 81> startsap r3
Checking JEP Database
Database is running
-------------------------------------------
Starting Startup Agent sapstartsrv
OK
Instance Service on host sendbox started
-------------------------------------------
starting SAP Instance ASCS00
Startup-Log is written to /home/jepadm/startsap_ASCS00.log
-------------------------------------------
/usr/sap/JEP/ASCS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start
startup of Instance failed
See /home/jepadm/startsap_ASCS00.log for details

Solution:
------------

The folloiwng error has occured:
----------------------
EXECUTING /usr/sap/JEP/DVEBMGS01/exe/sapcontrol
(/usr/sap/JEP/DVEBMGS01/exe/sapcontrol) -prot NI_HTTP -host sendbox -nr
01 -function StopWait 300 10
12.02.2012 09:01:14
Stop
FAIL: HTTP error, HTTP/1.1 401 Unauthorized
Process with ID 508234 terminated with status 1
BLOCKED SIGNALS: ''

Kindly check these things:
1) is there sapstartsrv process runnin with the profile O.S instance 01
on the server sendbox?
2) If the sapstartsrv is running it should create a stream file in the
/tmp called ".sapstream5<instance number>13", in your case:
/tmp/.sapstream50113
take a look if this file has the right permition, something like that:
srwx 1 <sap>adm sapsys .sapstream50113
What you can do to solve this problem is:
a) you can try restart the sapstartsrv for isntance 01;
(you need make sure that the stream file will be created)
b) you can manually start the instance 01.
Please be informed that sapstartsrv offers 2 authentication models. One
is http basic authentication which requires you to provide user and
password. Additionally it offers a so called trusted connect. On Unix
this is based on a Unix domain socket created by sapstartsrv at startup
(/tmp/.sapstream5??13). Unix startsap / stopsap script tries to use
this trusted connect. When running locally as <sid>adm it should be ableto connect via the Unix domain socket. However if it cannot connect thisway it falls back to http basic authencation. Since startsap/stopsap
never provide user/password to sapcontrol this fallback will not work.
If tursted connect doesn't work one of the following might have
happened:

1) sapstarstrv was not able to create /tmp/.sapstreamXXX, e.g. because
it already exist and is owned by a different user.
2) Someone / something deleted /tmp/.sapstreamXXX after sapstartsrv
had been started (e.g. some automatic cleanup in /tmp ?).
3) sapstartsrv or startsap/stopsap are not executed with the
same <sid>adm user.
Please check these and please also review following notes
1250195 - No UDS available when configuring service/hostname
(please try to set service/hostname as per the note)
927637 - Web service authentication in sapstartsrv as of Release 7.00
877795 - Problems w/ sapstartsrv as of Release 7.00 & 6.40 patch 169
(Please check the 6th point)

Then I compare with a working as follows and rename the below files
cd /tmp
mv .sapstream50113 .sapstream50113.orig
mv .sapstream50013 .sapstream50013.orig
========================================================================================
---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 0, release: "720"
---------------------------------------------------
pid        409892
[Thr 01] Sun Feb 12 18:01:13 2012
No halib defined => HA support disabled
CCMS agent initialization: return code 0.
CCMS agent start: return code 0.
Initializing SAPControl Webservice
Starting AutoRestart thread
AutoRestart thread started
SapSSLInit failed => https support disabled
Starting WebService thread
Webservice thread started, listening on port 50013

srwx------    1 400      sapsys            0 Feb 01 09:45 .sapstream50013
srwx------    1 410      sapsys            0 Feb 01 09:45 /tmp/.sapstream50113
srwx------    1 400      sapsys            0 Feb 01 09:45 /tmp/.sapstream50013

==============================================================================
# cat sapstartsrv.log
---------------------------------------------------
trc file: "sapstartsrv.log", trc level: 0, release: "700"
---------------------------------------------------
pid        2752654
Mon Jan 23 06:28:32 2012
No halib defined => HA support disabled
Initializing SAPControl Webservice
SapSSLInit failed => https support disabled
Starting WebService thread
Webservice thread started, listening on port 50013
Trusted http connect via Unix domain socket '/tmp/.sapstream50013' enabled.

# ls -ltr /tmp/.sapstream50013
srwx------    1 jepadm   sapsys            0 Jan 23 06:28 /tmp/.sapstream50013
# ls -ltr /tmp/.sapstream*
srwx------    1 jepadm   sapsys            0 Jan 23 06:28 /tmp/.sapstream50013
srwx------    1 jepadm   sapsys            0 Jan 23 06:29 /tmp/.sapstream50113

===============================================================================================
and started by sapstart r3 and it got started