This is a snippet of the include script that is called from the main product file: <Binary Id="Sql_ServerInstall" SourceFile="Components\Data\ERS\Database\ERSServer.sql" />
<!--Execute SQL Scripts-->
<sql:SqlDatabase Id="LocalDbServer" Server="[SQLSERVER]" Database="master"
/>
<!--Server-->
<DirectoryRef Id="INSTALLDIR">
<Component Id="SqlErsServerInstall"
Guid="da6e0c89-2cfd-4bf4-92ae-40c8568bfd83" KeyPath="yes">
<sql:SqlScript Id="InstallBaseScript"
SqlDb="LocalDbServer"
BinaryKey="Sql_ServerInstall"
ContinueOnError="no"
ExecuteOnInstall="yes"
Sequence="1" />
<Condition><![CDATA[NOT ERS_VERSION AND NOT
PLUS_VERSION]]></Condition>
</Component>
</DirectoryRef>
The attached SQL script is an obfuscated snippet of the SQL script we call
which is a functioning script and I still get the failure described. If I
can provide any other information let me know, but due to the nature of the
product, I can't send you the full on scripts and files without an NDA.
Regards,
//aj
On 5/22/07, Rob Mensching <[EMAIL PROTECTED]> wrote:
That was a huge integration last week. It is possible that you've found a bug in the integration (or even scarier a bug that wasn't fixed in WiX v2 either). Is it possible to share the .wxs and SQL script? The last bugs we've fixed have all been edge cases where the SQL Script had to be set just so. Difficult to review. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Aaron Shurts *Sent:* Tuesday, May 22, 2007 9:55 AM *To:* Bob Arnson *Cc:* Mike Dimmick; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Problem with SQL custom actions. Maybe I am grasping at straws trying to get this v3 to work, but the latest weekly release (3.0.2921.0) doesn't even get in to the custom action DLL. Now I am getting this: MSI (s) (FC:3C) [09:35:15:234]: Doing action: ConfigureSql Action 9:35:15: ConfigureSql. Configuring SQL Server Action start 9:35:15: ConfigureSql. MSI (s) (FC:E4) [09:35:15:250]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI10D.tmp, Entrypoint: ConfigureSql MSI (s) (FC:3C) [09:35:15:312]: Note: 1: 1723 2: ConfigureSql 3: ConfigureSql 4: C:\WINDOWS\Installer\MSI10D.tmp Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action ConfigureSql, entry: ConfigureSql, library: C:\WINDOWS\Installer\MSI10D.tmp MSI (s) (FC:3C) [09:35:16:531]: Product: Enterprise Reporting Server -- Error 1723.There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action ConfigureSql, entry: ConfigureSql, library: C:\WINDOWS\Installer\MSI10D.tmp Action ended 9:35:16: ConfigureSql. Return value 3. Any thoughts / suggestions? The DLL is actually in the binary table, so it's not a matter of the DLL missing. Regards, //aj On 5/21/07, *Bob Arnson* <[EMAIL PROTECTED]> wrote: Aaron Shurts wrote: > I decided to go with v3 because I didn't feel like re-writing all the > deprecated tags when v3 is released. I think we have a fix for it in > the meantime, but it sure would be nice if the fixes were propagated > in to the v3 code branch. Check the latest weekly release: >>> RobMen: Reverse integrate WiX v2 CustomAction fixes. -- sig://boB http://joyofsetup.com/
ERSServer.sql
Description: Binary data
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
