Buildspace missing in CBS

Hello Experts,
When i am login to NWDI Server from NWDS ,Following login Warning is Showing up:
"There is no Build Space with Identifier 'BuildSpaceName' .
Earlier BuildSpace was present in CBS but Some how it is Missing now.
Any Suggestions/inputs are most Welcome.
Thabks & Regards,
Siddharth Jain

Siddharth,
I recommend you to create a CMS track with the new name and restore SCs in DTR and CBS this way.
The process begins with CMS landscape configurator.
You specify SCs "for development" and "required" SCs.
When you save the track, CBS buldspaces _D and _C are created as well as DTR workspaces for storing the source code of DCs, which are part of SCs mentioned above.
Next step is Check-in and Import of SCs via SCA files.
All required SCs should be put into the CMS inbox directory, checked-in and imported.
At this moment CBS gets populated.
SCs, which come with the source code also populate DTR workspaces, so you can get access to their DCs via NWDS for development. If your original track had any development going on there are two options for you to bring it to the new track:
1. Get the latest assembled development SCs and import them into the new track. This is an easy way. You will loose all version history, but you will get the latest versions of dev DCs at the moment of the assembly.
2. Integrate activities between old DTR workspaces and new DTR workspaces.
http://help.sap.com/saphelp_nw04s/helpdata/en/3a/2057a1a9598c419182828eba347f55/frameset.htm
This is more complicated process, but it will make all versions available for developers. This is why I recommended you a new track, so you can use it as a source. In the old versions of NWDI there was an option to export-import workspace, but it was removed and should come back in NW7 EHP1 next year.
This was a long explanation of what Pascal mentioned earlier, but I hope it makes sense for you and will help.
Regards,
Slava

