Yes. I'd moved it to a network drive to make working between my main machine and my laptop easier. When I moved it back, the error went away. I'm thinking it's a latency thing with accessing the folders, but <shrug>. Something for one of the experts to dive into I guess.
Thanks for confirming.