nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue with filename ending with .iwtmp

btrotter

I have a deployment configured to push a security file named .htaccess to the htdocs level of several websites on a target Windows 2003 webserver. The deployment runs and the OD console indicates "completed with errors" but I don't find any errors in the logging that I can see. When I look in the htdocs folders on the target server I do see the file but instead of being named .htaccess, it is named .htaccess.iwtmp. This base and target receiver has other deployments that are working. Not sure why the file is getting this additional extention from OD and failing to deploy correctly.

Find more posts tagged with

Comments

claudiag

.iwtmp is the file extension OD adds while it's sending content over to the target. After it finishes sending over data, it should rename that file, removing the .iwtmp extension. It looks like it's failing on that step. My first thought is permissions.

Check the od receiver logs on your target.

ISCBorisB

Not sure why the file is getting this additional extention from OD and failing to deploy correctly

That's two questions

1. Why the file is getting this additional extension...

iwtmp is an extension that OD Receiver uses to create new File copy in non-transactional Deployment.
The file either gets renamed to proper target name on success or gets removed during OD "Clean Up"
phase on failure.

The very fact that File(s) with this extension are still present indicates serious Receiver (not just Deployment!)
failure sometime in the past.

2. why the file [...] failing to deploy correctly...

We do not know, there are can be various reasons. Try to analyze receiver micro log for this particular
deployment leg, you may find some error indications there.

Also, make sure that no deployment sessions are in progress and manually remove files with iwtmp extension.

Adam Stoller

Just a guess, but the pre-existing .htaccess file may be held in lock by the web server. There are options you can use in the deployment configuration to try to deal with this in some cases, in other cases you would need both a pre- and post-operative DNR script (one to stop the web server and one to restart it)