NWDI/DI configuration

Hi!
Can anybody here say, where is full step by step configuration guide for NWDI or CBS/DTR/CMS/...?
We have DTR/CBS etc. on DEV server. But some configuration issues were missed:
1. CMS Landscape configurator -> Domain Data -> Update CMS:
SLD (URL http://serverxxx:50000) server exception: CIM_ERR_FAILED: No such instance: sld/active:SAP_DependencyContext.Name="BuildTime",Type="Development"
2. http://serverxxx:50000/dtr
<DAV:error>
<DAV:access-denied/>
</DAV:error>
Any answer will be appreciate.
Regards,
Maxim

Hi Sandeep!
Thanks for the manual! I re-configured SLD in accordance with it. And problem with access to DTR solved, but after server was re-started, I get this message when try to get "Administration" link in SLD:
The initial exception that caused the request to fail, was:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
Do you have any idea?
P.S. In Visual Admin "Send Result - Success" and "CIM Client Test - Passed"
Thanks in advance!
Edited by: Maxim Pak on Oct 17, 2008 1:29 PM
Edited by: Maxim Pak on Oct 17, 2008 1:31 PM

Similar Messages

  • CTS+ configuration for NWDI - Development configuration error

    Hi All,
    I really need some help on this. we are configuring CTS+ on Solution Manager system for NWDI, EP landscape (EPD, EPQ,EPP) and SLD system.
    we made EPD as development system and trying to use CM Services to configure the NWDI scenario SDA/SDC Deployment.
    I have created all NON-ABAP systems and created the CTSDEPLOY Http connections. I am getting the popup to configure the Development Configuration,"What is the User I have to use here and  of which system?" and what are the authorizations required to configure this.
    As soon as the popup comes, It is asking for the user ID and Password. I am entering Solution Manager (Admin user with all CMS actions also assigned) user then it is giving the following error on the screen. " Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function "
    I have give the SLD url correctly, and the admin user for SLD and Password. I have cross checked the user for password, every thing is fine.
    I really appreciate your help.
    Thanks,
    Ramu J.

    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
    Hi Ramu,
    Pls answer me for below.
    specified SLQ as my SLD
    1.
    You said SLQ is you SLD, but You configuring CTS on solution manager. but solution manager has its own SLD.
    a. SMG solution manager SLD
    b. SLQ is also SLD
    If there is two sld then you should get error
    " Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function "
    This is becuase you are giving the user which is present in SLQ SLD but CTS is checking the Solution manager SLD.
    For CTS you should have centralied SLD.
    2.
    Can you tell me one more thing, in CTSDEPLOY do I need to give the SMG host and port number or EPD's host and Port number?
    You have to specify the host and port in CTSDEPLOY of the system on which CTS contoller should work i.e EPD or SMG.
    To resolve your all this problem first of all make the SLD as central . i.e Make solution manager ( CLQ ) as SLD or SLD system in you landscape ( SLQ ) as SLD.
    don't keep two different SLD . If you keep Solman as its own SLD then CTS will search component from SMG SLD
    Pls follow the guide
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
    3.
    Could not connect to SLD; contact your System Administrator: User SAPNWDI is not allowed to do this function
    Can you tell us in which system this SAPNWDI user is present
    Check the SLD of of system in which SAPNWDI user  i present
    system is whether in SMG SLD or SLQ SLD
    If you are not clear with my above suggestion pls let me know.
    Thanks
    Anil
    Edited by: Anil Bhandary on Oct 24, 2009 10:28 AM

  • Problem in NWDI - CMS configuration.

    Hi
    I have a problem in NWDI product creation. Actually I follow the steps given in
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0b1f2c8-54e0-2910-9ab3-b85f15093655
    I successfully created Track and configured the landscape in CMS - as per the link.
    Then I try to check-in component in transport studio of CMS, There is no check-in component listed in the check-in tab. I don't know what to do further? Plz suggest solution.
    Regards
    Saba

    Hi,
    which components are missing?
    Do you need the standard J2EE Components from SAP?
    All SDA Files that you havn't created on your own, you have to  put into the folder <Drive>:\usr\sap\JTrans\CMS\inbox.Like SAP_BUILDT.sca, SAP_JTECHS.sca and SAP-JEE.sca. You own DC's must not be checked in. They will be visible in the Development Tab after activacan and release in the NWDI.
    regards,
    Dennis

  • Configuration od NWDI

    Hi All,
       We need to configure NWDI for my Client
       I need procedure to configure NWDI in Admin side
       which stepd to need fallow and I want to know from starting point i.e installation part also
        and  connection  with Webdynpro java to NWDI
        Cretion of Tracks , DC's  Common libraries etc..
        If any body have good knowledge please share ..
    Thanks
    Renu

    Renu,
    Go through this doc. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f04a930b-893f-2b10-1bb1-85fcd51030aa
    It lists out NWDI admin configuration as well as track creation.
    Hope it helps,
    Ameya

  • Import local DCs into Development Configuration

    Hi all.
    I have some local DCs already developed. From now I have available NWDI Development Configuration and I want to export those local DCs to the Remote Development configuration.
    I'm trying to implement/configurate a team development enviroment.
    I try sharing the DC project (DTR option into Webdynpro perspective) but when I import the shared content to a project in another Developer Studio, the DC metadata is lost.
    Its possible to move my local DCs to the Remote Development Configuration? If so, how can I do that?
    Regards.
    Gregory.

    hi,
    Follow the below mentioned steps:
    Creating a New Development Component
           1.      Create a new Web Dynpro DC project.
    You create an empty u201Ccontaineru201D for a Web Dynpro DC that does not yet have any functions. The new DC should include all relevant development objects of the local project.
    Do not check in the newly created DC into the DTR yet.
    Copying Packages from the Local Project
           2.      In the Web Dynpro perspective, switch to the Navigator view.
           3.      Select the local Web Dynpro project to be migrated and expand the project structure down to the source folder:  ® src ® packages.
           4.      Select all packages and from the context menu choose Copy.
    Inserting Packages into the New DC Project
           5.      Now choose the DC project that was just created and expand the project structure in the Navigator view, again down to the source folder.
           6.      Select the Packages node and choose Paste.
    The Add Files to DTR dialog box appears.
           7.      Choose OK to confirm your selection.
           8.      Assign an activity either by creating a new activity or by choosing an existing one.
    Execute Reload
           9.      Switch to the Web Dynpro Explorer.
       10.      Select the project node of the DC project and choose Reload.
       11.      In the displayed dialog box, again choose Reload.
    Reloadnow also reloads the Web Dynpro metadata into the new project.
    Building the Project
       12.      Execute a local rebuild for the entire DC project. Choose the function Rebuild project.
       13.      If there are no errors in the task view, execute a DC-based build by choosing the function Development Component ® Build.
    regards,
    amit bagati

  • Createing Local DC based on Existing DC from NWDI Inactive DC's

    Friends,
    How do i create a Local Development Component from existing Development Component which is existed in NWDI Development Configuration perpective , inactive DC's?
    Thanks in adnvace.
    Pete

    Hi Peter,
    If I understood your question correctly, you want to create a local DC and it should be using the DC that exists in the NWDI track....
    DC can be created 2 ways...
    log into NWDI go to Local Development -> MyComponents-> right click and select create DC
    else in webdynpro perspetive select File -> New -> Development Component Project..
    This is how the Local DC will be created...
    Now expand the DC and DC Metadata-> DC Definition -> Used DCs -> right click select Add Used DCs..
    and add the DC that  exists in NWDI track

  • How to do the modification in standard ESS/MSS business packges using NWDI?

    Hi Gurus,
    I have requirement where in which set up is ready ESS/MSS business packges are available in NWDI now my question is......
    How to do the modification in certain ESS/MSS standard iviews? using your local machine NWDS?
    How will you download the ESS/MSS iviews that are available in NWDS?
    My EP server version is EP 7.0 and backend ecc5.0......
    Can you guys tell me how to do the changes in standard ESS/MSS stuff that are avaiable in NWDI using your local machine NWDS.
    once the changes is done how you will upload the same into NWDI to reflect the changes globally.
    Its an urgent requirement....Please provide me step by step approach of the same.
    Thanks in Advance,
    Dharani

    Hi Dharani,
         Have a look at my weblog,
    For your 1st Question:
    "How to do the modification in certain ESS/MSS standard iviews? using your local machine NWDS?" -
    1.After you configured your track for ESS/MSS business package in NWDI try importing the track in NWDI by configuring NWDI server in NWDS, goto Windowsàpreferences-Java Development Infrastructure-Development Configuration
    and specify the URL where you have configured your NWDI
    2. create a project for the views which you want to modify.
    3. Checkout and create a new activity for the DC
    4. Make the changes as per your requirement
    5. Checkin the activty once you are done with the changes
    6.Activate and release
    These are all the steps involved in customization of any business package.
    Mail me back if you have any doubts.
    Hope this helps,
    Regards,
    Vinoth.M
    Edited by: Vinoth.Murugaiyan on Feb 13, 2008 3:14 PM

  • NWDI Tracks Lost in dev.

    Dear All,
    We are in some peculiar position. We have our nwdi tracks confitgured in our development system including dtr, cms and cbs.
    so when we deploy application it should go to dev and then transported to other 2 systems. We have a central SLD in production system box.
    Due to some issues, our dev system went down during Support pack upgrade and now we cannot login: login failure: all modules disabled.
    We also dont have the backup as the backup is erased. what we have is offline file system backup.
    We are planning to put our qa backup, in development system and then change all JCO and system objects paths to point to our R3 dev system. but we will loose all our tracks, versions of developed components in this activity.
    My questions is how we can again apply our tracks and version, code of already developed components in the nwdi after configuring it again in the dev system.
    Please help
    ANkur

    HI Ankur,
    if you have an offline filesystem backup everything should be ok. because after all a DB Backup with brtools rman or other tool is jsut saving the database files to another location.
    So i would just do a recovery of your database with this files.
    In case this is not possilbe, The only change I see to recover your sources is if they went to assembly once. In this case you can find SCA files of your application in your CMS/archives folder. In default this is located under /usr/sap/trans/EPS/in.
    If the SCAs are assembled with sources you can setup your track and checkin this SCAs. You will have the sources of the last release then in your new track.
    If they don't went through assembly or without sources and your databse is broken with no way to recovery, things look mighty bad in my opinion.
    Hope this helps
    Jan

  • NWDI- activation failed.

    Hi Experts,
    I created project and i modified in developement under NWDI developement configuration for ESS,when I'm  tring to activate the DC's, Here i'm getting error in action view log
    CBS Build Log - [  NDV_NDVDEV_D/sap.com_SAP_ESS_1/default/  /sap.com/ess/us/pdata 
    No build log available. The DC has not been built in this request.
    anybody help me on this.
    Edited by: MaheeshReddY on Jan 28, 2010 10:47 AM
    Edited by: MaheeshReddY on Jan 28, 2010 10:48 AM
    Edited by: MaheeshReddY on Jan 28, 2010 10:56 AM

    Hi MaheeshReddY,
    Did you try building you project locally (locally means just right click your DC and chose the option DC-->Build) first? if no then please do it, after building please check the build log whether it contains any errors or not?
    Case 1:
    If the errors are present then resolve those errors first, then check in your activities into DTR, because if you have checked in your activity without resolving build errors, and then if you try activating those activities with "Activate even if Build Fails option checked, then it will result in a failure.
    Case 2:
    If the build is successful then please check whether any components that are present locally but not on DTR.
    Any required dependency that you might have forgotten to check-in. In such a scenario your local build will be successful as your required dependency is present in local environment, but when you will activate the changes. the CBS will not be able to process the complete build request as the dependecies that are required are still not checked into the DTR and hence missing. So untimately the end result comes out as an activation failure.
    Regards,
    Shreyas Pandya

  • Cannot create SAPUI5 UI Component from a BPM Process

    Dear friends,
    For a very strange reason I am not able to create a SAPUI5 UI Component from a BPM Process. I am trying to create SAPUI5 UI's for an Human task as part of my BPM process. I am using NWDS 7.3 EHP1 SP15 PAT0000.
    We are using NWDI development configuration.
    The error log shows the following error:
    BC-BMT-BPM-CMP#      [Error: com.sap.glx.ide.flow.util.logger.IDEAbstractDynamicParticipant$TRACEENTRIES  Thread[main,6,main]]
    If I try to do the same under my LocalDevelopment I'm able to create a SAPUI5 component.
    Any ideas what could be causing this issue or where to look for more information about the error?
    Thank you in advance,

    Does anyone has any idea? This is rather urgent...
    Thank you,

  • Error while Creation on Track(create/save) CBS authorization exception?

    Hi All,
    I am trying to create Track in CMS in NWDI. When I am saving after importing relevant SC (ESS/MSS),
    I got below error while saving.
    CBS (URL http://sapdevep:50000/tc.CBS.Appl/archiveapi2/) authorization exception: User not authorized to log into build server. ( Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://sapdevep:50000/CBSWebService/CBSHttpSOAP?style=rpc" )
    request you guide me for this problem.
    Thanks,
    Rafi Shaik

    Rafi,
    You might want to refer to this
    Cannot create a new track:  User not authorized to log into build server
    Also check this SAP Note
    #840523 -- NWDI server configuration: user, group and security role
    Thanks
    Prashant

  • SLD server exception: IO error: Read timed out

    Hi,
    I have deployed the components for NWDI and after that when i am creating the Domain,I am doing update CMS data for creating a Track. I am getting the following error:
    SLD server exception: IO error: Read timed out
    Can any one help on this.
    Thanks
    Ravi.S

    Hi,
    My SLD is a PI 7.0 system and my NWDI is configured on a standalone Java system.
    I have done the SLDDataSupplier check, and it connects fine to the SLD.
    Also on my http://<hostname>:<port>/devinf/main in the NWDI system, the SLD link points to the right SLD and im able to connect.
    Still at the CMS update stage it gives the error -
    SLD (URL http://<hostname>:<port>/) server exception: IO error: Read timed out

  • Can't create shared project in MII

    The MII architect is trying to create a shared project in the Workbench and is receiving an error. It looks to me they have something already checked out and thus cannot create the project. Could this be something wrong in the NWDI/MII configuration. Any suggestions on what I can do to find the cause?
    Here is the error:
    Error while creating the Project hierarchysahad
    [EXCEPTION]
    com.sap.xmii.contentmanagement.exception.ContentManagementException: Cannot create resource sap.com.miitest1; parent resource is checked out for create in a separate activity
    Thanks!

    Hi,
    The CE/MII system is running NW 7.11 SPS7
    The NWDI system 7.0 EHP1 SP3
    We are creating a shared project in the MII Workbench within the "File" menu "Created Shared Project".
    I'm the Technical BASIS lead here and the MII team is saying this error is a system error. I don't know enough about MII and the development environment to argue this point.
    Regards...

  • CE 7.1 Ehp1 SP5 on Oracle 10.2.0.4 Performance - XSS track import of SCAs

    Hi,
    I'm currently building a new track on my newly built CE server which has the NWDI capability configured. I've had a few problems importing the SCA files into the track. I've been getting DTR internal server errors. Looking through the logs I couldn't see a specific reason as per OSS 774339 and the subsequent notes this refers to. After restarting the CE server I've imported the SCA files individually and this has at least enabled me to get the SCA files imported without error.
    The time taken to import is very long - the ESS SCA file (290 MB) took 3.5 hours alone.
    I've read OSS 1361525 which is related to DTR performance with Oracle but the Patch provided is for 7.01 / 7.02 releases of CE.
    I have already patched my CE 7.1 Ehp1 SP5 server with the available patches for DICMS05, DICLIENTS05 & DICBS05* - there is none current available for download for the DIDTR05* CE 7.1 Ehp1 release.
    Can anyone suggest what could be done to reduce the import runtimes ?.
    I'm regularly updating the Oracle Statistics as per OSS 1229080 and the Oracle params have been set as per OSS 830576.
    Regards,
    Brian.

    Hi Ervin,
    1. The NWDI Server is a distributed configuration - the DB instance is on it's own Solaris 10 zone and the central services & instance are on another Solaris zone. Both zones have plenty CPU/Memory resources and the load values on both are low. The systems are not overloaded.
    2. THis is a new build and I'm setting up the first track to enable the customer to start a XSS development project. The first 10 or so SCs imported without error into the track. ESS, MSS & PCUI_GP SCA files are the ones remaining and are failing to import.
    3. Our OS is Solaris 10 on Sun Sparc - so no windows type anti-virus software to contend with.
    4. I've run the statistics a few times over the last day or so :-
    brconnect -u / -c -o summary -f stats -o SAPSR3DB -t all -p 8 -f nocasc
    5. Trace levels are default.
    6. The logs & traces have no OutOfMemory errors as per OSS 1001502. The error received is :-
    20100908171424 Info   :Starting Step CBS-make at 2010-09-08 17:14:24.0632 +1:00
    20100908171425 Info   :wait until CBS queue of buildspace S01_Sandbox_D is completely processed, before starting the import
    20100908171425 Info   :CBS queue of buildspace S01_Sandbox_D is completely processed. Starting the import now.
    20100908181425 Fatal  :CBS throws exception during activation:
    20100908181425 Fatal  :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out):Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out)
    The interesting thing here is that the error is thrown exactly one hour after the CBS-make operation starts.
    7. We've got Oracle DB.
    Hopefully you'll be able to suggest how best I can resolve the error and continue.
    Also - from the logs there was further error activity for this same import operation 3 hours later after I'd gone home  :-
    #2.#2010 09 08 21:34:50:064#+0100#Info#/Applications/CBS/Service#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200680000000E000004DB#14060650000000783##com.sap.tc.cbs.server.rt.rq.RequestOrc####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[CBS Request Orc,5,SystemThreadGroup]#Plain##
    Request arranged for processing for BuildSpace S01_Sandbox_D. [bsID:3, rID:62, node:14060650]#
    #2.#2010 09 08 21:34:50:086#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000006F000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Build number assigned: 67#
    #2.#2010 09 08 21:34:50:088#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000070000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Change request state from QUEUED to PROCESSING#
    #2.#2010 09 08 21:34:50:095#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000071000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:096#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000072000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    REQUEST PROCESSING started at 2010-09-08 20:34:50.095 GMT#
    #2.#2010 09 08 21:34:50:098#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000073000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        ACTIVATION request in Build Space "S01_Sandbox_D" at Node ID: 14,060,650
            [id: 62; parentID: 0; type: 4]
            [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]#
    #2.#2010 09 08 21:34:50:149#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000074000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:150#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000075000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        Waiting for access: 54 ms#
    #2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000076000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000077000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        ===== Pre-Processing =====  started at 2010-09-08 20:34:50.150 GMT#
    #2.#2010 09 08 21:34:50:152#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000078000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            List of requested for activation activities:#
    #2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000079000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                ''sap.com_SAPPCUI_GP_1'' compartment#
    #2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007A000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                    CMS_sap.com_SAPPCUI_GP_590_aabfda99de4511d9b84800300530c04f#
    #2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007B000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                        [ISN 2][created by MAIN at 2010-09-08 17:14:24.0][OID e4fdda79781d11dec2470030057116fe]#
    #2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007C000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                There is 1 activity in compartment sap.com_SAPPCUI_GP_1#
    #2.#2010 09 08 21:34:50:186#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007D000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                1 activity will be processed by this request#
    #2.#2010 09 08 21:34:50:647#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007E000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007F000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze dependencies to predecessor activities... started at 2010-09-08 20:34:50.647 GMT#
    #2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000080000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Analyzing predecessors in compartment "sap.com_SAPPCUI_GP_1"#
    #2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000081000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                    No dependencies to predecessor activities found.#
    #2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000082000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze dependencies to predecessor activities... finished at 2010-09-08 20:34:50.669 GMT and took 22 ms#
    #2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000083000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000084000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze versions... started at 2010-09-08 20:34:50.670 GMT#
    #2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000085000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                ===== Pre-Processing =====  finished at 2010-09-08 20:34:50.711 GMT and took 561 ms#
    #2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000086000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Change request state from PROCESSING to FAILED#
    #2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000087000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Error! The following problem(s) occurred  during request processing:#
    #2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000089000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Error! The following error occurred during request processing:Server error [500 Internal Server Error]#
    #2.#2010 09 08 21:34:50:714#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008B000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            REQUEST PROCESSING finished at 2010-09-08 20:34:50.714 GMT and took 619 ms#
    #2.#2010 09 08 21:34:50:728#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008C000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Regards,
    Brian.

  • CMSPermissionDeniedException

    Hi.. My system is
    sap.com/SAP-JEECOR  6.40 SP12 (1000.6.40.12.0.20050510033908)  20051122131622 
    sap.com/SAP-JEE  6.40 SP12 (1000.6.40.12.0.20050510034043)  20051122131702 
    i try to import configuration using NW Developer Studio to our NWDI server.
    But i hit error :
    internal CMS connector error: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
    com.sap.cms.client.ideAPI.CmsException: internal CMS connector error: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
         at com.sap.cms.client.ideAPI.CmsConfiguration.getConfiguration(CmsConfiguration.java:35)
         at com.sap.ide.eclipse.component.devconf.DevConfManager.getDevConfStream(DevConfManager.java:424)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.getInputStream(DevConfWizard.java:93)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.initDevConf(DevConfWizard.java:327)
         at com.sap.ide.eclipse.component.wizard.LoadDevConfPage.getNextPage(LoadDevConfPage.java:343)
         at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:677)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:316)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.eclipse.component.provider.actions.DevConfNewMenuAction.openWizard(DevConfNewMenuAction.java:39)
         at com.sap.ide.eclipse.component.provider.actions.DevConfNewMenuAction.run(DevConfNewMenuAction.java:33)
         at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
         at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:207)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
         at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
         at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
         at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:791)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:604)
    This is from Cms.log
    3:01:34 PM com.sap.cms.client.ideAPI.CmsConfiguration [main] PATH: -> 15:1:34 -> entering getConfiguration
    3:01:34 PM com.sap.cms.client.ideAPI.CmsConfiguration [main] DEBUG:   cmsServer = http://cias109:50000; configurationId = dev_devcias_D; user = muda
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: -> 15:1:34 -> entering CMSEncoder
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: <--- exiting CMSEncoder
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering CMSConnector(url)
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   is a sender (service = organizer)
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   cmsServer = http://cias109:50000/CMS/Organizer
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting CMSConnector(url)
    3:01:34 PM com.sap.cms.client.organizerAPI.CMSTransportOrganizerAPI [main] PATH: -> 15:1:34 -> entering getConfiguration
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering createConnection
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   connection object http://cias109:50000/CMS/Organizer got
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] PATH: -> 15:1:34 -> entering CMSParser
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] PATH: <--- exiting CMSParser
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting createConnection
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering writeXMLHeader
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting writeXMLHeader
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   encode object: id = cmsService
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: -> 15:1:34 -> entering objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] DEBUG:   convert object java.lang.String to XML (id = cmsService)
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: <--- exiting objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   encode object: id = user
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: -> 15:1:34 -> entering objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] DEBUG:   convert object java.lang.String to XML (id = user)
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: <--- exiting objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   encode object: id = configurationId
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: -> 15:1:34 -> entering objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] DEBUG:   convert object java.lang.String to XML (id = configurationId)
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: <--- exiting objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering callMethod
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   encode object: id = cmsMethod
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: -> 15:1:34 -> entering objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] DEBUG:   convert object java.lang.String to XML (id = cmsMethod)
    3:01:34 PM com.sap.cms.client.connector.CMSEncoder [main] PATH: <--- exiting objectToXML
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting encodeObject
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: -> 15:1:34 -> entering writeXMLFooter
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] PATH: <--- exiting writeXMLFooter
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   connected to http://cias109:50000/CMS/Organizer
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   *** [0] value = 
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   *** [0] value = com.sap.cms.util.exception.misc.CMSPermissionDeniedException
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   valueString =   + com.sap.cms.util.exception.misc.CMSPermissionDeniedException
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   *** [0] value = User is not allowed to do this function
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   *** [0] end value tag: type = null
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] PATH: -> 15:1:34 -> entering isExceptionRaised
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   exceptionRaised = true
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] PATH: <--- exiting isExceptionRaised
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] PATH: -> 15:1:34 -> entering getException
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   exception = com.sap.cms.util.exception.misc.CMSPermissionDeniedException message = User is not allowed to do this function
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] ERROR: exception class not found Exc=java.lang.ClassNotFoundException: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
    3:01:34 PM com.sap.cms.client.connector.CMSParser [main] DEBUG:   stack trace: Exc=java.lang.ClassNotFoundException: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
         at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:866)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:141)
         at com.sap.cms.client.connector.CMSParser.getException(CMSParser.java:401)
         at com.sap.cms.client.connector.CMSConnector.callMethod(CMSConnector.java:224)
         at com.sap.cms.client.organizerAPI.CMSTransportOrganizerAPI.getConfiguration(CMSTransportOrganizerAPI.java:133)
         at com.sap.cms.client.ideAPI.CmsConfiguration.getConfiguration(CmsConfiguration.java:33)
         at com.sap.ide.eclipse.component.devconf.DevConfManager.getDevConfStream(DevConfManager.java:424)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.getInputStream(DevConfWizard.java:93)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:126)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:612)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:582)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:712)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:606)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:791)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:604)
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] ERROR: internal CMS connector error Exc=com.sap.cms.client.connector.CMSParserException: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
    3:01:34 PM com.sap.cms.client.connector.CMSConnector [main] DEBUG:   stack trace: Exc=com.sap.cms.client.connector.CMSParserException: com.sap.cms.util.exception.misc.CMSPermissionDeniedException
         at com.sap.cms.client.connector.CMSParser.getException(CMSParser.java:404)
         at com.sap.cms.client.connector.CMSConnector.callMethod(CMSConnector.java:224)
         at com.sap.cms.client.organizerAPI.CMSTransportOrganizerAPI.getConfiguration(CMSTransportOrganizerAPI.java:133)
         at com.sap.cms.client.ideAPI.CmsConfiguration.getConfiguration(CmsConfiguration.java:33)
         at com.sap.ide.eclipse.component.devconf.DevConfManager.getDevConfStream(DevConfManager.java:424)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.getInputStream(DevConfWizard.java:93)
         at com.sap.ide.eclipse.component.wizard.DevConfWizard.performFinish(DevConfWizard.java:126)
         at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:608)
         at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:321)
         at org.eclipse.jface.dialogs.Dialog$1.widgetSelected(Dialog.java:423)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.jface.window.Window.runEventLoop(Window.java:583)
         at org.eclipse.jface.window.Window.open(Window.java:563)
         at com.sap.ide.eclipse.component.provider.actions.DevConfNewAction.run(DevConfNewAction.java:46)
         at com.tssap.selena.model.extension.action.SelenaActionCollector$GenericElementActionWrapper.run(SelenaActionCollector.java:229)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.processInternal(MenuFactory.java:612)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.access$100(MenuFactory.java:582)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction$BusyProcessWorker.run(MenuFactory.java:712)
         at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
         at com.tssap.util.ui.menu.MenuFactory$DelegateAction.process(MenuFactory.java:606)
         at com.tssap.util.ui.menu.internal.MenuListenerFactory$ProcessAdapter.widgetSelected(MenuListenerFactory.java:172)
         at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
         at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
         at com.tssap.util.startup.WBLauncher.run(WBLauncher.java:79)
         at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
         at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.ide.eclipse.startup.Main.basicRun(Main.java:291)
         at com.sap.ide.eclipse.startup.Main.run(Main.java:791)
         at com.sap.ide.eclipse.startup.Main.main(Main.java:604)
    anyone could help me ? tag
    Message was edited by: Muda Ikhsan

    Hi Muda,
    I assume you refer to the Development Configuration import (triggered in your NWDS) in order to get the track from the server side.
    Please check whether you are doing this operation at least with an NWDI Developer user.
    #840523 - NWDI server configuration: user, group and security role
    (http://service.sap.com/sap/support/notes/840523)
    An other useful test would be to logon to the NWDI (in NWDS) using the NWDI Administrator user you have also maintained on the Domain Data tab of the Landscape Configurator of the CMS webui and attempt the import with this user. If that works, then you need to doublecheck the permissions of the other user as per the above mentioned note.
    Best Regards,
    Ervin

Maybe you are looking for

  • Unable to open WAD (web application designer) in BW 3.5!

    Hi, when i open WAD through menu path (start->programs        ->Business explorer->Web application designer), i am getting the following error! WADConst Please log on to a Netweaver BI 7.x system. System J2E does not have the minimum version required

  • Connect HDMI notebook to Thunderbolt iMac

    I just ordered an iMac 21,5" and would like to use it also as an external monitor for my PC. Does anybody know how to connect the HDMI interface of my notebook with the Thunderbolt interface of the iMac?

  • Common Header in each page in WP8

    Hi, I am creating a Windows Phone application.I have a common header that I have to display in each page.Is there a way to create a common UI that could be included in every xaml page.If yes, then how can I do it?

  • Help on access restrictions

    Hi everyone. Thanks for reading this. I'm using a WRT54GS wireless router. My boss asked me to create a policy in this router in order to: 1. Block Windows Live Messenger ports in two computers. Searching some other threads I've found that I have to

  • Going from Sybase to Oracle

    Hi. I'm kind of new at this, so please bear with me. We're moving from Sybase towards Oracle, and there we have a problem. I'd like to know if you have to change the way you make the Java SQL-queries, in order to make it work with Oracle DB's. Any he