If I normally start our XAF application via IIS locally it runs without problems, lets say: http://somexafapp.local.
It uses the IIS APPPOOL\somexafapp as the application pool identity.
XAF is a RAD tool we use and are normal ASP.NET applications (we use the latest 18.x version running on Windows 2016 development servers). We connect to a locally installed SQL Server Development edition.
Now I tried to profile 1 XAF app by choosing the 'IIS - ASP.NET' option and running on the original port and it gives the above error which is strange because the web.config never uses the master database to create something.
If I normally start our XAF application via IIS locally it runs without problems, lets say: http://somexafapp.local.
It uses the IIS APPPOOL\somexafapp as the application pool identity.
XAF is a RAD tool we use and are normal ASP.NET applications (we use the latest 18.x version running on Windows 2016 development servers). We connect to a locally installed SQL Server Development edition.
Now I tried to profile 1 XAF app by choosing the 'IIS - ASP.NET' option and running on the original port and it gives the above error which is strange because the web.config never uses the master database to create something.