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
Related
I just ran into problem described in header. Trying to connect to w3wp process on remote server.
Rider cannot find the path described in error to upload it's files on server. You need just create this folder
I have created a Windows Service using ASP.Net Core 3.x and C#. I started with the new Windows Service template when I built the project. When I run it from my development environment or from a console window it runs fine. When I install it as a Windows Service and attempt to start the service I get an
"Error 5: Access is denied." error.
I tried numerous things which I will outline below to eliminate the error but nothing seemed to work so I downloaded the sample app provided by Microsoft, at sample
Same result...when I run the sample app from within Visual Studio it runs fine, when running as a service I get the Access Denied error.
I am running all of this on my local machine, which I am an admin on.
I originally tried to run it using the default Local System account; got the Access Denied error.
I changed the Log On As to my domain account, the same one I use to log into my local machine which is an admin on this machine; got the same Access Denied error.
My account has the privilege set to run as a service.
The Event Viewer just shows the one message which says "Access Denied", no other messages are created.
I believe the Access Denied error is occurring before the C# code is even executed. What makes me believe this is that I added one line to the very top of the Program.Main.... File.WriteAllText("C:\\temp\\ws.log", $"Test of Worker Service # {DateTime.Now}. Content Root Path: {AppContext.BaseDirectory}");. My account has full access to the temp folder. This file gets created when I run the app from Visual Studio but it does not get created when I run the app as a service.
I have read numerous web sites, include this one and this one. No luck, everything I tried from these sites still produce the Access Denied error.
I have run out of ideas and am hoping someone here can provide me the answer. Thanks!
I found the solution and believe me I feel really stupid!!!
When I installed it as a service I only put the path in "binPath".
sc create WindowsService1 binPath="C:\temp".
Once I actually added the executable to the binPath parameter everything worked.
Changed it to sc create WindowsService1 binPath="C:\temp\WindowsService.exe" and it worked.
I know it is an Id10t error but Microsoft should really provide better messaging for the "sc" command. A message like "Cannot find file specified in the binPath parameter" would have been really helpful. Would have saved me about 6 hours of work.
Thanks everyone for reviewing and replying to this question.
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 an application built by C# on VS 2010 (.NET 4.0) to a Windows server 2008 R2.
I just followed the instructions ("publish to a file share or path") here:
https://msdn.microsoft.com/en-us/library/31kztyey.aspx
Now, the UNC path specified in the publish profile can be accessed. It is a location of a remote server.
But, in the browser, I can open the link:
\\serverName\e$\myPath\publish.htm
There is an install button on the webpage, it points to
file://serverName/e$/myPath/setup.exe
When I clicked it, it downloaded setup.exe to
C:\Users\myname\Downloads
When I ran it, I got:
* Activation of C:\Users\myName\Downloads\myApp.Host.application resulted in exception. Following failure messages were detected:
+ Downloading file:///C:/Users/myName/Downloads/myApp.Host.application did not succeed.
+ Could not find file 'C:\Users\myName\Downloads\myApp.Host.application'.
System.Net.WebException
- Could not find file 'C:\Users\myName\Downloads\CWIL.Host.application'.
But, the
myApp.Host.application
has been created at:
\\serverName\e$\myPath\Application Files\myApp.Host_2_1_6_7
Did I miss something here ?
Any help would be appreciated.
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