Hi @CheKazuAz,

It is a very generic issue and there can be several reasons for it such as,

• reinstalling the delivery without shutting down the servers.
• enabled any security scanner tool, which remove tmp files from the machine, once they are created. It is recommended to always have the security scanner tool disabled on the machine.
• running Anti Virus scan can lock files and halt the IFS Middleware Server installation process. It is recommended to always have the Anti Virus Protection disabled on the machine.
• Due to an O/S problem.

I think you have got the error for a basic requirement like having the servers started and steady during the installation. That’s why after a restart of the Middleware Server the issue has been resolved. I Hope this clears your question! If this comment satisfy you please mark it as the best answer so others will also get benefited from this post.

I had a similar experience when installing a delivery

When I check the stack trace in the log, this error “The system cannot find the path specified” was specified as a java.io.IOException.

In my case, reason was failing to create the local temporary file by IFS Connect server as the connect server service user didn’t have write access to <Extended server>\XXXX\MWS\tmp folder.

After the reconfiguration, this was solved, as it allowed the connect server to find the directory and write temporary file.

I think your situation also a similar one.

@CheKazuAz , if the error is related to certificated, it would be a different error.

Please check below posts for more details about that.

Hi Ragaventhan and Manoj,
Thank you very much for answering my question very quickly with inportant information.
They help me a lot for doing my job later.

Thank you again.
Best regards,
Kazu

What is the point of having antivirus software if you disable it for the most risky folders (like %TMP%) and at the most risky times (like software installation)? In such a situation, can you still legitimately tell your management that your machines are protected? This is like buying the strongest lock you can afford for your front door but then leaving the key taped to the door for the convenience of package delivery drivers.

If a system is compromised after following this advice, I sincerely doubt IFS will accept responsibility and underwrite the loss.

Instead, I recommend you point your IFS installer to its own private TMP/TEMP directory where it can have its own private area to play. Then when you exclude that folder from scanning, the viruses will still be caught in the standard TMP directory.

I wrote up more details here:
UPD11 delivery triggering antivirus software (Sophos) | IFS Community