.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

SPD 2007 Manually Start Workflow access denied

Posted By:      Posted Date: October 05, 2010    Points: 0   Category :SharePoint

Im having  a isssue i have encountered before, however the fix seems to either have sliped my mind or the fix i thought should fix it seems to be having a issue as well.


I have created a workflow in SPD 2007 to manually start and update a list item, however before i can even get to the "start" page i get access denied with EVERY user except the Site collection administrator.

The fix i had: Check the workflow out in SPD and check back in, BUT im also getting a error with ANY File upon trying to check back in "Cannot perform this operation. the file is no longer checked out or has been deleted" BOTH are not true.

So any input would be greatly appreciated.

View Complete Post

More Related Resource Links

Attach Workflow to Task List, don't get option to manually start workflow via dropdown on task item



I am running WSS 3.0 with other workflows which are functioning correctly.  I created a new workflow in Visual Studio 2008 and was able to successfully run it in my dev environment.  I attached the workflow to a task list in my dev environment and was able to manually start the workflow by using the drop down workflow option and using the menus to manually start it.  I installed this workflow in our production environment and attached it to the task list (which had a SPD workflow attached to it which stopped working about a month ago).  I made sure that the option to manually start the workflow was checked.  When I tried to manually start the workflow, (hover mouse over title, drop down) there isn’t a workflow option.  The workflow also will not start automatically when a task is changed.


I attached this same workflow to a different task list in production and get the option to start it.


I have tried creating a small workflow in SPD 2007 and attaching it to the task list.  It shows that it is attached, when I look at the workflows that are attached to the task list, but I still don’t get the option to manually start it.


I have checked my security and I have fu

VS Studio WorkFlow Failed on Start in MOSS 2007 ON Windows Server 2008 64 Bit


I have created a sequential sharepoint workflow in WSP Builder in my Sharepoint Server and Deployed it.

But the workflows says Failed on start and retrying ans stops there forever says couldn't start the workflow.

I repaired .NET Framework 3.5sp1 installed

 tried this

 1. I tried again, in C Prompt:  Lodctr "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini"  it says initiation file cannot be found

2   i again tried this C prompt Lodctr /R "c:\Windows\Microsoft.Net\Framework\v3.0\Windows Workflow Foundation\perfcounters.ini"

it says reloaded  from the system restored

i am still getting the same error.

When i manually go to my  C:\Windows\Microsoft.NET\Framework\v3.0\Windows Workflow Foundation i can see a folder for SQL that's it nothing more than that..

I dont know what is happening i am trying it from 2 days and still no solution.

any ideas would be real great help for me.

My system is 64 bit , Window server 2008, MOSS SP2, Visual Studio 2008 Version 9.0.30729.

.Net Framework 3.5 sp1

and WSP builder the one from Codeplex for 64 bit machines

SharePoint 2007 Expiration Policy Not working : Access denied for the site


I have a SharePoint 2007 List with Expiration Enabled in Information and Policy Management. I have a datatime column ExpiryDate which i used in Expiration. On Expiration I have chose to delete the item. Through Central Admin I run the expiration by clicking "Process Expired Items now" button. I got the following error in the Windows event viewer.

Expiration Service for site http://md-rmanimaran failed.

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

EventID: 5016

Category: Information Policy Management 

Where I need to specify the login details to get rid of this error? Anybody Please help..




Access Denied/The workflow could not copy the item workflow error after Sharepoint 2010 upgrade

We have a sharepoint designer workflow that copies a document from one library to another on the same site.  Before the upgrade to 2007 it worked fine, but now with 2010 it gives an error and cancels the workflow when it gets to the copy list item step.   The error on the workflow page: The workflow could not copy the item. Make sure the source and destination lists have the same columns and column settings.  Access Denied   Specifically it is the "copy list item current item to documentlibrary" sharepoint designer workflow action.   I have given the system account full permissions to the library and double checked that all columns are the same in both libraries. These are the verbose trace logs:   09/01/2010 09:46:04.05 w3wp.exe (0x17C4) 0x093C SharePoint Foundation Workflow Infrastructure 72er Medium System.UnauthorizedAccessException: <nativehr>0x80070005</nativehr><nativestack></nativestack>Access denied. at Microsoft.SharePoint.SPFile.UpdateInternal(Boolean migrationSemantics, Boolean reGhost) at Microsoft.SharePoint.Workflow.SPWinOEWSSService.CommitCopyFile(Transaction txn, Object[] transData) 09/01/2010 09:46:04.05 w3wp.exe (0x17C4) 0x093C SharePoint Foundation Workflow Infrastructure 72fe High Error in commiting pending workflow batch items: Sys

