Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Error [1601] when installing in Windows 2000 Pro S


3 replies to this topic

donghocat_phl

donghocat_phl
  • Full Members
  • 5 posts

Posted 21 January 2010 - 09:50

Hi all,
I'm working in InstallScript MSI project.
I set my app in InstallShield to install Windows Installer 3.1 before loading dialog [SdWelcome] to install my app.
When I install my app in Windows XP Pro SP1 (default version of Windows Installer is 2.0), first, my app install Windows Installer 3.1. And then loading dialog [SdWelcome] & many dialogs after that to install my app.
Here is my problem: after I press button [Install] in dialog [SdStartCopy2], a message box with error code [1601] occur: "The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or the Windows Installer is not correctly installed. Contact your support personnel for assistance. " (content of this error like this link: http://consumerdocs....0722&sliceId=1)
When I set value for property [REBOOT]="ReallySuppress" and build my project by InstallShield 2010, I fixed this error in Windows XP Pro SP1.
But when installing my app in Windows 2000 Pro SP4, I saw this error again.
I wonder if the reason is my InstallScript MSI project (I use this project type to install my app in RECORD mode & SILENT mode). Cauz I developed the same app by Basic MSI project and I didn't meet this error (I can't use this project type to install my app in RECORD mode & SILENT mode).
How can I fix this error ?
Any suggestions'll be appreciated.
Regards.

Edited by donghocat_phl, 21 January 2010 - 09:51.


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 22 January 2010 - 11:50

But in the Basic MSI project you didn't install MSI 3.1 in a custom action, but by setup.exe, so before the Windows Installer part of your install starts. If you try to update the MSI engine in your InstallScript at this point the MSI engine is already running, which might be the cause for the problem.

When using Basic MSI you don't need to record a response file. Instead you can specify the property values on the command line (each edit field, checkbox etc. has an associated property). E.g.:

msiexec /i your.msi INSTALLDIR="C:\Program Files\My custom install dir"

donghocat_phl

donghocat_phl
  • Full Members
  • 5 posts

Posted 25 January 2010 - 03:31

But when using Basic MSI project, I can't install my app in silent mode.
What should I do to fix above error in InstallScript MSI project ?

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 25 January 2010 - 11:33

QUOTE
But when using Basic MSI project, I can't install my app in silent mode.
Why not?

QUOTE
What should I do to fix above error in InstallScript MSI project ?
Don't try to update the engine when your msi setup is already running. Instead ket the setup.exe launcher handle this. You can specify this in the release wizard (I think, however I haven't used Installcript MSI in a while)