Turns out that this issue is fairly common. Saw this happen in both SXA and the Publishing Service.
The solution is to clear the Temporary Asp.Net files from IIS.
Michael West
- 18.6k
- 2
- 42
- 105