on 12-12-2006 9:58 PM
We're trying to apply SPS 08 for Solution Manager 4.0. We're at SPS 06 already from the initial installation. The ABAP kernel & support packs have been applied successfully; when we launch JSPM and it catalogs the deployed components via the SDM, the connection is terminated. Looking in the SDM we see errors like this:
Dec 12, 2006 3:27:39 PM Info: CAF: Sync deployment...
Dec 12, 2006 3:27:39 PM Info: CAF: Component: software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956'
Dec 12, 2006 3:27:39 PM Error: CAF: Location of software component 'CAF'/'sap.com'/'MAIN_APL70P06_C'/'1000.7.00.6.0.20060221161956' unknown.
Dec 12, 2006 3:27:39 PM Error: CAF: system component version store not updated.
We get that same error for the following components: CAF, CAF-UM, ADSSAP, BI_UDI, KM-KW_JIKS, SAP_JEECOR, JSP_JTECHF, UMEADMIN, BASETABLES, BI_MMR, LM-TOOLS, SAP_JTECHS, SAP-JEE (13 components in all).
When I look at the /usr/sap/<SID>/DVEBMGS<##>/SDM/program/config/sdmrepository.sdc file for any of these (let's pick on CAF for fun), I see:
<Sca>
<SoftwareComponent>
<Name>CAF</Name>
<Vendor>sap.com</Vendor>
<Location>MAIN_APL70P06_C</Location>
<Count> 1000.7.00.6.0.20060221161956</Count>
</SoftwareComponent>
<Release>7.00</Release>
<SPNumber>6</SPNumber>
<SPPatchLevel>0</SPPatchLevel>
<RelativeLocation isUnknown="true"></RelativeLocation>
</Sca>
That <RelativeLocation isUnknown="true"> tag looks like it may be a problem... when I look at the component information via the URL (http://host:port/sap/monitoring/ComponentInfo) it shows all 13 "missing" components and their locations (MAIN_APL70P06_C). There are also other components with the same location (e.g. caf/runtime/security/content & tc/lm/webadmin/httpprovider/lib) that have the same location, so it really seems to be confined to these components.
I've dug around in OSS a bit and found note 756084 with common SDM problems; it makes a reference to note 828978 for this specific error, but that note talks about a system copy where the database is copied but not the SDM config file; it does talk about doing an 'SDM systemcomponentstate' call to sync the BC_COMPVERS table with the deployed components (see also note 910073).
I tried the sync and got the same response.
Has anyone else seen this before?
Thanks,
Rich
Hi,
Check the central note:
Note 891983 - JSPM: Central SAP Note SAP NetWeaver 2004s AS Java
Regards,
Siddhesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check this one, although its not related it speaks about a work around such type of errors.
Note 903609 - CAF 7.0 SPS05 Deployment problem over SPS04 using JSPM
It suggests that you apply the patch via SDM instead of JSPM by doing the following..
Go to the "Deployment" tab and select the component. Use the plus button and select "Update deployed SDA/SCAs that have any version" from the Deployment configuration options below and complete the deployment.
and then stop SDM and start JSPM again.
If you have a sandbox , you may take a backup and try this option if it works, you might be well ahead..
hope it helps,
Regards,
Siddhesh
Hi Siddesh,
_*When there is an error , corresponding error page should be displayed instead of whole stack trace.
*_I want to achieve this with CE 7.1 EHP1.
To cary out this i am not finding HTTP property ServiceUnavailableResponse and Webcontainer property ApplicationStoppedFile in nwa system configuration.
Please can you help to know how to get this properties in nwa .
It is urgent.
Regards
Mahesh
Sorry, I used JSPM for everything; rather than "SP Stack" I selected "Single support package" to apply the JSPM SP10 patch, then re-started JSPM (now running PL10 instead of PL06) and tried the "SP Stack" option again... and got the disk space error. PL06 just bombed with no errors.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I thought I'd post the fix in case anyone else stumbles across the same issue. I found out that I could apply single support packs, but not the entire SP stack. JSPM SP06 wasn't giving me enough detail in the logs on the error, but manually applying JSPM SP10 lead me in the right direction as it displayed a 'no space left on device' error. There wasn't enough room in the SDM area for the 3 copies of all the SCA files (almost 1 GB worth in EPS/in)... adding 4 GB of space to the file system allowed me to apply the rest of the SP's as a stack.
Rich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.