Access Denied while using Sharepoint designer 2007 to create a work flow

I am using Sharepoint Designer 2007 to create a work flow that sends emails to different people in a group depending on status of a record. For example, when some one reports a problem, an email is posted to concerned person and as soon as he/she checks the problem and updates the status an email is sent to next department and so on. Starting the work flow creation wizard is no problem but as soon as I press 'Finish' to create workflow I get 'Access Denied' message box. Any Ideas? I am using WSS 3.0 on 2003 Server.

Access denied when starting workflow


I have a workflow that when started by a site collection admin, allows it to start. But if a user starts it they get access denied. I've set the user up with full access to the document library, tasks and workflow settings and still the same. If I then add the user as a site collection admin all is well.

The workflow has been created using sharepoint designer.

I've tried everything I can think of, so any ideas welcome.




Custom Workflow Activity Works 'Manually' but can't be fired using CodePlex's 'Start Another Wo


Consider 2 lists.  In one list, a workflow runs on an item and if conditions are right, it creates an item in another list, pauses for 5 min, then starts another workflow on that newly created list item (using CodePlex's old 'Start Another Workflow' routine).

All of that works great, used it many times in many situations without fail, so long as I put a pause between the item creation and calling the workflow on the newly created item.

I've started writing my own custom workflow activities, all of them work just fine, up to 5 now, really useful to do little things that SPD Workflow can't do by itself.  The 5th one I added was a very simple 'Now' routine.  The class itself is called 'GetNow' and has a 'RightNow' property that's DateTime and it works great.  I have the need to stamp something with the current date/time, and I haven't modified the underlying record yet, and setting a Date/Time variable only takes Today or a static date/time, with 'Today' returning the current date, but '12 am', which is redunculous, but I digress.

So my step compiles, updated my .ACTIONS file which holds the definition for the other 4 custom routines.  I have the context 'in' parameter and one 'out' parameter for 'RightNow' defined as System.DateTime (which I think is where the problem is, possibly), and it all works if I

sequential workflow Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))



   When i am creating a Sharepoint  sequential workflow  it is gives the

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

PLease can you guys help.




Access Denied error when attaching VS2008 workflow debugger to 64-bit IIS if VS2008 user differs fro

I am trying to attach VS2008 to debug a workflow hosted in IIS (using the workflow debugger option so I can step through the visual workflow designer breakpoints, not the managed code debugger).  It is actually a WF 3.5 WCF workflow service hosted in IIS but I don't think that is the issue.  When I attach from VS2008 I always get the error "Unable to attach to process.  Access is denied."

I can attach for managed code debugging no problem.  Also, if I configure the IIS worker process app pool to use the same account as the account I am running VS2008 under I can attach not problem and debug using the workflow debugger.

So my remaining problem is that I would like to be able to attach while running VS2008 as my normal user account and leave the w3wp.exe app pool running as the usual networkservice account so that my debugging represents how the w3wp.exe will act in production.  I'm on Vista SP1 64-bit with .Net 3.5 SP1 and VS2008 SP1. 

Q: Is there a special privilege I can grant the worker process account so that I can debug while using a different user account?

I saw a very old post here http://blogs.msdn.com/sonalic/archive/2006/05/10/594703.aspx that hinted there is something special for 64-bit.  Does anyone know if there is something special about 64-bi

Web analytics service failed to start : access denied


I came a cross an error in my sharepoint environemnt whic indicates that Web analytics service  fails to start.

Web analytics service failed to start : access denied