Similar Messages

  • DC not build in CONS buildspace

    Hi,
    we have the problem that our DCs are correctly build in the DEV buildspace of the CBS server but not in the CONS buildspace.
    We already checked all compartments and the DTR workspaces. Everything is identical.
    When building the DCs in the CONS buildspace the files seem not to be checked out from DTR.
    Below I attached the build log from DEV buildspace (that works fine) and from CONS buildspace (that does not build the DC correctly).
    Does anyone have an idea how to fix this problem?
    Thanks in advance.
    Helmut
    build log from CONS buildspace (extract):
    Build Plugin Version: 1.11.0 (630_VAL_REL) from 20 February 2005 11:50:18
    Start: 04.10.2005 05:26:50
    Temp dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361
    prepare:
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/eon.com/eby/asz/recherch/model/_comp/gen/default/deploy
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/gwd/packages
    gen:
        [ddgen]
        [ddgen] [Info]    Property deployment is true: Deployment information is provided!
        [ddgen] [Info]    Property sourcepath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/eon.com/eby/asz/recherch/model/_comp/src/packages
        [ddgen] [Info]    Property targetpath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/gdd
        [ddgen] [Info]    Property archivename: eon.com~eby~asz~recherch~model
        [ddgen] [Info]    Property vendor: eon.com
        [ddgen] [Info]    Property dcname: eby/asz/recherch/model
        [ddgen] [Info]    Property language: Available languages are automatically determined!
        [ddgen] [Info]    Property addpaths ...
        [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
        [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
        [ddgen] [Info]    Destination directory /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/gdd does not exist
        [ddgen] [Info]    Destination directory /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/gdd is created
        [ddgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/dict/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
        [ddgen] [Info]    Generating dbtables/sdmDeployDd.xml
        [ddgen] [Info]    Generation finished (2 seconds)
        [ddgen]
        [wdgen]
        [wdgen] [Info]    Property deployment is true: Deployment information is provided!
        [wdgen] [Info]    Property sourcepath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/eon.com/eby/asz/recherch/model/_comp/src/packages
        [wdgen] [Info]    Property targetpath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/gwd
        [wdgen] [Info]    Property archivename: eon.com~eby~asz~recherch~model
        [wdgen] [Info]    Property vendor: eon.com
        [wdgen] [Info]    Property dcname: eby/asz/recherch/model
        [wdgen] [Info]    Property language: Available languages are automatically determined!
        [wdgen] [Info]    Property addpaths ...
        [wdgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [wdgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [wdgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
        [wdgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
        [wdgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/DCs/sap.com/tc/bi/wd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
        [wdgen] [Info]    Generating portalapp.xml
    [Warning] no version info found for SapMetamodelCore: NullPointerException null
    [Warning] no version info found for SapMetamodelCommon: NullPointerException null
    [Warning] no version info found for SapMetamodelDictionary: NullPointerException null
    [Warning] no version info found for SapMetamodelWebDynpro: NullPointerException null
    [Warning] no version info found for SapGenerationFrameworkCore: NullPointerException null
    [Warning] no version info found for SapDictionaryGenerationCore: NullPointerException null
    [Warning] no version info found for SapDictionaryGenerationTemplates: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationCore: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationTemplates: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationCTemplates: NullPointerException null
    [Warning] no version info found for SapIdeWebDynproCheckLayer: NullPointerException null
        [wdgen] [Info]    Generating wd.xml
        [wdgen] [Info]    Generating application.xml
        [wdgen] [Info]    Generating application-j2ee-engine.xml
        [wdgen] [Info]    Generating PublicPartFileList.properties
        [wdgen] [Info]    Generating PublicPartFileList.xml
        [wdgen] [Info]    Generation finished (0 seconds)
        [wdgen]
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/3a/.B/5886/t/C40F9815EE21490043334C9F48DA1361/classes
    build log from DEV buildspace (extract):
    Build Plugin Version: 1.11.0 (630_VAL_REL) from 20 February 2005 11:50:18
    Start: 30.09.2005 02:33:38
    Temp dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361
    prepare:
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/eon.com/eby/asz/recherch/model/_comp/gen/default/deploy
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/gwd/packages
    gen:
        [ddgen]
        [ddgen] [Info]    Property deployment is true: Deployment information is provided!
        [ddgen] [Info]    Property sourcepath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/eon.com/eby/asz/recherch/model/_comp/src/packages
        [ddgen] [Info]    Property targetpath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/gdd
        [ddgen] [Info]    Property archivename: eon.com~eby~asz~recherch~model
        [ddgen] [Info]    Property vendor: eon.com
        [ddgen] [Info]    Property dcname: eby/asz/recherch/model
        [ddgen] [Info]    Property language: Available languages are automatically determined!
        [ddgen] [Info]    Property addpaths ...
        [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [ddgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
        [ddgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
        [ddgen] [Info]    Destination directory /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/gdd does not exist
        [ddgen] [Info]    Destination directory /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/gdd is created
        [ddgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/dict/_comp/gen/default/public/def/lib/java/SapDictionaryGenerationCore.jar!/DictionaryGenerationConfigurationCompiled.xml
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/types/Bauform.gsimpletype
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/types/PackagePointer.java
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/types/Name_First.gsimpletype
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/types/Adat.gsimpletype
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/ebyasz/types/EBYASZModel.gdictionary
        [ddgen] [Info]    Generating datatypes/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/types/EBYASZModelRecherche.gdictionary
        [ddgen] [Info]    Generating dbtables/sdmDeployDd.xml
        [ddgen] [Info]    Generation finished (7 seconds)
        [ddgen]
        [wdgen]
        [wdgen] [Info]    Property deployment is true: Deployment information is provided!
        [wdgen] [Info]    Property sourcepath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/eon.com/eby/asz/recherch/model/_comp/src/packages
        [wdgen] [Info]    Property targetpath: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/gwd
        [wdgen] [Info]    Property archivename: eon.com~eby~asz~recherch~model
        [wdgen] [Info]    Property vendor: eon.com
        [wdgen] [Info]    Property dcname: eby/asz/recherch/model
        [wdgen] [Info]    Property language: Available languages are automatically determined!
        [wdgen] [Info]    Property addpaths ...
        [wdgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [wdgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/mm/_comp/gen/default/public/def/lib/model
        [wdgen] [Info]       SapMetamodelDictionaryContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/ddic/metamodel/content/_comp/gen/default/public/default/lib/java
        [wdgen] [Info]       SapMetamodelWebdynproContent.zip - /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/wdp/metamodel/content/_comp/gen/default/public/default/lib/java
        [wdgen] [Info]    Initialize generation templates from configuration jar:file:/usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/DCs/sap.com/tc/bi/wd/_comp/gen/default/public/def/lib/java/SapWebDynproGenerationCore.jar!/WebDynproGenerationConfigurationCompiled.xml
        [wdgen] [Info]    Generating packages/de/isenergy/eby/zaehlerwesen/model/wdp/IPublicModelComp.java
        [wdgen] [Info]    Generating packages/de/isenergy/eby/zaehlerwesen/model/wdp/IPrivateModelComp.java
        [wdgen] [Info]    Generating packages/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/Z_E_Asz_Getorderplanswapelec_Input.java
        [wdgen] [Info]    Generating packages/de/isenergy/eby/zaehlerwesen/rfcmodel/model/recherche/Z_E_Asz_Getorderperrepgas_Output.java
        [wdgen] [Info]    Generating configuration/Components/de.isenergy.eby.zaehlerwesen.model.ModelComp/ModelComp.xml
        [wdgen] [Info]    Generating packages/de/isenergy/eby/zaehlerwesen/model/wdp/ResourceModelComp.properties
        [wdgen] [Info]    Generating portalapp.xml
    [Warning] no version info found for SapMetamodelCore: NullPointerException null
    [Warning] no version info found for SapMetamodelCommon: NullPointerException null
    [Warning] no version info found for SapMetamodelDictionary: NullPointerException null
    [Warning] no version info found for SapMetamodelWebDynpro: NullPointerException null
    [Warning] no version info found for SapGenerationFrameworkCore: NullPointerException null
    [Warning] no version info found for SapDictionaryGenerationCore: NullPointerException null
    [Warning] no version info found for SapDictionaryGenerationTemplates: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationCore: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationTemplates: NullPointerException null
    [Warning] no version info found for SapWebDynproGenerationCTemplates: NullPointerException null
    [Warning] no version info found for SapIdeWebDynproCheckLayer: NullPointerException null
        [wdgen] [Info]    Generating wd.xml
        [wdgen] [Info]    Generating application.xml
        [wdgen] [Info]    Generating application-j2ee-engine.xml
        [wdgen] [Info]    Generating PublicPartFileList.properties
        [wdgen] [Info]    Generating PublicPartFileList.xml
        [wdgen] [Info]    Generation finished (11 seconds)
        [wdgen]
        [mkdir] Created dir: /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/classes
        [javac] Compiling 136 source files to /usr/sap/D16/JC00/j2ee/cluster/server1/temp/CBS/39/.B/5838/t/C40F9815EE21490043334C9F48DA1361/classes

    Hi Helmut,
    It looks like only the activity that creates the DC was transported to cons, but not the actual WD content. The source folder (src/packages) is there in both cases, but it looks like the WD generator just doesn't find any wd-sources in cons.
    Did you compare the DTR workspaces? Could you check for unreleased activities ?
    If the workspace comparison (between dev/active and cons/inactive) shows that they are identical, then could you check what happens when you import the cons configuration in the IDE and try to build the DC from within the IDE?
    Regards,
    Manohar

  • Import failed in Con System

    Hello everybody,
    I did some development using the NWDS (JDI installed). After i have checked in my application / activated it and released it it was shown in the import queue at the Consolidation Tab of the CMS application. So far everything worked great, no error what so ever. So i continued to import the application into the Cons system. But it failed. The logs at the detail view says the error occured during the CBS-make step.
    Here is the log:
    Info:Starting Step CBS-make at 2006-03-25 11:29:47.0966 +1:00
    Info:wait until CBS queue of buildspace ABS_ESS_C is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:wait until CBS queue of buildspace ABS_ESS_C is completely processed, before asking for build results
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms (1)
    Info:CBS server log has been written to CBS log
    Fatal:the compartment abs-team.de_ABS_ESS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment abs-team.de_ABS_ESS_1 (dcname=ess/example2 dcvendor=abs-team.de)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-03-25 11:30:18.0778 +1:00
    The CBS server log mentioned above says the following
    Build number assigned: 15596
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "ABS_ESS_C" at Node ID: 7,411,650
         [id: 6,706; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-03-25 10:29:54.169 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         abs-team.de/ess/example2
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-03-25 10:29:54.200 GMT
    Analyse dependencies to predecessor activities... finished at 2006-03-25 10:29:54.200 GMT and took 0 ms
    Analyse activities... started at 2006-03-25 10:29:54.200 GMT
    Analyse activities... finished at 2006-03-25 10:29:54.200 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-03-25 10:29:54.216 GMT
         Synchronize development configuration... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-03-25 10:29:54.216 GMT and took 32 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-03-25 10:29:54.216 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-03-25 10:29:54.231 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment abs-team.de_ABS_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-03-25 10:29:55.028 GMT and took 797 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-03-25 10:29:55.028 GMT and took 812 ms
    REQUEST PROCESSING finished at 2006-03-25 10:29:55.028 GMT and took 859 ms
    I tried to build the application using the CBS. So i went to the respective cons build space and the DC shows with compile state yellow (middle icon). I clicked on the DC and build it. The buidling process failed, with the following request log:
    Build number assigned: 15696
    Change request state from QUEUED to PROCESSING
    BUILD request in Build Space "ABS_ESS_C" at Node ID: 7,411,650
         [id: 6,747; parentID: 0; type: 2]
    REQUEST PROCESSING started at 2006-03-25 11:04:39.622 GMT
    ===== Pre-Processing =====
    Calculate all combinations of components and variants to be built...
         "abs-team.de/ess/example2" variant "default"
    Prepare build environment in the file system... started at 2006-03-25 11:04:39.872 GMT
         Synchronize development configuration... finished at 2006-03-25 11:04:39.872 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-03-25 11:04:40.294 GMT and took 422 ms
         Synchronize sources...
    Prepare build environment in the file system... finished at 2006-03-25 11:04:40.512 GMT and took 640 ms
    ===== Pre-Processing =====  finished at 2006-03-25 11:04:40.512 GMT and took 890 ms
    Change request state from PROCESSING to FAILED
    ERROR! The following problem(s) occurred  during request processing:
    ERROR! The following error occurred  during request processing:Failed to synchronize D:usrsapER4DVEBMGS00j2eeclusterserver0tempCBS3e.CACHE296DCsabs-team.deessexample2_comp/src/packages
    REQUEST PROCESSING finished at 2006-03-25 11:04:40.512 GMT and took 890 ms
    Anyone has an idea what could be the problem, as this error occurs with every application i developed so far. Everything worked great until i have to import it to the cons system.
    p.s.: importing the standard SAP ESS SCs into the Cons system did work great, just with my very own applications i get this problem
    best regards,
    Markus

    Hello Kiran,
    yes i have made sure that these 3 required SCs are added.
    everything is working from loading the Development Configuration into the NWDS, to checking in the changes, to activate them and to release them. Just when it comes to import them into the CONV Workspace, i get the error.
    When i click on Import at the CMS i get this first error at the default trace (right after i initiated the import, first entry made!)
    SQL statement is 'SELECT 'VSE'.'OBJECTID','VO'.'OBJECTTYPE' 'INTERNALTYP
    E','VSE'.'DEACTIVATED','R'.'RESOURCEID','R'.'RESOURCETYPE'
    ,'R'.'OBJNAME','R'.'PATHURI','R'.'PATHID','R'.'FULLPATHID'
    ,'R'.'DISPLAYNAME','R'.'CREATORNAME','R'.'CREATIONTIME','V
    SE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'.'CONTENTTYPE','R
    '.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','R'.'ISMASTERLANGU
    AGE','R'.'SOURCEURI','V'.'ISDELETED','R'.'DOCUMENTTYPE','R
    '.'FORMATVERSION','R'.'DOCTYPESTATUS','R'.'CONTENTSTOREID'
    ,'R'.'FULLCONTSTOREID','R'.'CONTENTMD5','R'.'TOUCHEDPROPER
    TY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM','CS'.'CONTENTBL
    OB','VSE'.'ACTIVATIONSEQNO' FROM 'PVC_VSETELEMENT' 'VSE'
    INNER JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7
    DESC,9,3'.","Error","/System/Database/sql/jdbc/direct","co
    m.sap.sql.jdbc.direct.DirectPreparedStatement","sap.com/tc
    ~dtr~enterpriseapp","SAPEngine_Application_Thread[impl:3]
    _26","7411650:D:usrsapER4DVEBMGS00
    j2eeclusterserver0
    logdefaultTrace.trc","000C297D05810064000002B90000035C00
    040FE39A4D1378","com.sap.sql.jdbc.direct.DirectPreparedSta
    tement","-2009,I2009,[-2009]: Join columns too
    long,erp04.abs-
    team.de:ER4:SAPER4DB,SELECT 'VSE'.'OBJECTID','VO'.'OBJECTT
    YPE' 'INTERNALTYPE','VSE'.'DEACTIVATED','R'.'RESOURCEID','
    R'.'RESOURCETYPE','R'.'OBJNAME','R'.'PATHURI','R'.'PATHID'
    ,'R'.'FULLPATHID','R'.'DISPLAYNAME','R'.'CREATORNAME','R'.
    'CREATIONTIME','VSE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'
    .'CONTENTTYPE','R'.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','
    R'.'ISMASTERLANGUAGE','R'.'SOURCEURI','V'.'ISDELETED','R'.
    'DOCUMENTTYPE','R'.'FORMATVERSION','R'.'DOCTYPESTATUS','R'
    .'CONTENTSTOREID','R'.'FULLCONTSTOREID','R'.'CONTENTMD5','
    R'.'TOUCHEDPROPERTY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM
    ','CS'.'CONTENTBLOB','VSE'.'ACTIVATIONSEQNO'
    FROM 'PVC_VSETELEMENT' 'VSE' INNER
    JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7 DESC,9,3,","-2009,I2009,[-2009]: Join
    columns too long,erp04.abs-
    team.de:ER4:SAPER4DB,SELECT 'VSE'.'OBJECTID','VO'.'OBJECTT
    YPE' 'INTERNALTYPE','VSE'.'DEACTIVATED','R'.'RESOURCEID','
    R'.'RESOURCETYPE','R'.'OBJNAME','R'.'PATHURI','R'.'PATHID'
    ,'R'.'FULLPATHID','R'.'DISPLAYNAME','R'.'CREATORNAME','R'.
    'CREATIONTIME','VSE'.'LASTMODIFIED' 'MODIFICATIONTIME','R'
    .'CONTENTTYPE','R'.'CONTENTLENGTH','R'.'CONTENTLANGUAGE','
    R'.'ISMASTERLANGUAGE','R'.'SOURCEURI','V'.'ISDELETED','R'.
    'DOCUMENTTYPE','R'.'FORMATVERSION','R'.'DOCTYPESTATUS','R'
    .'CONTENTSTOREID','R'.'FULLCONTSTOREID','R'.'CONTENTMD5','
    R'.'TOUCHEDPROPERTY','CS'.'ISINDELTA','CS'.'DELTAALGORITHM
    ','CS'.'CONTENTBLOB','VSE'.'ACTIVATIONSEQNO'
    FROM 'PVC_VSETELEMENT' 'VSE' INNER
    JOIN 'DAV_RESOURCE' 'R' ON 'R'.'RESOURCEID'
    = 'VSE'.'VERSIONID' INNER JOIN 'PVC_VERSIONEDOBJ' 'VO'
    ON 'VSE'.'OBJECTID' = 'VO'.'OBJECTID' INNER
    JOIN 'PVC_VERSION' 'V' ON 'VSE'.'VERSIONID'
    = 'V'.'VERSIONID' LEFT OUTER JOIN 'DAV_CONTENTSTORE' 'CS'
    ON 'CS'.'CONTENTSTOREID' = 'R'.'CONTENTSTOREID'
    WHERE 'VSE'.'VERSIONSETID' = ? AND 'R'.'PATHURI' LIKE ?
    ESCAPE ? AND 'R'.'OBJNAME' LIKE ? ESCAPE ?
    AND 'VSE'.'LASTMODIFIED' > ? AND 'VSE'.'ACTIVATIONSEQNO'
    > ? ORDER BY 7
    DESC,9,3,","erp04.abs45team.de_ER4_7411650","0e1778e0bcb61
    1daab59000c297d0581","CMS_USER","0","0","com.sap.sql_0003"
    ,"1","/System/Database/sql/jdbc/direct","","461","com.sap.
    sql.jdbc.direct.DirectPreparedStatement","SAPEngine_Applic
    ation_Thread[impl:3]_26","","CMS_USER",
    regards,
    Markus

  • Simple J2EE application fails under activation

    Hi,
    I have a simple J2EE application which contains one Servlet.
    I have two DCs: SSORedirector (Enterprise application project) and SSORedirectWebModuleWebModule (Web Module)
    (there is a third DC which is a child DC to SSORedirector, but I don't think it causes any problems)
    The web module has by default public part called war (an I haven't touched this).
    The Enterprise application project I have addeed the required references to the web module in the application.xml(this automatically set a Used DC reference).
    When right-clicking the enterprise application and selecting build, it builds a correct ear file, and if I deploy it to my local workplace installation, the J2EE application works as expected.
    However, when I try to check in and activate the activity the SDM deployment fails with the message: Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
    I've retrieved the .sda file on the file system (shouldn't it be an .ear file) and it contains the application.xml under the folder meta-inf. The complete contents of the sda file is
    ./d1c66970ddbec7e6ffcc4d01c4705600.HASH
    ./META-INF/application-j2ee-engine.xml
    ./META-INF/application.xml
    ./META-INF/MANIFEST.MF
    ./META-INF/SAP_MANIFEST.MF
    ./META-INF/sda-dd.xml
    ./src/java/src.zip
    ./bouvet.com~SSORedirectorServlets.war
    What could possibly be wrong?
    Below are some logs.
    <b>Deployment log</b>
    SAP Change Management Service
    System sapJDI.st.bouvet.no
    Build space JDI_ZEPSSO_D
    Request 8554
    Step Deployment
    Log /sapmnt/JDI/global/TCS/LOG/JDI_ZEPSSO_D2006021618420025.log
    Info:deploy every archive associated to the buildspace: JDI_ZEPSSO_D
    Info:getting DC SSORedirector from CBS for buildspace: JDI_ZEPSSO_D
    Info:archive /sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda for DC SSORedirector was transfered
    Info:Start deployment:
    Info:The following archives will be deployed (on http://sapED2.st.bouvet.no:50018)
    Info:/sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
    Info:SDM log:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:
    Info:Feb 16, 2006 7:39:58 PM  Info: -
    Starting deployment -
    Info:Feb 16, 2006 7:40:01 PM  Info: Loading selected archives...
    Info:Feb 16, 2006 7:40:01 PM  Info: Loading archive '/usr/sap/ED2/JC00/SDM/program/temp/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda'
    Info:Feb 16, 2006 7:40:11 PM  Info: Selected archives successfully loaded.
    Info:Feb 16, 2006 7:40:11 PM  Info: Actions per selected component:
    Info:Feb 16, 2006 7:40:11 PM  Info: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
    Info:Feb 16, 2006 7:40:14 PM  Info: The deployment prerequisites finished withtout any errors.
    Info:Feb 16, 2006 7:40:14 PM  Info: Saved current Engine state.
    Info:Feb 16, 2006 7:40:15 PM  Info: Error handling strategy: OnErrorSkipDepending
    Info:Feb 16, 2006 7:40:15 PM  Info: Update strategy: UpdateAllVersions
    Info:Feb 16, 2006 7:40:15 PM  Info: Starting: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
    Info:Feb 16, 2006 7:40:15 PM  Info: SDA to be deployed: /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
    Info:Feb 16, 2006 7:40:15 PM  Info: Software type of SDA: J2EE
    Info:Feb 16, 2006 7:40:15 PM  Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    Info:Feb 16, 2006 7:40:15 PM  Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Info:Feb 16, 2006 7:40:15 PM  Error: Aborted: development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596':
    Info:Caught exception during access of archive "/usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda":
    Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
    Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
    Info:Feb 16, 2006 7:40:26 PM  Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Info:Feb 16, 2006 7:40:27 PM  Error: -
    At least one of the Deployments failed -
    Info:end of log received from SDM
    Info:End deployment:
    Info:deploy finished for SSORedirector (8554) with rc=12
    Info:deployment finished for buildspace: JDI_ZEPSSO_D
    <b>CBS log</b>
      CBS Request Log - [  8554/JDI_ZEPSSO_D  ]
      sapjdi.st.bouvet.no SAP Component Build Server   
    Build number assigned: 8596
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "JDI_ZEPSSO_D" at Node ID: 37,956,050
         [id: 8,554; parentID: 0; type: 4]
         [options: NO OPTIONS]
    REQUEST PROCESSING started at 2006-02-16 18:41:35.949 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
         1 activity in compartment "bouvet.com_PASSTHROUGH_SSO_1"
              C049689.6 - Passthrough SSO
                   [seq. no 17][created by 433937 at 2006-02-16 19:41:49.0][ID 44ed44bc9f1911daae5b0012799e50b6]
    Analyse activities... started at 2006-02-16 18:41:35.967 GMT
         Synchronizing component "bouvet.com/SSORedirector" from repository... finished at 2006-02-16 18:41:37.129 GMT and took 1 s 10 ms
              Component "bouvet.com/SSORedirector" is to be CHANGED by this activation.
         Synchronizing component "bouvet.com/SSORedirectWebModule" from repository... finished at 2006-02-16 18:41:37.933 GMT and took 802 ms
              Component "bouvet.com/SSORedirectWebModule" is to be CHANGED by this activation.
         Synchronizing component "bouvet.com/SSORedirectorServlets" from repository... finished at 2006-02-16 18:41:39.144 GMT and took 1 s 211 ms
         3 components to be build in compartment "bouvet.com_PASSTHROUGH_SSO_1"
    Analyse activities... finished at 2006-02-16 18:41:39.202 GMT and took 3 s 235 ms
    Calculate all combinations of components and variants to be built...
         "bouvet.com/SSORedirector" variant "default"
         "bouvet.com/SSORedirectorServlets" variant "default"
         "bouvet.com/SSORedirectWebModule" variant "default"
    Prepare build environment in the file system... started at 2006-02-16 18:41:39.410 GMT
         Synchronize development configuration... finished at 2006-02-16 18:41:39.430 GMT and took 20 ms
         Synchronize component definitions... finished at 2006-02-16 18:41:39.469 GMT and took 38 ms
         Synchronize sources...
         Synchronize sources... finished at 2006-02-16 18:41:40.891 GMT and took 1 s 422 ms
         Synchronize used libraries...
              public part "war" of component "bouvet.com/SSORedirectWebModule" ... OK
                   [PP "war" of DC 381 variant "default"][SC 142][last successfull build: 0]
              public part "default" of component "sap.com/ejb20" ... OK
                   [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jdbc20" ... OK
                   [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jms" ... OK
                   [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/servlet" ... OK
                   [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/ejb20" ... OK
                   [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jdbc20" ... OK
                   [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/jms" ... OK
                   [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
              public part "default" of component "sap.com/servlet" ... OK
                   [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
         Synchronize used libraries... finished at 2006-02-16 18:41:43.712 GMT and took 2 s 820 ms
    Prepare build environment in the file system... finished at 2006-02-16 18:41:43.712 GMT and took 4 s 302 ms
    ===== Pre-Processing =====  finished at 2006-02-16 18:41:43.713 GMT and took 7 s 755 ms
    ===== Processing =====
    BUILD DCs
         "bouvet.com/SSORedirectorServlets" in variant "default"
              Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
              The build was SUCCESSFUL. Archives have been created.
         "bouvet.com/SSORedirectWebModule" in variant "default"
              Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
              The build was SUCCESSFUL. Archives have been created.
         "bouvet.com/SSORedirector" in variant "default"
              The build was SUCCESSFUL. Archives have been created.
    ===== Processing =====  finished at 2006-02-16 18:41:56.154 GMT and took 12 s 436 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         "bouvet.com/SSORedirectorServlets" in variant "default"   OK
         "bouvet.com/SSORedirectWebModule" in variant "default"   OK
         "bouvet.com/SSORedirector" in variant "default"   OK
    Update component metadata...
         "bouvet.com/SSORedirector"  has been CHANGED
         "bouvet.com/SSORedirectWebModule"  has been ACTIVATED
    STORE build results...
         "bouvet.com/SSORedirectorServlets": store meta-data
         "bouvet.com/SSORedirectorServlets" in "default" variant  is PROCESSED
         "bouvet.com/SSORedirectWebModule": store meta-data
         "bouvet.com/SSORedirectWebModule" in "default" variant  is PROCESSED
         "bouvet.com/SSORedirector": store meta-data
         "bouvet.com/SSORedirector" in "default" variant  is PROCESSED
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-02-16 18:41:56.364 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to the results of this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Integration of activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" started at 2006-02-16 18:41:56.785 GMT
              "C049689.6 - Passthrough SSO"   OK
         Integration of 1 activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" finished at 2006-02-16 18:42:16.614 GMT and took 19 s 829 ms
    Analyse effect of applied changes to buildspace state... finished at 2006-02-16 18:42:16.615 GMT and took 20 s 251 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-02-16 18:42:16.617 GMT and took 20 s 451 ms
    REQUEST PROCESSING finished at 2006-02-16 18:42:16.618 GMT and took 40 s 669 ms

    Managed to solve it in a obscure way.
    I had earlier deployed the .ear file directly from NWDS to our dev system (hadn't installed dev workplace then). By removing the application from the deploy service in visual admin, the import suddenly worked.
    Dagfinn

  • CMS import failure - ESS (Dirty DC)

    Hi jdi gurus,
    Please help out ...
    the MSS, pcui, buildt, jee, jtech packages have been imported successfully into development and consolidation.
    however the ess package is not being imported into development.
    with respect,
    amit
    WebAS 640, EP 6.0, SP 13 on Windows with MS SQL server, ESS 100, SP 9.
    CMS-make
    Info:Starting Step CBS-make at 2006-09-14 17:03:44.0842 +12:00
    Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before asking for build results
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms (1)
    Info:CBS server log has been written to CBS log
    Fatal:the compartment sap.com_SAP_ESS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre dcvendor=sap.com)
    Info:dirty DC in compartment sap.com_SAP_ESS_1 (dcname=ess/tra/tre/trs dcvendor=sap.com)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2006-09-14 17:04:18.0077 +12:00
    CBS Log :-
      CBS Request Log - [  295/EPD_ESSTrack_D  ]
      devep SAP Component Build Server   
    Build number assigned: 305
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
         [id: 295; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         sap.com/ess/tra/tre/trs
         sap.com/ess/mx/addr
         sap.com/ess/fr/addr
         sap.com/ess/tra/trp
         sap.com/ess/de/fam
         sap.com/ess/br/addr
         sap.com/ess/tra
         sap.com/ess/au
         sap.com/ess/tra/tre
         sap.com/ess/it/pdata
         sap.com/ess/hk/fam
         sap.com/ess/us/pdata
         sap.com/ess/tw/fam
         sap.com/ess/sg/addr
         sap.com/ess/de/pdata
         sap.com/ess/ca/addr
         sap.com/ess/kr/bank
         sap.com/ess/be/fam
         sap.com/ess/us
         sap.com/ess/kr/fam
         sap.com/ess/ar/addr
         sap.com/ess/hk/addr
         sap.com/ess/ph/pdata
         sap.com/ess/wtcor
         sap.com/ess/us/addr
         sap.com/ess/at/addr
         sap.com/ess/mx/pdata
         sap.com/ess/wiw
         sap.com/ess/ca/empeq
         sap.com/ess/th/bank
         sap.com/ess/dk/fam
         sap.com/ess/tw/bank
         sap.com/ess/th/pdata
         sap.com/ess/grt/srv
         sap.com/ess/be/bank
         sap.com/ess/mx/fam
         sap.com/ess/es/fam
         sap.com/ess/at/pdata
         sap.com/ess/ie/fam
         sap.com/ess/ch/fam
         sap.com/ess/id/addr
         sap.com/ess/xx
         sap.com/ess/ca/pdata
         sap.com/ess/nz/pdata
         sap.com/ess/de/dcomp
         sap.com/ess/gb/pdata
         sap.com/ess/au/addr
         sap.com/ess/th/fam
         sap.com/ess/cn/bank
         sap.com/ess/ve/bank
         sap.com/ess/nl/fam
         sap.com/ess/es/bank
         sap.com/ess/sg/perid
         sap.com/ess/skl
         sap.com/ess/cat
         sap.com/ess/nl/addr
         sap.com/ess/fr/pdata
         sap.com/ess/se/pdata
         sap.com/ess/au/bank
         sap.com/ess/ben
         sap.com/ess/lea
         sap.com/ess/it/addr
         sap.com/ess/ie/bank
         sap.com/ess/au/pdata
         sap.com/ess/th/pid
         sap.com/ess/be/pdata
         sap.com/ess/id/bank
         sap.com/ess/de/addr
         sap.com/ess/nz/bank
         sap.com/ess/tra/tri
         sap.com/ess/jp/addr
         sap.com/ess/au/rep
         sap.com/ess/us/w4
         sap.com/ess/us/bank
         sap.com/ess/rep
         sap.com/ess/nz/addr
         sap.com/ess/za/pdata
         sap.com/ess/tra/trr
         sap.com/ess/cn/addr
         sap.com/ess/de
         sap.com/ess/be/addr
         sap.com/ess/tw/pdata
         sap.com/ess/my/addr
         sap.com/ess/hk/perid
         sap.com/ess/cod
         sap.com/ess/th/addr
         sap.com/ess/gb/fam
         sap.com/ess/au/tax
         sap.com/ess/us/fam
         sap.com/ess/ch/pdata
         sap.com/ess/ca/bank
         sap.com/ess/ie/addr
         sap.com/ess/ca/fam
         sap.com/ess/za/fam
         sap.com/ess/se/bank
         sap.com/ess/jp/bank
         sap.com/ess/fr/fam
         sap.com/ess/ve/fam
         sap.com/ess/ve/pdata
         sap.com/ess/sg/fam
         sap.com/ess/ph/bank
         sap.com/ess/sg/bank
         sap.com/ess/au/fam
         sap.com/ess/sg/pdata
         sap.com/ess/sg
         sap.com/ess/ve/addr
         sap.com/ess/com
         sap.com/ess/ar/pdata
         sap.com/ess/gb/addr
         sap.com/ess/nl/pdata
         sap.com/ess/kr/addr
         sap.com/ess/tw/pid
         sap.com/ess/no/pdata
         sap.com/ess/cn/fam
         sap.com/ess/hk/bank
         sap.com/ess/es/pdata
         sap.com/ess/pt/bank
         sap.com/ess/se/fam
         sap.com/ess/id/fam
         sap.com/ess/dk/pdata
         sap.com/ess/jp/pdata
         sap.com/ess/no/fam
         sap.com/ess/at/bank
         sap.com/ess/it/fam
         sap.com/ess/per
         sap.com/ess/br/fam
         sap.com/ess/ie/pdata
         sap.com/ess/pt/pdata
         sap.com/ess/gb/bank
         sap.com/ess/hk/pdata
         sap.com/ess/my/pdata
         sap.com/ess/jp/fam
         sap.com/ess/za/bank
         sap.com/ess/tw/addr
         sap.com/ess/mx/bank
         sap.com/ess/ar/bank
         sap.com/ess/cn/pdata
         sap.com/ess/pt/addr
         sap.com/ess/at/fam
         sap.com/ess/rem
         sap.com/ess/my/bank
         sap.com/ess/it/bank
         sap.com/ess/br/pdata
         sap.com/ess/nl/bank
         sap.com/ess/ch/addr
         sap.com/temp/testit0188
         sap.com/temp/testit0185
         sap.com/temp/testit0006_au
         sap.com/temp/pers_data_sg
         sap.com/temp/essmenu
         sap.com/temp/ESS_Homepage
         sap.com/temp/bentest
         sap.com/temp/address_sg
         sap.com/ess/id/pdata
         sap.com/ess/de/bank
         sap.com/ess/tim
         sap.com/ess/my/fam
         sap.com/ess/se/addr
         sap.com/ess/kr/pdata
         sap.com/ess/ar/fam
         sap.com/ess/no/bank
         sap.com/ess/pt/fam
         sap.com/ess/nz/fam
         sap.com/ess/no/addr
         sap.com/ess/tra/trp/trt
         sap.com/ess/dk/bank
         sap.com/ess/ph/fam
         sap.com/ess/ch/bank
         sap.com/ess/es/addr
         sap.com/ess/id/pid
         sap.com/ess/org
         sap.com/ess/dk/addr
         sap.com/ess/ph/addr
         sap.com/ess/my/pid
         sap.com/ess/za/addr
         sap.com/ess/fr/bank
         sap.com/ess/br/bank
         sap.com/ess/tri
         sap.com/ess/trt
         sap.com/ess/tev
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Analyse activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
         Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment sap.com_SAP_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms
    Message was edited by: Amit Chawathe

    Hi Marc,
    Thank you for your time and attention to the problem at hand. It is most appreciated.
    The CBS log life of the request in question is pasted below.Please let me know if there is any more information you would require.
    with respect,
    amit
      CBS Request Log - [  295/EPD_ESSTrack_D  ]
      devep SAP Component Build Server   
    Build number assigned: 305
    Change request state from QUEUED to PROCESSING
    ACTIVATION request in Build Space "EPD_ESSTrack_D" at Node ID: 5,717,050
         [id: 295; parentID: 0; type: 4]
         [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]
    REQUEST PROCESSING started at 2006-09-14 05:03:52.280 GMT
    ===== Pre-Processing =====
    List of activities to be activated:
    The following components belong to activities which already have been activated before:
         sap.com/ess/tra/tre/trs
         sap.com/ess/mx/addr
         sap.com/ess/fr/addr
         sap.com/ess/tra/trp
         sap.com/ess/de/fam
         sap.com/ess/br/addr
         sap.com/ess/tra
         sap.com/ess/au
         sap.com/ess/tra/tre
         sap.com/ess/it/pdata
         sap.com/ess/hk/fam
         sap.com/ess/us/pdata
         sap.com/ess/tw/fam
         sap.com/ess/sg/addr
         sap.com/ess/de/pdata
         sap.com/ess/ca/addr
         sap.com/ess/kr/bank
         sap.com/ess/be/fam
         sap.com/ess/us
         sap.com/ess/kr/fam
         sap.com/ess/ar/addr
         sap.com/ess/hk/addr
         sap.com/ess/ph/pdata
         sap.com/ess/wtcor
         sap.com/ess/us/addr
         sap.com/ess/at/addr
         sap.com/ess/mx/pdata
         sap.com/ess/wiw
         sap.com/ess/ca/empeq
         sap.com/ess/th/bank
         sap.com/ess/dk/fam
         sap.com/ess/tw/bank
         sap.com/ess/th/pdata
         sap.com/ess/grt/srv
         sap.com/ess/be/bank
         sap.com/ess/mx/fam
         sap.com/ess/es/fam
         sap.com/ess/at/pdata
         sap.com/ess/ie/fam
         sap.com/ess/ch/fam
         sap.com/ess/id/addr
         sap.com/ess/xx
         sap.com/ess/ca/pdata
         sap.com/ess/nz/pdata
         sap.com/ess/de/dcomp
         sap.com/ess/gb/pdata
         sap.com/ess/au/addr
         sap.com/ess/th/fam
         sap.com/ess/cn/bank
         sap.com/ess/ve/bank
         sap.com/ess/nl/fam
         sap.com/ess/es/bank
         sap.com/ess/sg/perid
         sap.com/ess/skl
         sap.com/ess/cat
         sap.com/ess/nl/addr
         sap.com/ess/fr/pdata
         sap.com/ess/se/pdata
         sap.com/ess/au/bank
         sap.com/ess/ben
         sap.com/ess/lea
         sap.com/ess/it/addr
         sap.com/ess/ie/bank
         sap.com/ess/au/pdata
         sap.com/ess/th/pid
         sap.com/ess/be/pdata
         sap.com/ess/id/bank
         sap.com/ess/de/addr
         sap.com/ess/nz/bank
         sap.com/ess/tra/tri
         sap.com/ess/jp/addr
         sap.com/ess/au/rep
         sap.com/ess/us/w4
         sap.com/ess/us/bank
         sap.com/ess/rep
         sap.com/ess/nz/addr
         sap.com/ess/za/pdata
         sap.com/ess/tra/trr
         sap.com/ess/cn/addr
         sap.com/ess/de
         sap.com/ess/be/addr
         sap.com/ess/tw/pdata
         sap.com/ess/my/addr
         sap.com/ess/hk/perid
         sap.com/ess/cod
         sap.com/ess/th/addr
         sap.com/ess/gb/fam
         sap.com/ess/au/tax
         sap.com/ess/us/fam
         sap.com/ess/ch/pdata
         sap.com/ess/ca/bank
         sap.com/ess/ie/addr
         sap.com/ess/ca/fam
         sap.com/ess/za/fam
         sap.com/ess/se/bank
         sap.com/ess/jp/bank
         sap.com/ess/fr/fam
         sap.com/ess/ve/fam
         sap.com/ess/ve/pdata
         sap.com/ess/sg/fam
         sap.com/ess/ph/bank
         sap.com/ess/sg/bank
         sap.com/ess/au/fam
         sap.com/ess/sg/pdata
         sap.com/ess/sg
         sap.com/ess/ve/addr
         sap.com/ess/com
         sap.com/ess/ar/pdata
         sap.com/ess/gb/addr
         sap.com/ess/nl/pdata
         sap.com/ess/kr/addr
         sap.com/ess/tw/pid
         sap.com/ess/no/pdata
         sap.com/ess/cn/fam
         sap.com/ess/hk/bank
         sap.com/ess/es/pdata
         sap.com/ess/pt/bank
         sap.com/ess/se/fam
         sap.com/ess/id/fam
         sap.com/ess/dk/pdata
         sap.com/ess/jp/pdata
         sap.com/ess/no/fam
         sap.com/ess/at/bank
         sap.com/ess/it/fam
         sap.com/ess/per
         sap.com/ess/br/fam
         sap.com/ess/ie/pdata
         sap.com/ess/pt/pdata
         sap.com/ess/gb/bank
         sap.com/ess/hk/pdata
         sap.com/ess/my/pdata
         sap.com/ess/jp/fam
         sap.com/ess/za/bank
         sap.com/ess/tw/addr
         sap.com/ess/mx/bank
         sap.com/ess/ar/bank
         sap.com/ess/cn/pdata
         sap.com/ess/pt/addr
         sap.com/ess/at/fam
         sap.com/ess/rem
         sap.com/ess/my/bank
         sap.com/ess/it/bank
         sap.com/ess/br/pdata
         sap.com/ess/nl/bank
         sap.com/ess/ch/addr
         sap.com/temp/testit0188
         sap.com/temp/testit0185
         sap.com/temp/testit0006_au
         sap.com/temp/pers_data_sg
         sap.com/temp/essmenu
         sap.com/temp/ESS_Homepage
         sap.com/temp/bentest
         sap.com/temp/address_sg
         sap.com/ess/id/pdata
         sap.com/ess/de/bank
         sap.com/ess/tim
         sap.com/ess/my/fam
         sap.com/ess/se/addr
         sap.com/ess/kr/pdata
         sap.com/ess/ar/fam
         sap.com/ess/no/bank
         sap.com/ess/pt/fam
         sap.com/ess/nz/fam
         sap.com/ess/no/addr
         sap.com/ess/tra/trp/trt
         sap.com/ess/dk/bank
         sap.com/ess/ph/fam
         sap.com/ess/ch/bank
         sap.com/ess/es/addr
         sap.com/ess/id/pid
         sap.com/ess/org
         sap.com/ess/dk/addr
         sap.com/ess/ph/addr
         sap.com/ess/my/pid
         sap.com/ess/za/addr
         sap.com/ess/fr/bank
         sap.com/ess/br/bank
         sap.com/ess/tri
         sap.com/ess/trt
         sap.com/ess/tev
    They will be removed from this request.
    Analyse dependencies to predecessor activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse dependencies to predecessor activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Analyse activities... started at 2006-09-14 05:03:52.733 GMT
    Analyse activities... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Calculate all combinations of components and variants to be built...
    Prepare build environment in the file system... started at 2006-09-14 05:03:52.733 GMT
         Synchronize development configuration... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize component definitions... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize sources...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize sources... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
         Synchronize used libraries...
                   ...Skipped for Activation with option : IGNORE BROKEN DC
         Synchronize used libraries... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    Prepare build environment in the file system... finished at 2006-09-14 05:03:52.733 GMT and took 0 ms
    ===== Pre-Processing =====  finished at 2006-09-14 05:03:52.733 GMT and took 438 ms
    ===== Processing =====
    ===== Processing =====  finished at 2006-09-14 05:03:52.748 GMT and took 0 ms
    ===== Post-Processing =====
    Check whether build was successful for all required variants...
         ..SKIPPED. Request option "IGNORE BROKEN DC" was given.
    Update component metadata...
    STORE build results...
    Change request state from PROCESSING to SUCCEEDED
    Analyse effect of applied changes to buildspace state... started at 2006-09-14 05:03:52.764 GMT
    Handle Cycles...
         No cycles detected.
    Determine components that have become DIRTY due to this request...
         No such components have been found.
    Integrate activities into active workspace(s)...
         Nothing to integrate in compartment sap.com_SAP_ESS_1
    Analyse effect of applied changes to buildspace state... finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    Request SUCCEEDED
    ===== Post-Processing =====  finished at 2006-09-14 05:03:53.327 GMT and took 563 ms
    REQUEST PROCESSING finished at 2006-09-14 05:03:53.327 GMT and took 1 s 47 ms

  • DCs are broken in consolidation only

    Hi All
    I have a Software component which is imported from an old NWDI
    I the new NWDI I have a track consist of this SC + the 3 standard SCs (JEE, JTECHS and BUILDT)
    I have checked-in all the components into the transport studio. And transported them all the way to assembly.
    The SCs are all building perfectly in development.
    l have  also checked out all DCs in NWDS, all DCs are compiling as they should here also.
    But, when I try to assemble the components on the server I get error messages. (The Check-assembly.log file)
    Info:Starting Step Check-assembly at 2011-02-21 15:56:24.0882 +1:00
    Info:Checks for software component mycorp.com,COMMON are performed now:
    Fatal:Contact CBS administrator: Nonempty list of broken DCs -stopping export now
    Error:list of broken DCs:
    Info:Step Check-assembly ended with result 'fatal error' ,stopping execution at 2011-02-21 15:11:32.0190 +1:00
    If I look into CBS BuldSpaces Information, I have this these information regarding the DCs
    TRACK_C:  Total DCs: 17, Broken DCs: 17, Dirty DCs 0
    TRACK_D:  Total DCs: 189, Broken DCs: 0, Dirty DCs 0
    To me it looks like the SC from SAP is somehow not available for assembly, but when I read the log statement, It only mentions the DCs from my own SC.
    The three SCs is available on the test tab, so I know that they have been assembled succesfully.
    Best Regards
    Søren Madsen

    Hi Søren,
    it is indeed then very strange how comes that the DCs haven't been imported in the first place (I mean the "Total DCs" column that displays 0 for the CONSolidation buildspace). You said that the import into the consolidation was succesful ("import finished" for each SCs on Consolifation tab of the "Transport Studio of CMS") .
    Can you please confirm the followings?
    1 a Restore System State in CONS, and a new import of all the SCs brings no solution, but still 0 is displayed in CBS webui, however CMS states that import finished succesfully in case of each SC imports.
    2 deleting the CONS buildspace, (you can do it in the main "Buildspace" view of CBS webui), resaving the track (this will recreate _C) and proceeding as described in point 1 brings no solution. Please delete only _C.
    3 As you know an import stands of "a) DTR Repository import, b) CBS-Make and c) Deployment". If you go to the "History" of the Consolidation tab (in CMS), you list the imports took place in the past, and you click on a finished import, and press the "Details..." button, you can confirm that all of these 3 steps were really succesful as per the logs and traces. Do the same for each SC.
    You also stated that after you faced this phenomenon, you tried a restore system state in DEV, and tried a new import and it was succesful. Can you please check the History, and via that all the Log Details (as mentioned above) of all the imported SCs ? Were the imports really succesful ? Can you try again a Restore System State in DEV and a reimport after you resave the track ? Are the SC still not displayed on the CONS tab after a succesful import on the Development tab ?
    I hope this helps.
    Thank you!
    Best Regards,
    Ervin

  • Error in JDI Configuration

    Hi All,
    i am getting an error in JDI configuration in the step importing MSS.sca file in CMS transport studio/development.
    error description as follows
    Fatal:the compartment sap.com_SAP_MSS_1 contains dirty DCs after the CBS build process:
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ecm dcvendor=sap.com)
    Info:dirty DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec dcvendor=sap.com)
    Info:the compartment sap.com_SAP_MSS_1 contains broken DCs after the CBS build process:
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/budget dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/equ dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/ewa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/finutils dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/lpa dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mas dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mol dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/mov dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pcr dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/per dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/pla dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtp dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/qtt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/cand dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rec/req dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/rpt dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=mss/tmv dcvendor=sap.com)
    Info:broken DC in compartment sap.com_SAP_MSS_1 (dcname=temp/testforisrlpd dcvendor=sap.com)
    Fatal:communication error: CBS error: dirty DCs in buildspace after the CBS build process
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2007-02-26 04:52:23.0586 +1:00
    please help me.
    thanks in advance.
    Srinivas.

    Hi ...
    Maintain one more characterictic like Zprice and in Addl data give table as SDCOM and field as VKOND and no values, this is characteristics for variant price and include it in the class which u have created earlier.
    goto CT04 and goto values .... there select one value eg RED and then goto object dependency and give code as
    $self.Zprice = 'A1'
    and for all values give it like that..
    Now goto VK11 and give VA00 .....
    then enter varaitn as A1 and give price
    give A2 and give price
    like all variants 'A1' etc etc etc which u maintained in object dependency ....
    now u can create profile in Cu41 and then run sales order
    so what ever u select ...red, blue green etc in order for eg color characterictics .. u have maintained for each value in characteristics .. object dependency .... as $self.Zprice = 'A1', so A1 price maintained in VK11 so if u select Red ... then price from A1 comes ..
    same procedure u follow for all values in other characterictics .. with only one characteristics Zprice ... i.e $self.Zprice = 'B1' etc .. and maintain values for B1 etc in Vk11 in Va00.
    Reward if useful
    Krishna

  • Need to reinstall Windows 7 on H320 series PC!

    I have a series H320 PC currently running with Windows 7 Home Premium (64bit) and which seems to have a corrupt or missing file (CBS Manifest) needed to install Windows Updates.  There are currently three updates that I have which, so far, have defied all attempts that I have made to install them.  The Windows error message that I receive is 80070490 and I have tried everything listed with that error message except to re-install  Windows 7.  I do have a set of four recovery discs from Lenovo for the H320; however, starting with disc #1, I am told that the only thing to do is to completely reformat my system.  This I do not want to do unless absolutely necessary.  Disc #2 named "Operating System Recovery Disc" is shown as being Windows 7 Home Premium ; however, trying to reinstall from that disc without beginning with disc #1 does not seem to work for me.  I might add, by the way, that I did NOT receive  any instructions as regards to various options in using the four Recovery Discs that I have and if there is a way to use one or all of them WITHOUT REFORMATING, I would appreciate further usable instructions.  Thank you for any and all hopeful responses to my dilema.  

    Hi elbojon,
    Welcome to the Lenovo Community Forums.  I am sorry to see you are having difficulties with your system as of this time.
    I am not sure what steps you have tried out but you may want to try these steps out.
    You may want to try out running the System update Readiness Tool.  Steps are outlined on the link provided. However, if this does not work then a reinstallation of the operating system may be needed. 
    The set of four recovery discs that you have are used to reinstall the system back to factory settings.  For the steps regarding using the Recovery CD you just simply have to boot the system up using the first disc and then agree that you will be restoring system back to factory settings then it will prompt you to insert the next discs then follow the prompts till the installation is finished.  These set of 4 recovery discs however does not provide you with any option to repair your windows installation.
    If the System Update Readiness tool does not resolve the problem, the next best option would be to back up your files and reinstall the operating system via the One Key Recovery.  One Key Recovery can be accessed by hitting F2 after powering the system up from shutdown.  This option allows you to return the system to factory settings however this means data loss.
    Hope the readiness tool helps resolve your issue.
    Don

  • CBS Buildspace for consolidation gone

    We have been making changes to our set up - creating new SCs for the track and moving DCs from one SC to another.  In the process, our buildspace for consolidation (_C) is no longer listed in the CBS.  In the Design Time Repository perspective in NWDS I can still see the configuration for cons, I can see the folder structure and files.  Is there anything I can do to recreate the consolidation buildspace?  If I try to save the track again to do the Save and Restore, I get the following error message:
    Unexpected error; inform your system administrator: CBS Server Error: Another BuildSpace owns one or more workspaces mentioned in configuration. Only workspace owning BuildSpace has rights to access it( internal code: BS_NOT_OWNED_WORKSPACE)
    Thanks for any help.
    Jeff Mathieson

    Hi Jeff,
    re-saving the track is usually the right way to do it.
    From the error message I'd guess that you either somehow managed to create two tracks that try to access the same DTR workspaces or that something went horribly wrong with CBS (how was the buildspace deleted?).
    If you browse the "technical details" of the affected workspaces using the DTR WebUI you can find a property "x:cbs-owner-buildspace". CBS sets this property in DTR to avoid collisions - image what happens if two CBS try to activate a change in the same workspace. In your case the buildspace was somehow deleted, but the flag was not properly removed.
    If you know what you are doing you may delete this property using the DTR command line tool (hidden in the IDE installation in plugins\com.tssap.dtr.client.vfs).
    Otherwise I'd recommend to contact SAP support.
    Regards,
    Marc

  • Regarding CBS buildspace / JDI Track

    Dear all,
       I've a total of 0 broken DCs in EPD_EMITRACK_D..and all these  Dcs are healthy,built successfully .but in EPD_EMI_TRACK_C,there's one broken DC,and it leads to fail of transportation of the activity. Any idea how to solve it? thank you
    Regards,
    Joan

    Hi
    see the following link ,it will be helpful for u.
    [CBS Build Error |CBS Build Error]
    Regards
    Hazrath

  • Cons buildspace not building in CBS

    We've run into a snag in our JDI build process. Somehow, even though all of our DCs build fine in the dev buildspace, they fail in the cons buildspace. We know the exact locations of the build failures and the specific files look OK. It isn't related to external dependencies. So, something is off in the source code.
    Has anyone else encoutered a problem like that? Would synching the two DTR branches up so they are consistent help (cons and dev)? How would I do that?
    Thanks.
    Rob

    Hello Rob,
    Since you are using SP11, you can use the following utility in DTR to compare workspaces in DEV and CONS. Please log into DTR and from the base url (http://<serverName>:<port>/dtr), Please follow the path System-tools > Reports > Workspace Comparison. You can use this page to compare any 2 workspaces. So, to find
    1. Unreleased activities:
       The left workspace would be DEV/active and the right workspace would be CONS/inactive. You can check for integrations to know the activities that have not been integrated into cons (and if there are any, you can release and import them).
    2. Pending activities:
       The left workspace would be cons/inactive and the right workspace would be CONS/active. You can check for integrations to know the activities and activate if there are any.
    As a sanity check, you can check all files between dev/active and cons/active to make sure they are identical.
    As for the child DC, if it is not used by anyone else, I don't see how it would cause a problem. However, you might want to delete the child DC locally to see whether it results in any of the DCs being broken.
    If all this doesn't work - you might want to work with the finer details. Please look at the build log of the broken DC to see what the compile time errors are and that will give you an idea of which DC the problem is due to.
    Do get back to me in case of any clarifications.
    Regards
    Rathish

  • DCs missing in SAP-JEE, SAP_BUILDT, SAP_JTECHS compartments in Track

    Hi All,
    I reimported the Updated version of  Development configuration in NWDS.
    After importing i found out that Standard SAP SCs SAP-JEE, SAP_BUILDT, SAP_JTECHS are empty and does not contain any Standard SAP Dcs.
    Because of this all the custom Dcs in the particular Track are not building when i am Creating Projects from these DCs in NWDS.
    I checked In the CBS WebUI that all the DCs are  Broken because their meta data is Broken because of the missing DCs in the above mentioned SAP Standard SCs.
    Please suggest how to resolve this issue and figure out the root cause of Problem.
    Thanks & Regards,
    Siddharth Jain

    Hi Siddharth,
    sometimes changes to the track definition on CMS will lead to the invalidation of the CBS buildspaces. In this case, check-in the required SCs SAP-JEE, SAP_BUILDT and SAP-JEE again into your track (using CMS Transport Studio, Check-In tab) and import them again into the DEV and the CONS stages of your track. This usually leads to a rebuild of your "own" DCs and -- maybe after leaving and starting the NW Developer Studio again -- should fill the CBS buildspaces. As a result you should see the DCs again in the NW Developer Studio.
    Please note that the situation might be different if you have changed the SP stack level of your DEV / CONS system in the meantime. In this case you need to import the "correct" version of SAP-JEE, SAP_BUILDT and SAP_JTECHS and this different version may result in broken DCs during the build (if some public parts have changed in the meantime).
    Best regards
    Thomas

  • Buildspaces PDE_TRCKXSS_C with all the DCs Broken

    Hi my friends
    In the CBS I have the Buildspaces: PDE_TRCKXSS_D and PDE_TRCKXSS_C.
    In the PDE_TRCKXSS_D  not present any error, while the PDE_TRCKXSS_C appear all the DCs as Broken .
    In the CBS Buildspace Details PDE_TRCKXSS_C appears several SC without DCs: This SC are: SAP-JEE, SAPPCUI_GP, SAPPCUI_GP, SAP_JTECHS.
    In the column total DCS displays 0
    This does not permit me to make transport in the CMS.
    Thank you very much for the help they can provide me

    HI,
    As you see this the problem occur due to the missing dependecies.
    so you have a option to import those dependecies(SAP-JEE, SAPPCUI_GP, SAPPCUI_GP, SAP_JTECHS.) again in you track.
    Go to CMS-> consolidation tab -> Go to history button -> choose proper history date which will show your dependecie-> select those depenecies and say -> add to queue -> back to import queue
    from here you can import them again in youe cosolidation compartment.
    If your cms is not showing the dependecies in history of consolidation, then you need to perform import throught from check-in to assembly.

  • NWDI CMS Assembly broken DC - missing DCs as Dependency

    Hi Everyone,
    I need your advise/help:
    in NWDI CMS, when assembly my custom application i.e. b2b_bd, I got broken DC error with below details from CBS log file.
    Seems there are 2 missing DCs:
    sap.com/tc/bi/bp/enterpriseApplication' DC, does not exist [public-part: enterpriseApplication] AS Build Plugin Dependency
    'sap.com/crm/isa/web/b2b' DC, does not exist [public-part: war] AS Build-Time Dependency
    My question is  prior to my custom application assembly, do we need to do any dependency steps - sap standard DCs (SP related DCs) assembly?
    here is the CBS's log details:
    Analyze effect of applied changes to buildspace state... started at 2009-10-27 19:45:59.564 GMT
    INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.
    'sap.com/b2b_vanilla' DC of 'sap.com_CUSTCRMPRJ_1' compartment USES 'sap.com/tc/bi/bp/enterpriseApplication' DC, does not exist [public-part: enterpriseApplication] AS Build Plugin Dependency
    [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
    'sap.com/b2b_bd' DC of 'sap.com_CUSTCRMPRJ_1' compartment USES 'sap.com/tc/bi/bp/enterpriseApplication' DC, does not exist [public-part: enterpriseApplication] AS Build Plugin Dependency
    [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
    'sap.com/b2b_vanilla' DC of 'sap.com_CUSTCRMPRJ_1' compartment USES 'sap.com/crm/isa/web/b2b' DC, does not exist [public-part: war] AS Build-Time Dependency
    [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
    'sap.com/b2b_bd' DC of 'sap.com_CUSTCRMPRJ_1' compartment USES 'sap.com/crm/isa/web/b2b' DC, does not exist [public-part: war] AS Build-Time Dependency
    [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
    Skip check for build time dependency cycles. DC metadata is not changed.
    Determine components that have become DIRTY due to the results of this request started at 2009-10-27 19:45:59.615 GMT
    No such components have been found.
    Determine components that have become DIRTY due to the results of this request finished at 2009-10-27 19:45:59.616 GMT and took 1 ms
    No Internal Build Requests are canceled by this request
    Any advises / suggestions / help?
    Thanks, Jin

    Hi eCommerce Developer,
    Thank you so much for your quick response, email and help.
    The DC was broken because of a problem in a used DC or build plug-in, 'sap.com/tc/bi/bp/enterpriseApplication'  and 'sap.com/crm/isa/web/b2b', are not available while assembling.  My question is how to make them avaiable?  I don't think I can edit/activate them from NWDS, only Basis can import a patched version of the used SC into CMS, please correct me if I'm wrong.
    Any advises / suggestions?
    Thanks again, Jin

  • Missing .dcref/ topleveldcs in consolidation build space

    Hi NWDI experts
    We are trying to migrate our track from one NWDI to another.
    But, today we found that in the workspace comparision that , the topleveldcs in the dtr's dev/active missing in the consolidation/active folder.
    /ws/folder/mytrackname/cons/active
    vs
    /ws/folder/mytrackname/dev/active
    Because these are missing, in the new NWDI, when we import the SCA file, all the ToplevelDCs are missing.
    Please suggest me how to restore and make the dev and cons build spaces sync?

    spooky indeed...
    Yes, CBS caches sources to minimize data transfer between CBS and DTR. You can maybe find something locally in <CBS tempdir>\<buildspace id>\.CACHE\<dc id>\..., e.g. F:\cbstemp\94\.CACHE\1234\DCs\...
    CBS should notice if the cache is not up-to-date but there was one bug with DTR where this failed, especially if there were integration conflicts. As ultimate weapon "init compartment" resolves the issue.
    Marc

Maybe you are looking for

  • HP LaserJet Pro 100 color MFP M175nw unable to communicate with product

    Hi guys, I've had a HP LaserJet Pro 100 color MFP M175nw for 12months now and it has worked great over my wireless network. I recently upgraded from router from a 5 year old single band router to a late model dualband wireless N router. Since i did t

  • Need help with overlaying divs

    I want a top nav bar within the (top) banner. I am doing this by putting a div (#toplinks) within the banner div (#banner). But I want a bottom allignment on that nav bar.  When I give it a top margin to push it down, it pushes the banner down. #wrap

  • Is the Nintendo DS compatible with my router?....

    i just saw a commercial on TV a few days ago. it was saying that the DS can be connected to some wireless routers.... so i went to the site they had they did not say to much about it, or to really go about connecting it... and since the Nintendo site

  • Combine two layer names in one command

    Hello Community, I have a tiny question: Can those two lines be combined to one command by somehow group the names? I have throught about an array but I would like to have the names still visible. Maybe there is something smarter ... ? myDokument.lay

  • Reg : LOGO in ALV

    HI,        I am using ALV grid , i used ALV commentry write to attch the logo, in the display the logo is coming, but while taking the printout the logo is not coming... kindly suggest me a solution. With Regards, S.Barani