The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.
LoadUserProfile set to true in IIS
Profiling on original port (SSL)
It should also be noted that at one point, this worked without issue - now it does not.