[WiX-users] MSMQ/MessageQueue: create public queue

2009-03-26 Thread Chris Eldredge
Using WiX 3.0.5120.0, I can create a private queue easily enough, but if 
I try to create a public queue the installer fails.

The log says:

MessageQueuingExecuteInstall:  Error 0xc00e0005: Failed to create 
message queue
MessageQueuingExecuteInstall:  Error 0xc00e0005: Failed to create 
message queue, key: FooQueue
MessageQueuingExecuteInstall:  Error 0xc00e0005: Failed to create 
message queues
Action ended 14:15:55: InstallFinalize. Return value 3.
MessageQueuingRollbackInstall:  Error 0xc00e0003: Failed to get format name
MessageQueuingRollbackInstall:  Failed to rollback add message queue 
permission, hr: 0xc00e0003, key: Whatever
Action ended 14:15:56: INSTALL. Return value 3.

My markup:

http://schemas.microsoft.com/wix/MsmqExtension";
Id="FooQueue"
Label="Foo"
PathName=".\Foo"
PrivLevel="none"
Authenticate="no"
ServiceTypeGuid="24a3b544-9359-4f92-a1cc-695891caddff"/>

Is this supported?  I've tried variations for the PathName such as 
[COMPUTERNAME]\Foo, .\Foo ActualServerName\Foo and none seem to work 
except for .\Private$\Foo.  But I need a public queue.

Thanks,

Chris


--
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] The website root appears blank after configuring existent site - another IIS extension bug?

2009-01-28 Thread Chris Eldredge
Sorry for the all the self-replies but I've been updating as I go. 
Build 3.0.4827.0 works for me on Server 2003 and on Vista.

Chris Eldredge wrote:
> Actually, scratch that.  Neither build works on my Windows Server 2003 / 
>   IIS 6 box, but both work on my Windows Vista / IIS 7 box.
> 
> I haven't tracked down why, but looking at the logs, 
> WriteMetabaseChanges comes before ConfigureIIs on the packages built on 
> the Vista box, and on the failed builds ConfigureIIsExec comes before 
> WriteMetabaseChanges.
> 
> Chris Eldredge wrote:
>> I've confirmed this seems to be a bug for me too, in 3.0.4923.0.  Going 
>> back to 3.0.4909.0 resolved the issue.
>>
>> Yan Sklyarenko wrote:
>>> Hello WiX developers,
>>>
>>> Sorry, but it seems I found another bug in the IIS extension. 
>>> WiX version is 3.0.4917.0. Here is a component definition:
>>>
>>> >> Guid="{YOURGUID-2023-4D19-90D2-EE9101C71E44}" Directory="WebsiteFolder"
>>> Permanent="yes">
>>> >> Directory="WebsiteFolder" ConfigureIfExists="yes">
>>> 
>>> 
>>> 
>>>
>>> The properties IISSITE_NAME and IISSITE_PORT are set with the command
>>> line to 'Default Web Site' and '80' appropriately. When the product is
>>> installed, it appears that the root path is set to blank ('Home
>>> Directory' tab, 'Local path' field in IIS console). 
>>> 'WebsiteFolder' is an Id of a valid Directory table entry.
>>>
>>> This used to work before, thus I'm thinking this is a new build
>>> (3.0.4917.0) which causes the problem.
>>> The behavior is reproduced for both IIS5 and IIS6. 
>>>
>>> Here's a log file snippet (no errors there):
>>> ...
>>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>>> ID: 1023
>>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>>> ID: 2021
>>> WriteMetabaseChanges:  Writing Metabase Value Under Key:
>>> /LM/W3SVC/1/Root ID: 3001
>>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>>> ID: 1015
>>> ...
>>>
>>> Do you think it's worth registering as a bug?
>>>
>>> -- Yan
>>>
>>>
>>> --
>>> This SF.net email is sponsored by:
>>> SourcForge Community
>>> SourceForge wants to tell your story.
>>> http://p.sf.net/sfu/sf-spreadtheword
>>
>> --
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
> 
> 
> --
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] The website root appears blank after configuring existent site - another IIS extension bug?

2009-01-28 Thread Chris Eldredge
Actually, scratch that.  Neither build works on my Windows Server 2003 / 
  IIS 6 box, but both work on my Windows Vista / IIS 7 box.

