Re: [WiX-users] ServiceInstall failure?
I have an open ticket with Microsoft. They pointed me to http://support.microsoft.com/kb/264678/EN-US/ I have been unable to get to this link with IE 9. They also said: "When AD calls are made with a UPN name(username@Domainname) with a bad password, an initial attempt is made with Kerberos, and when that fails, an additional attempt is made with NTLM. That is why we are seeing the badpwdcount attribute being incremented twice. When the same attempt is made with a SAM account name (domain\username), only one attempt with Kerberos is made, and consequentially the badpwdcount attribute is being incremented once." My experience with our domain controller is that the count gets bumped to 3 when using UPN and 2 when using SAM. Anyway apparently the way a user name is specified does matter and using UPN formatted user name can more readily cause an account lockout. The link mentions this as a problem with Windows 2000 server domain controllers. I am using a Windows 2008 server R2 domain controller which seems to exhibit different characteristics and it hasn’t been fixed there yet. Just FYI. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 3:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? There are no builtin facilities in Windows Installer nor WiX for checking credentials. You'll need to write a custom action to perform this type of check but beware that this check will likely count against the lockout count if the credentials are incorrect. In other words, if you use the custom action as part of the UI and the user tries to validate wrong credentials enough times, then they will still lockout the account. If the MSI does not have a UI then you'll have to run the installer multiple times with invalid credentials to lockout the account with a validation custom action. In other words, I don’t think you can truly avoid the problem as it depends on how many times a user specifies invalid credentials. I have never seen a single installation attempt lockout an account. In my experience the service fails to start and causes the installation to fail initiating a rollback. No lockout. If I attempt the installation enough times with invalid credentials, then I'll see a lockout which is the same as above. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com<http://www.fiserv.com> P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Wednesday, March 09, 2011 4:58 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > I consistently get an account lockout when I install and start a > service with the wrong credentials. Everything works fine when the > proper credentials are supplied. I know it is probably an FAQ but I am > just beginning. What facilities are available for checking the > credentials and rolling back the installation > *before* starting the service? I see recently, someone else queried > about conditionally installing/starting a service but I was not able > to follow the conclusion. Thank you. > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com<mailto:kev...@buyseasons.com> > > -Original Message- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: Friday, January 28, 2011 5:16 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > InstallServices standard action in itself cannot *directly* cause an > account lockout. For that matter, I don't think I've ever ( in 7 > years ) seen an install > *directly* fail because of InstallServices. > > StartServices is another story though. > > If the service can't start for whatever reason, then StartServices can > result in a rollback. Also given enough opportunities, a bad password > injected by InstallServices can lead to StartServices locking the account. > > Conversely I've also seen ( at Continental Airlines ) a locked account > fail an install because the service could not start. Again, this > manifests as a problem in StartServices not I > > > --- > Christopher Painter, Author of Deployment Engineering Blog Have a hot > tip, know a secret or read a really good thread that deserves > attenti
Re: [WiX-users] ServiceInstall failure?
It is locking out the account. It is rolling back so nothing is installed but the account is locked out when invalid credentials are supplied. I don't know how to go about debugging this issue. -Original Message- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Wednesday, March 09, 2011 3:39 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? There are no builtin facilities in Windows Installer nor WiX for checking credentials. You'll need to write a custom action to perform this type of check but beware that this check will likely count against the lockout count if the credentials are incorrect. In other words, if you use the custom action as part of the UI and the user tries to validate wrong credentials enough times, then they will still lockout the account. If the MSI does not have a UI then you'll have to run the installer multiple times with invalid credentials to lockout the account with a validation custom action. In other words, I don’t think you can truly avoid the problem as it depends on how many times a user specifies invalid credentials. I have never seen a single installation attempt lockout an account. In my experience the service fails to start and causes the installation to fail initiating a rollback. No lockout. If I attempt the installation enough times with invalid credentials, then I'll see a lockout which is the same as above. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Wednesday, March 09, 2011 4:58 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > I consistently get an account lockout when I install and start a > service with the wrong credentials. Everything works fine when the > proper credentials are supplied. I know it is probably an FAQ but I am > just beginning. What facilities are available for checking the > credentials and rolling back the installation > *before* starting the service? I see recently, someone else queried > about conditionally installing/starting a service but I was not able > to follow the conclusion. Thank you. > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: Friday, January 28, 2011 5:16 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > InstallServices standard action in itself cannot *directly* cause an > account lockout. For that matter, I don't think I've ever ( in 7 > years ) seen an install > *directly* fail because of InstallServices. > > StartServices is another story though. > > If the service can't start for whatever reason, then StartServices can > result in a rollback. Also given enough opportunities, a bad password > injected by InstallServices can lead to StartServices locking the account. > > Conversely I've also seen ( at Continental Airlines ) a locked account > fail an install because the service could not start. Again, this > manifests as a problem in StartServices not I > > > --- > Christopher Painter, Author of Deployment Engineering Blog Have a hot > tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > > ----- Original Message ---- > From: "Castro, Edwin G. (Hillsboro)" > To: General discussion for Windows Installer XML toolset. > > Sent: Fri, January 28, 2011 1:08:58 PM > Subject: Re: [WiX-users] ServiceInstall failure? > > ServiceInstall is standard functionality provided by Windows Installer. > > I've never had its use result in an account lockout. In my experience > the installer fails after the first time it tries to register the > service but fails because the username/password are invalid. I've > never experienced it to retry any number of times. > > Edwin G. Castro > Software Developer - Staff > Electronic Banking Services > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > P Please consider the environment before printing this e-mail > > > > -Original Message- > > From: Kevin Burton [mailto:kev...@buyseasons.com] > > Sent: Friday, January 28, 2011 10:50 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-use
Re: [WiX-users] ServiceInstall failure?
There are no builtin facilities in Windows Installer nor WiX for checking credentials. You'll need to write a custom action to perform this type of check but beware that this check will likely count against the lockout count if the credentials are incorrect. In other words, if you use the custom action as part of the UI and the user tries to validate wrong credentials enough times, then they will still lockout the account. If the MSI does not have a UI then you'll have to run the installer multiple times with invalid credentials to lockout the account with a validation custom action. In other words, I don’t think you can truly avoid the problem as it depends on how many times a user specifies invalid credentials. I have never seen a single installation attempt lockout an account. In my experience the service fails to start and causes the installation to fail initiating a rollback. No lockout. If I attempt the installation enough times with invalid credentials, then I'll see a lockout which is the same as above. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Wednesday, March 09, 2011 4:58 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > I consistently get an account lockout when I install and start a service with > the > wrong credentials. Everything works fine when the proper credentials are > supplied. I know it is probably an FAQ but I am just beginning. What > facilities > are available for checking the credentials and rolling back the installation > *before* starting the service? I see recently, someone else queried about > conditionally installing/starting a service but I was not able to follow the > conclusion. Thank you. > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: Friday, January 28, 2011 5:16 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > InstallServices standard action in itself cannot *directly* cause an account > lockout. For that matter, I don't think I've ever ( in 7 years ) seen an > install > *directly* fail because of InstallServices. > > StartServices is another story though. > > If the service can't start for whatever reason, then StartServices can result > in > a rollback. Also given enough opportunities, a bad password injected by > InstallServices can lead to StartServices locking the account. > > Conversely I've also seen ( at Continental Airlines ) a locked account fail an > install because the service could not start. Again, this manifests as a > problem > in StartServices not I > > > --- > Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, > know a secret or read a really good thread that deserves attention? E-Mail > Me > > > > - Original Message > From: "Castro, Edwin G. (Hillsboro)" > To: General discussion for Windows Installer XML toolset. > > Sent: Fri, January 28, 2011 1:08:58 PM > Subject: Re: [WiX-users] ServiceInstall failure? > > ServiceInstall is standard functionality provided by Windows Installer. > > I've never had its use result in an account lockout. In my experience the > installer fails after the first time it tries to register the service but > fails > because the username/password are invalid. I've never experienced it to > retry any number of times. > > Edwin G. Castro > Software Developer - Staff > Electronic Banking Services > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > P Please consider the environment before printing this e-mail > > > > -Original Message- > > From: Kevin Burton [mailto:kev...@buyseasons.com] > > Sent: Friday, January 28, 2011 10:50 AM > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] ServiceInstall failure? > > > > Since it is so basic can you envision a situation where it would cause > > an account lockout? By basic what is the underlying implementation being > used? > > > > Kevin Burton > > Senior Software Engineer > > BUYSEASONS > > 262-901-2000 Office > > 262-901-2312 Fax > > kev...@buyseasons.com > > > > -Original Message- > &
Re: [WiX-users] ServiceInstall failure?
I consistently get an account lockout when I install and start a service with the wrong credentials. Everything works fine when the proper credentials are supplied. I know it is probably an FAQ but I am just beginning. What facilities are available for checking the credentials and rolling back the installation *before* starting the service? I see recently, someone else queried about conditionally installing/starting a service but I was not able to follow the conclusion. Thank you. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > > > Is to repeatedly try, even when the password is invalid, until the > > account specified is locked out. I was wondering if there was a way to > > catch the first error and display it to the user. > > > > Also I would like to associate some sort of progress bar with the > > installation and starting of this service. Is there a good reference > > for this type of function? > > > > Thank you. > > > > Kevin > > > > > > -- > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > > value)! > > Finally, a world-class log management solution at an even better > > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free A
Re: [WiX-users] ServiceInstall failure?
Assuming that I can translate this to C#, what would be the WiX code that needs to be in place to call this function? I am fairly new to 3.x and I remember that with 2.0 there needed to be a fair amount of plumbing in place to call a C# (managed) custom action. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Wednesday, February 02, 2011 2:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? A usual way to validate credentials is to use the LogonUser() Win32 API, but that's a logon that can fail, which is what you don't want. The only other way I'm aware of is SSPLogonUser(), huge C++ example here: http://support.microsoft.com/kb/180548 Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, February 02, 2011 6:55 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? No impersonations myself. This started occurring when there was a problem with my Custom UI which among other things prompted for a password. The UI was not showing up and so the password was not valid. But the install continued. It got to and and the task failed because of an invalid password but the account (my account) that the service was installed under was locked out. My administrator indicated that something or someone tried and failed too many times so the account was locked out. I hate to try it again because it takes I am guessing the Domain Admin to unlock the account again and I hate to continually asked the admin to unlock my account. Hence the question. If you have suggestions on how I might implement the custom action to validate the credentials I would be very appreciative. That may solve my problem. I have a WiX 2.0 script that works right now so I am reasonably sure that my account has the proper rights. I have subsequently successfully installed and started the service using that installation script. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Tuesday, February 01, 2011 10:52 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ServiceInstall failure? Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023)
Re: [WiX-users] ServiceInstall failure?
A usual way to validate credentials is to use the LogonUser() Win32 API, but that's a logon that can fail, which is what you don't want. The only other way I'm aware of is SSPLogonUser(), huge C++ example here: http://support.microsoft.com/kb/180548 Phil Wilson -Original Message- From: Kevin Burton [mailto:kev...@buyseasons.com] Sent: Wednesday, February 02, 2011 6:55 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? No impersonations myself. This started occurring when there was a problem with my Custom UI which among other things prompted for a password. The UI was not showing up and so the password was not valid. But the install continued. It got to and and the task failed because of an invalid password but the account (my account) that the service was installed under was locked out. My administrator indicated that something or someone tried and failed too many times so the account was locked out. I hate to try it again because it takes I am guessing the Domain Admin to unlock the account again and I hate to continually asked the admin to unlock my account. Hence the question. If you have suggestions on how I might implement the custom action to validate the credentials I would be very appreciative. That may solve my problem. I have a WiX 2.0 script that works right now so I am reasonably sure that my account has the proper rights. I have subsequently successfully installed and started the service using that installation script. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Tuesday, February 01, 2011 10:52 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ServiceInstall failure? Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD v
Re: [WiX-users] ServiceInstall failure?
No impersonations myself. This started occurring when there was a problem with my Custom UI which among other things prompted for a password. The UI was not showing up and so the password was not valid. But the install continued. It got to and and the task failed because of an invalid password but the account (my account) that the service was installed under was locked out. My administrator indicated that something or someone tried and failed too many times so the account was locked out. I hate to try it again because it takes I am guessing the Domain Admin to unlock the account again and I hate to continually asked the admin to unlock my account. Hence the question. If you have suggestions on how I might implement the custom action to validate the credentials I would be very appreciative. That may solve my problem. I have a WiX 2.0 script that works right now so I am reasonably sure that my account has the proper rights. I have subsequently successfully installed and started the service using that installation script. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: MikeR [mailto:michael.ru...@gmail.com] Sent: Tuesday, February 01, 2011 10:52 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] ServiceInstall failure? Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
Are you explicitly doing any impersonation of the logon user in custom actions yourself? If you are obtaining logon credentials from the user (via dialog or command line) I would implement a custom action to validate those credentials before you make any system changes and prevent the install from proceeding until you have valid credentials. I would also recommend checking that the account has the ServiceLogonRight policy set so to ensure it can be used to run services. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ServiceInstall-failure-tp5967359p5981755.html Sent from the wix-users mailing list archive at Nabble.com. -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
I am just trying to imagine scenarios where the lockout could happen. Because it is happening. I realize that the service is not started but I was thinking that somewhere in the code it is not checking that the service is started or not it is just trying to stop the service. -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Monday, January 31, 2011 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? #1 could happen. #2 could not happen because a) the service isn't started so there's nothing to stop and b) a login is not required to stop the service. #3 could not happen because a login is not needed to remove the service. The credentials are only needed when attempting to start the service. Even if the account is locked while the service is running you may not notice if the service doesn't do anything to authenticate itself such as connect to another service. It's only when loading the security token would it matter. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Kevin Burton To: General discussion for Windows Installer XML toolset. Sent: Mon, January 31, 2011 8:44:01 AM Subject: Re: [WiX-users] ServiceInstall failure? OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior fo
Re: [WiX-users] ServiceInstall failure?
I am just trying to imagine scenarios where the lockout could happen. Because it is happening. I realize that the service is not started but I was thinking that somewhere in the code it is not checking that the service is started or not it is just trying to stop the service. I was thinking #3 more or less in the same vein as #2. An impersonation attempt was made without checking whether it was needed or not. Can a failed rollback trigger another rollback and start a cascade? -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Monday, January 31, 2011 8:59 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? #1 could happen. #2 could not happen because a) the service isn't started so there's nothing to stop and b) a login is not required to stop the service. #3 could not happen because a login is not needed to remove the service. The credentials are only needed when attempting to start the service. Even if the account is locked while the service is running you may not notice if the service doesn't do anything to authenticate itself such as connect to another service. It's only when loading the security token would it matter. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Kevin Burton To: General discussion for Windows Installer XML toolset. Sent: Mon, January 31, 2011 8:44:01 AM Subject: Re: [WiX-users] ServiceInstall failure? OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the >
Re: [WiX-users] ServiceInstall failure?
#1 could happen. #2 could not happen because a) the service isn't started so there's nothing to stop and b) a login is not required to stop the service. #3 could not happen because a login is not needed to remove the service. The credentials are only needed when attempting to start the service. Even if the account is locked while the service is running you may not notice if the service doesn't do anything to authenticate itself such as connect to another service. It's only when loading the security token would it matter. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Kevin Burton To: General discussion for Windows Installer XML toolset. Sent: Mon, January 31, 2011 8:44:01 AM Subject: Re: [WiX-users] ServiceInstall failure? OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> >
Re: [WiX-users] ServiceInstall failure?
OK it doesn't cause the lockout *directly* but can this happen? 1) Service fails to start because of bad password. (one bad login attempt) 2) Since service does not start it triggers a rollback which first tries to stop the service (second bad login attempt) 3) To remove the service an impersonation attempt is made (third bad login attempt) I think (I will have to verify with the administrator) that the account lockout occurs after three bad login attempts. Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 5:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com P Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > > > Is to repeatedly try, even when the password is invalid, until the > > account specified is locked out. I was wondering if there was a way to > > catch the first error and display it to the user. > > > > Also I would like to associate some sort of progress bar with the > > installation and starting of this service. Is there a good reference > > for this type of function? > > > > Thank you. > > > > Kevin > > > > > > -- > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > > value)! > > Finally, a world-class log management solution at an even better > > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY!
Re: [WiX-users] ServiceInstall failure?
Exactly - it will depend on the account lockout policy for things like password failures. If the policy says that the threshold is 1 invalid logon, and the service starts up with the wrong password then boom, you're locked out. Phil Wilson -Original Message- From: Christopher Painter [mailto:chr...@deploymentengineering.com] Sent: Friday, January 28, 2011 3:16 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > > > Is to repeatedly try, even when the password is invalid, until the > > account specified is locked out. I was wondering if there was a way to > > catch the first error and display it to the user. > > > > Also I would like to associate some sort of progress bar with the > > installation and starting of this service. Is there a good reference > > for this type of function? > > > > Thank you. > > > > Kevin > > > > > > -- > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > > value)! > > Finally, a world-class log management solution at an even better > > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > virtually, Rob Mensching - h
Re: [WiX-users] ServiceInstall failure?
InstallServices standard action in itself cannot *directly* cause an account lockout. For that matter, I don't think I've ever ( in 7 years ) seen an install *directly* fail because of InstallServices. StartServices is another story though. If the service can't start for whatever reason, then StartServices can result in a rollback. Also given enough opportunities, a bad password injected by InstallServices can lead to StartServices locking the account. Conversely I've also seen ( at Continental Airlines ) a locked account fail an install because the service could not start. Again, this manifests as a problem in StartServices not I --- Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: "Castro, Edwin G. (Hillsboro)" To: General discussion for Windows Installer XML toolset. Sent: Fri, January 28, 2011 1:08:58 PM Subject: Re: [WiX-users] ServiceInstall failure? ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of >the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > > > Is to repeatedly try, even when the password is invalid, until the > > account specified is locked out. I was wondering if there was a way to > > catch the first error and display it to the user. > > > > Also I would like to associate some sort of progress bar with the > > installation and starting of this service. Is there a good reference > > for this type of function? > > > > Thank you. > > > > Kevin > > > > > > -- > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > > value)! > > Finally, a world-class log management solution at an even better > > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > -- > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _
Re: [WiX-users] ServiceInstall failure?
ServiceInstall is standard functionality provided by Windows Installer. I've never had its use result in an account lockout. In my experience the installer fails after the first time it tries to register the service but fails because the username/password are invalid. I've never experienced it to retry any number of times. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Kevin Burton [mailto:kev...@buyseasons.com] > Sent: Friday, January 28, 2011 10:50 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > Since it is so basic can you envision a situation where it would cause an > account lockout? By basic what is the underlying implementation being used? > > Kevin Burton > Senior Software Engineer > BUYSEASONS > 262-901-2000 Office > 262-901-2312 Fax > kev...@buyseasons.com > > -Original Message- > From: Rob Mensching [mailto:r...@robmensching.com] > Sent: Friday, January 28, 2011 7:43 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ServiceInstall failure? > > The built in service install of the Windows Installer is pretty basic. One of > the > few standard actions I've seriously considered replacing with a custom action. > > On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton > wrote: > > > It seems that the default behavior for this code > > > > > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > > Services" Interactive="no" Account="[SERVICEUSER]" > > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > > Type="ownProcess" Vital="yes" /> > > > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > > > Is to repeatedly try, even when the password is invalid, until the > > account specified is locked out. I was wondering if there was a way to > > catch the first error and display it to the user. > > > > Also I would like to associate some sort of progress bar with the > > installation and starting of this service. Is there a good reference > > for this type of function? > > > > Thank you. > > > > Kevin > > > > > > -- > > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > > value)! > > Finally, a world-class log management solution at an even better > > price-free! > > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > > February 28th, so secure your free ArcSight Logger TODAY! > > http://p.sf.net/sfu/arcsight-sfd2d > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > -- > virtually, Rob Mensching - http://RobMensching.com LLC > -- > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
Since it is so basic can you envision a situation where it would cause an account lockout? By basic what is the underlying implementation being used? Kevin Burton Senior Software Engineer BUYSEASONS 262-901-2000 Office 262-901-2312 Fax kev...@buyseasons.com -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Friday, January 28, 2011 7:43 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ServiceInstall failure? The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton wrote: > It seems that the default behavior for this code > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > Services" Interactive="no" Account="[SERVICEUSER]" > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > Type="ownProcess" Vital="yes" /> > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > Is to repeatedly try, even when the password is invalid, until the > account specified is locked out. I was wondering if there was a way to > catch the first error and display it to the user. > > Also I would like to associate some sort of progress bar with the > installation and starting of this service. Is there a good reference > for this type of function? > > Thank you. > > Kevin > > > -- > Special Offer-- Download ArcSight Logger for FREE (a $49 USD > value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ServiceInstall failure?
The built in service install of the Windows Installer is pretty basic. One of the few standard actions I've seriously considered replacing with a custom action. On Thu, Jan 27, 2011 at 10:38 AM, Kevin Burton wrote: > It seems that the default behavior for this code > > > Name="ServiceExeFile" Description="Windows Service host for Bsi Web > Services" Interactive="no" Account="[SERVICEUSER]" > Password="[SERVICEPASSWORD]" ErrorControl="normal" Start="demand" > Type="ownProcess" Vital="yes" /> > Start="install" Stop="uninstall" Remove="uninstall" Wait="yes" /> > > Is to repeatedly try, even when the password is invalid, until the account > specified is locked out. I was wondering if there was a way to catch the > first error and display it to the user. > > Also I would like to associate some sort of progress bar with the > installation and starting of this service. Is there a good reference for > this type of function? > > Thank you. > > Kevin > > > -- > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ServiceInstall failure?
It seems that the default behavior for this code Is to repeatedly try, even when the password is invalid, until the account specified is locked out. I was wondering if there was a way to catch the first error and display it to the user. Also I would like to associate some sort of progress bar with the installation and starting of this service. Is there a good reference for this type of function? Thank you. Kevin -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users