Error during upload in SPAM RC=8

[former_member614155]

Hi Experts,

Can you please help me with the below error in FIORI production server. We are getting this error while uploading packages from SPAM to patch ST-PI/A-PI. Infact, none of the files are being read.

spam-error.png

Also even when uploading from front end, it gives the below error

Internal error: The path \\<hostname>\sapmnt\trans\tmp\k-74009instpi.sar is not within $(DIR_TRANS)/tmp and therefore not allowed!

Please note that the path is accessible from prod server and also the note has been checked which talks about the length of DIR_EPS_ROOT being less than 60 characters.

Regards,

Vishwanath

[S_Sriram]

Hi Vishwanath.

Is this any authorization or permission issue? normally when you are unloading the the sar file it will go in the following path \\<hostname>\sapmnt\trans\EPS\in,in this case why its going to \tmp folder?

Is it possible to do manually uncar the file and copy the files in \EPS\In folder then try the SPAM.

Regards

SS

[former_member614155]

HI Sriram,

Thanks for the info. This has been done but even manual Uncar does not work.

Regards,

Vishwanath

[S_Sriram]

Hi Vishwanath,

Could you tell us details about the upgrade of STPI & ST-API? Why you are selected spam? share full log?

Regards

SS

[dasistdochscheisse]

Hello Vishwanath,

check the access to DIR_TRANS in Al11. If the share is located on a Windows-Server you have to set the permissions for the share and for the file system itself.

Did it work before? Can you upload the SAR file in SPAM or SAINT?

Best regards
ulf

[former_member614155]

Hi Ulf,

Thanks for the reply. I have checked DIR_TRANS in al11 as well. THe files are accessible.

It was working 1 month ago when we applied ST-PI and A/PI patches. The problem is that SAR files cannot be uploaded either via front end or via application server.

Regards,

Vishwanath

[S_Sriram]

Hi Vishwananth.

As i told you, you can manually uncar files, keep it on SAP CI folder path (Not on application server) \\<hostname>\sapmnt\trans\EPS\in and then start the SPAM to upgrade the ST-PI & ST-A/PI components.

In case of any error message could you share the screen shot and check the any error message in transaction code SM21 log

Regards

SS

[former_member614155]

This has been tried as well. PFA the screenshot. SM21 logs does not show anything related to this

st-pi-error.png

[S_Sriram]

Hi Vishwanath

1. Have you selected right version of upgrade components? From the screen shot it not showing the package name and status RC008,

2. could you share the your sap system version details and Upgrade component before and target version details?

Regards

SS

[former_member614155]

Hi Sriram,

Yes, we are currently on the below versions

ST-PI 740 0008

ST-A/PI 01T_731 0000

We have the below components downloaded since we want to update to ST-PI 740 SP11 as we have done it for dev and qa as well were we had no issues

K-74009INSTPI.SAR

K-74010INSTPI.SAR

K-74011INSTPI.SAR

Our SAP system is SAP Netweaver 7.4 SPS 16 running on MS SQL Release 11.00.6615.02

Regards,

Vishwanath

[dasistdochscheisse]

was there a change in the firewall settings?

Try to uncar the files on your desktop. Then, the path ...\EPS\in should be created in the current directory. If this does not happen, i would download the files again from SAPNet.

[S_Sriram]

Hi Vishwanath.

As you said that you have completed the upgrades in Dev & Qas systems without any issues, could you pls copy the same files either Dev or QAS \EPS\in to production system \EPC\in folder and then try to upgrade the ST-PI & ST-A/PI components.

Regards

[ImtiazKaredia]

Check SAP Note 2502557 - Error when trying to Load Packages from Application server in SPAM.

[former_member614155 · Accepted solution]

Hi All,

Apologies for the late reply. We have fixed the issues. The root cause was that there were certain security recommendation notes implemented in the DEV and QA system for "vulnerability checks at the filesystem level". THis was not moved to production. So once it was moved to prod, the SPAM extraction went through.

This is the way we backtracked the problem in order to find out the root cause

When debugged, at some point, the class CL_FS_WINDOWS_PATH is called while uploading the the files from application server.

I noticed that the behavior of this class is different in QA and Production.

The problem is the CONSTRUCTOR. If you go to se24->class CL_FS_WINDOWS_PATH -> CONSTRUCTOR, I saw that the code in QA is different than in Production. And this was due to missing note implementation in prod which was done in dev and QA. Hope this helps all in future.

Thanks all for the help

Regards,

Vishwanath