Ah, a server log file. That explains the path issue I thought was messed up. I have never seen that error. If things are running well, keep moving forward with the deployment, but check that log every once and a while to make sure the error does not keep coming back.