cancel
Showing results for 
Search instead for 
Did you mean: 

Error while upgrading from EP5 SP5 to EP5 SP6

Former Member
0 Kudos

Hi,

While upgrading to EP5 SP6, I got an error "The SCA file deployment failed".

The log file shows the following error:

Log started Wed Apr 13 21:55:06 EST 2005

===========================================================================

21:55:06 INFO: Starting to execute command deploy

21:55:06 INFO: Starting SDM - Software Delivery Manager...

21:55:06 INFO: Version 1.3/6.20.20030328124637.0000

21:55:07 INFO: Reading the SDM Repository...

21:55:07 INFO: ... succeeded

21:55:09 INFO: Write backup data to d:\sdm_home\config\sdmrepository.bak ...

21:55:09 INFO: ... succeeded

21:55:11 INFO: -


Start deployment -


21:55:11 INFO: Starting to execute deployment action WASCallsEJB

21:55:11 INFO: Starting Deployment Action (1/deploy) for SAP J2EE Engine for 'd:\sdm_home\comp_root\origin\sap.com\com.sap.rr.connect\6.20.20020904173714.0000\SAPWASCALLEJB.ear' and software type 'J2EE'.

21:55:13 INFO: ***** Begin of J2EE Engine Deployment (J2EE application) *****

21:55:15 ERROR: Deployment of SDA aborted with errors. See below for details:

21:55:15 ERROR: Error: Caught the following deploy manager exception:

ERROR: ID90509: Can't make connection to Host : [localhost] with UserName : [Administrator]

Check your Login Info.

Exception is :

javax.naming.NamingException: Connection lost.

ID003814 : JNDI Exception in getInitialContext of InitialContextFactoryImpl [Root exception is com.inqmy.services.rmi_p4.P4IOException: Connection lost.]

Can anyone suggest how to overcome this error.

Thanks

Naveen

Accepted Solutions (1)

Accepted Solutions (1)

jpolus
Contributor
0 Kudos

Hi Naveen,

It looks like you don't have the correct credentials for logging onto SDM. You either don't have the Administrator user or the password being used is wrong.

Make sure you have the correct user and password and start it up again.

John

Former Member
0 Kudos

Hi Naveen,

We need to check the IIS related dll's. it might got corrupted. or repair your IIS.

Thankx & Regards

Paul

Answers (0)