Hi Michael,
1. As per your dev_w0 logs Maybe your MaxDB software directory is not accessible. Can you make the permission as 777 and try again.Also try to keep the DVD path smaller.
2. Suggest you to put the new kernel in the path /usr/sap/SID/SUM-ehp/abap/exenew and /usr/sap/SID/SUM-ehp/abap/exe and after that restart the SUM tool.
3.Can you please check and attach the dev_disp trace file in the work directory of the shadow instance if there is some issue in starting the dispatcher
Also check shadow instance profiles and make sure that there are no duplicate profiles in the profile
directory. From the SAPup.ECO file, u can find the commands used by the upgrade to start the shadow instance may be u can try to start the shadow instance manually.
4.Check the SAP Note 525677:Problems when starting Shadow Instance.
5.Note 39439 might be helpful to recreate the XUSER entries.
6.Try with the DEFAULT connection for your User YourDomain\SAPServiceSID
Hope this will work i.e.
On Windows, the XUSER entries are stored in the registry. For the operating system users <sid>adm and SAPService<SID>, create the XUSER entries mentioned below. As of MaxDB Version 7.5 and above, an operating system user that has administrator rights can store the XUSER entries for SAPService<SID>. To do this, use the XUSER option '-c'; for example:
xuser -c <domain>\SAPService<SID> ...
Kindly let me know if any of the above Points worked for you.If it worked then please provide the Points for this.
Many Thanks
Ajitabh