Import CTS+ transport into QA Portal failed

[Former Member]

I have the following configuration in the landscape:

1. Solution Manager 7.0 (Dual Stacks) with SP15 on UNIX

2. NW 7.0 - Portal usage with SP15 (Development and QA) on Windows 2003

3. CTS+ is configured the Solution Manager as communication systems

4. Portal development system is the Source System setting

5. Portal QA systems is the target system

I could created and released the transport in Transport Organizer Web UI and the transport show in the QA buffer on Solution Manager's t-code STMS. When I tried to import into Portal QA, I got RC=12. The tp log show the epa file does not exist. I checked the file does show in AIX Unix level (/usr/sap/trans). The following the to log:

CTS Deploy Service - Version 0.92 06.03.2007

========================================================================

Deploy web service destination = CTSDEPLOY

Directory = /usr/sap/trans/data

SDM Deploy URL = http://<portal QA host name>:50018

SLD Deploy URL =

XI Deploy URL =

Non-ABAP system EPQ (communication system SMP)

Deploy for SDM

Deploy File = test_Address_20090116_114234.epa

Start of Web Service Log

Deploy Service called with following parameters:

CommunicationData-Type:0

CommunicationData-Address:http:<portal QA host name>:50018

CommunicationData-Host:<portal QA host name>

CommunicationData-Port:50018

CommunicationData-User:'filled'

CommunicationData-Password:'filled'

Deployable(0)

Deployable-Type:0

Deployable-Id:/usr/sap/trans/data/EPDK900002/test_Address_20090116_114234.epa

Returncode:'12'

class java.io.IOException:The file (\usr\sap\trans\data\EPDK900002\test_Address_20090116_114234.epa

) does not exist on the filesystem.

com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:55)

com.sap.sdm.util.sduread.impl.SduReaderImpl.readFile (SduReaderImpl.java:44)

com.sap.cts.converter.ConversionSelector.isArchiveAnSdu (ConversionSelector.java:83)

com.sap.cts.converter.ConversionSelector.execute(ConversionSelector.java:31)

com.sap.cts.core.Deployables.convert (Deployables.java:62)

com.sap.cts.core.DeployManager.deploy (DeployManager.java:57)

com.sap.cts.ejb.DeployBean.deploy (DeployBean.java:100)

com.sap.cts.ejb.DeployLocalLocalObjectImpl0_0.deploy (DeployLocalLocalObjectImpl0_0.java:103)

sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)

sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39)

sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)

java.lang.reflect.Method.invoke (Method.java:324)

com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod (EJBImplementat

ionContainer.java:126)

com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:157)

com.sap.engine.services.webservices.runtime.RuntimeProcessor.process (RuntimeProcessor.java:79)

com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost (ServletDispatcher

Impl.java:92)

SoapServlet.doPost (SoapServlet.java:51)

javax.servlet.http.HttpServlet.service (HttpServlet.java:760)

javax.servlet.http.HttpServlet.service (HttpServlet.java:853)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet (HttpHandlerImpl.java:401)

com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest (HttpHandlerImpl.java:266

)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:386)

com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:364)

com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer (RequestAnalizer.java:

1039)

com.sap.engine.services.httpserver.server.RequestAnalizer.handle (RequestAnalizer.java:265)

com.sap.engine.services.httpserver.server.Client.handle (Client.java:95)

com.sap.engine.services.httpserver.server.Processor.request (Processor.java:175)

com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process (A

pplicationSessionMessageListener.java:33)

com.sap.engine.core.cluster.impl6.session.MessageRunner.run (MessageRunner.java:41)

com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

java.security.AccessController.doPrivileged (AccessController.java:-2)

com.sap.engine.core.thread.impl3.SingleThread.execute (SingleThread.java:102)

com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

End of Web Service Log

Return Code = 12

Highest Return Code = 12

Deployment

End date and time : 20090116220312

Ended with return code: ===> 12 <===

######################################

Thanks for the help.

Regards,

Leon

Edited by: Leon Chan on Jan 17, 2009 6:11 AM

[Former Member · Accepted solution]

If the file \usr\sap\trans\data\EPDK900002\test_Address_20090116_114234.epa exists then check the permission on the file. Try to make it 775 and run again.

[Former Member · Accepted solution]

Hi Pankaj,

Thanks for the info.

I changed the permission to 775 and 777 for the file, but I still have the same the problem. Any other idea? Thanks.

Regards,

Leon

[Former Member · Accepted solution]

Check the mount point on both the system is correct. /usr/sap/trans should be mounted on both the systems. Also check on your windows box what permissions you have for /usr/sap/trans. Also do a consistency check in STMS

[Former Member]

Leon,

Please check "Note 1232674 - class java.io.IO exception during import"

As per this note.

Try checking file and folder permissions to the path of this file again.

If the file permission is fine as you said then try checking the user (<SID>adm) who is accessing this file....

You could also check the file-system space etc.

Cheers

[Former Member]

Hi, Gurus!

I have encountered the same problem while deploying CTS+ transport to the Portal (system XO3):

Returncode:'12'

class java.io.IOException:The file (
\solman.mycompany.com\sapmnt\trans\data\BIGK900007\ctsplus.par) does not exist on the filesystem.

Full log text:

       -----------------------------------------------------------------------------------------------------------------------------------------
       |   ######################################                                                                                
|   Deployment                                                                                
|   Transport request   : BIGK900007                                                                                
|   System              : XO3                                                                                
|   tp path             : tp                                                                                
|   Version and release: 372.04.71 700                                                                                
|                                                                                
|   Deploy Service called with following parameters:                                                                                
|   CommunicationData-Type:0                                                                                
|   CommunicationData-Address:http://portalXO3.mycompany.com:50218                                                                  
       |   CommunicationData-Host:portalXO3.mycompany.com                                                                                
|   CommunicationData-Port:50218                                                                                
|   CommunicationData-User:'filled'                                                                                
|   CommunicationData-Password:'filled'                                                                                
|   Deployable(0)                                                                                
|   Deployable-Type:0                                                                                
|   Deployable-Id:\\solman.mycompany.com\sapmnt\trans\data/BIGK900007/ctsplus.par                                                    
       |   Returncode:'12'                                                                                
|   class java.io.IOException:The file (\\\solman.mycompany.com\sapmnt\trans\data\BIGK900007\ctsplus.p                                
       |   >>>ar) does not exist on the filesystem.                                                                                
|   Deployment                                                                                
|   End date and time : 20100106154329                                                                                
|   Ended with return code:  ===> 12 <===                                                                                
|   ######################################              

I have checked the "Note 1232674 - class java.io.IO exception during import" and set up the full control permissions to access "\sapmnt\" for the local (solman) user SAPServiceXO3 but it does not help. The file ctsplus.par exists at the right place.

Especially strange looks the Deployable-Id:
solman.mycompany.com\sapmnt\trans\data/BIGK900007/ctsplus.par. Maybe the different slashes "\" and "/" are the cause of the porblem?

Both systems (Portal and Solution manager) run on Windows 2003 Servers. I've created a local "SAPServiceXO3" user in the server of Solman and have given to it highest permissions.

Maybe it is not the right, but is it possible in Windows 2003 to share folders to the local user of other machine?

Have anybody some ideas how to resolve the problem?

Thanks in advance.

Edited by: Mikhail Palstsianau on Jan 6, 2010 3:22 PM

Edited by: Mikhail Palstsianau on Jan 6, 2010 3:25 PM