Cannot install my Clickonce App on a user's computer

Question

My clickonce app has the following pre-requisites:

Answer 1

The above was the scenario impacting computer 1. The following is computer 2's scenario: This computer also can not install the clickonce application. When attempting to launch the setup.exe, all of the pre-requisites are installed and right as it 'verifies the application', I get a pop up that says 'Application can not be started. Contact the application vendor'. I click on the Details button of the pop up and the following log appears:



PLATFORM VERSION INFO
 Windows    : 5.1.2600.131072 (Win32NT)
 Common Language Runtime  : 2.0.50727.3082
 System.Deployment.dll   : 2.0.50727.3053 (netfxsp.050727-3000)
 mscorwks.dll    : 2.0.50727.3082 (QFE.050727-3000)
 dfdll.dll    : 2.0.50727.3053 (netfxsp.050727-3000)
 dfshim.dll    : 2.0.50727.3053 (netfxsp.050727-3000)

SOURCES
 Deployment url   : file://RT445/Everyone/Database/PDB.application

ERROR SUMMARY
 Below is a summary of the errors, details of these errors are listed later in the log.
 * Activation of \\RT445\Everyone\Database\PDB.application resulted in exception. Following failure messages were detected:
  + Configuration system failed to initialize
  + Unrecognized configuration section system.serviceModel. (c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 146)

COMPONENT STORE TRANSACTION FAILURE SUMMARY
 No transaction error was detected.

WARNINGS
 There were no warnings during this operation.

OPERATION PROGRESS STATUS
 * [4/10/2009 2:12:57 PM] : Activation of \\RT445\Everyone\Database\PDB.application has started.

ERROR DETAILS
 Following errors were detected during this operation.
 * [4/10/2009 2:12:58 PM] System.Configuration.ConfigurationErrorsException
  - Configuration system failed to initialize
  - Source: System.Configuration
  - Stack trace:
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
   at System.Configuration.ClientConfigurationSystem.PrepareClientConfigSystem(String sectionName)
   at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
   at System.Configuration.ConfigurationManager.GetSection(String sectionName)
   at System.Configuration.PrivilegedConfigurationManager.GetSection(String sectionName)
   at System.Diagnostics.DiagnosticsConfiguration.GetConfigSection()
   at System.Diagnostics.DiagnosticsConfiguration.Initialize()
   at System.Diagnostics.DiagnosticsConfiguration.get_Sources()
   at System.Diagnostics.TraceSource.Initialize()
   at System.Net.Logging.InitializeLogging()
   at System.Net.Logging.get_On()
   at System.Net.WebRequest.Create(Uri requestUri, Boolean useUriBase)
   at System.Net.WebRequest.Create(Uri requestUri)
   at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
   at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
   at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
   at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
   at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
   at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
  --- Inner Exception ---
  System.Configuration.ConfigurationErrorsException
  - Unrecognized configuration section system.serviceModel. (c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 146)
  - Source: System.Configuration
  - Stack trace:
   at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
   at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
   at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
   at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)

COMPONENT STORE TRANSACTION DETAILS
 No transaction information is available.



I've tried the following but with no success:
-deleted the c:\documents and settings\USER NAME\local settings\App\2.0 folder so that upon attempting to re-install it would re-create the folder and hopefully resolve the issue.
-tried to successfully run ServiceModelReg.exe -i (and /i) to register the component which appears to be wrongfully referenced in the machine.config file.
-uninstall then re-install some hotfixes of .net that appear to be supposedly related. I am reluctant to do a full out install of .NET 2.0 on the user's computer because the feeling of causing more problems than resolving. I must have put in 20+ hours trying to find a solution, test it, realize I didn't yet find the right fix, and went back to the drawing board.

Any help would be appreciated. Take into consideration that at least 30 computers have installed the clickonce app without a problem, only 2 have been unsuccessful. I've seen some theories about altering 'my.settings'. As far as I can recall, I have not fiddled with my.settings, and since the 2 computers have been affected, more computers continue to install without a problem.

Answer 2

Hello,

Do you have a solution ? I have exactly the same problem.

Thanks

Answer 3

This was the solution for the computer with the following platform information:

Windows    : 5.1.2600.131072 (Win32NT)
 Common Language Runtime  : 2.0.50727.3053
 System.Deployment.dll   : 2.0.50727.3053 (netfxsp.050727-3000)
 mscorwks.dll    : 2.0.50727.3053 (netfxsp.050727-3000)
 dfdll.dll    : 2.0.50727.3053 (netfxsp.050727-3000)
 dfshim.dll    : 2.0.50727.3053 (netfxsp.050727-3000)

I uninstalled .NET 3.5 SP 1 . Then ran my ClickOnce install executable which pre-installs all the MS components before the UI. It re-installed .NET 3.5 and the ClickOnce application installed fully.

Likely corrupted config and/or driver files somewhere.

Answer 4

This was solution to computer 2 with the following platform info:
PLATFORM VERSION INFO Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.3082
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3082 (QFE.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)

This was more of a pain and the neck to troubleshoot. In fact, I put in more hours trying to figure out the solution to this one than computer 1. Note the different version #s referenced above whereas computer 2 were all 2.0.50727.3053 from CLR down to dfshim.dll .

Uninstalling .NET 3.5 alone did not resolve things. I noticed on this computer there were way more subheadings listed below the .NET framework headings in Add/Remove Programs, likely post installed fixes and the like. I removed .NET 3.5, .NET 3.0, and .NET 2.0 (which really was the culprit because the error pointed to 2.0). This had to done in said order because you can't uninstall an older version without uninstalling a more recent version. Its important to also bear in mind before you undertake this, to keep attention if the .NET installations are versions with service packs. Its best to keep consistent when re-installing. After uninstalling them, I re-installed it in the opposite order, 2.0, 3.0, then 3.5.

After re-installing 3.5, it should definitely by then force you to reboot. One thing that was odd when I just attempted to uninstall 3.5 then re-install (thinking this alone would do it because it did for the other computer) it, was it didn't force a reboot which seemed suspect to me. Both computers install my ClickOnce app now. This stupid error took several months to figure out!

Answer 5

Ouch, something in ClickOnce is just plain not working right.. IMO....To reinstall all of .NET with the error messasges indicated is just stupid.  MSFT should clean up their error reporting act on ClickOnce install issues.  These babies take days to fix...because everybody is forced to guess at solution.

---

Javaman

Answer 6

If there is a better solution, I'm all ears. As I had said, the latter computer took me months to troubleshoot successfully.

It was a major pain, but I fixed the problem. MSFT 'should' sounds like an oxymoron.