The application is improperly formatted - ClickOnce

  • Thread starter Thread starter baerland
  • Start date Start date
B

baerland

Hi

I'm suddenly having some problems with clickOnce deplyment of a windows
form.
Up till now I have succesfully published and downloaded updates without
problems. But today, after adding some new buttons and icons, I get
this error when trying to update my clients. The publishing seems to
work, without any 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 : http://www.test.no/my.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed
later in the log.
* Activation of http://www.test.no/my.application resulted in
exception. Following failure messages were detected:
+ Exception reading manifest from http://www.test.no/my.application:
the manifest may not be valid or the file could not be opened.
+ There are multiple root elements. Line 25, position 3692.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [11.12.2005 21:05:29] : Activation of
http://www.test.no/my.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [11.12.2005 21:05:29]
System.Deployment.Application.InvalidDeploymentException
(ManifestParse)
- Exception reading manifest from http://www.test.no/my.application:
the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String
localPath, ManifestType manifestType, Uri sourceUri)
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)
at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)
--- Inner Exception ---
System.Xml.XmlException
- There are multiple root elements. Line 25, position 3692.
- Source: System.Xml
- Stack trace:
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
at System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlTextReader.Read()
at
System.Deployment.Application.ManifestValidatingReader.XmlFilteredReader.Read()
at System.Xml.XmlCharCheckingReader.Read()
at System.Xml.XsdValidatingReader.Read()
at System.Deployment.Application.ManifestReader.FromDocument(String
localPath, ManifestType manifestType, Uri sourceUri)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
 
I failed to mention that I publish through Visual Studio 2005, and that
there is no manual editing of the manifest files.

I suspect there is a permission setting on the deployment server I'm
missing. Because if I start the .application file on the server from
explorer (not the internet browser), it starts.

Any help would be greatly appreciated. Thanks.
 
I failed to mention that I publish through Visual Studio 2005, and that
there is no manual editing of the manifest files.

I suspect there is a permission setting on the deployment server I'm
missing. Because if I start the .application file on the server from
explorer (not the internet browser), it starts.

Any help would be greatly appreciated. Thanks.
Click to expand...

Well, if you could post the manifest file, it would probably help quite
a lot...
 
I never found out the exact problem, but I suspect it had something to
do with some header settings in iis which was modified during an
installation of awstat. One day I rebooted the server, and now it works
perfectly again.
 
Back
Top