I have created a program and publish it. It's working fine on my pc. But when I try to run it in a particular PC it gives this error. I use VB.net and access. Use system dsn to connect to the database. I have installed visual studio on that machine and if i open the project and run, it working fine. Which means the machine got all the prerequisites required to run the program. Any Idea what will be the problem.I am adding the contents of the error log file for your reference.
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.34209
System.Deployment.dll : 4.0.30319.34209 built by: FX452RTMGDR
clr.dll : 4.0.30319.34209 built by: FX452RTMGDR
dfdll.dll : 4.0.30319.34209 built by: FX452RTMGDR
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url : file:///F:/Inventory%20Master/Application%20Files/WindowsApplication2_1_0_0_5/WindowsApplication2.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of F:\Inventory Master\Application Files\WindowsApplication2_1_0_0_5\WindowsApplication2.application resulted in exception. Following failure messages were detected:
+ Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [27/03/2017 8:10:44 PM] : Activation of F:\Inventory Master\Application Files\WindowsApplication2_1_0_0_5\WindowsApplication2.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [27/03/2017 8:10:44 PM] System.UnauthorizedAccessException
- Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IsolationInterop.GetUserStore(UInt32 Flags, IntPtr hToken, Guid& riid)
at System.Deployment.Internal.Isolation.IsolationInterop.GetUserStore()
at System.Deployment.Application.ComponentStore..ctor(ComponentStoreType storeType, SubscriptionStore subStore)
at System.Deployment.Application.SubscriptionStore..ctor(String deployPath, String tempPath, ComponentStoreType storeType)
at System.Deployment.Application.SubscriptionStore.get_CurrentUser()
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.
I have solved the problem. There is some problem or restrictions in that particular account although it's an administrator privilege. I have create a new user account with administrative rights and program runs without error.
Related
I have created a vb.net application using Visual Studio 2013, I have published it and installed it on my work pc (windows 7) and my laptop (also windows 7) and they both work fine. I tried installing it on the pc this application is to go on which is windows xp, I got an error with the following details:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 4.0.30319.1022
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.1022 (RTMGDR.030319-1000)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : file:///D:/Visitors.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of D:\Visitors.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from file:///D:/Visitors.application: the manifest may not be valid or the file could not be opened.
+ Manifest XML signature is not valid.
+ SignatureDescription could not be created for the signature algorithm supplied.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [14/08/2014 13:43:54] : Activation of D:\Visitors.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [14/08/2014 13:44:00] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from file:///D:/Visitors.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, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- SignatureDescription could not be created for the signature algorithm supplied.
- Source: System.Security
- Stack trace:
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignature(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
This is the first time I have published an application so I don't know why this is happening, I can only assume that it has something to do with windows xp. I would appreciate any help with this problem.
Update:
The .NET framework is targeted at 4.0, and the target cpu was 'Any CPU' and I changed it to x86. The xp pc in question has .NET4.0, XP SP3 and is 32-bit but this still hasn't solved my problem. Also, I am using sql server 2008r2 express in this application if that makes any difference.
The old error is not coming up and the new one says:
'SqlExpress2008R2 is not a valid Win32 application.'
Update 2:
As well as having to do what I said in my first update, I also had to change the signing from 'Sign the ClickOnce manifests' to 'Sign the assembly' and my application is now working on windows xp.
You can can't run or build vb.net 2012/2013 or later in Windows XP.
Solution - Use vb.net 2010 in Windows XP, run and build your code there.
If any question pleasure to answer.
The .NET framework is targeted at 4.0, and the target cpu was 'Any CPU' and I changed it to x86. The xp pc in question has .NET4.0, XP SP3 and is 32-bit.
I also had to change the signing from 'Sign the ClickOnce manifests' to 'Sign the assembly' and my application is now working on windows xp.
I`m working on a project which requires the using of older (2005) library.
When I try to add the library to references, an error pops up telling me that(see picture attached)
The following is exception details:
System.DllNotFoundException occurred
HResult=-2146233052
Message=Unable to load DLL 'edk.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Source=DotNetEmotivSDK
TypeName=""
StackTrace:
at Emotiv.EdkDll.Unmanged_EE_EmoEngineEventCreate()
at Emotiv.EdkDll.EE_EmoEngineEventCreate()
at Emotiv.EmoEngine..ctor()
at Emotiv.EmoEngine.get_Instance()
at MindComposer.EmotivSDK.HeadsetConnection.Main(String[] args) in c:\Users\Vlado Bogdanov\Documents\Visual Studio 2013\Projects\MindComposer\MindComposer\NeuroProcessing\HeadsetConnection.cs:line 37
InnerException:
I'm using Visual Studio 2010 and VB.NET. My target environment is .NET Framework 4.0.
So I'm facing this problem when I'm publishing my project by using the provided Setup.exe file. After the verifying application requirement popped up, an alert popped up with text:
Cannot Continue. The application is improperly formatted. Contact the application vendor for assistance.
When I clicked on the "Detail" button, it showed me this error:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.239
System.Deployment.dll : 4.0.30319.1 (RTMRel.030319-0100)
clr.dll : 4.0.30319.239 (RTMGDR.030319-2300)
dfdll.dll : 4.0.30319.1 (RTMRel.030319-0100)
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment URL : file:///I:/ProjectBMTRelease/ProjectBMT.application
IDENTITIES
Deployment Identity : ProjectBMT.application, Version=1.0.0.6, Culture=neutral, PublicKeyToken=7439f62500c0364d, processorArchitecture=x86
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 I:\ProjectBMTRelease\ProjectBMT.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from file:///I:/ProjectBMTRelease/Application%20Files/ProjectBMT_1_0_0_6/ProjectBMT.exe.manifest: the manifest may not be valid or the file could not be opened.
+ Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x80070c81
Start line: 0
Start column: 0
Host file:
+ Exception from HRESULT: 0x80070C81
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [6/23/2012 5:21:36 PM] : Activation of I:\ProjectBMTRelease\ProjectBMT.application has started.
* [6/23/2012 5:21:36 PM] : Processing of deployment manifest has successfully completed.
* [6/23/2012 5:21:36 PM] : Installation of the application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [6/23/2012 5:21:36 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from file:///I:/ProjectBMTRelease/Application%20Files/ProjectBMT_1_0_0_6/ProjectBMT.exe.manifest: 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.DownloadApplicationManifest(AssemblyManifest deploymentManifest, String targetDir, Uri deploymentUri, IDownloadNotification notification, DownloadOptions options, Uri& appSourceUri, String& appManifestPath)
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)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x80070c81
Start line: 0
Start column: 0
Host file:
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
at System.Deployment.Application.Manifest.AssemblyManifest..ctor(FileStream fileStream)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Runtime.InteropServices.COMException
- Exception from HRESULT: 0x80070C81
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IsolationInterop.CreateCMSFromXml(Byte[] buffer, UInt32 bufferSize, IManifestParseErrorCallback Callback, Guid& riid)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
I checked my project's manifest file, but I am not good enough to find any problem there. For other information, I created simple "Hello World !" application to see if it will get published well, and it did.
What is the solution?
Check the following:
Does the user have .NET 4 installed on their computer?
How are you publishing the application, are you using Visual Studio?
Are you making any changes to the deployment after publishing it?
If you are manually moving the files to the deployment location, is the structure identical to the original structure?
Try enabling detailed logging and see if that provides more information. The
article Enhanced Logging in ClickOnce Deployment shows you how to do that.
I got this very same error. The problem got resolved after I renamed my assembly name found on the first tab under application properties. It seems like having an assembly name with a space creates a manifest filename with a blank space and it seems to create problems. My application assembly name was named "Capital Manager". After I changed it to "Capital_Manager" (I replaced the space with an under score "_") the issue got resolved.
I received an error report and call stack pretty much identical to yours when attempting to run the ClickOnce installer. My findings so far may be helpful to others arriving here, so I'll post the details, but I have a feeling this same error report may be caused by a range of different problems.
The first thing I noticed was that my application manifest (the one that lists all of the files for the application + a signature hash for each) had entries for assemblies that had an invalid publicKeyToken, for example,
<asmv1:assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv3="urn:schemas-microsoft-com:asm.v3" 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" xmlns:co.v1="urn:schemas-microsoft-com:clickonce.v1">
<asmv1:assemblyIdentity name="foo.exe" version="1.2.3.4" publicKeyToken="0000000000000000" language="neutral" processorArchitecture="msil" type="win32" />
Further down the file instead of seeing dependentAssembly elements for assemblies some of the assemblies were listed as plain content files (file elements).
These problems certainly make the ClickOnce deployment invalid, and the cause was using a version of Mage that was compiled against an older version of .NET than the assemblies it was trying to create manifests for. When creating the application manifest Mage will attempt to read assemblies as follows:
AssemblyIdentity.FromFile(fileName);
And for Mage compiled against .NET 3.5 (CLR 2.0) trying to load a .NET 4.0 assembly results in a BadImageFormatException exception which is handled, and the fall-back behaviour is to treat these files as content files.
Does your application folder have subfolders? I got this same HRESULT just yesterday, and the root cause was that a library (EntityFramework.dll) was in both the top level and in a subfolder. (There was a MAGE warning about this, but it was not handled as an error.) I updated my script to remove EntityFramework.dll from the subfolder, and the ClickOnce is fine now.
Just another possibility - I got a similar error when adding a dpiAware to a newly created app.manifest file. ClickOnce started failing immediately.
I followed the advise here: Installing ClickOnce published DPI-aware application
So if you've been doing dpi things, maybe look there.
So I installed RavendDB on a Win2003 server using these instructions:
http://old.ravendb.net/documentation/docs-deployment-iis
And i get the following error when I try to browse to the site. Any ideas?
Version of log file is not compatible with Jet version
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Isam.Esent.Interop.EsentBadLogVersionException: Version of log file is not compatible with Jet version
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[EsentBadLogVersionException: Version of log file is not compatible with Jet version]
Microsoft.Isam.Esent.Interop.Api.Check(Int32 err) in C:\Work\ravendb\SharedLibs\Sources\managedesent-61618\EsentInterop\Api.cs:2739
Microsoft.Isam.Esent.Interop.Api.JetInit(JET_INSTANCE& instance) in C:\Work\ravendb\SharedLibs\Sources\managedesent-61618\EsentInterop\Api.cs:131
Raven.Storage.Esent.TransactionalStorage.Initialize(IUuidGenerator uuidGenerator) in c:\Builds\raven\Raven.Storage.Esent\TransactionalStorage.cs:207
[InvalidOperationException: Could not open transactional storage: C:\Inetpub\wwwroot\RavenDB\Data\Data]
Raven.Storage.Esent.TransactionalStorage.Initialize(IUuidGenerator uuidGenerator) in c:\Builds\raven\Raven.Storage.Esent\TransactionalStorage.cs:220
Raven.Database.DocumentDatabase..ctor(InMemoryRavenConfiguration configuration) in c:\Builds\raven\Raven.Database\DocumentDatabase.cs:151
Raven.Web.ForwardToRavenRespondersFactory.Init() in c:\Builds\raven\Raven.Web\ForwardToRavenRespondersFactory.cs:62
Raven.Web.RavenDbStartupAndShutdownModule.<Init>b__0(Object sender, EventArgs args) in c:\Builds\raven\Raven.Web\BootStrapper.cs:12
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +213
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +76
The RavenDB datastore uses Esent under the hood. As a result it's not portable across OS versions. I.e. if you create a store on one version of an OS, it won't necessarily work on another just by copying the files across.
You can use the RavenDB smuggler tool to import/export the data. Or do it manually.
We're running SQL 2005 on Win2K3 server and are using SSRS. Here's the situation:
I can run Report Builder from localhost
My coworker can run Report Builder on his Vista computer
Another coworker can run Report Builder on his XP SP3 computer (IE7)
I can NOT run Report Builder on my XP SP3 computer (IE7)
I'm told that it could be anything from an errant registry entry to a group policy problem. Here is what I've tried:
Put the site into "Trusted Sites" with "low" security
re-install .NET
create a new local user account and attempt to run it
The results? Every single time, I get a dialog box: "Application cannot be started. Contact the application vendor"
I click the details button and get this:
PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 2.0.50727.3607
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3607 (GDR.050727-3600)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)
SOURCES
Deployment url : http://www.example.com/ReportServer/ReportBuilder/ReportBuilder.application
Server : Microsoft-IIS/6.0
X-Powered-By : ASP.NET
X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity : ReportBuilder.application, Version=9.0.3042.0, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=msil
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://www.example.com/ReportServer/ReportBuilder/ReportBuilder.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
* [4/7/2010 2:53:57 PM] : Activation of http://www.example.com/ReportServer/ReportBuilder/ReportBuilder.application has started.
* [4/7/2010 2:53:58 PM] : Processing of deployment manifest has successfully completed.
ERROR DETAILS
Following errors were detected during this operation.
* [4/7/2010 2:53:58 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, String activationParameter, Boolean useActivationParameter)
at System.Deployment.Application.SubscriptionStore.ActivateApplication(DefinitionAppId appId, String activationParameter, Boolean useActivationParameter)
at System.Deployment.Application.ApplicationActivator.Activate(DefinitionAppId appId, AssemblyManifest appManifest, String activationParameter, Boolean useActivationParameter)
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
* Transaction at [4/7/2010 2:53:58 PM]
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreTransactionOperationType (27)
- HRESULT: 0x0
I'm really at a loss. I'm certain there is something on my PC preventing the application from running - but I just don't know what. Google hasn't been much of a help because most problems are related to the server configuration (which I know is correct since it works on other PCs)
Help me, Overflow Kenobi, you're my only hope..
Since you asked so long ago, most probably you don't need this anymore.
Hopefully, since you found the answer and not because you simply quit.
I ran against this problem, also. After some time, found the reason: when a ClickOnce application is executed for the first time on a machine, the URL it was installed from becomes part of this apps' signature.
Unfortunately, this also means when you try to run same application, with exactly same manifest, from another URL you get this or very similar errors.
So if you have a local instance of SQL Server with Reporting Services, and run Report Builder 3.0 for the first time from Report Manager's "Start Report Builder" then next time you try to run it from a real server's Report Manager's link (not from your localhost's) you'll get this error.
The workaround is to manually purge the ClickOnce cache (source):
For Windows Vista:
Find folder <user>\AppData\Local\Apps
Delete the 2.0 folder
Pre-Vista:
Find folder ...\Documents and Settings\<user>\Local Settings\Apps
Delete the 2.0 folder