I am using VS 2019 and web app is asp.net. I have signed into my Azure/Microsoft account through VS. When I tried to publish the app, I got the screenshot below. Somehow the "Next" button is greyed out so I cannot move forward to create my publish profile. By the way, I am learning Azure and using the free App Service Plan now.
You need to create App Serviceļ¼
see: Publish your web app.
Here is what happened. To associate with Azure, a Microsoft account is linked to an Azure Directory. When I sign into Visual Studio with the Microsoft Account, the link is supposed to established automatically. But somehow it was not for my case. In Visual Studio, open "Personalization Account" page, click "Apply Filter" link, the next scene is where I can select which directory to be linked. I had only one directory but somehow it was not checked. Once I checked it, I am able to publish.
Our company ships an MVC based product (targeting v4.5) which has stopped working on a customer site for what appear to be environmental issues - a build which worked with no problems once upon a time now gives a 403.14 - The Web server is configured to not list the contents of this directory.
.
What I think is happening...
The user accesses http://server/AppName
Because it's an MVC app, the default route (Reports/Index) should be used.
Instead IIS is looking for a default document...
... and, not finding one, it assumes the user wants to list the contents of the directory...
...which is not enabled so it throws a 403.14.
.
What I've tried so far...
Accessing the route directly.. results in 404 error. So I'm pretty
sure IIS doesn't realise it should use routing.
Use aspnet_regiis to register ASP.Net with IIS. This was done from the Framework64 folder since...
OS is 64 bit - Windows Server 2008 (Standard without Hyper-V)
IIS is 64 bit - though Enable 32-Bit Applications is true
Checked AppPool is targeting v4 of the framework - it is.
Changed AppPool mode to Classic - was pretty sure it should be integrated but was worth ruling it out. It is now back to Integrated
Confirmed RunAllManagedModulesForAllRequests is set to true in the web.config.
Checked permission conditions defined in <system.webServer> section of web.config are met - they are.
Created the simplest of MVC applications and deployed it - same problem.
Running the command shell as Administrator unregistered ASP.Net using aspnet_regiis -ua and re-registered using aspnet_regiis -enable -i. We hit a couple of permission problems - and the Temporary ASP.NET Files directory was missing but once they were address we were back to the same error.
Added a simple default.htm - when present, this is served in response to the http://server/AppName request.
I'm clean out of ideas and all google hits suggest some combination of the above - or enabling directory browsing (which I think is just a symptom rather than the root cause).
Also, not sure if it's relevant but the amount of configurable elements available for the application in IIS seems a bit below what I would have expected...
Have you Checked the user the application pool process is running under? I think Your site needs to run with permissions to execute the .net libraries and I've seen this just change for seemingly no reason (probably related to an overzealous update to the system).
You can try with the Enabling directory browsing .
assuming you are under Windows Server 2012 or Windows Server 2012 R2
On the taskbar, click Server Manager.
In Server Manager, click the Manage menu, and then click Add Roles
and Features.
In the Add Roles and Features wizard, click Next. Select the
installation type and click Next. Select the destination server and
click Next.
On the Server Roles page, expand Web Server (IIS), expand Web
Server, expand Common HTTP Features, and then select Directory
Browsing. Click Next.
On the Select features page, click Next. On the Confirm installation
selections page, click Install. On the Results page, click Close.
if you using the Windows PC try this in your command prompt as follows:
go to C:\Program Files\IIS Express
then press Enter:appcmd set config
/section:system.webServer/directoryBrowse /enabled
Maybe this is your case https://forums.iis.net/t/1157304.aspx
SQL Server Reporting Services creates a folder called Reports by
default if you install it on IIS. If you install SQL 2008 then
Reporting Services doesn't need to use IIS and instead will try to
reserve the URL with the HTTP.Sys service.
I believe this is the cause of the conflict you are seeing. What you
could try is changing the URL that Reporting Services uses via the SQL
Server Configuration Wizard.
Also I found that
Report Manager of SQL Server can use reports path http://<server name>/reports
Configure a Native Mode Report Server for Local Administration (SSRS)
I think the problem is IIS features that are not installed yet. I have met this kind of problem frequently in Windows Pro. Make sure to turn on every feature under Internet Information Service -> World Wide Services because by default IIS is configured to use WebForms. So there might be some features that not installed yet to use MVC, especially ISAPI filters. In my case, that was the solution. I hope it helps.
Something similar i encountered using VS 2017 & ASP.NET MVC.
Was working on the project for long with no problems at all but suddenly the routing started misbehaving & stopped working.
So I changed the Port in Project Properties Page & it started working.
I really don't know what is the relation between a port & MVC routing modules. Someone else can enlighten if at all this helps.
I had the same problem and I just created an application pool out of the Default Web Site in IIS and stoped the default web site. With that difference you will not have the application pool's path
I know it's been a long time since this question but i've had the same problema recently. I've tried every single configuration, just like #amcdermott did, but the only action that solve the problem was reinstalling .NET Framework.
My app was built under .NET Framework 4.5.2. The application server had the version 4.6.1 and 4.5.2 installed. So, i uninstalled all framework versions and installed the one that i needed.
Please, make sure that no other applications use superior versions of .NET Framework if you going to try this solution.
Here are some quote I find on Microsoft official site which I think may help:
For site administrators
This problem occurs because the Web site does not have the Directory Browsing feature enabled, and the default document is not configured. To resolve this problem, use one of the following methods:
Method 1: Enable the Directory Browsing feature in IIS (Recommended)
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Directory Browsing.
In the Actions pane, click Enable.
Method 2: Add a default document
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Default Document.
In the Actions pane, click Enable.
In the File Name box, type the name of the default document, and then click OK.
Method 3: Enable the Directory Browsing feature in IIS Express
Note This method is for the web developers who experience the issue when they use IIS Express.
To do this, follow these steps:
Open a command prompt, and then go to the IIS Express folder on your computer. For example, go to the following folder in a command prompt:
C:\Program Files\IIS Express
Type the following command, and then press Enter:
appcmd set config /section:directoryBrowse /enabled:true
I am trying to connect my Microsoft Project Professional 2013 with Microsoft Project Server 2013 but following error keeps popping up.
Unfortunately I can't tell you why exactly you are getting that error, but I can give you some tips on troubleshooting:
Make sure you can connect and do have permissions to the PWA site. From that same machine, can you browse to it in the web browser and view/create projects?
Assuming #1 looks good, you can use a tool like Fiddler to inspect the web requests that Project client is making to the server. Look at the responses coming back from the web server - does it yield any clues (error codes perhaps) as to what is wrong?
Maybe you can edit your question to add whatever information you find?
Presuming your URL is correct (including http vs. https) the issue is most like related to permissions.
The solution will depend on your security configurations for the Project Server environment. If your Project Server 2013 environment is in Project Permission Mode, then the Global permissions for at least one your role(s) must have the following global permission selected:
Log on to Project Server from Project Professional
"Allows a user to load the Enterprise Global Template when he or she connects Project Professional to Project Server. Grant this permission to all users in your organization who will be using Project Professional to connect to Project Server."
If your Project Server Permissions are in SharePoint mode, the user must be a member of one of these groups:
Administrators
Portfolio Managers
Project Managers
Resource Managers
Permissions model references:
Project Server Mode: https://technet.microsoft.com/en-us/library/cc197631.aspx
SharePoint Mode: https://technet.microsoft.com/en-us/library/jj219510.aspx
I'm managing a third party vendor that uses Microsoft Web Deploy to push an ASP.NET website to our server. Is there somewhere I can find a history of where/when the files were published?
According to the MS Docs, Web Deploy automatically logs to the event log at Applications > Microsoft Web Deploy, but when I look there I don't see anything related to Web Deploy.
PS - I know that I can look at the timestamp on the app's folder in our filesystem, but that only gives me the time of the very last change, and not who made it...
Update - Under Event Viewer > Application and Service Logs > Microsoft > Microsoft Web Deploy, I can see history of web deployments that encountered an error, but I do not see a history of successful deployments.
I know this is old, but I found this while looking for the solution myself and stumbled upon the full log.
Instead of directly going to the Web Deploy folder in the event view, navigate to Event Viewer -> Applications and Services Logs -> Microsoft -> Windows -> WebDeploy. From there you can view ConnectionInfo to review successful deployments
I found this in %SystemDrive%\Inetpub\logs\WMSvc. Timestamp, AD username, and sitename published. All I needed!
I am getting the error:
This service instance was suspended by
a BizTalk administrator.
However I didn't force a suspense and it's on my local machine. I get this message all the time with every item i input. The thing is I changed a line in assembly which was a small translation, however this couldn't possibly be the cause. So I was wondering if anyone has encountered this problem before and what they did to fix this.
Thx
This can happen when you rebuild your Visual Studio project, depending upon the BTS project settings. A newly built DLL cannot be deployed while there are running instances. Check your project properties page (from the Project in Sln Explorer, right-click -> Properties).
Have you ever changed the logon as? this might be the cause of the error.
Check the account which the biztalk is running under:
1- open services console
2- right click the biztalk service instance
3- click properties and click the "logon as tab".
4- Make sure the user is an administrator or part of these groups:
- Administrators
- Biztalk Application Users
- Biztalk Isolated Host Users.