I have everything up and running, is there a special service with a special privileges that need to be setup for this service?

Thanks in advance

MOSS 2007 - Access is denied. Check that the Default Content Access Account has access to this cont


Greetings folks,

I have MOSS 2007 running on Windows 2008 server.  I'm getting the following error when trying to crawl content.  "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content."  I have tried everything to correct this, and i'm about ready to pull my hair out.



Access Denied error on custom workflow task list item


We have created a two level custom approval workflow on (an InfoPath) form library using SharePoint Designer (SPD) with first and second approver. The workflow works fine as long as the approver is in the Site Collection Administrators group. The approvers who are not in the admin group can get to the custom Task form for approve/reject, but they can only view the form. When they click on the “Edit Item” button of the task list item, they receive “Access Denied” error. We have given these approvers “Approve”, “Contribute” permissions on the Form library and even Full Control on the task form list (all items). Note: The users use their domain account and the error they are getting is: Access Denied, You are currently signed as DomainName\LoginName, Sign in as a different user.

We have read through several forums and have found people having the same issue. We tried all of the suggestions described in the following links - but no success so far.

SharePoint Designer Workflows, Tasks, and the Annoying “Access Denied” Error

moss 2007 workflow error failed on start(retrying)


i am getting this error "failed on start(retrying)" on a custom workflows.

The error does not occur very frequently, once a week (the workflow is triggered roughly 50 times a day).

Any ideas? Or where can I get more details on this error (some log files elsewhere?)



SharePoint 2007 Workflows - Things to Consider Before You Start

SharePoint 2007 (MOSS) utilizes the Workflow Foundation (WF) to enable workflows on lists and content types. But before you start doing cartwheels there are few things you should know before you get started. The experiences I'll be discussing are not from book smarts but from building real MOSS solutions that are in production today.

Access to report file denied. Another program may be using it.


Migrated from Windows 2000 ASP.NET 1.1 to Windows 2003, ASP.NET 2.0 and had this error. All the forums/MSDN/Blogs says to give Read/Write Access to C:\Windows\Temp folder. Why should we give Full Access to some folder in Production server?? In windows 2000, ASP.NET 2.0 development machine, no files are created when we run crystal reports from aspx pages. Then why in Windows 2003 servers, we need to give rights to temp folder?? It is a simple code


And the code is not storing anything on the disk. Then why should it store the GUID.rpt file in Temp file in Windows 2003 server?? Any alternative is there not to store anything on the disk when Crystal Reports are opened in aspx page??


"Access is denied. Check that the Default Content Access Account has access to this content"


Our search is not working. The crawl log indicates following error: "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".


If I check the event viewer, it indicates following error: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <local machine>]"


My default content access account is another one than this NT AUTHORITY\NETWORK SERVICE account. The content access account password is correct. Apparently this content access account is translated to the NETWORK SERVICE account upon a crawl. And this network service account doesn't has the appropriate rights on database level. How can I fix this?


Workflow "Failed on Start (retrying)" when new item created by BizTalk SharePoint Adapter


We've been using the BizTalk SharePoint Adapter to load various different contents into a MOSS 2007 Document Library. The library has a Microsoft Office SharePoint Designer 2007 workflow (sequential workflow created in Designer) which starts automatically when a new item is added to the Document Library. Or, at least, it eventually starts automatically.


For some unknown reason--and this is what we're hoping some of you may have some ideas on--the workflow fails to start on the first try, producing the "Failed to Start (retrying)" message. When the timer job comes back the second time, the workflow starts successfully, but this causes us to loose five minutes of potential work time (not to mention making us look bad to the VPs and CTO because they see the failure message).


In checking the log, I find the following pair of error messages each time the "Failed to Start (retrying)" status occurs:


08/27/2007 13:49:43.24  w3wp.exe (0x0CA0)                        0x1438 Windows SharePoint Services    Workflow Infrastructure        72fs Unexpected RunWorkflow: Microsoft.SharePoint.SPException: <Error><CompilerError Line="1" Column="1" Text="The root activity type is invalid.&q
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend