Taylor, this is very interesting. Thank you very much for reporting the issue. We have seen this problem very rarely and were never able to reproduce it on our side. A great help would be if you can let us know, how did you get into that state. Alternatively if you can zip 2.0 folder contents and export reg keys from HKEY_CURRENT_USER\Software\Classes\SOFTWARE\Microsoft\Windows\CurrentVersion\Deployment and send to me, I might be able to recreate your scenario on my machine and then debug it out. There is one issue here, that contents of 2.0 folder may have something you do not want to share. In that case do not send it, we may need to figure out some other way of debugging the issue.

I've got the same problem and do not know what to do. The source appers to be the mscorlib. If you find an aswer, please share it.

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:/Meus%20documentos/Visual%20Studio%202005/Programas%20Trabalhistas/Acordos%20Trabalhistas%20Word&Open/Acordos%20Trabalhistas.application
Application url: file:///C:/Meus%20documentos/Visual%20Studio%202005/Programas%20Trabalhistas/Acordos%20Trabalhistas%20Word&Open/Acordos%20Trabalhistas_2_0_0_0/Acordos%20Trabalhistas.exe.manifest

IDENTITIES
Deployment Identity: Acordos Trabalhistas.application, Version=2.0.0.0, Culture=neutral, PublicKeyToken=595c38c0162eacff, processorArchitecture=msil
Application Identity: Acordos Trabalhistas.exe, Version=2.0.0.0, Culture=neutral, PublicKeyToken=595c38c0162eacff, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Meus documentos\Visual Studio 2005\Programas Trabalhistas\Acordos Trabalhistas Word&Open\Acordos Trabalhistas.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [18/5/2006 19:04:37] : Activation of C:\Meus documentos\Visual Studio 2005\Programas Trabalhistas\Acordos Trabalhistas Word&Open\Acordos Trabalhistas.application has started.
* [18/5/2006 19:04:37] : Processing of deployment manifest has successfully completed.
* [18/5/2006 19:04:37] : Installation of the application has started.
* [18/5/2006 19:04:37] : Processing of application manifest has successfully completed.

ERROR DETAILS
Following errors were detected during this operation.
* [18/5/2006 19:04:38] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

The issue seems to be having an inplace update attempt of the deployment manifest. Whidbey ClickOnce unfortunately does not give a reasonable error message. Basically you will hit this problem when

- You have installed Deployment v1.0 (say D1)with application v1.0 (A1) on your machine.

- Now you have made change in your application, possibly adding new files or assemblies but you do not revise the version of the application manifest (keeping it still 1.0). Say this new application is A1'.

