|
From: Ryan M. <rm...@hy...> - 2007-03-27 16:58:22
|
I should also mention that I tested this on 3.0.2. I seem to recall a bug in the 3.0 beta or 3.0.1 time frame that would cause that message to not go away once the resource has been configured. So a server upgrade to 3.0.2 may be in order. -Ryan |