Hi everyone, I have an SBS 2008 domain with WSS 3.0 (SQL 2005 Express) default install. I added a child site and must have accidentally clicked the "Manage Permissions of Parent" instead of the "Edit Permissions" link which you inherit and then break off inheritance to create unique permissions. Unfortunately I did not catch my mistake until it was much too late. All my permissions were working well before this. I have recreated all my Parent Site permissions, but they are not working properly. They are also not working on the child site, either. All the rights that I did not change in creating the permissions for the child site work properly. The ones I have recreated aren't allowed any "Design" functionality. They cannot start work flows, mark tasks assigned to them as complete (edit Tasks), anything that requires the slightest permission above read. They can edit documents and save them in the libraries, but nothing in the Edit SharePoint realm as I have granted them rights to do. I haven't found anything specific to this problem online. Any help on this will be greatly appreciated. As it is now, I have built all these lovely work flows that people were able to use and now they cannot. They are growing irritable. John Technical Director Harvest America Corporation

If your problem is to re inherit parent permissions you can go to Site Permissions and Inherit Permissions under actions will re inherit parent permissions. HTH Nagesh **If you find this post helpful, please click the 'Vote as Helpful' link. If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.**

Nagesh, The permissions were/are different then the for the parent site. For the majority of the parent site the majority of my users have "Read only" permissions. I removed this from inheriting and the hand full of users have unique permissions - except they don't work "as advertised". I have gone to the extreme of giving the users "Full control" and they still aren't allowed to access the "Start workflow" page or edit a task to mark it complete. These were all working fine until I mistakenly edited the top level permisions and then attempted to return them to the proper settings through out the companyweb site. I could try reinheriting and re-uninherting to see if that changes anyhting. Thanks for your reply. JohnJohn Miles Technical Director Harvest America Corporation

Could it be possible the Document Library that the workflow is working on has not inherited permissions from site? If you log in as a farm administrator are you able to start the workflow? HTH Nagesh **If you find this post helpful, please click the 'Vote as Helpful' link. If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.**

Could it be possible the Document Library that the workflow is working on has not inherited permissions from site? If you log in as a farm administrator are you able to start the workflow?

Nagesh, I did reinherit, disinherit and create my unique permissions again, but it still doesn't work. If I log in as a farm admin I can start the workflows and mark tasks completed. Thanks again, JohnJohn Miles Technical Director Harvest America Corporation

Check if the specified Document Library also inherits from parent site and does not have its own unique permissions. Check same with Workflow Tasks list. Check permission levels, you might habe mistakenly removed/chnged permission levels.

Check if the specified Document Library also inherits from parent site and does not have its own unique permissions. Check same with Workflow Tasks list. Check permission levels, you might habe mistakenly removed/chnged permission levels. Sameer Dhoot My Blog : http://sharemypoint.in/ Did I answer your question? If YES, Mark as Answer. If NO, reply with details to continue dialogue.

According to http://office.microsoft.com/en-us/windows-sharepoint-services-help/manually-start-a-workflow-on-a-document-or-item-HA010154433.aspx , you must have the Edit Items permission to start a workflow. Some workflows may require that you also have the Manage Lists permission, or another specific permission, to start a workflow on a document or item. Is the option “Editing users and permissions” check in Site Settings->Configure Audit Settings, so that you can see what change you had made to permissions in site settings->Audit log reports->Security Settings

According to http://office.microsoft.com/en-us/windows-sharepoint-services-help/manually-start-a-workflow-on-a-document-or-item-HA010154433.aspx , you must have the Edit Items permission to start a workflow. Some workflows may require that you also have the Manage Lists permission, or another specific permission, to start a workflow on a document or item. If the option “Editing users and permissions” is checked in Site Settings->Configure Audit Settings, you can see what change you had made to permissions in site settings->Audit log reports->Security Settings

Check if the specified Document Library also inherits from parent site and does not have its own unique permissions. Check same with Workflow Tasks list. Check permission levels, you might habe mistakenly removed/chnged permission levels. Sameer Dhoot My Blog : http://sharemypoint.in/

For the Item where you can run workflow as farm administrator look at Item permissions. that should tell you if the users have Edit permissions or not. HTH Nagesh **If you find this post helpful, please click the 'Vote as Helpful' link. If this post answers your question, click the 'Mark As Answered' link below. It helps others who experience the same issue in future to find the solution.**

For the Item where you can run workflow as farm administrator look at Item permissions. that should tell you if the users have Edit permissions or not.

Thanks for your replies. I'm actually home sick today. While I could remote in and check these, reading my emails is about my limit. I'll let you know. JohnJohn Miles Technical Director Harvest America Corporation

GuYuming and Nagesh S, First, I obvoiusly don't have the audit enabled - I can't even find the option. I have looked in Site Settings as well Central Administration and cannot find it. I have gone into all the lists and libraries to double check the permissions and I began with READ, added DESIGN(didn't allow anything but read rights, still) added CONTRIBUTE - no change. I'm thinking this install is corrupt. I can no longer connect to MICROSOFT##SSEE in SQL management. I was going to backup the SQL content for the site, uninstall, reinstall and restore content to avoid starting completely from scratch. I have backed up via STSADM, but I'm finding moving that to another place difficult to restore as a test. I see in my Event Log that after each time I restart SharePoint Seqarch cannot connect to MICROSOFT##SSEE and that it appears to "restoring from a snapshot?" Yet it works. I cannot log into MICROSOFT##SSEE in SQL management studio, yet apparently I can change the log size via command prompt!? (have since gotten into \\.\pipes\mssql$microsoft##ssee\sql\query. Who thought that was a good name!!) I'm thinking this may be more of an SQL matter than a SharePoint matter, but I am unsure how to proceed. (Have been looking into the permissions in SQL to see if that is why there are connection problems) (Considering rerunning SharePoint Configuration Wizard and attempt to reconnect the Content DB) Thank you for the help thus far and any more you can lend John John Miles Technical Director Harvest America Corporation

GuYuming and Nagesh S, First, I obvoiusly don't have the audit enabled - I can't even find the option. I have looked in Site Settings as well Central Administration and cannot find it. I have gone into all the lists and libraries to double check the permissions and I began with READ, added DESIGN(didn't allow anything but read rights, still) added CONTRIBUTE - no change. I'm thinking this install is corrupt. I can no longer connect to MICROSOFT##SSEE in SQL management. I was going to backup the SQL content for the site, uninstall, reinstall and restore content to avoid starting completely from scratch. I have backed up via STSADM, but I'm finding moving that to another place difficult to restore as a test. I see in my Event Log that after each time I restart SharePoint Seqarch cannot connect to MICROSOFT##SSEE and that it appears to "restoring from a snapshot?" Yet it works. I cannot log into MICROSOFT##SSEE in SQL management studio, yet apparently I can change the log size via command prompt!? I'm thinking this may be more of an SQL matter than a SharePoint matter, but I am unsure how to proceed. Thank you for the help thus far and any more you can lend JohnJohn Miles Technical Director Harvest America Corporation

Ok, this is what I have learned since my last post (that I edited): The rights issues with editing forms was due to an inability for the form to "see" its template (i.e. I moved the form to another library with my workflow and the user needs to have read rights on the form library for the form to work. This now works). Other issues with SQL are non issues. Everthing connects and works. The problems aren't with everything in the libraries. The problems appear to be with permissions with my custom workflows and anything associated with them. I have changed the permissions on the Workflows Folder within Sharepoint Desginer, but still nothing. I will try rebuilding my workflows. Thanks again, JohnJohn Miles Technical Director Harvest America Corporation

A follow on. My final issues were due to permissions between libraries. I assumed (yes, at least of me) that the system account would be moving these, but apparewntly the users do. So they need permissions to be allowed access. I would prefer the permissions not be accross the different libraries. If anyone knows a way to acheive this please let me know. Here is a useful link on my last issue: http://office.microsoft.com/en-us/sharepoint-designer-help/troubleshoot-workflow-errors-HA010237912.aspx#BM34 I had so many different issues going on that it was very hard to isolate them. It took looking at the problem from many different ways including from a sick bed! So my issues were: Infopath template was not "seen" from library where I passed it. Needed to add READ rights to users in passed to libraries. Needed to give rights to CONTRIBUTE rights to users to libraries being passed to to allow workflow to COPY LIST ITEM. Needed to give permissions on Worflow folder to users to allow use in SPDesigner. It all works now, even if people have acces to things I'd rather they not! Thanks to everyone and I hope this helps someone else who may have run into tis problem John Miles Technical Director Harvest America Corporation John Miles Technical Director Harvest America Corporation