Please Help

I am trying to deploy an application to our web server and I get the error Cannot Continue. The application is improperly formatted. Contact the application vendor for assistance (I am the vendor). This is the details:

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://slsappstage/installs/pbi/PreboardingInterface.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://slsappstage/installs/pbi/PreboardingInterface.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from http://slsappstage/installs/pbi/PreboardingInterface.application: the manifest may not be valid or the file could not be opened.
+ Data at the root level is invalid. Line 20, position 3740.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [4/20/2006 11:56:44 AM] : Activation of http://slsappstage/installs/pbi/PreboardingInterface.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [4/20/2006 11:56:44 AM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from http://slsappstage/installs/pbi/PreboardingInterface.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
- Data at the root level is invalid. Line 20, position 3740.
- 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.ParseRootLevelWhitespace()
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.

Can someone please help me out



Answer this question

Please Help

  • Heathcliff

    I should...our dev/stage environment are on the same web-server. We just have different instances.
  • Chris Durkin

    Could you try rebuilding your manifests and see if that fixes the problem
  • rkuerbitz

    Do you have any idea why it only works in dev under your login I have a feeling that if you can figure out the reason for that, you will know how to make it work in staging. What kind of IIS security settings are you running What settings do you have in your web.config for security

    If all permissions and IIS settings are the same, and you are publishing to the staging environment directly with no changes (which is on the same server); then I don't see much of an opening for a problem. Is there anything hardcoded in your application by any chance that could be responsible for this problem

    I feel like I'm grasping at straws at this point, but there must be a reasonable explanation for your problem.


  • sasman

    Did you change any of the files or the location of the files after they were published Or did your install fail without you making any changes after publishing
  • The Werewolf

    If you mean republishing the application, I've done that many times. Otherwise, how would you go about rebuilding the manifest
  • FugersonHall

    I would double check the IIS settings you currently have for the two virtual directories and see what differences you might be able to find between the two, if any. That may lead you in the right direction.

    Otherwise:

    "Data at the root level is invalid. Line 20, position 3740"

    What appears in your manifest in Line 20, position 3740


  • Chester Flake

    I did confirm the IIS settings, they are exactly the same (only different is the global footer web address).

    3740 is the absolute end of the manifest. Line 20 has 3739 characters, so 3740 is right past that. That's what is confusing to me.


  • Joel C

    It just failed without making changes after publishing. We have two environments, a dev/stage area, I can get it to publish and run from dev, but it only works from my login; Stage just doesn't work period.
  • REDLINE

    Did you publish a second time directly into the staging environment, or did you simply copy the files from the development environment If you simply copied the files, then I can explain why they won't work.
  • Tegs

    I have tried to publish to our staging environment multiple times. I have not tried to copy from Dev to Stage, though I could and just resign the manifest to see if that works. But Dev doesn't quite work either since only my Windows Login Name can access it.
  • Sovman

    Is it possible that you are simply encountering a permissions problem Your error did mention something about possibly not being able to open the manifest. The fact that it works fine in dev under your login, but doesn't work for other logins or in staging would seem to suggest that. Do you have permissions in your staging environment under your login
  • Please Help