Installation Error

[Crust]

This is one of the critical issues from our customer, trying to install our application.
User is an adminstrator
He has tried both cmd line and normal install process.

Please look into it. Help would be much appreciated!


Error:-Cannot create the directory. C:\users\A67ED~1\AppData\Local\Temp\miaE5DB.tmp\mySetup.exe. A file with this name already exists. Please rename or remove the file and click retry or click Cancel to exit.
Here are the excerpts from installation log:


*** MSI Database ***
C:\Users\A67ED~1\AppData\Local\Temp\mia1\MySetup.msi

*** GUID ***
{63DF23E8-2D93-4019-AAB9-621921C48B5E}

*** Data Directory ***
C:\PROGRA~3\{7CA10~1
*** Media Directory ***
\PROGRA~3
*** MSI Directory ***
C:\Users\A67ED~1\AppData\Local\Temp\mia1

MSI (s) (24:E4) [11:33:09:072]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
MSI (s) (24:E4) [11:33:21:283]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:21:331]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (24:E4) [11:33:21:409]: Product: MySetup-- Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.

MSI (s) (24:E4) [11:33:21:492]: Note: 1: 1312 2: C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe
MSI (s) (24:E4) [11:33:21:500]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:21:508]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
MSI (s) (24:E4) [11:33:22:532]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:22:558]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (24:E4) [11:33:22:566]: Product: MySetup-- Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.

MSI (s) (24:E4) [11:33:22:576]: Note: 1: 1312 2: C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe
MSI (s) (24:E4) [11:33:22:626]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:22:732]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
MSI (s) (24:E4) [11:33:23:382]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:23:390]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (24:E4) [11:33:23:398]: Product: MySetup-- Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.

MSI (s) (24:E4) [11:33:23:408]: Note: 1: 1312 2: C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe
MSI (s) (24:E4) [11:33:23:444]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:23:514]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
MSI (s) (24:C4) [11:33:24:668]: I/O on thread 4008 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:692]: I/O on thread 6376 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:748]: I/O on thread 6848 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:774]: I/O on thread 4924 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:782]: I/O on thread 7460 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:790]: I/O on thread 6884 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:799]: I/O on thread 8020 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:842]: I/O on thread 8604 could not be cancelled. Error: 1168
MSI (s) (24:C4) [11:33:24:881]: I/O on thread 8536 could not be cancelled. Error: 1168
MSI (s) (24:E4) [11:33:24:889]: Note: 1: 2205 2: 3: Error
MSI (s) (24:E4) [11:33:24:897]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (24:E4) [11:33:24:906]: Product: MySetup-- Error 1312. Cannot create the directory 'C:\Users\A67ED~1\AppData\Local\Temp\miaE721.tmp\MySetup.exe'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.

[FrancescoT]

Dear Crust,

are you installing the package under SYSTEM account?

Regards

[Crust]

Thanks for a response.

No, when I see the install process in task manager, it shows that it runs as user (myname); which is administrator.

[FrancescoT]

Dear Crust,

... are you sure it runs under your user context?

I am saying this because, it seems strange to me the user name within the path reported with the error; "C:\users\A67ED~1\AppData\Local\Temp\miaE5DB.tmp\mySetup.exe".

So with the above path, your user context should be something as "A67ED~1".

In addition, are you able to replicate the issue Always or with a particular target machine only?


Regards

[Crust]

Yes, it does run under user context. But that's the problem.
Its' happening with 2 of our customers.
One user is A67ED and other is Workstation
but the error are being reported in paths like:-
C:\users\A67ED~1\AppData\Local\Temp\miaE5DB.tmp\mySetup.exe".
C:\users\Workstation~1\AppData\Local\Temp\miaE5DB.tmp\mySetup.exe".

Not sure if they are running setup under a domain account and if that's causing the problem.

[FrancescoT]

Dear Crust,

if your customers are installing the package via domain deploy, it is probably the case that it runs under SYSTEM ACCOUNT anf if it's this the case, I suggest you to have a look at the following link;
http://www.installaware.com/forum/viewtopic.php?f=2&t=6658&start=15&hilit=user+account

Otherwise, it may be a problem caused by a security policy or account restriction.

Regards