- You generate new deployment manifest, againignored updating its version, although contents have changed (D1').

- Now any attempt toinstall D1'-A1' combination will give theerror you have mentioned.

ClickOnce does not support such scenario where deployment or application content is changed but version is not revised. But this could be common in development time, and at this moment a menaingful error message is absent. To avoid this problem

- Update versions of deployment and application manifest

- Or uninstall older version, and reinstall the newer one.

I started having the same problem yesterday. I had made some changes to the application in question and published the new version, then discovered a problem and published a newer version soon after. When I tried to run the application it informed me of a new version and I clicked yes to download. I immediately got the error everyone else is getting. I uninstalled the application and tried to reinstall from the htm screen on the publised site and got the same error on install. The "+ Value does not fall within the expected range." message tells me nothing. Help!

Error info:

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:///H:/AppMaster/AppMaster.application
Deployment Provider url: file://fileserver/public/AppMaster/AppMaster.application
Application url: file://fileserver/public/AppMaster/AppMaster_1_0_0_29/AppMaster.exe.manifest

IDENTITIES
Deployment Identity: AppMaster.application, Version=1.0.0.29, Culture=neutral, PublicKeyToken=83b64f2dd6e54e1d, processorArchitecture=msil
Application Identity: AppMaster.exe, Version=1.0.0.29, Culture=neutral, PublicKeyToken=83b64f2dd6e54e1d, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of file:///H:/AppMaster/AppMaster.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [10/12/2006 8:13:02 AM] : Activation of file:///H:/AppMaster/AppMaster.application has started.
* [10/12/2006 8:13:05 AM] : Processing of deployment manifest has successfully completed.
* [10/12/2006 8:13:05 AM] : Installation of the application has started.
* [10/12/2006 8:13:06 AM] : Processing of application manifest has successfully completed.
* [10/12/2006 8:13:06 AM] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [10/12/2006 8:13:06 AM] System.ArgumentException
- Value does not fall within the expected range.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IStore.LockApplicationPath(UInt32 Flags, IDefinitionAppId ApId, IntPtr& Cookie)
at System.Deployment.Internal.Isolation.Store.LockApplicationPath(IDefinitionAppId app)
at System.Deployment.Application.ComponentStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.SubscriptionStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.FileDownloader.PatchFiles(SubscriptionState subState)
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Could you translate this into a plainer "do this" post, please? I am encountering the same issue, and I have been in the habit of doing the following for every ClickOnce publish of a VB2005 app:

- update assembly version (in My Project/Application/Assembly Information) by manually incrementing

- update file version (in My Project/Application/Assembly Information) by manually incrementing

- update publish version (in My Project/Publish) by manually incrementing

- update minimum version (in My Project/Publish/Updates)

I have been in the practice of setting all these to exactly the same value. For example, I recently deployed an updated build, and changed all versions above from 2.2.3.5 to 2.2.4.0 and got the problem. I have never *not* changed the versions prior to a ClickOnce publish.

If you could post about what I am doing wrong, or not doing (and add this to some sort of "you must do this for ClickOnce to work..." doc or better yet fix Visual Studio so all these separate versions can be managed in one place) I would appreciate it a lot, since I have an understandably unhappy client.

Additional information that may or may not be relevant: in addition to all the usual VB2005 files, I am also deploying a VB6/COM app plus several COM DLLs that my client needs. Basically, I am launching the VB/COM app from the VB2005 app when the client needs the legacy functionality (credit where credit due, got this idea from an article on MSDN). In order to make the COM DLLs work without regsvr32, I am also deploying a [legacy app name].exe.manifest file to enable the client systems to use one particular COMDLL that is getting deployed with the app. I have *not* been changing the version in this manifest file. I have had the VB6/COM exe and DLLs set to deploy always and also only when changed; this seems to not have made any difference in functionality. The legacy app name is completely different from the VB2005 app name. Below is the content of the legacy manifest file in case it could be causing problems...

Thanks - Patrick

<?xml version="1.0" encoding="utf-8"?>

<asmv1:assembly manifestVersion="1.0" xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<asmv1:assemblyIdentity name="[hidden].exe" version="1.0.0.50" publicKeyToken="0000000000000000" language="neutral" processorArchitecture="x86" type="win32" />

<file name="msstdfmt.dll" asmv2:size="118784" xmlns="urn:schemas-microsoft-com:asm.v1">

<hash xmlns="urn:schemas-microsoft-com:asm.v2">

<dsig:Transforms>

<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />

</dsig:Transforms>

<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />

<dsig:DigestValue>QXhzyMP4rsQTylneRNT1YNRxUg4=</dsig:DigestValue>

</hash>

<typelib tlbid="{6b263850-900b-11d0-9484-00a0c91110ed}" version="1.0" helpdir="C:\WINDOWS\system32\vb98.chm" resourceid="0" flags="HASDISKIMAGE" />

<comClass clsid="{2b11e9b0-9f09-11d0-9484-00a0c91110ed}" threadingModel="Apartment" tlbid="{6b263850-900b-11d0-9484-00a0c91110ed}" progid="MSSTDFMT.StdDataValue.1" description="StdDataValue Object" />

<comClass clsid="{6d835690-900b-11d0-9484-00a0c91110ed}" threadingModel="Apartment" tlbid="{6b263850-900b-11d0-9484-00a0c91110ed}" progid="MSSTDFMT.StdDataFormat.1" description="StdDataFormat Object" />

<comClass clsid="{99ff4677-ffc3-11d0-bd02-00c04fc2fb86}" threadingModel="Apartment" tlbid="{6b263850-900b-11d0-9484-00a0c91110ed}" progid="MSSTDFMT.StdDataFormats.1" description="StdDataFormats Object" />

</file>

</asmv1:assembly>

I am recieveing this error on first install, so the above solution deons't make senxe to me? This attached is my applicaiton manifest and I can't seem to see any issues with it but this is the first time I've looked at one?

Has anyone found the cause or a work around to this issue?

Thanks,

Greg

<?xml version="1.0" encoding="utf-8"?>
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v2" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:xrml="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<assemblyIdentity name="TSPT.application" version="2.0.1.2" publicKeyToken="f46112656f702cd2" language="neutral" processorArchitecture="msil" xmlns="urn:schemas-microsoft-com:asm.v1" />
<description asmv2:publisher="TSPT" asmv2:product="TSPT" xmlns="urn:schemas-microsoft-com:asm.v1" />
<deployment install="true" mapFileExtensions="true">
<subscription>
<update>
<beforeApplicationStartup />
</update>
</subscription>
<deploymentProvider codebase="file://shaker/cdtmfgstrat$/Perrego%20&amp;%20Assoc/TSPT/Install/TSPT.application" />
</deployment>
<dependency>
<dependentAssembly dependencyType="install" codebase="TSPT_2_0_1_2\TSPT.exe.manifest" size="7138">
<assemblyIdentity name="TSPT.exe" version="2.0.1.2" publicKeyToken="f46112656f702cd2" language="neutral" processorArchitecture="msil" type="win32" />
<hash>
<dsig:Transforms>
<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>XUYxAmZeWQqYhVy1JlY2nLoNamk=</dsig:DigestValue>
</hash>
</dependentAssembly>
</dependency>
<publisherIdentity name="CN=SBS\gperrego" issuerKeyHash="aecde72af34e4e7a5bf4112a29abb126cb03920d" /><Signature Id="StrongNameSignature" xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><DigestValue>2JIqAbFyNoGiAnEfinwHdMNzWT4=</DigestValue></Reference></SignedInfo><SignatureValue>NeQ4ByjFgpd2FGP+RArAR7fgtEpJFf8J0ZnpouCpFom8h0elRh40/Uhut4d9ZozhBpQWmfdmWeSlzmDdyEKDNtwYulcHIyyAzPhuztmbfe54sovYpiJOizoYMTXHAW5IEc6wNt+Rmtzo/q+CM/OIklvd//mROLJuWhi2Oc8ALrM=</SignatureValue><KeyInfo Id="StrongNameKeyInfo"><KeyValue><RSAKeyValue><Modulus>skw+VnpjrdqTTsiKgusf9nOAUhMfJ/8dGLigcoKBd73LQVUBXxWsZFiFgfebyP/x4agEmGJvB6w9LOb83lnTyCkcZShwFvFcIJ+8jgs1/KGU8mumZTFcRKtq1svs3+h0dXGL2C+0GcitB/ys9LDRATxmdm7PPM4rJET9AckCoi0=</Modulus><Exponent>AQAB</Exponent></RSAKeyValue></KeyValue><msrel:RelData xmlns:msrel="http://schemas.microsoft.com/windows/rel/2005/reldata"><r:license xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS" xmlns:as="http://schemas.microsoft.com/windows/pki/2005/Authenticode"><r:grant><as:ManifestInformation Hash="3e5973c374077c8a1f7102a2813672b1012a92d8" Description="" Url=""><as:assemblyIdentity name="TSPT.application" version="2.0.1.2" publicKeyToken="f46112656f702cd2" language="neutral" processorArchitecture="msil" xmlns="urn:schemas-microsoft-com:asm.v1" /></as:ManifestInformation><as:SignedBy /><as:AuthenticodePublisher><as:X509SubjectName>CN=SBS\gperrego</as:X509SubjectName></as:AuthenticodePublisher></r:grant><r:issuer><Signature Id="AuthenticodeSignature" xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" /><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" /><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" /></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" /><DigestValue>HjtKGJuZ0LvuIwhpzSIGGHb91Mg=</DigestValue></Reference></SignedInfo><SignatureValue>Fbtfp0UZxIDeb4bj0AXtGdhvh+tQmhwM8Qxe1f512A4mBrVrpLjccseu5o/CRChHfYSWp39ZCPFCJXqX7GFuY1BBXqpCXDz+JNG5wSy0FO+UfGdu1HLAsts/rdmLi8jx3S0rA1aSU5nlUj39DLip5f5vNIu4aWFy7vsYjMVeQfk=</SignatureValue><KeyInfo><KeyValue><RSAKeyValue><Modulus>skw+VnpjrdqTTsiKgusf9nOAUhMfJ/8dGLigcoKBd73LQVUBXxWsZFiFgfebyP/x4agEmGJvB6w9LOb83lnTyCkcZShwFvFcIJ+8jgs1/KGU8mumZTFcRKtq1svs3+h0dXGL2C+0GcitB/ys9LDRATxmdm7PPM4rJET9AckCoi0=</Modulus><Exponent>AQAB</Exponent></RSAKeyValue></KeyValue><X509Data><X509Certificate>MIIBwTCCAS6gAwIBAgIQcZWwwEiDwIxG0xxe9DudCjAJBgUrDgMCHQUAMCMxITAfBgNVBAMeGABTAEIAUwBcAGcAcABlAHIAcgBlAGcAbzAeFw0wNjEwMTgyMDUyNDlaFw0wNzEwMTkwMjUyNDlaMCMxITAfBgNVBAMeGABTAEIAUwBcAGcAcABlAHIAcgBlAGcAbzCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAskw+VnpjrdqTTsiKgusf9nOAUhMfJ/8dGLigcoKBd73LQVUBXxWsZFiFgfebyP/x4agEmGJvB6w9LOb83lnTyCkcZShwFvFcIJ+8jgs1/KGU8mumZTFcRKtq1svs3+h0dXGL2C+0GcitB/ys9LDRATxmdm7PPM4rJET9AckCoi0CAwEAATAJBgUrDgMCHQUAA4GBABK8nq+ZaiGINf1kLI+J5zDOiFvey5WDnTVA4QKGmI8QFKgRGkKbhr0z5v3GW4+g2Eg8gLOv+3i6tCJPgrrtQJbR5/BS+C0Ac3Xc+V5H2UbvKxaJLYmXaByaWf+o0kYTuH0gXSVRI0GfBmnYfU/eNu1e7MQZndXDFYHs5USuK1qw</X509Certificate></X509Data></KeyInfo></Signature></r:issuer></r:license></msrel:RelData></KeyInfo></Signature></asmv1:assembly>

Here is antoher copy of the error.

ERROR DETAILS
Following errors were detected during this operation.
* [10/22/2006 4:36:51 PM] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

This is still an issue for me and I am onsite doing an install, has there been any progress on this issue?

I recieve this error on first install. Even if I remove all files from the file share and then re jpublish I get the error?

Thanks,

Greg P.

I posted above about having this issue (I wrote about updating version numbers etc. and still seeing the problem, after trying to decipher the post about updating manifests and so on).

Have you tried to update assembly versions and also ClickOnce version (and minimum version number) as I describe above? Maybe that could help in your situation.

Good luck - Patrick

Sorry I did not see your comment previously. So in plain words if you hit this error do this:

- Update the version of your application manifest, resign.

- Then update version of deployment manifest and resign etc.

As long as they are different from anything you have already in your machine it should work.

Could you please describe exact steps you recommend (i.e. select this menu, click this button, etc.)? Please see my earlier post about what I already do versioning-wise and still get the problem, so I would like to see detailed steps you are recommending so I can see if I am missing anything.

Also the machines it is happening on for me have certainly never had anyone attempt manual intervention with any security policies.

Thanks - Patrick

I finally did get this working. I'm not really sure what solved the issue. I was attempting topublish the updatesvia VPN and I think the Windows user accounts caused some issues. If I posted to my machine and then move the files over to the share drive it worked? I'm not sure why?

I can still reproduce if I try to publish directly to the share... ? If someone at microsoft want more info on this let me know.

Thanks for your thoughts,

Greg P.

For what it's worth, I'm having the same problems as others here.

In my case, I'm deploying to my local IIS server (figuring if I get that working, I can try deploying to our "real" IIS server, or at least copy from my local one), and the application in question (if it matters) is a WinApp.

This is failing upon the first run (and every one thereafter), with similar messages to what others are reporting (the log is at the bottom of this e-mail).

I did try the command "caspol -reset" as suggested, and republished the application.

One thing that may be complicating matters is that the version of my application itself is v1.1.0.0, where the publish version is 1.0.0.2. But this doesn't seem to make a difference, as if I change the publish version to v1.1.0.0 (to match the application), I get the same errors.

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/lyonsm/Start%20Menu/Programs/Dematic%20Corp/Document%20Generator.appref-ms
Server: Microsoft-IIS/5.1
X-Powered-By: ASP.NET
Deployment Provider url: http://mycomputer/DocumentGenerator/Install/Test/DocumentGenerator.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Documents and Settings\lyonsm\Start Menu\Programs\Dematic Corp\Document Generator.appref-ms resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [11/16/2006 12:58:19 PM] : Activation of C:\Documents and Settings\lyonsm\Start Menu\Programs\Dematic Corp\Document Generator.appref-ms has started.
* [11/16/2006 12:58:20 PM] : Performing necessary update check as specified by the deployment.

ERROR DETAILS
Following errors were detected during this operation.
* [11/16/2006 12:58:20 PM] System.ArgumentException
- Value does not fall within the expected range.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)
at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, TempFile& deployFile)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Any ideas what I can do so I can get this working?

