Skip to Content
0
Former Member
Apr 26, 2012 at 11:20 AM

SCA Deploy Problem on portal 7.30

97 Views

I have used the SAPMAKE Utilities on command line to package our application in SCA.

I first created SDA files for the given PAR and EPA files which are exported from portal 7.0 Before creating our SDA file for the specified EPA, I excluded the references from the EPA so that it wouldn't have the PAR files. Then I put all our SDAs in the same folder, and created an SCA package for that folder.(I also tried with the EPAs including the PARs)

When I try to deploy this SCA package on the 7.30 portal via JSPM, I get an error. You can find the related log below.

I especially wonder if it is because of the related line below "epaFile must be an existing file"

Thank you very much in advance

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[C:\usr\sap\J08\J00\j2ee\JSPM\log\log_2012_04_19_11_26_53\deploy_api.log]/-->

<!--PATTERN[deploy_api.log]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %M %m)]/-->

<!--ENCODING[UTF8]/-->

<!--FILESET[0, 5, 10485760]/-->

<!--PREVIOUSFILE[deploy_api.4.log]/-->

<!--NEXTFILE[deploy_api.1.log]/-->

<!--LOGHEADER[END]/-->

Apr 19, 2012 11:27:58 AM Error: com.sap.ASJ.dpl_api.001226 Could not establish connection to AS Java on [NW730:50004]. Cannot authenticate the user. Wrong or missing security credentials (password) for principal [test], or the specified principal has no permissions to perform JNDI related operations.

Apr 19, 2012 11:32:37 AM Info: com.sap.ASJ.dpl_api.001243 component version handling rule is [UpdateLowerOrChangedVersionsOnly].

Apr 19, 2012 11:32:37 AM Info: com.sap.ASJ.dpl_api.001244 deployment workflow strategy is [normal deploy strategy].

Apr 19, 2012 11:32:39 AM Info: com.sap.ASJ.dpl_api.001249 +++ Validation finished with status [Success] +++ [

===== Summary - Validate(1/1) Result - Start =====

------------------------

Type | Status : Count

------------------------

> SCA(s)

- [Admitted] : [1]

> SDA(s)

- [Admitted] : [1]

------------------------

------------------------

Type | Status : Id

------------------------

> SCA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

> SDA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

------------------------

===== Summary - Validate(1/1) Result - End =====

]

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

alidate(1/1) Result - Start =====

------------------------

Type | Status : Count

------------------------

> SCA(s)

- [Admitted] : [1]

> SDA(s)

- [Admitted] : [1]

------------------------

------------------------

Type | Status : Id

------------------------

> SCA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

> SDA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

------------------------

===== Summary - Validate(1/1) Result - End =====

]

Apr 19, 2012 11:32:39 AM Info: com.sap.ASJ.dpl_api.001249 +++ Validation finished with status [Success] +++ [

===== Summary - Validate(1/1) Result - Start =====

------------------------

Type | Status : Count

------------------------

> SCA(s)

- [Admitted] : [1]

> SDA(s)

- [Admitted] : [1]

------------------------

------------------------

Type | Status : Id

------------------------

> SCA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

> SDA(s)

- [Admitted] : name: 'bilaltest3', vendor: 'sweetlets.com',

------------------------

===== Summary - Validate(1/1) Result - End =====

]

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:41 AM Info: com.sap.ASJ.dpl_api.001023 Deployment of [name: 'bilaltest3', vendor: 'sweetlets.com' (sda)] finished.

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001041 Deployment Exception during deployment phase [DeploymentException], cause=[ASJ.dpl_dc.001085 Operation [deploy] of [sweetlets.com_bilaltest3] failed]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]

Apr 19, 2012 11:33:42 AM Error: com.sap.ASJ.dpl_api.001042 Deployment Items status: [

----- Sorted Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

2. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

----- Deployment Items -----

1. Client path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca'

Deploy status is 'Aborted'

Description:'1. Item is skipped because of failed deployment of item 'sweetlets.com_bilaltest3' and because the applied error strategy is OnErrorStop

2. Contains Aborted deployment component:

sweetlets.com_bilaltest3'.

SCA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '1000.2.4.00.0.0.20120418164238'

Composite Time statistics( ms ):

1.validate : -1

Contained DCs:

1.1 : Relative path '\\NW730\sapmnt\trans\EPS\in\bilaltest300_0.sca --> bilaltest3_sda.epa'

Deploy status is 'Aborted'

Description:'1. Cannot [deploy] application [sweetlets.com/bilaltest3].

-> epaFile must be an existing file

2. [ASJ.dpl_dc.006005] The reason for nested issue could be concurrency one in components involved in exception stack trace.

Hint: 1) Search in [std_server.out] file in work dir for message [Possible concurrency issue related to item [sweetlets.com_bilaltest3].] or thread dumps.'.

SDA : name 'bilaltest3', vendor 'sweetlets.com', location 'LOCAL', version '20120418163903', software type ('single-module', sub type ''), csn component '', dependencies :[( name 'com.sapportals.prt.portalruntime', vendor 'sap.com') ]

Time statistics( ms ):

1.validate : -1

]