Recently I've configured a Django site in a virtualenv on windows server 2016 with IIS and fastcgi. This was done with a user account that was later replaced by a technical account(has more rights). The site ran and still runs great.
The problem now is that with this new technical account I can not configure a new site following the exact same steps. It keeps throwing a 500 error when visiting the site. If I change the web.config file to point to the original venv it works. It seems wfastcgi capabilities are locked to virtual env's created by that original user account.
I've double checked the app pool permissions on the folder with the new virtual environment and site, they are exactly the same as the original folder. I've checked with a monitoring application if there's access denied errors for this new folder, this seems not be the case. I've double checked the web.config file, it points to the correct wfastcgi script and python.
Could it be since I installed Fastcgi under the old account it's operations are fully locked onto this account?