For what it's worth, my testing is happening on a Virtual PC, running Windows XP Sp2, so I can start with a truly clean system again after each try (just rolling back the changes).

Thanks!

FYI:

We were having the failure in this thread when deploying to a MyDocuments folder that resided on a file server:

Based on the tips in this thread we set the target to c:\temp and that worked for us.

Please reply if you need more info about our network setup.

yes I have a thread on this below im able to replicate this error there are quite a few threads about this but one does not see any definitive answer from MS I dont know about the professional editions but with express editions ( which is aimed at hobbyists students etc ) bug will def occur

As there is no answer I have worked my way around it by changing the app name to for example 'program v1.1' to program v1.2' everytime I make an update then setup will simply create another program rarther than replace existing one ( which if replaced due to same app name and one tries to remove from add/remove progs , you will get error when you try to install from then on any app) I can then remove old version from add remove no problem as it has not been replaced.

But obvisuly it should simply update existing version rarther than simply replace shortcut on start menu and create mumbo jumbo somewhere on hard dsik where app code lies and whatever it does in registry.

I have struggled with the same issue and finally have a solution or at least a workaround. Somehow the manifest signature or iteration has gotten out of synch. If you delete the manifest folder completey, uninstall the application, then deploy again via ClickOnce, the manifest folder gets recreated and you are back on track.

C:\Documents and Settings\dsouthern\Local Settings\Apps\2.0\DNWPG3ZG.8XV\AJPH1GD4.TX2

Of course, change the user name under docs and settings to you and the exact path will vary, but, you will find the manifest folder following this example. Let me know if this doesn't work.

Lets say I send my friend a program on CD created with click once, he installs this program and appends to say a text file with that program.I then make an alteration to said program and put updated program back on CD using clik once and send it to him, he installs my updated program but his text with the alterations he made have gone.

Instead of getting update he more or less got a new app thats starts all over again looks same program on start menu etc but does not work like an update.

He then removes program from add/remove in control panel, I then send him a new prgram using clik once and now he cant install that becasue hes getting 'value does not fall witihn expected range' error

This is visual basic express edition is intended for hobbyists students and novice programmers im sure a seasoned pro can just go in andplay around with registries manifests etc.. to correct problem but for average joe he'l spend countless hours looking in these forums and encounter a conundrum of answers regarding this issue I think i've seen 1 reply from MS concerning this its all very strange !

Well i had the same problem!!

Solution for this is:

goto IIS delete all previous published versions....

goto C:\Documents and Settings\"Local User Account"\Local Settings\Apps\2.0\625KN8NL.0OO\XD5VZ6A8.NOP delete all the files in this directory!!

this should work guys!!!!!!!!!!!!

Thanks,

Krishna

OK, I just wanted to write a quick post that I figured out why the problem was occuring for me.

Turns out when I publish to a share that included the "&" character (like s:\share\this & that\), I got the message "value does not fall within expected range" There was a reference to MSCORLIB in the error message.

That's it.. no version checking or deleting files... etc.. just a lousy ampersand..

Ugh..

Max

This is a confirmation of what Max has written:

1) If the path contains an ampersand symbol (&) this triggeres the described error.

2) Removing the ampersand (&) from the path immediately resolves the problem.

3) I wasted about two working days on tracing this. This forum and Max'es posting saved me.

Plamka

This is a post-factum posting, intended to save the time of all new readers of this thread:

1) The described problem, which is reported in the previous posting, and which has been encountered independentlyby several different persons, has been resolved. For the solution see Max'es posting on this threadof 09/Jan/2007.

2) You may continue to read the thread from the beginning to Max'es posting, but this is unlikely to provide youany useful information or any practical ways of resolving the issue (apparently this thread went througha lot of wild-goose chase and the investigation moved in allpossible directions, but not until the posting of Max was the issue clarified and resolved.

3) And to save you even more time, here is what Max reported (this happens to be my case too): an ampersand ("&") in the installation path of the deployed application causes the describederror. Renaming the folder orchanging the installation path to a different one immediatelly resolves the problem.

