Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Failed to map the path

Failed to map the path

Scheduled Pinned Locked Moved ASP.NET
helpcsharpasp-netwindows-adminsecurity
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mlauahi
    wrote on last edited by
    #1

    We created an ASP.NET account and made him "Act As Part Of The Operating System". This was a bad thing to do. We removed him from that security setting but all .NET 2.0 ASP.NET applications generate the same error when running IIS under this new ASP.NET account. An Example to SecurityWebService which is a Web Service generates: Exception type: InvalidOperationException Exception message: Failed to map the path '/SecurityWebService/App_GlobalResources/'. There is no App_GlobalResources under this Web Service. When the processmodel line in the machine.config file gets set back to its default, everything works fine, when we change the line to be the new ASP.NET domain account all 2.0 apps fail. Any help????

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups