Has anyone had trouble with the roles NOT refreshing from Raiser's Edge?  This function has not worked even though we have update/upgraded etc. etc. 

We really have no problems with Role Refresh. If you are on Version 5, you may want to check the easy things like the Blackbaud NetCommunity Service is running and that it is not erroring off in any of the event logs.

Kathy,

Yes, we have the same periodic problem. Blackbaud support is analyzing why at times are roles don't refresh.

Will let you know when resolution is made.

 Gene Witt
Director of Technology
The American School in Japan

We have similar problems with roles not refreshing, and deleting all the roles.  It has been worse since we upgraded to 5.5.

Blackbaud is working on it but they don't know what is causing it.  Sorry I'm not very helpful but it nice to know there are others out their and it's not just us. :)

Hi guys, has anyone had this issue solved?

We're having massive problems with roles not refreshing at the moment and Blackbaud have been unable to help so far.

Still on 5.1 currently, but I think the time we had a problem with role refresh a restart of the NetCommunity Service on the web server helped.

When roles stop refreshing, does data also stop being pulled into the Raiser's Edge NetCommunity tab? That has happened for us occasionally. The "Clear BBNC tab data" plug-in that Blackbaud provided has been helpful in those instances. It flushes everything and then starts populating again from scratch (can take days to catch up with itself, but does eventually). However, I'm not sure the two issues - role refresh and tab data - are linked.

Do you notice other issues when roles stop refreshing? Eg. Stuck email?

Nicki

Thanks for your reply Nicki. 

I've tried restarting the service with no joy. Emails are still fine, and data is still being pulled into Raiser's Edge - I think the query from Netcommunity for roles is one-way only. Weirdly another role we use that is fed by a query still works - it's our 'standard members' role that isn't getting the data from Netcommunity. I think it might be because there's a large amount of members that come under that role and the web service is timing out before it can grab them all.

Very irritating.