Page 1 of 1

Installaware Developer - Built .EXE not deploying

Posted: Fri Apr 13, 2007 7:51 am
by NigelArnold
Hello

I purchased Installaware Developer and in general have had no problems with it. I deploy my built .EXE's as a single standalone EXE which customers download from my website.

I have one customer, who cannot install the software no matter what.

He is using Vista (I've tested it on our Vista PC's and it works fine)
He is an Administrator

Basically he gets the message

Cannot create the directory
c:\\users\\USERNAME\\AppData\\Local\\Temp\\miaF297.tmp\\myappname.exe

A file with this name already exists. Please rename or remove the file.

The customer assure's me, he has cleared down everything under c:\\users\\USERNAME\\AppData\\Local\\Temp and below and this happens everytime he runs it

Help ..
Thanks in advance

Posted: Fri Apr 13, 2007 8:46 am
by MichaelNesmith
Any conflicting anti virus software that might need disabling?

Posted: Tue May 01, 2007 12:13 pm
by HarvestInstaller
I'm getting the exact same error at one of my customers, but only on some computers.

We've verified that their anti-virus is turned off during the install.

Posted: Thu May 03, 2007 5:33 pm
by MichaelNesmith
We need more information to help you troubleshoot this issue.

Posted: Fri May 04, 2007 10:56 am
by nicocizik
Hi Michael,

I'm receiving the same error. This is occuring on my Vista machine and an XP virtual machine I built.

It's the same exact problem as described above. The install program begins installing files, then tries to create a directoy named AppName.exe in the same directory that the install .exe file is located. If I go and move the install executable, the installation continues without problems.

Inside the newly created folder \\AppName.exe\\ are a number of folders and files also included in my installation. The strange thing is that if I comment out the "Install Files" commands for these specific files, they are still installed into that extra directory. I've tried deleting any files from my project that are not needed with no success. I honestly don't know where the installer could be getting access to these files now. They technically shouldn't even be copied into the install app when I build.

Posted: Fri May 04, 2007 1:54 pm
by MichaelNesmith
There still isn't enough information for us to reproduce and resolve the issue. We need you to provide a mechanism for us to reproduce the issue before we can offer any kind of advice or resolution.

Posted: Mon May 07, 2007 5:33 pm
by nicocizik
Hi Michael,

After some further research, I isolated the problem and was able to work around it. For some reason one of my variables was not returning a value even though it was being set right above in code. I believe when the variable has no value, the Windows installer was using some sort of default directory to install the files. My suggestion to others with this issue would be to take a look at the progress text when the error occurs to see which file is being installed, then inside your script, be sure the variable you are using as the install location contains a valid value.