How can I solve this error when the application is published:
You probably have just installed it, but you've done it running the setup from a different location.
Uninstall the application and run again the setup. Remember to run the setup from the same location when you update it.
I'm not 100% sure about it, but form my experience it's correct.
Related
I have a custom bootstrapper (C# WPF) and it works well enough. If the installer gets run from the command line after it was installed, it brings up a window allowing the user to select if they want to modify, repair or uninstall. So far so good. Modify mode starts the UI which ends up calling Bootstrapper.Plan(LaunchAction.Modify). The problem is that if I call it from the launcher UI it immediately complains that a prior install requires a reboot.
I have not found any good examples on what this should do. Even the WiX mailing list came up blank.
Any ideas?
It would be helpful with the screenshot for that reboot message - just to get a feel for where it might be coming from and to get a literal string to search for. Did you have a look in the WiX source code yourself btw? (WiX 3.111 branch)
I started writing a lot of stuff about reboots. Not good. Maybe just some questions instead:
Does this happen every time you invoke modify and is it reproducible on more than one computer? Or maybe it is just Windows Update acting up on a problem computer?
I assume you have rebooted the computer where you see the problem and you see the problem again when you re-launch the bundle?
Do you schedule any reboots inside your MSI files during the initial installation?
Either using the ScheduleReboot action or a custom action which schedules a reboot with a call to MsiSetMode (for example)?
There is a long explanation here why such reboot-constructs cause problems, but that may be besides the point. Essentially badly configured reboot-constructs can trigger spontaneous, unexpected reboots without warning when packages are run in silent mode (plus other problems).
Could you try to run the test VBScript found in this answer: WiX behaving badly on XP machine with windows update issues in order to check if the script reports a reboot being necessary?
Other than that I guess you could try to run Burn yourself in debug mode (not sure how much plumbing that would be to get running) or perhaps first try a ProcMon.exe session to see if you can see something obvious. The latter should be quick to do?
There are some registry locations you can hunt down to see if you can figure out what triggered the reboot warning. Get-PendingReboot-Query. And a similar PowerShell script.
So in the end it was user error. :-( O well. I did learn a lot about how to figure out how Windows checks for the need to reboot etc.
The issue was simple in the end. During the modify run it was uninstalling, then reinstalling a number of services. The problem is that when it runs (seeing as you have to set it to repair to get it to work) it copies all the files again and the services were still running at the start of the install. The fix was to uninstall anything that might lock a file before the actual file copy starts and that solved the issue for me.
Thanks for your help guys, all the info helped me look in different directions until I found the issue. Awesome community as always!
I am using version 4.5.5 of jhipster.
My OS is Linux Mint.
I am using IntelliJ as my IDE.
Everything is working fine in terms of generating the code, building and running the code.
Client
Unfortunately, when I make changes to the client code (html or ts), the changes are not reflected until I recompile the client code completed. To achieve this I do "mvn -Pdev,webpack". It takes quite a while to restart the client and this is really holding me back.
Hot Deploy
What I expect to happen is that I can run "npm start" and when I save a change to a ts or a html file that it will be picked up and the change immediately visible in the browser.
Questions
Any ideas why the client hot deploy is not working ?
Any ideas how I identify where the issue is ?
For example, how do I know what folders are being watched by the hot deploy ?
Thanks a million for you help.
I am sure others have encountered the same issue and will read the answer gladly.
Kind regards,
Fergal.
PS Need any details, simply ask.
Figured it out.
Somebody else had a similar issue with a globally installed instance of webpack.
I installed a local version and the file updates are being detected and recompiled and the app hot deployed. Now working perfectly.
To install a local version webpack.js.org/guides/installation/#local-installation.
I'm following the instructions here but it seems not to work. I'll contact the developer, but wonder if someone has been able to make it work somehow.
The installation process is completed, but Netbeans doesn't see the plug-in. I assume it is deployed incorrectly.
Not sure how it got fixed but suddenly upon starting the IDE an update for the plugin showed up and it started working afterwards.
I've did research and still can't figure this out, but I know the problem. The problem is that Eazfuscator isn't installed on other peoples pc, but how would I get them to run it without getting this error, and without them installing eazfuscator? Or should I use another one?
Error when running protected application:
This application has been built with an evaluation version of Eazfuscator.NET, and therefore cannot be distributed. You can install Eazfuscator.NET on this computer to be able to run this application.
You need to purchase a developers license plain and simple. Until then they will see this message. When you get the license and compile the application this wont happen...
More about it here...
http://www.gapotchenko.com/eazfuscator.net/purchase
I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.