cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot exchange kernel binary archives.

Former Member
0 Kudos

I am running SUM to update NW 7.3 JAVA AS SPS2 to SPS12 and at the start of the Execution phase I am getting an error in the execution of the kernel path upgrade (see below log).  I have tried renaming the sapevents.dll file however, in the instance exe directory there is only a sapevents.dll_0.tmp file.  I have added my ssoadm user to Administrators group and given full control over the drive where the instance is installed.  When I run disp+work the version returns as 401. Please help!

Thanks,

Tamara

Jan 30, 2015 9:17:25 AM [Info  ]: Updating SAP KERNEL...

Jan 30, 2015 9:17:25 AM [Info  ]: Patching kernel SAP KERNEL UNICODE WINDOWS_X86_64 to version 7.21.401.0...

Jan 30, 2015 9:17:25 AM [Info  ]: You can find additional information in log file Y:\JAVA-AS\SUM\sdt\log\SUM\EXCHANGE_KERNEL_BINARIES_05.LOG.

Jan 30, 2015 9:17:25 AM [Error ]: Cannot move U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 using Windows console operation. 1

Jan 30, 2015 9:17:25 AM [Error ]: Cannot move file U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to directory U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 with overwrite flag true.

Jan 30, 2015 9:17:25 AM [Error ]: Could not finish Move operation with parameters fromFile '', toFile '', toDir 'U:/usr/sap/SSO/SYS/exe/uc/NTAMD64'. Check whether the current user has sufficient permission to execute this operation.

Jan 30, 2015 9:17:25 AM [Error ]: Could not execute the kernel patch. See previous messages.

Jan 30, 2015 9:17:25 AM [Error ]: Cannot exchange kernel binary archives.

Jan 30, 2015 9:17:25 AM [Info  ]: Deployment message for component SAP KERNEL UNICODE WINDOWS_X86_64 : Cannot exchange kernel binary archives.

Could not execute the kernel patch. See previous messages.

Could not finish Move operation with parameters fromFile '', toFile '', toDir 'U:/usr/sap/SSO/SYS/exe/uc/NTAMD64'. Check whether the current user has sufficient permission to execute this operation.

Cannot move file U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to directory U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 with overwrite flag true.

Cannot move U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 using Windows console operation. 1

Jan 30, 2015 9:17:26 AM [Info  ]: Overal deployment message : Deployment completed with error. See status messages for individual components.

Jan 30, 2015 9:17:26 AM [Info  ]: Saving data model Jump.JSPM.DataModel.xml ...

Jan 30, 2015 9:17:28 AM [Info  ]: Data model Jump.JSPM.DataModel.xml saved.

Jan 30, 2015 9:17:28 AM [Info  ]: Saving data model JUP.J2EE.DataModel.xml ...

Jan 30, 2015 9:17:32 AM [Info  ]: Data model JUP.J2EE.DataModel.xml saved.

Jan 30, 2015 9:17:33 AM [Error ]: The following problem has occurred during step execution: com.sap.sdt.jspm.service.JspmServiceException: Could not update components.

Deployment of queue Queue_2015.01.30 at 05:07:30 completed with error Deployment completed with error. See status messages for individual components.

sap.com/SAP KERNEL UNICODE WINDOWS_X86_64: Cannot exchange kernel binary archives.

Could not execute the kernel patch. See previous messages.

Could not finish Move operation with parameters fromFile '', toFile '', toDir 'U:/usr/sap/SSO/SYS/exe/uc/NTAMD64'. Check whether the current user has sufficient permission to execute this operation.

Cannot move file U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to directory U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 with overwrite flag true.

Cannot move U:\usr\sap\SSO\SYS\exe\uc\NTAMD64\new_kernel\vcredist_x64.msi to U:\usr\sap\SSO\SYS\exe\uc\NTAMD64 using Windows console operation. 1

.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I was able to get past this issue by removing the "Read-Only" option on the SYS directory, however now I am getting errors during the execution of the Run sapcpe for SCS.  Any thoughts?

Former Member
0 Kudos

I found that the sapevents.dll file had not been updated in the kernel update.  I manually updated the file from the new kernel. 

Answers (0)