I am working on project, where I need to have an access to debugging option.
I've tried to run my application as usually, but this time I received following message:
Unable to connect to web server 'IIS Express'
When I checked the console output I found there following note:
Failed to register URL "http://localhost:49748/" for site xxx application "/". Error description: The process cannot access the file because it is being used by another process. (0x80070020)
Successfully registered URL "https://localhost:44333/" for site xxx application "/"
I found also that 0x80070020 error - "in the case of IIS Express (or IIS) means that the port that it is attempting to listen on is being used by another process" (link to the similar question).
I can't understand what's happen here. When I try to run this application I'm receiving this error in my Visual Studio, but the application is starting in the background (I can manually navigate to the https://localhost:44333 and app is there). The problem is that I can't debug the code, cause the Visual Studio looks like 'unrelated' to this instance. Previously IIS Express was opening new browser window with URL of the application, and I was able to debugging my code.
I also can't understand why this problem is not appearing for brand new project - I've created new web app project to test this behaviour, and it does what I expect - I can use debugging in VS.
What I've tried to do so far is:
Restart VS,
Restart my local machine,
Change app url in solution explorer/properties/debug,
Remove applicationhost.config from .vs directory
and nothing works for me.
Before this issue appear I forked this repo: https://github.com/jasontaylordev/CleanArchitecture
and downloaded WSL and Docker - I doubt that this have an impact on my solution, but maybe this information will be helpful.
Is there anything what I can change/edit to back to my previous behaviour?
Thanks
I had this issue after upgrading to Windows 10 20H2. There are many answers I found on SO that did not work for me, but I found this blog that helped me figure out the problem. Try running netsh interface ipv4 show excludedportrange protocol=tcp on the command liine and check to make sure that the port you are using is not one of the excluded ports listed. If so, change it to one that is not excluded. I did this and everything worked as normal again.
I am getting the below error message for a 1st time into my aspnetzero db. I have tried many of the solutions suggested in other areas but none seem to work for my local db
The db owner is sa and i have made the default password set to the infamous '123qwe'; i checked user mapping to make sure that sa owns the db.
i get the below error message when i try to login to the zero system; so the migration works OK also.
{"result":null,"targetUrl":"/Account/ResetPassword?UserId=1&ResetCode=56FB4BDF82&ReturnUrl=%2FApp",
"success":true,"error":null,"unAuthorizedRequest":false,"__abp":true}
well for this issue; the problem was that I wanted 2 pc's, a PC for the road and a desktop for travel, to have a single solution; using GitHub.
in setting up the 2nd pc, I did not follow the exact instructions for creating the project.
Thought I downloaded GitHub repository, something did not work ok in doing the yarn, etc.
To finally fix the problem I re-deleted the solution on the local PC, downloaded the GitHub repository, made sure I did the yarn, vs2k17 build (do not run it) c) npm run create-bundles or npm run full-create.
the below is what helped:
https://support.aspnetzero.com/QA/Questions/6176
I just ran into the same error message.
My issue was caused by Visual Studio running the package restore via npm.
Deleting the node_modules folder and running the restore via yarn in the command line resolved the problem and allowed me to run the copy:node_modules gulp task without errors.
I have one automation project which does the job of building the setup using NSIS wrapper. The project is built with the VB6 code. During the execution of the project I am getting the error for deleting a file as “Method 'DeleteFile' of object 'IFileSystem3' failed” for the method ‘FileSystemObject.DeleteFile’ with force option set to true.
Scenario:
Server (Windows server 2012) drive is mapped to the local windows 7 system and whole operation is run in this mapped drive in client machine. And the project is run on the client machine.
Now when I run my project to build the setup, it copies all the application files to a folder called Temp under build1 and build2 directory and then it builds 2 separate setup exe using the NSIS (makeNSIS). After the creation of NSIS setups, it will delete all the source files from temp folder. While deleting the MDAC_TYP.exe file, I get the error as mentioned above. The above said error comes for both the Build1 & Build2 folders and the error comes occasionally (not every time) for the same exe.
I cannot rename/delete/move the file in any of the PC through UNC or even in server it cannot be deleted. If I try to rename/delete the file or its parent folder, the system from where I try to delete/rename gets stuck.
Other methods I tried are as below.
Tried my project under testing environment and there was no such error.
Checked for file handle using process explorer in both client as well as server – No handles were found
Checked for Open files in the Shared folders of the server. - No open file connection found for the file.
Tried rebooting the client machine – Not solved.
Tried to delete/Rename the file using command in server – Not possible.
Tried to delete/rename the file in server – No error and no message. Instead, server gets stuck.
Checked for disk problems using chkdisk in server. No problems reported.
Folder permission – The user ha full permission and there is no issue.
Tried running the same build process after reboot – Everything works fine. But, again repeats after some time/day.
Tried disconnecting the mapped drive at the time of error exists. But, still not able to rename.
No antivirus/Event viewer log in both client as well as server
After all these still I could not able to explain why exactly the error occurring.
Update:
I recently noticed that the same error also occurs when deleting the file msstdfmt.dll
Update 2:
I also got error for the ms word file, error is same. In all the 3 cases i found that there is only a common thing that is all 3 files has read-only attribute.
While trying to deploy an app from Visual Studio, I'm getting an error. I have already set developer mode and also deleted the app package from the packages folder, but it still won't work.
Here's the error message:
Error : DEP0700 : Registration of the app failed. Deployment Register
operation with target volume C: on Package
App_1.0.0.2_x64__m0fsgersa29a0 from: (AppxManifest.xml) failed with
error 0x80070002. See http://go.microsoft.com/fwlink/?LinkId=235160
for help diagnosing app deployment issues. (0x80073cf9)
Do I need to set anything else?
I got this when attempting to debug a project from a shared folder.
Opening the project from a local folder first resolved the issue.
I know there is already an accepted answer, but I had a totally different problem with the same excact error message. When th app was running I took a look in the SQLite database with a program that I didn't close when I uninstalled the app and re-run it from Visual Studio. I think that Visual Studio couldn't overwrite the database as I was 'using' it.
Closed the program and voila the app run smoothly.
Hope this helpes anybody else as I was stuck for precious hours!
In Windows 10 there are two possible cause of this problem are as follows,
Previously installed app is locked and preventing VS to delete while deploying the application. Goto C:\Users\{you user}\AppData\Local\Packages and delete the folder of your application. Now rebuild and deploy your application.(this was the solution in Windows 8 devices as well)
If it is still not working, double check if you have removed the below entry from appxmanifest file. If you are targeting Desktop Name="Windows.Desktop" entry should be there in the file. If it is Phone, Name="Windows.Mobile" should be there in the TargetDeviceFamily. You can have both in the configuration but sometimes Microsoft will suggest to keep separate configuration when you submit the application for STARTS testing.
< Dependencies>
< TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.0.0" MaxVersionTested="10.0.0.0" />
< /Dependencies>
Hope this help in figuring out the reason and solution for "Error : DEP0700 : Registration of the app failed" error.
Don’t worry, the solution is actually very simple.
Error: DEP0700: Registration of the app failed. An internal error occurred.
So you’ve started your Windows 8 app development journey. All things are going smooth until one day you hit this error when trying to run/debug your app. The error says “Error: DEP0700: Registration of the app failed. An internal error occurred with error 0x80073D05. See http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x80073cf6)”
This is a very cryptic error and does not give you any info about what the problem actually is. The problem is that Visual Studio is not able to delete the application data in your local packages folder.
Don’t worry, the solution is actually very simple. On your Windows 8 machine, go to C:\Users\\AppData\Local\Packages\ folder. There you will find a folder that has your application’s Package Family Name in it – you just need to delete that folder. The issue is that while your app is in development, it might have a random GUID as its Package Family Name, so the folder will also have that random GUID as its name which makes it hard to know which folder belongs to your app. Again, that is easy to find as well. Right click your project in Visual Studio and click properties. The value you see in the “Package Family Name” field is the name you should look for in the folder. Simply delete it and build your solution again and it will run like a charm.
Read more details at http://paraswadehra.blogspot.com/2012/12/error-dep0700-registration-of-app.html
For me this was caused by being signed in with my Microsoft account in windows instead of the local user account. Logging in as a local user fixed this.
DEP0700: Registration of the app failed
For me the error DEP0700: Registration of the app failed, was raised because my Store App was installed from the actual Microsoft Store. I had to uninstall it and then I could debug my app smoothly.
I got this when I tried to run the project from a ReFS filesystem. Running from NTFS worked. My error code was 0x80073cfd.
I stumbled over the same issue today and after a few hours I found out, that the problem was because I moved the AppIcon files into a subfolder and forgot to adjust the references inside my package.appxmanifest. Unfortunatly the corresponding error message didn't point into this direction and all the above mentioned solutions didn't help for me, so hopefully this helps someone else!
In my case, I was opening one of the App files (Log Files). When deploying, Visual Studio attempts to remove all the files and packages (if uninstall is on in the properties). It was unable to remove the Log file as it was opened. When I closed all files, and tried again, it worked.
I ran into this error when testing some code in domain-bound and non-domain-bound scenarios (which requires me to have a domain account and a non-domain account on the same machine).
I found that I had to uninstall the application from the account I originally deployed it from before I could deploy it again on the other account.
My problem is that there is another Microsoft account in my computer that installed the app from Microsoft Store.
Nothing from the provided solution helped.
The only thing that solved my problem is to delete that account that I installed the app there.
SQLlite database might be opened. Just close the sqllite and try to deploy again.
I have a webservice that I need to be able to write some logs for. The service is installed in c:\inetpub\wwwroot\myservice. The log files should be written to c:\inetpub\wwwroot\myservice\logging.
When I try running it in debug mode in Visual Studio, log files are created successfully. When I publish the site and try it, log files are not created.
I have tried giving write access for the logging folder to: NETWORK Service, IUSR, IIS_IUSRS, DefaultAppPool, ASP .NET 4.0 Classic but it made no difference. I also added Everyone with Full Control, but it made no difference.
Any ideas why I cannot get write access to this folder????
I have no idea what caused the issue, but IIS had somehow got corrupted. It would no longer display pages either by using localhost or 127.0.0.1.
Removed and re-installed IIS, all working now.