CMS Import failed

[Former Member]

Hello

I have a problem with importing Content into CONS XI.

Stack trace:

Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: XiTransportException received:

ClientServerException exception:Specified object version has an invalid status. "open" was expected but "closed" was actually transferred

com.sap.aii.utilxi.misc.api.ResourceException: Specified object version has an invalid status. "open" was expected but "closed" was actually transferred

Could you help me how to solve this problem?

[Former Member]

Denis,

were u able to solve the problem. Am also facing the same issue. I am able to succefully import the MSS PSS, ASR components but not able to import ESS.

Appreciate any help.

regards

sam

[Former Member]

Hi Denis,

CMS is a sophisticated method of transporting XI objects. CMS offers sort of single window approach. Its web GUI conveniently enables importing both IR, ID objects, checking the transport logs, keeping the track of transports moved. In addition, for transport from CON to PRD system, you can designate some approval authority to regulate and approve transports to PRD system. Having said this I think it still has to evolve to offer complete tracking of changes. Unfortunately present CMS doesn’t allow you to display the objects included in the respective export list. You need to separately document it. Incidentally, CMS is not part of WAS and we additionally need to install and configure it. It is a part of JDI (Java Development Infrastructure) initially introduced for managing Java logistics.

Please go through these links which actualy show you how to configure CMS and also gives you all information regarding it.So go through these links and compare it with what you have done to actually find the cause for your error...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff7...

http://help.sap.com/saphelp_nw04/helpdata/en/de/a4214174abef23e10000000a155106/content.htm

/people/daniel.wirbser/blog/2005/10/27/tcsfilecreateexception--error-while-assembly-of-software-components-in-nwdi

/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms

/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview

http://help.sap.com/saphelp_nw04/helpdata/en/f6/719a2172f74b67b150612a7cd3b7df/content.htm

http://www.sap-hefte.de/download/dateien/964/074_lesesprobe.pdf

I hope it helps...

Regards,

Abhy

[Former Member]

greg zen,Abhy Thomas

Unfortunatelly it doesn't help

I have no idea how to fix it

In past we have DEV, CONS XI systems (SP15) and JDI ONLINE SP15, JDI OFFLINE SP 9. It works fine.

Today we have DEV, CONS, PROD XI (SP17) and JDI ONLINE/JDI OFFLINE SP17 both. It doesn't work. I have recreated a track. doesn't help.

[Former Member]

Please

Use the fully qualified sever name (for example: hostname.company.com) within the track configuration of the CMS or make the name of the CMS server known within the domain of the XI servers.

Please let me know the outcome.

[sridharreddy_kondam]

Hi Denis,

Have u checked this configuration?

http://help.sap.com/saphelp_nw2004s/helpdata/en/53/75b3407e73c57fe10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/53/75b3407e73c57fe10000000a1550b0/frameset.htm

Regards,

Sridhar

[Former Member]

I'm not using CBS Server. The problem is in Repository-import step.