SMB - rename operation - STATUS_OBJECT_NAME_INVALID

Current Situation

• In some environments, when using the smbj provider, the rename operation fails with a STATUS_OBJECT_NAME_INVALID error.

  (STATUS_OBJECT_NAME_INVALID (0xc0000033): SetInfo failed for SMB2FileId{persistentHandle=d0 29 00 00 25 00 00 00})

Desired Behaviour

• Renaming files should work correctly.

Test Instructions

• Configure a Yade transfer with SMB as Target
• Use TransferOptions Transactional=true
• Expected result:
  • the transferred files with the atomix suffix ~ should be successfully renamed on the SMB server after the transfer

Patch

• JS7
  • Unzip the patch yade-1.13.20-PATCH-1.YADE-624.zip to the <agent install>/yade/lib/patches directory of JS7 Agent that run the YADE job.

Maintaner Notes

• This fix changes the default path separator passed to the underlying smbj library from a forward slash (e.g., a/b/c/1.txt) to a backslash (a\b\c\1.txt).
  • See:
    • smbj File separator #170
    • MS-FSCC 2.1.5 Pathname
  • If the path separator does not match the format expected by the server, it could be the cause of the ACCESS_DENIED or OBJECT_NAME_INVALID error messages.
  • This change is particularly significant when the SMB server is a Windows server or share.
• To fall back to the previous path separator in case of issues, the new sossmbj.pathSeparator property can be set.
  • Support of SMBFragment -> ConfigurationFiles by the smbj data provider:
    • the smbj specific settings can be provided with a configuration file in the following format:
      • smbj.config