I haven't tracked down why, but looking at the logs, 
WriteMetabaseChanges comes before ConfigureIIs on the packages built on 
the Vista box, and on the failed builds ConfigureIIsExec comes before 
WriteMetabaseChanges.

Chris Eldredge wrote:
> I've confirmed this seems to be a bug for me too, in 3.0.4923.0.  Going 
> back to 3.0.4909.0 resolved the issue.
> 
> Yan Sklyarenko wrote:
>> Hello WiX developers,
>>
>> Sorry, but it seems I found another bug in the IIS extension. 
>> WiX version is 3.0.4917.0. Here is a component definition:
>>
>> > Guid="{YOURGUID-2023-4D19-90D2-EE9101C71E44}" Directory="WebsiteFolder"
>> Permanent="yes">
>> > Directory="WebsiteFolder" ConfigureIfExists="yes">
>> 
>> 
>> 
>>
>> The properties IISSITE_NAME and IISSITE_PORT are set with the command
>> line to 'Default Web Site' and '80' appropriately. When the product is
>> installed, it appears that the root path is set to blank ('Home
>> Directory' tab, 'Local path' field in IIS console). 
>> 'WebsiteFolder' is an Id of a valid Directory table entry.
>>
>> This used to work before, thus I'm thinking this is a new build
>> (3.0.4917.0) which causes the problem.
>> The behavior is reproduced for both IIS5 and IIS6. 
>>
>> Here's a log file snippet (no errors there):
>> ...
>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>> ID: 1023
>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>> ID: 2021
>> WriteMetabaseChanges:  Writing Metabase Value Under Key:
>> /LM/W3SVC/1/Root ID: 3001
>> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
>> ID: 1015
>> ...
>>
>> Do you think it's worth registering as a bug?
>>
>> -- Yan
>>
>>
>> --
>> This SF.net email is sponsored by:
>> SourcForge Community
>> SourceForge wants to tell your story.
>> http://p.sf.net/sfu/sf-spreadtheword
> 
> 
> --
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] The website root appears blank after configuring existent site - another IIS extension bug?

2009-01-28 Thread Chris Eldredge
I've confirmed this seems to be a bug for me too, in 3.0.4923.0.  Going 
back to 3.0.4909.0 resolved the issue.

Yan Sklyarenko wrote:
> Hello WiX developers,
> 
> Sorry, but it seems I found another bug in the IIS extension. 
> WiX version is 3.0.4917.0. Here is a component definition:
> 
>  Guid="{YOURGUID-2023-4D19-90D2-EE9101C71E44}" Directory="WebsiteFolder"
> Permanent="yes">
>  Directory="WebsiteFolder" ConfigureIfExists="yes">
> 
> 
> 
> 
> The properties IISSITE_NAME and IISSITE_PORT are set with the command
> line to 'Default Web Site' and '80' appropriately. When the product is
> installed, it appears that the root path is set to blank ('Home
> Directory' tab, 'Local path' field in IIS console). 
> 'WebsiteFolder' is an Id of a valid Directory table entry.
> 
> This used to work before, thus I'm thinking this is a new build
> (3.0.4917.0) which causes the problem.
> The behavior is reproduced for both IIS5 and IIS6. 
> 
> Here's a log file snippet (no errors there):
> ...
> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
> ID: 1023
> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
> ID: 2021
> WriteMetabaseChanges:  Writing Metabase Value Under Key:
> /LM/W3SVC/1/Root ID: 3001
> WriteMetabaseChanges:  Writing Metabase Value Under Key: /LM/W3SVC/1/
> ID: 1015
> ...
> 
> Do you think it's worth registering as a bug?
> 
> -- Yan
> 
> 
> --
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword


--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] concurrent / parallel builds

2008-11-24 Thread Chris Eldredge
I'm on v3.0.3429.0.  I know it's (a) beta and (b) old, but apart from 
some transient failures it does what we need.