4) This may not be the whole truth. If you encounter exactly the same error message as quoted above, chancesare that it is caused by the same problem, but no warranty is given.

Plamka

Whoa - not so fast.

I am one of the people who encountered this repeatedly. Let me state this very clearly:

THERE WERE NO AMPERSANDS OR OTHER CHARACTERS NOT FOUND IN A LEGITIMATE URL,AND NO UNC PATHS,IN MY DEPLOY OR UPDATE PATH AT ANY TIME WHEN ENCOUNTERING THIS PROBLEM.

Given the inconclusive and uninformative error messages, I think we need a little bit more in the way of a real response from Microsoft. For example: does Visual Studio 2005 SP1 fix this? Under what conditions has MS reproduced this problem in internal testing?

Hi,

None of the proposed solution work for me.

Remove target files and temporary myDoc...

Manualy synchronize manifest and config version (they are equal)

Rename the project.

Check for encoding of the different deploy files.

Today i can't deploy.

Is Microsoft working about that ?

I am really sorry to see that this problem has been so widespread. There has been several issues identified that results in showing error text "Value does not ... range.". ClickOnce relies on different managed and unmanaged components, often several unmanaged errors get translated into one managed error hence confusing the scenario. As far as I know, most common reason is version and content mismatch. ClickOnce that has been released differentiates applications by their identities. ClickOnce v1.0 that was released back in Oct 2005 assumes that version of manifest and their contents are always in sync. So when anyone changes anything in the deployment, like adds a file or removes a file or component, ClickOnce assumes that they will always revise the version too. In practice this is not the case. Developersmodify their application package publish updates without really changing version. Current ClickOnce fails to recover from this gracefully and shows cryptic error of "Value does not ... range.".

Again this is not the only way you can get into this. In other cases call stacks are slightly different. One drastic solution is to delete the ClickOnce storage completely (but this would remove all other ClickOnce apps to).

As I mentioned in a previous post, I changed the ClickOnce published version as well as assembly info (file and assembly version) on *every single publish* (partly so users were advised that a newer version was available). I was extremely careful to do this.

The errors occurred despite this. It is beginning to sound like the current ClickOnce has deep problems and that this is not just some incidental bug? And again, was any of this addressed in VS2005 SP1?

Thanks.

pelazem, one way that you can make sure the versions were actually updated is to check the deployment manifest (.application file). Do you see it different, I dont have much idea on how VS generates those manifests, whether steps that you have taken will actually result in change in version of the deployment manifest. I can debug your particular case further if you can provide me a dump of your ClickOnce store where the failure is happenning. To create a dump, do this:

- From repro machinezip the ClickOnce app store folder. App store location on client machine:
XP: c:\documents & settings\<user>\local settints\Apps
VISTA: c:\users\<user>\AppData\Local\Apps

-Export registry key HKCU\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment to file.

-Also add the deployment payload which is failing to install.

Yes 'click once' needs a route canal, I installed using clik once then removed in add remove progs then reinstalled exatly same program ( no changeds made) then removed from add/remove progs on next attempt I got the error message after installing using clik once.

I never republished or made any changes to application I merely installed and reinstalled using the same setup files and removed using 'add/remove programs'

Ive read coumtless posts as to how people are getting this through various means but the fact is 'click once' is unreliable it can be compared to buying a used car from dodgy Frank it breaks down this week, you tweak it then it breaks down again.

Weather or not these problems exist in professional edition I dont know, but in the 'free' express edition' for idiots like me it certianly does.

Apart from 'click once' the rest of express works great

I don't kown if this can help you.

1) I had the related problem on the first issue on my projet.

2) After a lot of try and retry i have completly rebuild my projet under a new name, newfolder (everything new !)

3) The first remark i can do is that ClicOnce plublish version was not the same beween my old and my new project. On my old project the starting version was 0.0.0.0. On my new project it is 1.0.0.0.

4) Same remark on my project manifest : Old project "1.0.*" (Only 3 level with third = star ) . On the new manifest project 1.0.0.0.

5) I have also changed the target install directory (destroying the old named install3, creating a new named install4, uninstalling the remainder of my previus unsuccess install!).

Usingthese paranoiac precautions, my deployement was a success .

At the time i am writing i am still very anxious about the deplyoment of the future release...

Recently we got a good repro of this problem, particularly when the call stack looks like below. It seems this is caused by discrepancy in <assemblyIdentity> of componentsbetween application manifest and their assembly metadata. Verifying this is not easy, but you can do this if you want to:

-Check every <dependency> item in your application manifest (possibly the .exe.manifest). Open the correspindingdll/exe (see codebase attribuite for location) item in ildasm.exe. Now see whether the metadata identity matches with the <assemblyIdentity> of that <dependency>.

- Seems like sometimes there are extra attributes, particularly you have attribute Retargetable="Yes/No" in the metadata. If you have such attributes you are likely to get this "value does not fall ..." error, with a callstack like below.

To fix this manually update your application manifest to add the attribute (e.g. Retargetable) in your corresponding <depemdency><dependentAssembly><assemblyIdentity>and sign, generate deployment manifest.

This could be a labor intensive process, untilfix is made in the tools that generates manifests.

Callstack :

at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)
at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, Uri activationUri)
at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, TempFile& deployFile)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

Thanks everyone for reporting this issue.

This worked for me. Thanks.

Well, that's at least something, though are you talking about a .NET 4.0 since 3.0 has been out for a little while now????

Separately, I have been experiencing other ClickOnce problems in addition to this one. Despite insane efforts to wipe local storage and uninstall through Add/Remove, redo all versions (ClickOnce and assembly), double-check manifests with mageui.exe, ClickOnce is inconsistent in my scenario. Some machines fail with various errors seemingly at random; I googled all of them, found many reports of every one, and no solution to any one.

Examples include that the application is not packaged properly and to contact the application vendor; I found that this can happen when the manifest does not include a publisher and that the recommendation was to add it using mageui.exe. Well, it did, mageui saw the publisher, and still failed.

Eventually I got so desperate that I packaged ***exactly*** the same app as a setup.exe using a standard deployment project. I did not even change assembly versions or anything else. It worked; every single install using that has been flawless on machines that barfed with ClickOnce. Needless to say, this is a poor scenario for the customer, who now faces uninstall/reinstall per-machine labor; granted, they do not have a central deployment infrastructure in place and they should.

One final note that may hopefully help Microsoft. I have come across a couple of pieces of info that various network equipment (e.g. firewalls, proxy servers) filter out in-stream XML or other ASCII content. So even if one chooses to use the .deploy file extension to get around filename-based defenses, it's the HTTP stream that gets examined and ***maybe*** something is getting stripped out. The customer who is having all this trouble may have something like this on their network; I have been trying to get details.

So maybe a future, stronger version of ClickOnce could guard against this somehow, maybe by packaging all assembly, deployment, etc. info in one file and making it a binary file? Other than that ClickOnce is a great concept, it just needs to get more robust. Thanks for the update.

