Actually, it looks like you changed the name of the entry point to
InstallSqlData and added an UninstallSqlData, but did not change
src\ext\SqlExtension\wixlib\SqlExtension.wxs. You did change
src\ca\serverca\scawixlib\sca.wxs, but I don't think that file is used any
more in WiX v3.

 

Sorry, guys, looks like WiX 3.0.2921.0 isn't going to work for anyone who
needs the SQL features, unless you modify SqlExtension.wxs and build WiX
yourself.

 

-- 

Mike Dimmick

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick
Sent: 23 May 2007 00:06
To: 'Rob Mensching'; 'Aaron Shurts'; 'Bob Arnson'
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem with SQL custom actions.

 

Something got broken in the build process: ConfigureSql is not exported from
the CA DLL contained in WixSqlExtension.dll.

 

-- 

Mike Dimmick

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: 22 May 2007 18:48
To: Aaron Shurts; Bob Arnson
Cc: Mike Dimmick; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Problem with SQL custom actions.

 

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/  <http://joyofsetup.com/> 

 

-------------------------------------------------------------------------
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

Reply via email to