Matt Ziegler wrote:
> I run a continuous integration server and run multiple installer builds at
> the same time and haven't received this error before.  Are the 2 projects in
> the same working directory?  What version of WiX are you running?
> 
> Matt
> 
> On Thu, Nov 20, 2008 at 12:32 PM, Chris Eldredge
> <[EMAIL PROTECTED]>wrote:
> 
>> I have a continuous integration server with multiple, unrelated
>> projects.  The machine has multiple cores so I let the projects build
>> asynchronously.  When 2 instances of light.exe run at the same time, bad
>> things seem to happen.
>>
>> Can anyone confirm or deny that light.exe does something (maybe temp
>> files or something else) that causes 2 instances running at the same
>> time to crash?
>>
>> I had to delete the entire profile directory for my service account
>> today because I was getting this error:
>>
>> LGHT0001: The file exists. (Exception from HRESULT: 0x80070050)
>>
>> Unhandled Exception: System.AccessViolationException: Attempted to read
>> or write protected memory. This is often an indication that other memory
>> is corrupt.
>>at
>>
>> Microsoft.Tools.WindowsInstallerXml.Cab.Interop.CabInterop.CreateCabFinish(IntPtr
>> contextHandle)
>>at
>> Microsoft.Tools.WindowsInstallerXml.Cab.WixCreateCab.Dispose()
>>at
>> Microsoft.Tools.WindowsInstallerXml.Cab.WixCreateCab.Finalize()
>>
>>
>> -
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
> -
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] concurrent / parallel builds

2008-11-20 Thread Chris Eldredge
I have a continuous integration server with multiple, unrelated 
projects.  The machine has multiple cores so I let the projects build 
asynchronously.  When 2 instances of light.exe run at the same time, bad 
things seem to happen.

Can anyone confirm or deny that light.exe does something (maybe temp 
files or something else) that causes 2 instances running at the same 
time to crash?

I had to delete the entire profile directory for my service account 
today because I was getting this error:

LGHT0001: The file exists. (Exception from HRESULT: 0x80070050)

Unhandled Exception: System.AccessViolationException: Attempted to read 
or write protected memory. This is often an indication that other memory 
is corrupt.
at 
Microsoft.Tools.WindowsInstallerXml.Cab.Interop.CabInterop.CreateCabFinish(IntPtr
 
contextHandle)
at 
Microsoft.Tools.WindowsInstallerXml.Cab.WixCreateCab.Dispose()
at 
Microsoft.Tools.WindowsInstallerXml.Cab.WixCreateCab.Finalize()


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] InstallExecuteSequence for Sql Actions

2008-02-01 Thread Chris Eldredge
Doh! I figured out that the reference to the File ID was wrong, so the 
path to the assembly was evaluating to a blank string.  Turns out 
standard action sequence works fine for this scenario.

Thanks,

Chris

Alexander Shevchuk wrote:
> Hi Chris,
> 
> Sorry, I am still on WiX 2, but that should not matter. In WiX 2 both 
>  and  have a Sequence attribute.  Make sure that 
>  is scheduled after InstallFiles standard action (usual Sequence 
> number 4000).
> 
> Regards,
> Alex


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] InstallExecuteSequence for Sql Actions

2008-02-01 Thread Chris Eldredge
Actually, I'm trying to load the assembly from the file system, not the 
GAC.  Does that change your answer?

Thanks,

Chris

Adam Majer wrote:
> 
> No. GAC is updated after MSI install is finalized. Wix has no control
> over this.
> 
> - Adam
> 
> 


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] InstallExecuteSequence for Sql Actions

2008-01-31 Thread Chris Eldredge
I'm trying to create an MSI that installs a .NET assembly and registers 
it for use in SQL Server 2005.

The problem is that the SQL I'm executing inside a SqlString is telling 
SQL Server to load the assembly, but when I install the MSI it seems 
that the assembly hasn't been copied to its final destination when the 
SQL action executes.

My question: is it possible to change the order that the actions execute 
in such that the assembly will be where it is supposed to be by the time
the SQL commands start executing?

Thanks,

Chris

My WiX 3 markup (abridged)



   
 http://schemas.microsoft.com/wix/SqlExtension";
   Id="MyDb" ConfirmOverwrite="no" CreateOnInstall="yes"
   DropOnUninstall="yes" Server="[ComputerName]"
 
Database="MyDb">

   
 
 
   



-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


[WiX-users] prompt for password

2007-01-29 Thread Chris Eldredge
Is there an example of wix markup to prompt for a password during 
installation?  Also,  this is more of a stretch, but is there a custom 
action that could verify that a given username/password are valid in the 
domain?

Thanks,

Chris Eldredge


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users