Click-once application doesn't start

Click-once application doesn't start

• Leo Pedersen

  I've tried uninstalling all click-once applications and then cleaning up with mage -cc as suggested. Unfortunately, no dice :-(
  
  
  

• danielwetzler

  Interesting - I tried the test you suggested and it looks as though the folder length is the problem.
  
  I don't have Kensington Mouseworks as such - I just have a Kensington mouse driver that Windows Update pulled down for me one day. I removed this from Device Manager, because there isn't an entry for it in Add/Remove Programs. Now I've gone back to look and it looks like the driver got installed again.
  
  I'm going to make sure I delete every single instance of kmw_sys.sys from the hard disk and try again. I'll let you know how I get on.
  
  Many thanks for your help.
  
  -
  David
  
  
  
  
  

• Alwyn Rozario

  I would suspect either hosting process for semi trust is dying out or something to do with the apps in ClickOnce store location. You can cleanup the store suggested here - http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=160592&SiteID=1
  
  

• CET PRG455

  I do have a Kensington mouse, so I've uninstalled the driver but that didn't work.
  
  I tried running the application directly as you suggested, but it won't start, I think because it can't find the other assemblies the .exe depends on. If I copy all of the dependent assemblies into the same directory it fails to start, but doesn't give an error message so it looks like your paragraph:
  
  "If this direct activation of exe fails then looks like you have a general problem with launching managed apps on the machine not related to ClickOnce. If this is the case the general Windows Forms alias will be a better place to post the issue."
  
  may be the way to go for me.
  
  
  Many thanks for your help.
  
  
  
  

• PGMariotti

  Do you see any ClickOnce error dialog If "yes" what does it say in the log

  If "no" it is possible that app itself is silently crashing on your machine. You can retrieve older log from WinInet Cache, to see whether ClickOnce portion of the launch was succeded.

  
  
  

• E Jensen

  I didn't get any error messages. Where is the log file written to
  
  Today my application is working, so I'm going to have to wait for it to stop working again to debug any further.
  
  Thanks for your help,
  David
  
  
  

• Craig68

  I'm getting the following log, which as you can see shows no errors. My first thought would be to suspect that the application is dying on startup, except that:
  
  a) This problem is affecting all click-once deployments on my machines - even ones that used to work and haven't been updated.
  
  b) The app runs fine locally.
  
  Any help much appreciated!
  
  ---log---
  PLATFORM VERSION INFO
  Windows : 5.1.2600.131072 (Win32NT)
  Common Language Runtime : 2.0.50727.42
  System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
  mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
  dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
  dfshim.dll : 2.0.50727.42 (RTM.050727-4200)
  
  SOURCES
  Deployment url : file:///C:/Documents%20and%20Settings/David.XXXXX/Desktop/Connect.appref-ms
  Server : Microsoft-IIS/6.0
  X-Powered-By : ASP.NET
  Deployment Provider url : http://www.XXXX/YYYYY.application
  
  ERROR SUMMARY
  No errors were detected during this operation.
  
  COMPONENT STORE TRANSACTION FAILURE SUMMARY
  No transaction error was detected.
  
  WARNINGS
  There were no warnings during this operation.
  
  OPERATION PROGRESS STATUS
  * [24/02/2006 09:51:27] : Activation of C:\Documents and Settings\David.XXXXX\Desktop\YYY.appref-ms has started.
  * [24/02/2006 09:51:27] : Performing necessary update check as specified by the deployment.
  * [24/02/2006 09:51:29] : Activation of C:\Documents and Settings\David.XXXXX\Desktop\YYY..appref-ms succeeded.
  
  ERROR DETAILS
  No errors were detected during this operation.
  
  COMPONENT STORE TRANSACTION DETAILS
  No transaction information is available.
  
  
  
  
  

• HeatherS2006

  Easy test to see if the Kensington Software is causing problems is:

  - Create a very simple HelloWorld.exe single binary app using VS
  - Create a test folder that's longer than 128 chars in length
  - Copy this exe to the test folder and try running it from there

  The exe will probably shutdown immediately on its own. If you run the same exe from shorter path it will work. If this is the behavior you're seeing then run exe under debugger and see if kmw_dll.dll is being loaded in the process. If so then Kensington Mouseworks is still present on the machine.

  Can you confirm couple of things:
  - You uninstalled Kensington Mouseworks from Add/Remove Programs right
  - Did you reboot after uninstall

  Can you find kmw_dll.dll on your machine If so try renaming it and see if that helps fix the problem.

  Regards,
  Sameer

  
  
  

• Stane Bozic

  Log is located in WinInet Cache, "\Documents and Settings\<UserName> \Local Settings\Temporary Internet Files" and starts with prefix "System_Deployment_Log".
  
  

• maxnis

  Try running EXE directly from ClickOnce store location and see if that works.

  To do this:
  - navigate using explorer to clickonce store folder where application is installed.
  - It's under a few levels of obfuscated folders so easiest thing is to search for <appname>.exe under "%userprofile%\local settings\Apps".
  - Run <appname>.exe

  Note: Do this as a troubleshooting step only. For regular activation of ClickOnce apps use the start menu shortcut (or url to .application file) so that the right update and security checks are done.

  If this direct activation of exe fails then looks like you have a general problem with launching managed apps on the machine not related to ClickOnce. If this is the case the general Windows Forms alias will be a better place to post the issue.

  One additional thing to check - do you by any chance have Kensington Mouseworks software installed We've seen problems with Winforms apps crashing when run on machines with this software installed. The mouse software has a bug that causes winforms app run from location greater than 128 chars in length to crash. This causes ClickOnce apps to crash. We are following up with Kensington Mouseworks to get this fixed.

  If this is indeed the problem on your machine you will need to uninstall the Kensington Mouseworks software from Add/Remove Programs. It will prompt for reboot after which the minimal mouse drivers should get reinstalled automatically. Your mouse as well as ClickOnce apps should then work.

  After uninstalling this software some extended mouse features and effects may not work but basic mouse functionality will be fine. I would recommend keeping the mouse software CD handy in case Windows is unable to auto-install the drivers from the web. We've seen a couple of people run into this issue and they both are able to use their mouse as well as run ClickOnce apps after uninstalling the software.

  Regards,
  Sameer

  
  
  

• Baris Guner

  Hi,
  
  Did someone solved this issue
  
  Im having the same problem and can't solve it
  
  Thanks
  
  
• Click-once application doesn't start