I'm getting the following exception when I try to install a ClickOnce application:
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\user\Downloads\appname.application resulted in exception. Following failure messages were detected:
+ Downloading file://192.168.2.9/appdir/appname.application did not succeed.
+ The network name cannot be found.
+ The network name cannot be found.
+ The network name cannot be found.
I haven't been able to figure it out. I've tried looking around on the net and there don't seem to be any resources on the issue. Does anybody know how to resolve this?
This turned out to be a problem with the installation URL in the publish settings. Rather than using a web path, I was using a share for the path. The actual location was set up in IIS, so of course the file could not be found at the share.
Changing the field "Installation Folder URL" from:
\\\server-name\path
to
http://server-name/path
resolved the problem. Silly mistake.
I fixed the issue in this way. Check the Permission in both IIS AND Folder
Give the IIS Full control Permision to Everyone
Share the physical path folder to Everyone
Mostly these kind of error messages are due to wrong connection string that cannot be found over network. Rechecking the Datasource value or server value and and database name in connection string will solve the problem
Related
Sorry for my lack of knowledge about application deployment, but I have an issue after deploying my application on a network drive - I get the following error; here is a summary of the errors, details of these errors are listed later in the log:
Activation of Y:\DataBase\MSR-SEK\LessonsLearnt\Application Files\LessonsLearntAlert_1_0_0_2\LessonsLearntAlert.application resulted in exception. Following failure messages were detected:
+ Downloading file:///Y:/DataBase/MSR-SEK/LessonsLearnt/Application Files/LessonsLearntAlert_1_0_0_2/Application Files/LessonsLearntAlert_1_0_0_2/LessonsLearntAlert.exe.manifest did not succeed.
+ Could not find a part of the path 'Y:\DataBase\MSR-SEK\LessonsLearnt\Application Files\LessonsLearntAlert_1_0_0_2\Application Files\LessonsLearntAlert_1_0_0_2\LessonsLearntAlert.exe.manifest'.
+ Could not find a part of the path 'Y:\DataBase\MSR-SEK\LessonsLearnt\Application Files\LessonsLearntAlert_1_0_0_2\Application Files\LessonsLearntAlert_1_0_0_2\LessonsLearntAlert.exe.manifest'.
+ Could not find a part of the path 'Y:\DataBase\MSR-SEK\LessonsLearnt\Application Files\LessonsLearntAlert_1_0_0_2\Application Files\LessonsLearntAlert_1_0_0_2\LessonsLearntAlert.exe.manifest'.
Please note that the application is deployed for online run from network drive. There is no issue on my local machine issue to run the application from network drive, but the other PCs on the network have the above issue.
I have no idea why I get this error:
Could not find a part of the path 'Y:\DataBase\MSR-SEK\LessonsLearnt\Application Files\LessonsLearntAlert_1_0_0_2\Application Files\LessonsLearntAlert_1_0_0_2\LessonsLearntAlert.exe.manifest'
Appreciate if anyone could help and look into the issue. Thanks
Adding a private Font works fine on my local dev machine with Windows 10 Pro. However on Windows Server 2012 R2 the very same code results in the following error:
System.Runtime.InteropServices.ExternalException: A generic error
occurred in GDI+. at
System.Drawing.Text.PrivateFontCollection.AddFontFile(String filename)
var privateFontCollection = new PrivateFontCollection();
privateFontCollection.AddFontFile("Roboto-Regular.ttf");
When I delete the file it results in a NotFoundException, so the file path has to be right. I ensured that every user has every possible permission on the file. (I found out that if I deny every permission on my local win 10 machine the same "generic error" occurs - so it might be a permission problem)
Has anybody a solution for this problem?
Could it be possible that the service user on the productive machine lacks some other rights that are necessary for "installing" private fonts? Maybe the font gets installed to a specific directory which is not allowed - but I could not find out where this would be.
Please help me with this very self explaining "generic error".
It seems to have been a problem with not using an absolute path. Didn't think of it at first, because deleting the file resulted in an explicit FileNotFound.
Using an absolute path did the trick.
This question is related to my previous question.
I need to publish a C# application (that has been set up in IIS 6.0 and built in VS2010) to a desktop with win7.
I have set up IIS on my desktop well. Now I can install the application on my laptop by accessing the URL
http://myDesktopName.domain.com/MyApp
pointing to a physical location in desktop
e:\myPath\myApp\myAppService.svc
When I publish a new version of the web service, the application should get updated when I open it.
But, it gave me an error:
**the filename,directory name, or volume label syntax is incorrect**
After searching online, I found this error is normally caused by some unacccepted chars in the link. Here is the code that the msi (MS installer) needs to access and get the new version of the application.
System.Diagnostics.Process.Start("msiexec", "/favmuso \"" + myurl + "\"");
here,
myurl is http://myDesktopName.domain.com/MyApp/MyAppSetup.msi
Here, http://myDesktopName/MyApp/ is the virtual directory set in IIS 6.0 on my desktop. I can access and download it from IE in my laptop without any problems.
But, when the application notified me that a new version is available for updating the old one, I clicked the pop-up ballon on the application icon and then I got the error:
Error 123. The filename, directory name, or volume label syntax is incorrect.
If I try to access it from the C# code, I got the same error.
Then, I did a test by running
msiexec **/favmuso** http://myDesktopName.domain.com/MyApp/MyAppSetup.msi /Lv mapp_msi.log
In the log file, i found :
MSI (s) (80:DC) [18:04:33:089]: SECREPAIR: Failed to open the
file:http://myDesktopName.domain.com/mypath/\myAppSdetup (10).msi for computing its hash. Error:123
Error 123. The filename, directory name, or volume label syntax is incorrect.
Why my applcation setup file name was changed to
\myAppSdetup (10).msi
The "/favmuso" options can be found at
https://technet.microsoft.com/en-gb/library/cc759262%28v=ws.10%29.aspx#BKMK_Install
Any help would be appreciated.
thanks
So I noticed that you've asked this question elsewhere, and everyone was focused on the /favmuso piece of it.
I've been recently exeriencing this issue when trying to repair MSIs with a URL source when the original application was installed by SCCM 2012.
The workaround I found was to add a registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer. The value below causes the MSI to skip the problematic portion of the repair and move on.
Name: SecureRepairPolicy
Type: REG_DWORD
Value: 1
To be a bit safer, you look into setting the registry value to 2 and using a whitelist as described in this Microsoft article: https://support.microsoft.com/en-us/kb/2918614. (Ctrl+F "Steps to opt-out the affected programs".)
I get the following error when trying to start the ASP.NET State Service:
Windows could not start the ASP.NET State Service service on Local Computer.
Error 2: The system cannot find the file specified.
Everything I found on google told me to go to the %windir%\Microsoft.NET\Framework\v1.1.4322 folder at the command prompt, and then type the following command: aspnet_regiis.exe -ir
which I did and didn't solve the problem. The path to the executable in my case is 2.0: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_state.exe.
So I tried the same comand on the v2 folder and I get the error:
"An attempt was made to load a program with an incorrect format".
thanks in advace for any help
As stated here, it's trying to load the 32-bit version while you need the 64-bit. If this is applicable, open RegEdit (own risk and so on) and change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\ImagePath
from %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_state.exe to %SystemRoot%\Microsoft.NET\Framework64\v2.0.50727\aspnet_state.exe.
You not need reinstall this service.
Just find in services "ASP.NET State Server" and start it.
Also you can set up to start this service automaticaly in preferences.
After deployment an ASP.Net application on a webserver, I get this error message by using code from a external assembly: "LinkDemand The type of the first permission that failed was: System.Security.PermissionSet The Zone of the assembly that failed was: MyComputer the error ".
The assembly is include in the \bin folder and not in the GAC.
I try to know what linkdemand exactly is and why this message will raised. But looking for more information, I don't get exactly the problem.
I try also to add the PermissionSetAttribute on the class where the exception message happens:
[System.Security.Permissions.PermissionSetAttribute(System.Security.Permissions.SecurityAction.LinkDemand, Name = "FullTrust")]
Then the exception will be raised on another class of the assembly. And so on..
My questions ares:
what exactly is going wrong here? Is it true that what I understand this error message displayed when the Jit cannot check the code security?
Is there maybe a security policy that block this (machine.config) or directly change the security?
Can I set the PermissionAttribute for all classes between a assembly?
Go to administrative tools and local security policy. Whilst, I do not know the exact reason you are getting the error, basically you are trying to execute code that is not allowed in the current security policy. Check your paths and your security policy and the permission requirements of the module. Some paths like desktop will run in reduced security by default.