Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure when installing SC #307

Closed
SimonCropp opened this issue Apr 11, 2014 · 14 comments
Closed

Failure when installing SC #307

SimonCropp opened this issue Apr 11, 2014 · 14 comments

Comments

@SimonCropp
Copy link
Contributor

Raised by @dannycohen
Migrated from by Particular/PlatformInstaller#133

Error executing powershell: [ERROR] Running C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\ServiceControlInstall.exe with /quiet  /L*V "C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\msiexe.log" was not successful. Exit code was '1638'.
Error executing powershell: ServiceControl did not finish successfully. Boo to the chocolatey gods!
-----------------------
[ERROR] [ERROR] Running C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\ServiceControlInstall.exe with /quiet  /L*V "C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\msiexe.log" was not successful. Exit code was '1638'.
-----------------------
Error executing powershell: Package 'ServiceControl.install v1.0.0-Beta8' did not install successfully: [ERROR] Running C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\ServiceControlInstall.exe with /quiet  /L*V "C:\Users\Danny\AppData\Local\Temp\chocolatey\ServiceControl\msiexe.log" was not successful. Exit code was '1638'.

See full log in email

@SimonCropp
Copy link
Contributor Author

Raised by @dannycohen

Update:

  1. I uninstalled SC and the installation proceeded as expected
  2. I assume this is related to me having a Beta version installed
  3. Can we detect this and provide better guidance ? (e.g. "Please unintsall beta installations of and try again").

@SimonCropp
Copy link
Contributor Author

Raised by @andreasohlund
We could detect the 1638 error and combine that with the package name to give a "X is already installed, please unistall it manually" error? cc @SimonCropp

@SimonCropp
Copy link
Contributor Author

Raised by @andreasohlund
Should I go ahead with this @SimonCropp ?

@SimonCropp
Copy link
Contributor Author

Raised by @SimonCropp
@andreasohlund not against doing this to add value for some things that cannot be fixed in the MSI but this is not one of those cases. If someone used the installer without the PI we dont want them having to debug msi error codes (if we can avoid it).

The installer should handle uninstalling previous versions even if they are beta. see #302

@SimonCropp
Copy link
Contributor Author

Raised by @andreasohlund
Makes sense, lets fix it in the installer if possible

Sent from my iPhone

On 10 apr 2014, at 08:23, Simon Cropp notifications@github.com wrote:

@andreasohlund not against doing this to add value for some things that cannot be fixed in the MSI but this is not one of those cases. If someone used the installer without the PI we dont want them having to debug msi error codes (if we can avoid it).

The installer should handle uninstalling previous versions even if they are beta. see #302


Reply to this email directly or view it on GitHub.

@johnsimons
Copy link
Member

Are we going to fix this or can we close it?

@andreasohlund
Copy link
Member

Since this turned out to inly be an issue when we put out betas I'd say we
could close this one and make sure we take this into account when putting
out new betas in the future?

On Mon, Apr 21, 2014 at 7:38 AM, John Simons notifications@github.comwrote:

Are we going to fix this or can we close it?

Reply to this email directly or view it on GitHubhttps://github.com//issues/307#issuecomment-40917397
.

@JeffreyAllenMiller
Copy link

What do you recommend if you had the Beta's installed. I have uninstalled ServiceInsight and even rebooted and I am getting the same error but for ServiceInsight.

Error executing powershell: [ERROR] Running C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe with /quiet  /L*V "C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log" was not successful. Exit code was '1638'.
Error executing powershell: ServiceInsight did not finish successfully. Boo to the chocolatey gods!
-----------------------
[ERROR] [ERROR] Running C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe with /quiet  /L*V "C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log" was not successful. Exit code was '1638'.
-----------------------
Error executing powershell: Package 'ServiceInsight.install v1.0.0' did not install successfully: [ERROR] Running C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe with /quiet  /L*V "C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log" was not successful. Exit code was '1638'.

@andreasohlund
Copy link
Member

1638 mean that the product is already installed.

Can you go into add/remove programs and double check that ServiceInsight
isn't there?

On Mon, Apr 28, 2014 at 8:15 PM, JeffreyAllenMiller <
notifications@github.com> wrote:

What do you recommend if you had the Beta's installed. I have uninstalled
ServiceInsight and even rebooted and I am getting the same error but for
ServiceInsight.

Error executing powershell: [ERROR] Running
C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L_V
"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.
Error executing powershell: ServiceInsight did not finish successfully.
Boo to the chocolatey gods! [ERROR] [ERROR] Running
C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L_V
"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.

Error executing powershell: Package 'ServiceInsight.install v1.0.0' did
not install successfully: [ERROR] Running
C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L*V
"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.

Reply to this email directly or view it on GitHubhttps://github.com//issues/307#issuecomment-41593508
.

@JeffreyAllenMiller
Copy link

I looked up that code and found the same thing. Attached you will find a
screen shot showing what is installed and clearly ServiceInsight is not in
the list.

On Mon, Apr 28, 2014 at 2:49 PM, Andreas Öhlund notifications@github.comwrote:

1638 mean that the product is already installed.

Can you go into add/remove programs and double check that ServiceInsight
isn't there?

On Mon, Apr 28, 2014 at 8:15 PM, JeffreyAllenMiller <
notifications@github.com> wrote:

What do you recommend if you had the Beta's installed. I have uninstalled
ServiceInsight and even rebooted and I am getting the same error but for
ServiceInsight.

Error executing powershell: [ERROR] Running

C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L*V

"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.
Error executing powershell: ServiceInsight did not finish successfully.
Boo to the chocolatey gods! [ERROR] [ERROR] Running

C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L*V

"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.

Error executing powershell: Package 'ServiceInsight.install v1.0.0' did
not install successfully: [ERROR] Running

C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\ServiceInsightInstall.exe
with /quiet /L*V

"C:\Users\jmiller.MPSRX\AppData\Local\Temp\chocolatey\ServiceInsight\msiexe.log"
was not successful. Exit code was '1638'.

Reply to this email directly or view it on GitHub<
#307 (comment)

.


Reply to this email directly or view it on GitHubhttps://github.com//issues/307#issuecomment-41597677
.

@indualagarsamy
Copy link
Contributor

@JeffreyAllenMiller - Can you check for both Particular Software ServiceInsight and for ServiceInsight?
I think the older beta's used to not named right.

@gbiellem
Copy link
Contributor

I've made a PS script to help cleanup betas of ServiceControl, ServicePulse and ServiceInsight. It will prompt for the removal of products based on the MSI product code so our various product name changes are catered for.
.
Script can be found here - https://gist.github.com/gbiellem/11394812

@JeffreyAllenMiller
Copy link

Indu,

I verified that neither of these are listed in the Services. I can only
assume there was some hiccup with the uninstall. Greg Bielleman provided a
PS clean up script which I will test this morning https://gist.github.com/
gbiellem/11394812

Thanks for the assistance.

On Mon, Apr 28, 2014 at 5:03 PM, Indu Alagarsamy
notifications@github.comwrote:

@JeffreyAllenMiller https://github.com/JeffreyAllenMiller - Can you
check for both Particular Software ServiceInsight and for ServiceInsight?
I think the older beta's used to not named right.


Reply to this email directly or view it on GitHubhttps://github.com//issues/307#issuecomment-41613237
.

@JeffreyAllenMiller
Copy link

I have tested Greg Bielleman's PS script and it worked, as I was able to successfully install ServiceInsight using the Platform Installer after executing this script. Note that it takes a while for the script to execute so please be patient. Thank you Greg and NServiceBus for all your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants