I had the same issue with the passive node complaining that it could not open the SQL Error log file which was placed on a cluster disk. I moved it to the C: drive making sure that exactly the same path existed on both nodes. After restarting, the error message stopped. But the problem is that each node now has part of the log history, so I seem to have solved one problem but created another.