on 02-19-2016 6:55 AM
Hallo everyone,
when trying to release activities on OS level I get the following error "workspace name does not exist" how can solve this?
Thanks in advance
Klaas,
Hello Klaas,
on OS level you mean when using the CMS Tool ?
What is the command you are using exactly ?
Could you please also doublecheck in the DTR webui (http://<host>:<port>/dtr) if the workspace is really there ?
Thanks and Regards,
Ervin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Klaas,
could you please copy here (or attach as file) the complete trace error you have when the release command fails ?
Take a look at this too
RELEASE / REL - Using Java - SAP Library
Thank you and Regards,
Ervin
Hello,
I meant first of all the exception you face in the output of the cmstool, but I understand it is most likely nothing more than what you sent as the title of this thread.
Perhaps there was a process now perfectly complete during a specific track operation. This case we often suggest to simply re-save the track in CMS Webui (Landscape Configurator -- Track Data -- select the track in question, change say the description only in order to have a dummy change and press save)
This helped in the past:
CMSUnexpectedException: Workspace name does not... | SCN
I hope it helps you as well.
Regards,
Ervin
Hi Klaas,
Can you try listing this way ?
la –s sap.com_R4_Interfaces -w –u <your nwdi admin username>
Also, as I can see on the sent screenshot you have a very similar other workspace (R4_INTERFACES) and I am wondering whether that caused any trouble. Can you create a dummy activity in any other workspaces to see whether you run into the same problem? You can use dtr webui to create such an activity. Maybe this way we can isolate the problem to see if it is a general one or workspace specific.
Regards
Ervin
Hello,
you could try but I doubt it'd help.
Deleting the CBS buildspace is called Buildspace reset (How to reset CBS buildspaces - Java Development - SCN Wiki) After track re-save you can get back your buildspaces (plus you need to reimport all SCs to dev and cons to get back to the original state before you deleted the buildspaces, afaik we described this in the above doc).
But the problem is you got problems in DTR and with the workspaces which I think the above action won't affect.
I am kind of thinking now this track might be corrupted somehow. If you cannot reproduce this with other tracks, then I am even more confident this could be perhaps the case.
Also wondering what would happen if you'd replicate this track to another track with a different name and see whether you got problems with that one. Here you can read about replication Replicating a Track into a Different DTR Repository - Using the Development and Production Infrastru...
Regards,
Ervin
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.