Last week I attempted an upgrade to WSS 3.0 SP1, which didn't succeed and hosed my install. I later found a post in one of the newsgroups claiming that if you have Groupboard Workspace, you should uninstall it and try running the upgrade again - which I did, andthe upgradesucceeded (). I now have the problem that every time I try to edit certain things within WSS, for exampleedit Site Columnsunder Galleries inSite Settings, I get the following error: 'Field type GbwConfidential is not installed properly. Go to the list settings page to delete this field. ' I cannot see this field in the list settings page, so I assume GBW leaves behind some lovely remnants when you uninstall it via add/remove programs. I triedinstalling GBW again, and this seems to fix the problem but: a) I don't wantGBW anywhere near my system again b) with GBW installed, I get other problems such as my search server will not start claiming that 'The specified SPContentDatabase Name=WSS_Content Parent=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object'. So, I'm in a catch 22 and I wish I'd never touched GBW. Any help would be greatly appreciated.

Install the GBW after you have completed all the configurations such as SSP Creation, Search Configurations. While applying MOSS SP1 even I faced the same problem where in it says the Content Database has been upgraded to a newer version and hence upgrade the application content files before accessing this object. Then I uninstalled the GroupBoard Workspace, ran the config wizard which was sucessful. Later I downloaded the GroupBoard Workspace and installed it on the server and it worked. Hope this helps! Thanks Prasad.

Hi, thank you for your reply, butI think you havemisunderstood my problem. I don't want GroupBoard Workspace on my server, however if I uninstall it I get an error (see my original post), and if I reinstall it I still get problems. Also I'm using WSS not MOSS.

Apologies! I have not tried with just WSS 3.0. Hopeyou will find the solution. Thanks Prasad

We are having the same issue and were wondering if you had found a solution that does not include re-installing GBW.

Not yet unfortunately. I will report back here if I do.

Daryll Holland wrote: Not yet unfortunately. I will report back here if I do. Boy, am I ever sorry I installed Groupboard! Daryll, I take it you haven't figured out a way to get completely rid of Groupboard? I'd love to completely eradicate groupboard from my servers, but even though it's uninstalled, it still appears in the list of available templates on the createsite.aspx page. It's beginning to appear that the only way to make this thing go completely away is a rebuild of the web farm. Regards, Mike

rdcpro wrote: Boy, am I ever sorry I installed Groupboard! Daryll, I take it you haven't figured out a way to get completely rid of Groupboard? I'd love to completely eradicate groupboard from my servers, but even though it's uninstalled, it still appears in the list of available templates on the createsite.aspx page. It's beginning to appear that the only way to make this thing go completely away is a rebuild of the web farm. As another data point for those struggling with this, I think if you originally got an error during the GroupBoard install, you won't be able to properly uninstall it. I've uninstalled GroupBoard quite a while ago, and I just noticed that it's still in the GAC. And looking in the registry show that it still has entries there as well. So not only is the template still lurking in there, but the other parts are as well. It doesn't appear that there is any way to reliably uninstall this thing, as Uninstall doesn't appear to do anything except take the program off the add-remove programs list. My advice: re-image the entire farm. >:-(

Hey Mike, I thought this thread died a death a long time ago. Thanks for contributing! I concur with each of your points, and the situation seemingly hasgotten worse. I now have a MOSS development environment and I'm trying to import aexport of my WSS 3.0 site collection which fails with 'could not find webtemplate sgs'. The 'fantastic 40' templates which I have used for several sites are installed on the MOSS server, so I can only assume the missing template is Groupboard related. Googling this error produces zero results. I'll confirm this after more testing. I'm also going to test another method of moving my content over to a MOSS development environment found here: http://www.sharepointblogs.com/aghy/archive/2008/04/06/wss-3-0-gt-moss-2007-migration.aspx. Daryll

In my case, I thought I had finally removed Groupboard, but when I tried to install SP1, the upgrade failed due to the missing GB template. I was told that re-installing GB would allow the upgrade to run, but since there is noway in hell I'llever install GB again, regardless of whether they've"patched" it or not, I ended up rebuilding the farm from scratch. Fortunately, there wasn't a lot of content on the farm yet, as we weren't in production.If you haven't installed SP1, make sure you try that out before calling it golden. Good luck with that approach! I'll be interested in hearing whetheryou succeed or not. Regards, Mike

Worked like a charm - although presumably I've copied acrosssome Groupboard remnants using this approach. With regards reinstalling GB to allow the SP1 upgrade to run - that definately works, but we shouldn't have to do it. Going back to my original upgrade; I removed Groupboard again after the successful upgrade, and I managed to fix the search issues with WSS 3.0 but I wonder if I'll experience this again with SharePoint 2007 SP2 ;-). Daryll

Hi there Daryll,I'm having exactly the same problems as you. Went to put SP1 on, failed due to GBW, uninstalled GBW, finished off SP1 and now I'm getting the error when editing site columns. Was your solution just to put GBW back on again? Or did you do something more fancy?! Many thanks,Steve

Sorry for the late reply. In short; yes I had to reinstall it.This thing is still causing me issues. I had to perform a database server migration last week (virtual SQL2005 to a physicalSQL2005 box), and the migration procedure failed when I tried to use the 'stsadm -o renameserver' command.In the end Idecided to cut my lossesand performa full restore but the restore process failed saying that the WSS_Content DB was a different version to my farm. As soon as I took off GBW, the restore process worked, but now I'm back to my original'Field type GbwConfidential is not installed properly. Go to the list settings page to delete this field. ' error whenever adding columns etc. I have to reinstall theapplication I'm desperately trying to get rid of in order to have normal functionality - it's ludicrous.Does anyone know how I can get rid of this thing once and for all without having to rebuild my farm from scratch?

Update - I believe I have fixed the issue (YAY!)Try at your own risk.1) I deactivated my GbwCommonFeatureID by running 'stsadm -o deactivatefeature -id7ECE0598-D1D7-41B4-8BF4-C4F879505458 -url http://intranet (not sure if this actually helped)2) I went into the Global Assembly Cache (%windir%\assembly), deleted any assemblies that started with 'Groupboard'.3) I renamed any'GBW...' folders from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES.4) Performed an IISResetTried to add a column again and all was okay....Perhaps somebody could comment on whether this fix is a good/bad idea?CheersDaryll A+, MCP, MCTS WSS 3.0 & MOSS 2007 Configuring

Just in caseit helps anyone else-I had a similar problem with site columns and found that Retracting the GBW solution from all sites I'd deployed it to, and then deleting it seems to have sorted my woes.

Is there a way to see where in a farm the GWB solution has been deployed?

yes please, that'd be great to know which farm has GBW installed ?/* Infrastructure Support Engineer */