wyupdate won't start

One of our end users has a machine where wyupdate.exe won't start outright. We use version 2.6.18.4His Windows version is 6.3.9600What happens is: no matter how I start wyupdate (through .NET code, manually through command line, etc), it exits immediately, no record in eventlog is given, %errorlevel% is zero.If I specify -server= parameter in command line, to existing or non-existing url, it won't change anything.The computer does not seem to have any anti-spyware, it's pretty new and almost nothing is installed. .NET was deployed properly through ClickOnce application.Anywhere else wyupdate works as one would expect. Any ideas of what may have gone wrong?

My guess is that the .NET 2.0 / .NET 4.0 is disabled (depending on the version of wyUpdate you're using). Enable the feature in Windows 8.

nope, host .net application (deployed through clickonce) is running alright, it uses .NET 4 and that's the same version used for wyUpdateis there any way to get more detailed error info?

What happens when you just double click wyUpdate.exe? Does it run?

No, it exits immediately - no %errorlevel% set, no messages, no trace in windows eventlog.

If it's crashing, please send me a full dump of the crash (send it to wyatt@wyday.com). If you don't know how to get a memory dump of a crashing app, then let me know and I'll give your instructions.

It honestly doesn't sound like a crash. My guess is that you have another instance of wyUpdate running in another session on the computer. Open the task manager, make sure all processes for all users is shown, then kill every single instance of wyUpdate.exe listed.

I don't think it's crashing, there's nothing in windows eventlog indicating the crash.

So is it a known issue that two users can't run wyUpdate in two sessions at the same time, even if the application is being installed into different folders? Our application is being deployed on per-user basis, and we do have customers who use Citrix (and perhaps other types of terminal services).

It's not that 2 instances of wyUpdate can't run at the same time, it's that 2 instances of wyUpdate installing the same app can't run at the same time. 2 instances of wyUpdate installing separate apps works fine (ditto for a billion instances of a billion separate apps, etc., etc.).

So either make sure your dueling apps only run one instance of wyUpdate at a time, or, better yet, install your app to a centralized location on the computer (e.g. C:\Program Files\YourApp).

We just had similar situation with another customer, and I was able to do a screenshare. There was no dueling applications. It was more like that the system was locked down. Maybe issue with UAC setting. Is there any way to get more detailed error information once wyUpdate has been terminated?

No, UAC shouldn't effect wyUpdate. wyUpdate is designed to handle UAC.

My guess is some anti-virus program (or some other "protection" program) is intercepting wyUpdate before it can execute. Try disabling all the anti-virus / protection / malware programs and try again. If wyUpdate runs, then it's a problem somewhere in the "protection" programs.

Also, try moving wyUpdate.exe and client.wyc to another folder. Try a proper programs file folder. See if it runs then. (Again, my guess is that something is detecting a false positive and blocking wyUpdate).

I have experience the same issue. It first occurred about a year ago on one of our customer's computers (I posted about it in this forum, too). I wasn't able to solve it back then and it even went away after some time.

But now its back and this time its worse. All the computers in one of our customer's offices are affected. Their IT guy tried a lot: Running as administrator, Running under an admin account, copying to C:\Program Files, disabling their Anti Virus software, setting an exception rule for wyupdate.exe in their Anti Virus software - all without success. Still double-clicking the executable produces no GUI, neither does calling it from our .NET application.

Well, this time I thought, I will be smarter than the error. I pulled wyUpdate's source, made a debug build, and sent it to them along with Microsoft's IntelliTrace Collector. But guess what, the damn wyUpdate.exe starts just fine when its run by the IntelliTrace tool. 👿 (and no, its not because of the debug build)

I'm at my wits' end. I like wyBuild, but I think I won't be able to use it any longer.

  1. Are you using our build of wyUpdate, or are you using a custom build of wyUpdate?
  2. Have you modified wyUpdate in any way?
  3. What versions of the .NET Framework are installed?
  4. What version of wyUpdate are you using (the one for .NET Framework 2.0 or the one for .NET Framework 4.0)?
  5. Have you tried running both builds?
  6. Is wyUpdate code-signed?

My guess is it's #3 and #4.

I debugged this problem and found that when the WyUpdate application is launched, the code checks for any existing instances of the application. To do this, it is calling the Mutex.WaitOne() method with a wait Timespan as 0. It is this line of code which was failing and when I changed the wait Timespan from 0 to 1 second, the WyUpdate application starts fine.

Make following change in the Program.cs file of the WyUpdate source.Change if (mutex.WaitOne(Timespan.Zero, true)) //Line 40 in Program.csTo if (mutex.WaitOne(1000, true))

That doesn't solve a real problem. Don't launch multiple instances of wyUpdate simultaneously and the real problem is solved.

Reply
Discard post