Possible bug in Bootstrapper run from UNC drive - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

MikeMurnane
Posts: 30
Joined: Wed Dec 08, 2010 5:46 pm

Possible bug in Bootstrapper run from UNC drive

Then I packaged my Setup.exe and MSI all together at: Media/Bootstrapper tab under package - I choose "Include install files in EXE" and under "Install Options"set "Extract Location" to [SETUPEXEDIR] ... then the Setup Part runs but when it tries to start up the MSI I get "Could not access Network Location". I have attached a screen shot of the message because the path that it is using is the bug. The path ends in two slashes which if pasted into the address window of a windows explorer will generate the same message.

I have "solved" the problem by choosing "Leave install files outside".
Attachments
Picture of the network location after executing Setup.exe -- just as it tries to start the MSI install.
Picture of the network location after executing Setup.exe -- just as it tries to start the MSI install.
edcFiler1_Access.jpg (360.26 KiB) Viewed 4350 times
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Possible bug in Bootstrapper run from UNC drive

Hi,

Most likely it doesn't have write privileges for the network path. If you use SETUPEXEDIR for the extraction path, the bootstrapper will extract files next to it. Therefore, it needs privileges to write files in that location.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MikeMurnane
Posts: 30
Joined: Wed Dec 08, 2010 5:46 pm

Re: Possible bug in Bootstrapper run from UNC drive

It does have write privileges - you can see that the Setup.exe has already extracted both the BookCitationBuilder.MSI and the disk1.cab file. It is the file path with the two slashes at the end that is the problem ... and as far as I can see that is internally generated.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Possible bug in Bootstrapper run from UNC drive

Hi,

Can you please send us the .AIP (project) file you are using to support at advancedinstaller dot com so we can investigate it?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Possible bug in Bootstrapper run from UNC drive

Hi,

Indeed, this is a bug in the bootstrapper. It's not related to UNC paths, it's actually a problem caused by the trailing backslash in SETUPEXEDIR. A bugfix will be included in the next release. Thank you for bringing it to our attention.

Until then a solution is to use an extract location which is not ended in a backslash, for example:

Code: Select all

[SETUPEXEDIR]install
Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”