InstallAware

When I run my installaware (v8) package on a windows 7 64 bit machine I am getting the following error:

Cannot create directory
c:\Users\64Bit\AppData\Local\Temp\miaD374.tmp\Install.exe
A file with this name already exists. Please rename or remove the file.

Indeed this file does exist, but it created by InstallAware at runtime so I don't even have the option to delete it!

Can anyone shed any light on how I can fix / workaround this? I tried checking the 64bit install option in InstallAware but I get the same message.

Thanks

Dear MattWilkinson,

Please try and clear your temp folder - I am not sure why you are receiving this error but clearing the temp folder might help. To do so, Start -> Run.. and type %temp%. Delete the files there and let me know if that helped matters.

giaviv wrote:Dear MattWilkinson,

Please try and clear your temp folder - I am not sure why you are receiving this error but clearing the temp folder might help. To do so, Start -> Run.. and type %temp%. Delete the files there and let me know if that helped matters.

I tried doing this but received the same message.
I then moved the location of the temp folder to a new drive and received the error again. This time however I could rename (but not delete) the Install.exe, which allowed the installation to continue, but this is clearly not an acceptable solution for our customers.

Dear MattWilkinson,

Then I guess that there's a problem with your code - what exactly does your installer do? Has it always behaved like this? Or was this caused by a change to your project?

giaviv wrote:Dear MattWilkinson,

Then I guess that there's a problem with your code - what exactly does your installer do? Has it always behaved like this? Or was this caused by a change to your project?

My code hasn't changed for a long time, but I think this is to do with permissions set on the files being compiled or the folders into which the files are being put. This seems to have come about after I put my package into Microsoft Team Foundation Server, which sets permissions on the files. Is there some specific issue with permissions that could cause this problem?

Dear MattWilkinson,

I am not aware of a specific issues that can cause this specific problem. However, it can very well be that your issue is caused by permission changes. Is there anyway to revert back to the original state and check if that fixes the problem?

giaviv wrote:Dear MattWilkinson,

I am not aware of a specific issues that can cause this specific problem. However, it can very well be that your issue is caused by permission changes. Is there anyway to revert back to the original state and check if that fixes the problem?

I have tried checking everything out of TFS, resetting the permissions on the folder and all sub folders and files to give everyone full control but I still get this issue. I have tried moving the whole folder to a new location, reset all the permissions again but this gives me the same error

This isn't 64 bit machine specific as I have now replicated this error on a 32 bit Windows 7 machine (a colleague has also reported the same error on a windows XP virtual machine)

Dear MattWilkinson,

I am sorry you are experiencing this. Could you please try to reinstall InstallAware (and to regenerate your license as well).
If this doesn't work, could you please send your project over to us at support at installaware.com?

I have uncovered the source of this error and believe it to be a bug in InstallAware (I have just upgraded to v10.10 and the same bug exists).

I was converting a path to a short path name. When I try to convert a path that does not exist to a short name InstallAware the path return is an invalid string.

Set a MYVAR to c:\Ptl\Data
Convert to Short Path: MYVAR
MYVAR now is set to the .exe path of the install !!

If the path exists then the short path name can be evaluated and the install works as expected. This is not as the documentation as this states: If the original path cannot be found, the command will return an empty string in the variable.

Dear MattWilkinson,

Thank you so much for your input. I will look into this and keep you posted!