Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I've got an event receiver that extracts and saves an icon from an exe file located on the network when an item in an underlying list is added or updated (the list contains the network location of the exe). This works fine.

I'm now trying to convert the event receiver code into a simple workflow so instead of working on a single item in a list, it goes through the entire list and extracts icons for all items in the list. I've hit a problem where the workflow can't see files located on the network. I am logged on as the domain administrator so should have unlimited access to the file system. Here is an extract of the code that is in the single code activity item in the workflow:

        string appLocation = listItem["AppLocation"].ToString().ToLower().Trim();

        FileInfo appInfo = new FileInfo(appLocation);

        if (appInfo.Exists)
        {
           // NEVER REACHES HERE AS FILE IS LOCATED ON THE NETWORK
        }

Why is it workflows can't see the entire file system - I was under the assumption that the local credentials were used in SharePoint?

share|improve this question
    
This might be an NTLM double hop issue? I'm working on this issue myself and will let you know what I end up with. Also check this out if you're still looking into this, it appears calling a WCF service to do you dirty work might be the best way. shillier.com/archive/2010/08/31/… –  William Dwyer Jun 15 '12 at 15:58
add comment

1 Answer 1

Your workflow will run using the credentials used by your Timer Service account. Try giving that account access to the file system.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.