I encountered the same error message before.Iwas able toinstall a fresh new one from another PC, however I cannot upgrade the one on my client PC successfully. (Note I had uninstalled it from Add/Remove Program files and it didn't even show up in the list any more.)

I finally resolved this by:

1. Remove all installation files for the application from my client PC (%HOMEPATH%\Local Settings\Apps\2.0\...)
2. Remove all registry entry for this installation (HKCU\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\SideBySide\2.0\...)

Hope this helps.

I have the same error and none of the suggestions here has affected it.

The firstinstall worked but every attempt since then has failed.

This happens even when doing a fresh install on a new machine.

I have tried deleting all the project outputs, all the manifests, turning ClickOnce off and releasing through an MSI and then turning it back on again. Following earlier messages I have checked through the manifests and all the dependencies are at the correct version and the attributes mentioned are not present.

What's more worrying is I contacted Microsoft for help and they pointed me at this thread and said the problem was solved. Does that mean no further effort is being made to resolve this issue?

As it stands it's hard to see how I or anybody else can use ClickOnce deployment. It seems this can happen at anytime even if the deployment is working fine at the moment. When it strikes every copy of your application will stop working and because we have no idea what's causing itthere will be nothing you can do to get it started again.

Has anybody else had a similar experience to me? Have they managed to resolve it?

It would be good to get this sorted because ClickOnce is such a great idea.

Mike

Mike, I am one of the previous posters here. I "solved" this (i.e. it rarely happens anymore) by turning off ClickOnce automatic version incrementing, and by making sure at every release I change the version in four places:

- assembly info for both assembly and file version

- ClickOnce version (making sure to keep the automatically increase version checkbox off)

- under Update, making sure I always set the minimum version to the same as elsewhere

A while back I tried out mageui.exe (one of the VS tools) and it told me essentially all was well - try in your env.

Also, under ClickOnce files to be deployed ("Application Files"), esp. when you change versions of dependent assemblies (e.g. UI toolkits etc.) make sure once in a while to hit Reset All. This has also cleaned up ClickOnce publish problems for me more than once.

All the above can be accessed from the various tabs on the My Project node in Solution Explorer.

One other thing I tried with cooperative sys admin is to delete all previously deployed versions of the app off users' PCs. Others here have mentioned this. It "fixed" the problem... Obviously, this may not always be possible.

As to Microsoft saying this is fixed, I got this problem just as much after Visual Studio 2005 SP1, so it's not fixed; they may mean that some people found workarounds or avoidances without knowing exactly why.

Separately, I reported a problem with the Windows Forms UI designer to Microsoft (repeatably got Visual Studio to crash by dragging a FlowLayoutPanel with non-Top/Left anchor across another FlowLayoutPanel, Microsoft confirmed it) and their response on Connections was that it was fixed. What did that actually mean? Looking at their response, they fixed it in theVS2008 beta, where the bug also existed, but never answered my question about whether they would also fix it in their current shipping, production version (VS2005)since some of us are still on that instead of the next beta for our daily work. Draw your own conclusions about what "fixed" means, then. Best of luck and hope the above help.

Thanks pe619,

I think you have summarised some of the many things covered in this thread. Nevertheless I went through them all and tried it but to no avail.

I think we may be looking at a symptom rather than a problem. I have the impression this error occurs if anything goes wrong with the installation. Unfortunately I can't find anything else in the log file which will show me where to look.

Thanks for taking the time to post anyway.

I have pasted the log from the latest attempt in case it means anything to anybody.

PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.832
System.Deployment.dll : 2.0.50727.832 (QFE.050727-8300)
mscorwks.dll : 2.0.50727.832 (QFE.050727-8300)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url: http://4ql-nb6/TOPS/TOPS.application
Server: Microsoft-IIS/5.1
X-Powered-By: ASP.NET
Deployment Provider url: http://4ql-nb6/TOPS/TOPS.application
Application url: http://4ql-nb6/TOPS/TOPS_1_0_2_10/TOPS.exe.manifest
Server: Microsoft-IIS/5.1
X-Powered-By: ASP.NET

IDENTITIES
Deployment Identity: TOPS.application, Version=1.0.2.10, Culture=neutral, PublicKeyToken=cd58d741c0ddbeda, processorArchitecture=msil
Application Identity: TOPS.exe, Version=1.0.2.10, Culture=neutral, PublicKeyToken=cd58d741c0ddbeda, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://4ql-nb6/TOPS/TOPS.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [08/08/2007 14:23:36] : Activation of http://4ql-nb6/TOPS/TOPS.application has started.
* [08/08/2007 14:23:37] : Processing of deployment manifest has successfully completed.
* [08/08/2007 14:23:37] : Installation of the application has started.
* [08/08/2007 14:23:37] : Processing of application manifest has successfully completed.
* [08/08/2007 14:23:38] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [08/08/2007 14:23:38] System.ArgumentException
- Value does not fall within the expected range.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IStore.LockApplicationPath(UInt32 Flags, IDefinitionAppId ApId, IntPtr& Cookie)
at System.Deployment.Internal.Isolation.Store.LockApplicationPath(IDefinitionAppId app)
at System.Deployment.Application.ComponentStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.SubscriptionStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.FileDownloader.PatchFiles(SubscriptionState subState)
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

I have solved my problem.

On closer inspection I found 2 (yes 2) copies of the application installed. When I un-installed these through Add/Remove programs the installation started working. It wasn't enough to clear the App folder.

How I managed to get 2 copies I have no idea. ClickOnce should have updated the first one.

At least now I know how to fix it if it happens again.

It's a pity the log file couldn't have given more relevant information. Perhaps that will be in the next version.

I would also like to say publicly that Microsoft eventually helped a lot. I had a phone call from Souvonik Mondal of Microsoftwho demonstrated real concern for the problems I was having and that ClickOnce should have such a serious flaw. Of course I now know it doesn't but we didn't know that at the time of his phone call.

If nothing else this will at least give you something else to check if you encounter the problem yourself.

Mike

Mike, glad to hear that your problem was at least partly solved for now. We understand the frustration some developers encounter while using ClickOnce. If you could repro your earlier problem it would be a great help if you can send us your ClickOnce store to us. It appears "value does not fall ..." error could happen for many different reasons, from the storage layer beneath ClickOnce. Each one seem to have different underlying design or code issues. We need help from developers like you to understand and fix the problems you hit. We have already made some of the fixes in Orcas (framework 3.5). We will continue to make fixes in storage layer or adjust ClickOnce code on top of it. Unfortunately storage layer gives almost identical error messages for all kinds of issues it has.

Hi Epsilone3,

I un-installed the ClickOnce Application. After you have run a ClickOnce application you will find it in the list of 'Add/Remove' programs. Depending on how you set up the install click Change/Remove will un-install the application or let you step back to the previous version.

In my case I had several version of the application installed. I'm still not sure how that happened but I now suspect one of them was because I had changed the authenticode key between versions. Anyhow, I un-installed them all and ClickOnce started to work again.

Out of all my difficulties, one thing is clear. This is not a single problem. The same error message appears for a whole range of different and perhaps completely unrelated problems. So, what works for one may not work for another. Hopefully in later versions the error reporting will be more precise.

Mike

Hi mike I really got a great eye and I've search the add/remove again and again and can't find any ClickOnce or Microsoft..ClickOnce app to Uninstall it..

I've still got this "Navigation canceld"

and this "Error message"

URI של אתחול: I:\SilverLight&Wpf\Wpf\Xbap\WebList\WebList\bin\Debug\WebList.xbap
זהות יישום: file:///I:/SilverLight%26Wpf/Wpf/Xbap/WebList/WebList/bin/Debug/WebList.xbap#WebList.xbap, Version=1.0.0.1, Culture=neutral, PublicKeyToken=d13d68eb2af935bb, processorArchitecture=msil/WebList.exe, Version=1.0.0.1, Culture=neutral, PublicKeyToken=d13d68eb2af935bb, processorArchitecture=msil, type=win32

System.ArgumentException: הערך אינו נמצא בטווח הנדרש.
ב- System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
ב- System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
ב- System.Windows.Interop.ApplicationLauncherXappDebug.Initialize()
ב- System.Windows.Interop.DocObjHost.MS.Internal.AppModel.IBrowserHostServices.Run(String path, String debugSecurityZoneURL, String viewerUri, String fragment, String applicationId, MimeType mime, Object streamContainer, Object ucomLoadIStream, Boolean isDebugMode, String progressAssemblyName, String progressClassName, String errorAssemblyName, String errorClassName)

-----------------------

PresentationHost.exe v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\system32\PresentationHost.exe
ntdll.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\ntdll.dll
kernel32.dll v5.1.2600.3119 (xpsp_sp2_gdr.070416-1301) - C:\WINDOWS\system32\kernel32.dll
ADVAPI32.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\ADVAPI32.dll
RPCRT4.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\RPCRT4.dll
USER32.dll v5.1.2600.3099 (xpsp_sp2_gdr.070308-0222) - C:\WINDOWS\system32\USER32.dll
GDI32.dll v5.1.2600.3159 (xpsp_sp2_gdr.070619-1300) - C:\WINDOWS\system32\GDI32.dll
msvcrt.dll v7.0.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\msvcrt.dll
ole32.dll v5.1.2600.2726 (xpsp_sp2_gdr.050725-1528) - C:\WINDOWS\system32\ole32.dll
SHELL32.dll v6.00.2900.3051 (xpsp_sp2_gdr.061219-0316) - C:\WINDOWS\system32\SHELL32.dll
SHLWAPI.dll v6.00.2900.3157 (xpsp_sp2_qfe.070614-1244) - C:\WINDOWS\system32\SHLWAPI.dll
urlmon.dll v7.00.6000.16512 (vista_gdr.070625-1522) - C:\WINDOWS\system32\urlmon.dll
OLEAUT32.dll v5.1.2600.3139 - C:\WINDOWS\system32\OLEAUT32.dll
iertutil.dll v7.00.6000.16512 (vista_gdr.070625-1522) - C:\WINDOWS\system32\iertutil.dll
WININET.dll v7.00.6000.16512 (vista_gdr.070625-1522) - C:\WINDOWS\system32\WININET.dll
Normaliz.dll v6.0.5441.0 (winmain(wmbla).060628-1735) - C:\WINDOWS\system32\Normaliz.dll
IMM32.DLL v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\IMM32.DLL
LPK.DLL v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\LPK.DLL
USP10.dll v1.0420.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\USP10.dll
comctl32.dll v6.0 (xpsp.060825-0040) - C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll
LVPrcInj.dll v11.1.0.2021 - C:\Program Files\Common Files\Logishrd\LVMVFM\LVPrcInj.dll
uxtheme.dll v6.00.2900.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\uxtheme.dll
MSCTF.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\MSCTF.dll
lgscroll.dll v3.30.165 - C:\Program Files\Logitech\SetPoint\lgscroll.dll
MSVCR80.dll v8.00.50727.1378 - C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1378_x-ww_5c7e3652\MSVCR80.dll
MSVCP80.dll v8.00.50727.1378 - C:\WINDOWS\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.1378_x-ww_5c7e3652\MSVCP80.dll
NTMARTA.DLL v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\NTMARTA.DLL
WLDAP32.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\WLDAP32.dll
SAMLIB.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\SAMLIB.dll
CLBCATQ.DLL v2001.12.4414.308 - C:\WINDOWS\system32\CLBCATQ.DLL
COMRes.dll v2001.12.4414.258 - C:\WINDOWS\system32\COMRes.dll
VERSION.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\VERSION.dll
xpsp2res.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\xpsp2res.dll
Secur32.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\Secur32.dll
ws2_32.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\ws2_32.dll
WS2HELP.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\WS2HELP.dll
dfshim.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\system32\dfshim.dll
mscoree.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\system32\mscoree.dll
mscorwks.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
PresentationHostDLL.dll v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\Microsoft.Net\Framework\v3.0\WPF\PresentationHostDLL.dll
mscorlib.ni.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\mscorlib\8e53e914db14e63bc604da831c2aefc6\mscorlib.ni.dll
System.ni.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System\fb257267fce81b957b63ec6eb3bb1122\System.ni.dll
WindowsBase.ni.dll v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\WindowsBase\e75b0da72a09fc1b710c05491f4321c3\WindowsBase.ni.dll
PresentationCore.ni.dll v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\PresentationCore\aff8bf5cc95aaf556d688841f20ec75a\PresentationCore.ni.dll
PresentationFramework.ni.dll v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\PresentationFramewo#\fb90e15ec802cbd67634a18de4c0f8b9\PresentationFramework.ni.dll
msctfime.ime v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\msctfime.ime
actxprxy.dll v6.00.2900.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\actxprxy.dll
SXS.DLL v5.1.2600.3019 (xpsp_sp2_gdr.061019-0414) - C:\WINDOWS\system32\SXS.DLL
PresentationHostProxy.dll v3.0.6920.1005 (lh_tools_devdiv_wpf_beta2(avdrt).061020-1904) - C:\WINDOWS\system32\PresentationHostProxy.dll
ieproxy.dll v7.00.5730.11 (winmain(wmbla).061017-1135) - C:\Program Files\Internet Explorer\ieproxy.dll
ctagent.dll v1, 0, 0, 5 - C:\WINDOWS\system32\ctagent.dll
DSOUND.dll v5.3.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\DSOUND.dll
WINMM.dll v5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) - C:\WINDOWS\system32\WINMM.dll
System.Xml.ni.dll v2.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System.Xml\2115a162ac3d4d43c5b54bc87a474500\System.Xml.ni.dll
mscorlib.resources.dll v2.0.50727.42 (RTM.050727-4200) - C:\WINDOWS\assembly\GAC_MSIL\mscorlib.resources\2.0.0.0_he_b77a5c561934e089\mscorlib.resources.dll
diasymreader.dll v8.0.50727.1378 (REDBITSB2.050727-1300) - C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\diasymreader.dll

My computer work find !

But maybe cause I've got a VS5 before with the same problem I Need to Format my machine.

But I do that please give me altrnative.

Thank's Guy.

You have misunderstood me. ClickOnce is not the application it is just the technology used to deploy the application. If you have managed to deploy your application using ClickOnce your application should appear in the Add/Remove Programs list.

Like I said the same error appears for a variety of reasons so what works for me will not necessarily be of any help to you.

I don't think it will be necessary to re-format your computer. That seems a bit extreme.

Mike

I don't know about the registry key, HKCU\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\. I have successful deployments created and installed on my computer and it doesn't have this key either. What were you expecting to find in it?

Your missing Add/Remove entries suggests you have never deployed successfully to this computer but the presence of the ..\Local Settings\Apps\2.0\... folder suggests you have. Is this a first time install or an update?

Are you running a beta copy of VS 2005? If so perhaps you would be better to upgrade to a full copy. It has been out for some time now.

Investigating me problem suggests this is not a fault in the ClickOnce but just poor reporting of deployment issues when they arise. MS have already said fixes to thiswill appear in later versions (not clear which version they mean though 3?, 4?). There has been no suggestion of a patch to current versions I have heard of. (But perhaps I just haven't heard about it, anybody care to enlighten me on this?)

Mike

Even i have faced the same problem, i tried in the same way as he explained.

Normally your application will beinstalled in this path only, C:\Documents and Settings\d3199\Local Settings\Apps\2.0.

if you have done any modifications in this folder, then you will face this problem. you just change the folder name 2.0 to some other name and install the application again. It will work properly.

2nd Error if you face this Error

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

If you have done any modifcations in this folderC:\Documents and Settings\d3199\Local Settings\Apps\2.0.

do the same thing. Just change the folder name to some name as explained above.

I'm outta this tarpit!

i made another app that has all the same refrences as the problem app.

that and a heelo button.

Bang! it works.

Good luck. thisis an ugly one.

PLATFORM VERSION INFO
Windows : 6.0.6000.0 (Win32NT)
Common Language Runtime : 2.0.50727.1433
System.Deployment.dll : 2.0.50727.1433 (REDBITS.050727-1400)
mscorwks.dll : 2.0.50727.1433 (REDBITS.050727-1400)
dfdll.dll : 2.0.50727.1433 (REDBITS.050727-1400)
dfshim.dll : 2.0.50727.1433 (REDBITS.050727-1400)

SOURCES
Deployment url: file:///C:/Users/James%20&%20Sara/Desktop/Test/WindowsGame1.application
Application url: file:///C:/Users/James%20&%20Sara/Desktop/Test/WindowsGame1_1_0_0_1/WindowsGame1.exe.manifest

IDENTITIES
Deployment Identity: WindowsGame1.application, Version=1.0.0.1, Culture=neutral, PublicKeyToken=c79b5e8c5516c505, processorArchitecture=x86
Application Identity: WindowsGame1.exe, Version=1.0.0.1, Culture=neutral, PublicKeyToken=c79b5e8c5516c505, processorArchitecture=x86, type=win32

APPLICATION SUMMARY
* Installable application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\James & Sara\Desktop\Test\WindowsGame1.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [28/02/2008 3:04:47 PM] : Activation of C:\Users\James & Sara\Desktop\Test\WindowsGame1.application has started.
* [28/02/2008 3:04:47 PM] : Processing of deployment manifest has successfully completed.
* [28/02/2008 3:04:47 PM] : Installation of the application has started.
* [28/02/2008 3:04:47 PM] : Processing of application manifest has successfully completed.

ERROR DETAILS
Following errors were detected during this operation.
* [28/02/2008 3:04:48 PM] System.ArgumentException
- Value does not fall within the expected range.
- Source: mscorlib
- Stack trace:
at System.Deployment.Internal.Isolation.IDefinitionAppId.EnumAppPath()
at System.ActivationContext.CreateFromNameAndManifests(ApplicationIdentity applicationIdentity, String[] manifestPaths)
at System.Deployment.Application.ActivationDescription.ToActivationContext()
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

James,

As the long topic suggests, this problemoriginatesfrom many different issues. In your case, however, I think I know how you can fix it...

In your Deployment URL and Application URL, you have an ampersand (&) in the paths:

C:/Users/James & Sara/Desktop/Test/WindowsGame1.application
C:/Users/James & Sara/Desktop/Test/WindowsGame1_1_0_0_1/WindowsGame1.exe.manifest

By removing the ampersand from your path, your ClickOnce deployment will likely be fixed. The key to your problem is in the ERROR DETAILS section of your installation log. When the failure is in Source: mscorlib, it's likely an ampersand in the path or application name.

Others here are getting errors with a source of System.Deployment. These seem to be related to Assembly, File, and Publish version issues.

Moral of the story? Take a look at the Source: in the ERROR DETAILS section of your installation log:

• If Source: mscorlib, then look for an ampersand in the deployment path or application name.
• If Source: System.Deployment, make sure you review your versioning and look for other workarounds in this thread.

Hope this helps!

Joe Cogan

Real Time Intelligence, Inc.

Yes, sorry I'd worked this out already.

It fails if the installer resides in a path with the "&" symbol.

Cheers,
James

ANOTHER CAUSE AND SOLUTION

This nasty error message showed up in one of our ClickOnce installations. After trying everything mentioned in this thread without success we found another cause and solution to this error.

We have a solution with 10 projects, three of these projects refernce the Microsoft.Ink library. There is also a reference in the main project this library so it is included in the ClickOnce deployment.

All references to this library should be to version 6.0.0.0 however a reference in one of theprojects pointed to version 1.7.2600.2181.

Changing the reference to point to version 6.0.0.0 fixed the problem.

I suspect thatupon launch of the application ClickOnce checks that all required versions of dlls are present and if not it throws this incredibly helpfulerror message. I assumethis would apply to any dll not just Microsoft.Ink.

Hope this helps someone.

Regards,

Dean

Hi,

the missunderstand is that (for me)

the problems are normal ve they have to solve. but why it works on some comp. doesn't work comp. we try on many different comp. it works on some, and doesn't work on many ones. every one has different error message. the error messages are defined in passed threads. I want this, if works on my comp. it should, must, have to work on every comp. of course if comps. have min. prequesties. Because .net isn't depent on operator system or comp. that's why people prefer.

it's a just complaint

Hi,

Our test engineer has reported the issue (which works on some comp and doesn't work on some comp) the ptroblem is internet explorer read everything from cache and you can remove application cache by your way. so you have to download mage(Manifest generator & editin tool) - it's also comes with vs 2008 in SDK COmmand Line.

When you type " mage -cc " in SDK Command Line (C:\Program Files\Microsoft Visual Studio 9.0\VC>)

then you will see the ie starts to download application...

I know this thread is old, but it is the most current information I could find on the Internet, andI thought I'd add my two sense.I've been working with Click-Once for a couple months now, and until this morning, I never ran into this problem.

My Click-Once app is a WPF application developed with VS2008 SP1. This morning, I attempted to run it and got this error. I wiped out every cache I could think of, and still no go. Then I had an idea. It was sparked by the fact that oddly enough, even when Iran my app within VS this morning, calling ApplicationDeployment.IsNetworkDeployed produced the same error?!

Yesterday, I installed a third-party .NET application that installed the .NET Java runtime, even though it was already installed. I hadn't tried my ClickOnce app since then. My thought was that perhaps it somehow corrupted my version of .NET (.NET 3.5 SP1). So, I ran the repair install and now everything works fine again. I'm not sure if this was caused by the java runtime, or just a conincedence, but it solved this problem for me where changing version numbers, etc, didn't.

As a sum-up, this last issue with Click-Once has broken the camel's back. I've had to develop so many work arounds when using Click-Once technology that it would be almost impossible for someone else to understand it all. I'm thinking that although I've tried to avoid it, I'm going to have to use awindowsinstaller and then implement my own version of an update program. Sorry guys. I gave Click-Once my best shot, but it just isn't flexible enough and has too many bugs.

Back to the drawing board.

I recently devloped a Com+ component and i used the Component into another project.

Everthing Worked fine and the application gave no errors .Until I changed My Com+ Activation Type in the Microsoft Management console from LIBRARY APPLICATION to SERVER APPLICATION and when i used the component again with my application it gave me the error "Value does not fall within the expected range".

So i again changed the Activation Type in the Microsoft Management console from SERVER APPLICATION to LIBRARY APPLICATION and it gave me no error

I dont know if this is helpfull because i still dont know why it is giving the error when i change my my Com+ Activation type.If anyone could give a reply it would be really helpfull

Since I spent the last day or so tracking dealing with this issue, I thought I would post my solution (such as it is). After reading this thread and whatever else I could find. My problem was happening at System.Deployment.Application.NativeMethods.CorLaunchApplication. I was able to successfully publish from the same source on another workstation. This led me to believe that my problem was related to my workstation. I had recently installed Office 2007 and recently uninstalled the Windows SDK and Visual Studio SDK. After installing Office and re-deploying my app, my users started getting this error:

Unable to install or run the application. The application requires that assembly office Version 12.0.0.0 be installed in the Global Assembly Cache (GAC) first.

Between getting this error and getting the "Value does not fall within the expected range" error is when I uninstalled the SDK's. I did a repair of my VS install to no avail.

This is where it gets very interesting. It appears that these 2 errors are actually related. Even though they had different manifestations on 2 workstations (publishing from the other workstation never caused the "valud does not fall" error), the same solution eventually worked for both. I am using a custom library to do all of the Office interop for this app. The references to the interop libraries are all set with Specific Version = False in the reference properties. However, another library had references to the interop libraries which had Specific Version = True. (In fact, these were COM references and not references to the .Net interop wrappers). Once I removed the references, replaced them with references to the .Net wrappers, and set Specific Version = False, the issue was resolved.

this site talks about the error not sure if it will help you now. Do you still have the problem now or you have solve it. System.ArgumentException. Value does not fall within the expected range

http://connectionstringexamples.com/article.php?story=Sharepoint-error-System-Argument

We are getting the same error but only for a couple of machines out of 100+ that are all using ClickOnce for the same app. Most machines are OK and update (as they did before) without a problem. We can fix the problem on the two problematic machines by deleting the contents of C:\Documents and Settings\username\Local Settings\Apps and reinstalling.

We always change the file version, assembly version and publish/minimum version with each publish. The machines were all OK before andnow they are experiencing the problem without any material change to the projects in the solution.

This problem is intermittent and only affects a small percentage of machines but the situation that we have at the moment is that after each release we could get a random number of failures. We are considering dropping ClickOnce altogether as this problem appears to have been around for years with no resolution forthcoming from Microsoft.

Does anyone have a permanent fix / suggestion for what might be causing this?

Summary details:

Application cannot be started. Contact the application vendor.

Value does not fall within the expected range @ System.Deployment.Application.NativeMethods.CorLaunchApplication

Full information:

PLATFORM VERSION INFO

Windows : 5.1.2600.196608 (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/ahunter/Start%20Menu/Programs/Sarasin/SIC.NET%20-%20Live.appref-ms

Deployment Provider url: file://solomon/Distribution/PMS/Live/PMS.UI.Live.application

ERROR SUMMARY

Below is a summary of the errors, details of these errors are listed later in the log.

* Activation of C:\Documents and Settings\ahunter\Start Menu\Programs\Sarasin\SIC.NET - Live.appref-ms resulted in exception. Following failure messages were detected:

+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY

No transaction error was detected.

WARNINGS

There were no warnings during this operation.

OPERATION PROGRESS STATUS

* [15/04/2009 09:55:13] : Activation of C:\Documents and Settings\ahunter\Start Menu\Programs\Sarasin\SIC.NET - Live.appref-ms has started.

* [15/04/2009 09:55:13] : Performing necessary update check as specified by the deployment.

ERROR DETAILS

Following errors were detected during this operation.

* [15/04/2009 09:55:15] System.ArgumentException

- Value does not fall within the expected range.

- Source: System.Deployment

- Stack trace:at System.Deployment.Application.NativeMethods.CorLaunchApplication(UInt32 hostType, String applicationFullName, Int32 manifestPathsCount, String[] manifestPaths, Int32 activationDataCount, String[] activationData, PROCESS_INFORMATION processInformation)

at System.Deployment.Application.ComponentStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)

at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, Uri activationUri)

at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, Uri activationUri)

