Page 1 of 1

Not a valid short file name

Posted: Mon Sep 02, 2013 3:32 am
by damoando
My install failes with message:

"<UserID> is not a valid short file name"

where user-id is my 9 charatcer ID.


I ran in logging mode. The related error lines in the log are:

MSI (s) (C8:38) [23:03:09:346]: Note: 1: 1325 2: E01940091
MSI (s) (C8:38) [23:03:09:346]: Note: 1: 2205 2: 3: Error
MSI (s) (C8:38) [23:03:09:346]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1325
Error 1325. 'E01940091' is not a valid short file name.
MSI (s) (C8:38) [23:03:12:299]: Note: 1: 2205 2: 3: Error
MSI (s) (C8:38) [23:03:12:299]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (C8:38) [23:03:12:299]: Product: Embarcadero ERStudio Data Architect 9.5 -- Error 1325. 'E01940091' is not a valid short file name.


Thansk,
Damian

Re: Not a valid short file name

Posted: Mon Sep 02, 2013 10:01 am
by FrancescoT
Dear Damian,

I am very sorry, but it is not really easy to find the source of your issue by the only information supplied.

What do you men exactly with "where user-id is my 9 characters ID"?

Regards.

Re: Not a valid short file name

Posted: Mon Sep 02, 2013 2:21 pm
by damoando
Hi

'E01940091' is my windows ID. My assumption is that the install is attempting to create an 8.3 file name using this but is failing since my ID is 9 chars long.

This is purely guess work but is consistent with the error messages.

I have attached the full log from the failed install.

Thanks,
Damian

Re: Not a valid short file name

Posted: Tue Sep 03, 2013 11:18 am
by FrancescoT
Dear Damian,

for what I see by your log, the installation fails due the 1603 error.

Very probably a file or a component that you are installing or updating, it is in use by another process and due of this, the installation can't continue.

Regards.

Re: Not a valid short file name

Posted: Wed Sep 04, 2013 3:26 am
by damoando
Hi

Thanks for your reply.

The error you mention occurs after the actual error that genertes the pop-up.

The entries in the log file that relate to the real issue, I believe, are:

MSI (s) (C8:38) [23:03:09:346]: Note: 1: 1325 2: E01940091
MSI (s) (C8:38) [23:03:09:346]: Note: 1: 2205 2: 3: Error
MSI (s) (C8:38) [23:03:09:346]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1325
Error 1325. 'E01940091' is not a valid short file name.
MSI (s) (C8:38) [23:03:12:299]: Note: 1: 2205 2: 3: Error
MSI (s) (C8:38) [23:03:12:299]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (C8:38) [23:03:12:299]: Product: Embarcadero ERStudio Data Architect 9.5 -- Error 1325. 'E01940091' is not a valid short file name.


Thanks,
Damian

Re: Not a valid short file name

Posted: Thu Sep 05, 2013 8:49 am
by FrancescoT
Dear Damian,

if you look at your log file, the "E01940091" value is assigned as LogonUser = E01940091.
This seems to be and for what reported by your log, the value for the the User Account context returned to the MSI engine and under where the process is running.

If fact, often in your log there are references to the "C:\Users\E01940091" root.

It is true that entries in the log file that relates to: "Error 1325. 'E01940091' is not a valid short file name." occurs before of the 1603 error ... but the error returned by the MSI engine is 1603.

I may suggest you at first, to verify if the files you are installing or one of them, it is not in use and then to verify what happens with using a different user context account.

Regards