> I thought a patch installer (.MSP) did not have a UI. You might have a
> more controlled environment, but without a UI we couldn't prompt for SQL
> credentials and thus couldn't run SQL Scripts in a patch. If you can
> hard code credentials or there actually is some way to display a dialog
> to
> > This fails giving the following error in the log.
> >
> > Action start 11:04:08: InstallSqlData.
> > InstallSqlData: Error 0x80070006: failed to get size of stream
> > InstallSqlData: Error 0x80070006: failed to read SqlScripts table
>
> Try using pyro's -notidy argument. Very helpful to
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Petersen
Sent: Wednesday, July 16, 2008 10:50 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SqlScript, XmlFile, Pyro and patching
I thought a patch installer (.MSP) did not have a UI. You might have a
more
ject: [WiX-users] SqlScript, XmlFile, Pyro and patching
Hi,
I'm trying to create a patch using Pyro (Version 3.0.4227.0). Our
product installer performs various functions, installs
executables/services, runs SqlServer scripts, configures settings files
based upon user settings etc. I now w
Colin Law wrote:
> This fails giving the following error in the log.
>
> Action start 11:04:08: InstallSqlData.
> InstallSqlData: Error 0x80070006: failed to get size of stream
> InstallSqlData: Error 0x80070006: failed to read SqlScripts table
Try using pyro's -notidy argument. Very helpful
Hi,
I'm trying to create a patch using Pyro (Version 3.0.4227.0). Our product
installer performs various functions, installs executables/services, runs
SqlServer scripts, configures settings files based upon user settings etc. I
now wish to create a patch to update installed files, but also ex
6 matches
Mail list logo