at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, TempFile& deployFile)

at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)

at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)

COMPONENT STORE TRANSACTION DETAILS

No transaction information is available.

I've beenexperimenting withClickOnce for onlyafew hours, just to seeifit's ready for prime-time. I took an existing WinForm app and began"adjusting"one thing at a time toget it to deployvia ClickOnce.

I got it to deployfor a while, then I starting getting the "Value does not fall within the expected range" exception (details below).

But backing-out each of my previous adjustmentsdidn't fix it... it will no longer deploy.

Is there no fix - or at least a workaround - for this problem? It's been reported for over 3 years.I don't want torecommendClickOnce forour customers appsifit's flaky.

Thanks,

DT


PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (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://npsisv03/ClickOnceForUSM/UltraSM.application
Application url: file://npsisv03/ClickOnceForUSM/UltraSM_1_10_0_15/UltraSM.exe.manifest

IDENTITIES
Deployment Identity: UltraSM.application, Version=1.10.0.15, Culture=neutral, PublicKeyToken=be93a9ce9f8aa28c, processorArchitecture=msil
Application Identity: UltraSM.exe, Version=1.10.0.15, Culture=neutral, PublicKeyToken=be93a9ce9f8aa28c, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Online only application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of file://npsisv03/ClickOnceForUSM/UltraSM.application resulted in exception. Following failure messages were detected:
+ Value does not fall within the expected range.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [9/8/2009 10:27:30 AM] : Activation of file://npsisv03/ClickOnceForUSM/UltraSM.application has started.
* [9/8/2009 10:27:30 AM] : Processing of deployment manifest has successfully completed.
* [9/8/2009 10:27:30 AM] : Installation of the application has started.
* [9/8/2009 10:27:30 AM] : Processing of application manifest has successfully completed.
* [9/8/2009 10:27:32 AM] : Request of trust and detection of platform is complete.

ERROR DETAILS
Following errors were detected during this operation.
* [9/8/2009 10:27:32 AM] System.ArgumentException
- Value does not fall within the expected range.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IStore.LockApplicationPath(UInt32 Flags, IDefinitionAppId ApId, IntPtr& Cookie)
at System.Deployment.Internal.Isolation.Store.LockApplicationPath(IDefinitionAppId app)
at System.Deployment.Application.ComponentStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.SubscriptionStore.LockApplicationPath(DefinitionAppId definitionAppId)
at System.Deployment.Application.FileDownloader.PatchFiles(SubscriptionState subState)
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
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)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

You mean that the development machine you are using to create the deployment is 64-bit?

What is the target CPU for the application?

RobinDotNet

---

Click here to visit my ClickOnce blog!