Error 1606 - 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!

tsellman
Posts: 24
Joined: Fri Sep 14, 2012 2:37 pm

Error 1606

New to installers...

System running windows XP. Did import of current products msi. Made what I thought were
the requisite changes. On invoking the newly built msi file, I get the "Could not access network location Allworx\OfficeSafe Service"
message. Looking at the log, I believe it's trying to use the APPDIR property. I would have thought this should contain the
value that the 'Application Folder' field (which is defined as [ProgramFilesFolder][Manufacturer]\[ProductName] on the Install Parameters tab
evaluates to. In the tool, 'Application Folder' does evaluate to "C:\Program Files\Allworx\OfficeSafe Service", but the log file indicates its
value is simply 'Allworx\OfficeSafe Service'. I am also suspicious that on the 'Files and Folders' tab, when examining the properties
of the Application Folder, the Source Name is '.'
Attachments
OFSImportCfg.aip
install config file
(95.52 KiB) Downloaded 345 times
AI_LOG.log
msi install log file
(82.8 KiB) Downloaded 270 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Error 1606

Hello and welcome to Advanced Installer forums,

This is very strange. Normally, as your project is set, the DIRCA_TARGETDIR custom action should never get executed.

Can you please try removing this custom action from both stages and see if the error persists?

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tsellman
Posts: 24
Joined: Fri Sep 14, 2012 2:37 pm

Re: Error 1606

Thank you very much! Your suggestion to remove the two custom actions solved
my issue. The install proceeded much further.

I have two other questions that arise:

(note: the MSI file that I imported from originally was from a previous developer and visual studio imbedded tools. Therefore,
some of the parameters derived during the import process may be leftover from non-completed attempts during install
development)

1. As defined now, I don't get any EULA dialog. I believe that this is due to the 'Next' button on the "First Time Install" WelcomeDlg
being set to bring up the folder dialog. Related to my note above, it appears to be two different EULA dialogs that are unused.
Would a possible correction be to re-define the 'Next' button event (Display a specific dialog) to use an argument of "EulaDlg" ?

2. This installer is to start a service. At one point (line 1270) in the log file (see attached), the attempt to start the
service occurs. In real-time, the installer seems to be paused for a bit, then eventually an error 1920 (failed to start... check privileges...)
is display. If that error is 'ignored', the installation proceeds and ultimately the service is actually installed and is running.

I assume that this has something to do with the 'automatic' value of the 'Start type' in the 'Services to Install' property for OfficeSafeService
(on the Service Properties tab).

Should I not have a Control Operations item for OfficeSafeService ? I don't understand the first attempt for the service install
as the logging messages imply that there's something going on within the registry.

Can you add any insight?

Thanks again
Attachments
AI_LOG.log
log file from running the install
(351.46 KiB) Downloaded 256 times
OFSImportCfg.aip
install configuration
(95.2 KiB) Downloaded 327 times
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Error 1606

Hello,

You're welcome, glad to help !
the MSI file that I imported from originally was from a previous developer and visual studio imbedded tools. Therefore,
some of the parameters derived during the import process may be leftover from non-completed attempts during install
development
Please keep in mind that the import features in Advanced Installer (the Repackager, the Import MSI feature etc.) are intended to be used to get a starting point for your installation package, not to completely reproduce other installation packages. After repackaging an installation or importing an .MSI some adjustments may be necessary in order to obtain a working installation package.
As defined now, I don't get any EULA dialog. I believe that this is due to the 'Next' button on the "First Time Install" WelcomeDlg
being set to bring up the folder dialog. Related to my note above, it appears to be two different EULA dialogs that are unused.
Would a possible correction be to re-define the 'Next' button event (Display a specific dialog) to use an argument of "EulaDlg" ?
You can add the LicenseAgreementDlg from the Dialogs page. Also, here are the Using the Dialog Editor tutorials.
This installer is to start a service. At one point (line 1270) in the log file (see attached), the attempt to start the
service occurs. In real-time, the installer seems to be paused for a bit, then eventually an error 1920 (failed to start... check privileges...)
is display. If that error is 'ignored', the installation proceeds and ultimately the service is actually installed and is running.
Here are a couple threads debating this sort of error:
Error 1920. Failed to start service.
Setup for windows service with special account

Also, here is the service installation tutorial that may also help:
Creating a Java Service Installation

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”