Visual studio ошибка 403

• any details for the 403 error?

  May 3, 2016 at 18:34

• No i get this «An error occurred while creating the WebJob schedule: Response status code does not indicate success: 403 (Forbidden).» error in the Error window of visual studio. I have pay as you go subscription, would there be anything related to that?

  May 4, 2016 at 5:22

• Just tried your process but didn’t encounter this issue, the web app was published successfully after adding console application as web job and configured recurring(daily). I find one similar issue here, it suggests change jobRecurrenceFrequency in webjob-publish-settings.json in the console application, I’ve checked after configuring the schedule from my side, the jobRecurrenceFrequency’s value is Day, in case missing anything, I’d suggest you check it from your side.

  May 4, 2016 at 7:17

• I tried deploying from another computer but results into same error. Just want to mention that Azure Web App project is part of SharePoint provider hosted app to be deployed for Office 365, but i dont think that should be a problem. Below is the details of output window log when error occurs: 2>Publish Succeeded. 2><project location>\packages\Microsoft.Web.WebJobs.Publish.1.0.9\tools\webjobs.console.targets(110,5): Error : An error occurred while creating the WebJob schedule: Response status code does not indicate success: 403 (Forbidden).

  May 4, 2016 at 13:28
  

• I got the issue resolved, once i got co-administrator privileges on the subscription.

  May 5, 2016 at 13:33

1 Answer

Please run your app using «start without debugging» to get much more information in your side.

I met this kind of error message before which was related to the visit/write access.

Running an ASP.net project with an Application Pool with a specific Identity yields «(403) Forbidden»

I know this is an old post, however, I have had the same problem within vs2019 after switching to IIS debugging. In my case, I was confident that IIS was set up correctly, as another application was attaching fine.

Eventially after reviewing the documentation, I discovered that your web.config may need altering to include the following attribute:

<configuration>
     <system.web>
         <compilation defaultLanguage="VB"
             debug="true"

After setting debug=»true» as stated, the debugger attached fine. Just make sure you’re running VS as Admin!

Other things to consider, that I have found along the way:

• Make sure you are running VS as Admin
• Ensure your IIS App pool user is correctly set up (correct read/write permissions). Apparently for .Net 4, this also includes read/write to: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
• A good old iisreset may also help (start > ‘cmd’ (as admin) > type: iisreset)
• Some people have found that setting Load User Profile to false also helps. You can find this in IIS Manager > AppPools > [Your app pool] > Advanced Settings > (category) Process Model. The default will be true
• The MS document also prompts to check your connection (request) limit (also within Advanced Settings > (category) Recycling

References

• Microsoft’s guide to enabling debugging (where I ultimately found my solution)
• Microsoft’s troubleshooting guide

A few other things to try

• IIS error, Unable to start debugging on the webserver
• Unable to start debugging on the web server. The remote server returned an error: (404) Not Found. Error when starting debug in Visual Studio (includes a screengrab of the required Windows Features — still applicable for 2021)

Ответы

• This error is indicating that you don’t have permissions to put the files where you have specified (in the build options dialog box), — try choosing somewhere that you have read & write access to.

  If you are seeing this message in Internet Explorer (and have gotten beyond the creation step), it could also be the following:

  This error is caused by an access control restriction.  You need to check that the IUSR account has permission to access the files.  Also, if the files are coming from a network share, you should make sure that the IUSR account has (at least) read permissions on the files (and write, etc. if dictated by your particular application needs).

  You can see what the name of the IUSR account is in the internet explorer properties for the site that you are interested in, under IIS manager.

  Just post back if you need information about changing file permissions, etc.

  — Jeremy