Deployment Issue - Access to path is denied error

[itg-assistant]

edmond girardi asked 2017-12-01 17:12:46 UTC

I'm getting this message in my browser when deploying to a new install of my WiseJ app on Server 2012:

"Wisej failed to initialize for the following reason: Access to the path 'C:\Windows\TEMP\Wisej\TPortal\Wisej.Web\Wisej.Web.Platform.QXDesktop.json' is denied.."

I checked ASP.Net Trust level - it is set to Full. Using the .Net 45 App Pool.

I don't recall getting this error the first time I set it up (re-did the server setup on a VM this time)

What would cause this ?

[itg-assistant]

edmond girardi answered 2017-12-01 17:22:22 UTC

My App Pool on the server – even though it says .NET 45 – it actually point to .NET 4.0.30319 – is this correct ?

[itg-assistant]

Luca answered 2017-12-01 17:25:08 UTC

It's the identity for the app pool that cannot write to temp.

The .NET v4.5 seems to be using NetworkService by default. While the the DefaultAppPool uses ApplicationPoolIdentity. I always use DefaultAppPool or create a new one for the application.

[itg-assistant]

edmond girardi answered 2017-12-01 17:25:54 UTC

Also looked in that path and there are a bunch of WiseJ files in there:
C:\Windows\Temp\Wisej\TPortal\

[itg-assistant]

edmond girardi answered 2017-12-01 17:29:17 UTC

Yeah -I tried that fisrt. But I get the error: “The Type Initializer for “WebApplication1.frmLogin’ threw an exception.

Not sure whats up – it runs fine on my Dev PC

[itg-assistant]

edmond girardi answered 2017-12-01 17:43:32 UTC

Switched it to Default App Pool and I get the Path issue – same as when I made my own App Pool.

[itg-assistant]

Luca answered 2017-12-01 17:49:59 UTC

Verify that the DefaultAppPool is Integrated Pipeline and .NET 4. A type initializer error means that .NET cannot load the class usually.

[itg-assistant]

edmond girardi answered 2017-12-01 17:53:05 UTC

Just noticed in the Webconfig you have a section” ”

Do i need to list the “Wisej.Ext.FontAwesome” in this section ? Although I don’t recall doing that before.

[itg-assistant]

edmond girardi answered 2017-12-01 17:57:34 UTC

Verified – it is .Net 4, Integrated Pipeline is selected. The Default App Pool that I have selected for the WiseJ App’s Identity is “ApplicationPoolIdentity”

[itg-assistant]

Luca answered 2017-12-01 17:59:04 UTC

The error is still “The Type Initializer for “WebApplication1.frmLogin’ threw an exception.”?

[itg-assistant]

edmond girardi answered 2017-12-01 18:03:25 UTC

No – Now I get the Path Denied message – still using Default App Pool as comment above.

[itg-assistant]

Luca answered 2017-12-01 18:09:22 UTC

Better. I checked my \Temp permissions and it has DefaultAppPool. I think that it’s added by the ASP.NET 4 installer but you can also do it manually.

[itg-assistant]

edmond girardi answered 2017-12-01 18:16:44 UTC

I went to the Windows\Temp folder – and I noticed the permissions of IIS_USER were not set. I set it to full control – now I’m back to the “Type initializer threw an exception” message.

[itg-assistant]

Luca answered 2017-12-01 18:18:08 UTC

DefaultAppPool doesn’t use IIS_USRS. I have DefaultAppPool as the user with permissions.

[itg-assistant]

edmond girardi answered 2017-12-01 18:26:12 UTC

Added that – still get the issue. What do you have under the server Roles\Web Server\Security – what boxes are checked ?