Bjammin
Posts: 29
Joined: Thu Jan 24, 2008 4:14 pm

Invalid Drive error

Getting an "Invalid Drive" (S:\) error on a client's PC. I know this has been installed on other PC, including some of ours without this issue. Install was built with Advanced Installer 17.7 Client PC is Windows 10... Log file is attached.

The log file doesn't help me find what it could be, but I bet it does.

Thank you for your help.
Attachments
Advandced Install Log - Invalid Drive.txt
(402.33 KiB) Downloaded 409 times
Bjammin
Posts: 29
Joined: Thu Jan 24, 2008 4:14 pm

Re: Invalid Drive error

Also, the "S:" drive is a valid drive.
Bjammin
Posts: 29
Joined: Thu Jan 24, 2008 4:14 pm

Re: Invalid Drive error

I have the same error with another client. Attached is another log.
Attachments
Advanced Installer Invalid drive 2 Breslin.txt
(403.54 KiB) Downloaded 313 times
Bjammin
Posts: 29
Joined: Thu Jan 24, 2008 4:14 pm

Re: Invalid Drive error

Guessing what is wrong is that the clients' Network Admins have drives mapped under the user account, but not for the Admin account. Hence the drive can't be found after permission is elevated. But seeing that I've had thousands of installs in the 13 years I've used this product, I doubt these are the first 2 bad network admins I've run into. Seems like a bug in a newer version of Advanced Installer or maybe more likely MSI. Wanting to know for sure if anybody does know. Error 1327 causing "Invalid Drive X:" message. Thanks.
Catalin
Posts: 7513
Joined: Wed Jun 13, 2018 7:49 am

Re: Invalid Drive error

Hello,

By having a look over the log file, we can see that it is the CostFinalize action that is failing.

As you may know, the above is a standard action, meaning it is proprietary to the Windows Installer technology (not to Advanced Installer).
CostFinalize: ends the disk space costing and resolves the folders in the project
In both logs, the SHGetFolderPath function returns a different drive for known folders:
MSI (c) (DC:E8) [11:15:44:064]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming
MSI (c) (DC:E8) [11:15:44:064]: SHELL32::SHGetFolderPath returned: C:\Users\User\Favorites
MSI (c) (DC:E8) [11:15:44:064]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (DC:E8) [11:15:44:065]: SHELL32::SHGetFolderPath returned: S:\Linda\Documents
MSI (c) (DC:E8) [11:15:44:065]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (DC:E8) [11:15:44:065]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (DC:E8) [11:15:44:066]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming\Microsoft\Windows\SendTo
MSI (c) (DC:E8) [11:15:44:066]: SHELL32::SHGetFolderPath returned: C:\Users\User\AppData\Roaming\Microsoft\Windows\Templates
...
(from the first log)
MSI (c) (4C:48) [09:58:01:002]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\AppData\Roaming
MSI (c) (4C:48) [09:58:01:003]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\Favorites
MSI (c) (4C:48) [09:58:01:003]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (4C:48) [09:58:01:003]: SHELL32::SHGetFolderPath returned: U:\My Documents
MSI (c) (4C:48) [09:58:01:003]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (4C:48) [09:58:01:003]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (4C:48) [09:58:01:004]: SHELL32::SHGetFolderPath returned: C:\Users\Barbara Breslin\AppData\Roaming\Microsoft\Windows\SendTo
...
(from the second log)

As we can see, all the other known folders are resolved using the default drive (C:\).

Judging by this information, I'd say that it is something specific to the PCs where the setup is installed.
Guessing what is wrong is that the clients' Network Admins have drives mapped under the user account, but not for the Admin account. Hence the drive can't be found after permission is elevated.
I can not really say for sure this is the case.

I've done a bit of digging and I've come accross the following Technet forum thread:

MSI installer closes with error 1327, Invalid drive on Win 7 Ultimate when My Documents is moved to a network drive

This looks to be somehow related to the second log you have provided, where the "My Documents" folder resides on the U:\ drive.

Hope this helps somehow!

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”