JohnGalt 13 Posted February 7, 2015 Posted February 7, 2015 The problem appears to have been due to the database reindexing after the upgrade to 6.0.6 and resolved itself once the index completed. Sorry to anyone reading this for wasting your time.
Idea
JohnGalt 13
The problem appears to have been due to the database reindexing after the upgrade to 6.0.6 and resolved itself once the index completed. Sorry to anyone reading this for wasting your time.
0 replies to this idea
Recommended Posts
Archived
This topic is now archived and is closed to further replies.