Hi gang, Checking spelling on our new MOSS 2007 site works just fine for me, but for normal users (I'm a site collection administrator), they see this error: Spelling did not complete properly. If this problem persists, notify your system administrator. Anyone else seen that? I can't even find a section in the configuration site to deal with spell checking etc. What am I missing? Cheers,Matt

Hi, A client of mine had the same problem. It took me a while but I managed to reproduce it nd find a workaround/solution. The problem Sharepoint has is that your users have access to specific subsites (e.g. http://sharepointserver/sites/SharePoint/Another%20Test/ or even only to a specific list of that subsite , but not to the topsite of the site collection (in the example that would be http://sharepointserver/sites/SharePoint) . In itself that is not an entirely logical situation: your user can only access the site using the complete URL, and cannot browse to it starting from the topsite. Solution? I have two: 1) Give all necessary users the contribute permission level on the top site (read is not sufficient). Next, break the inheritance on all lists, libraries and subsites of the top site where you do not want those users to have contributor access.Which users? You can use all authenticated users, but it is only those users that will be wanting to use the spell check for whom its necessary. So de facto that means only contributors or higher. 2) If you think the above solution is quite drastic and requires too much maintenance or could cause a security leak later, you can also a. On the top site, create a new permission level, e.g. spellcheck. Assign only the following site permissions to the permission level:- browse directories - view pages - use remote interfaces - open Any other will give more rights, any less will not solve the problem. b. On the top site again, assign the new permission level to the necessary users. The effect will be that i. they cn access the topsite but not view any content. They can use it to browse to their subsite ii. they can use the spellcheck Does it make sense that all this is necessary to be able to use the spellcheck on lower levels? Not to me. Possibly it will be the subject of a hotfix or service pack later on? Kind regards Pieter Jan Hermans

Hi, In my case it is the spell check in the wiki that is not working. The user can create and add to the wiki, but can not perfrom spell check. The user is given the same error "Spelling did not complete properly. If this problem persist, notify your system administrator." Is there a way to remove the Spell Check option for those who are not given the permisison? Thanks! HAPPY HOLIDAYS!

It is an excellent stuff and has solved my problem. Thanks alot to Pieter Jan Hermans.

We have created the permission level and contribute permission level has been provided for users. But still I get the error Spelling did notcomplete properly.If this Problem Persists,notify your system administrator. When I login as admin spell check works fine but,doesn't work for non-admin users though contribute permission has been given for users.Canyou please help me tosolve this Issue.

Hi Aakarshana, For your issue try the steps below: Turn off the below user permissions for the web app and try to do a spell check on any list item."Central Administration > Application Management > User Permissions for Web Application"1. Use Remote Interfaces.2. Use Client Integration Features. Hope those help.. Regards Catastrophic Failure (JV)

Hi All,I am site collection administrator for a Top level site collection and one below it and still get the same error in the lower level site collection i.e. "Spelling did not.....".I additionally checked the Security Policy in Central Admin - there are no Deny Permissions set there. We have MOSS 2007 SP2 installed on the server. If only users are getting this error - I can understand they may have not permissions as mentioned in posts above but it does not work me even - as a Site Collection Admin.Any ideas not why this would be happening? Our MOSS version # is: 12.0.0.6514 and this is August Cumaltive updates 2009 (which is after SP2)Here is the link for versions:http://www.wssdemo.com/Pages/versions.aspxThanks,Mo

Thanks Pieter Hermans this worked a. On the top site, create a new permission level, e.g. “spellcheck”. Assign only the following site permissions to the permission level:- browse directories - view pages - use remote interfaces - open Any other will give more rights, any less will not solve the problem. b. On the top site again, assign the new permission level to the necessary users. The effect will be that i. they càn access the topsite but not view any content. They can use it to browse to their subsite ii. they can use the spellcheckhttp://technet.microsoft.com/en-us/library/cc263239.aspx

Pieter Hermans' Option #2 worked perfectly for me. Our scenario is exactly as he described.