Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
After hours of banging my head against the wall over that config error, I finally found the culprit. It was my tree.cfg file. The last three entries were the culprits. These three were somehow set to "on" when they should have been "off". What I find so strange is that it didn't give an error in WF 5 using the very same config file.
Cheers!
