Amir,

There are two overloads on the DocumentExporter.ExportPage and DocumentExporter.ExportPages methods.  One accepts a Stream (filestream) as a parameter and one accepts a String (output path) as a parameter.  Your code example is using the filestream overload but you need to use the Create method on the filestream instead of the OpenWrite method.  Here is your modified code example that works on my machine;

        protected override void Execute()
        {
            // Get Path to Windows Folder for Exports
            String exportFolder = (String)GetTokenValue("DestinationPath");
            DocumentInfo doc = (DocumentInfo)this.BoundEntryInfo;
            DocumentExporter docExporter = new DocumentExporter();
            String exportPath = System.IO.Path.Combine(exportFolder, doc.Name + ".tif");
            docExporter.PageFormat = DocumentPageFormat.Tiff;
            //   this parameter will be changed to find the number of pages
            int pageNumber = 1;
            using (FileStream fs = File.Create(exportPath))
            docExporter.ExportPage(doc, pageNumber, fs);
        }

Here is the same code using the string output path overload and exporting all of the pages versus a single page;

        protected override void Execute()
        {
            // Get Path to Windows Folder for Exports
            String exportFolder = (String)GetTokenValue("DestinationPath");
            DocumentInfo doc = (DocumentInfo)this.BoundEntryInfo;
            DocumentExporter docExporter = new DocumentExporter();
            String exportPath = System.IO.Path.Combine(exportFolder, doc.Name + ".tif");
            docExporter.PageFormat = DocumentPageFormat.Tiff;
            docExporter.ExportPages(doc, doc.AllPages, exportPath);
        }

Depending on your use case my thought is that the output path overload is the cleaner piece of code.

I'm providing update as I'm sure someone else will run into this problem. As Ramsey and Jason pointed out its a version issue. DocumentServices was 10.4 and RepositoryAccess 11.0. Even though it was a warning and not an error, if the version numbers are different it will probably not work correctly. 

Problem was that DocumentServices 11.0 doesn't exist selection or browsing in the default folder. After downgrading to 10.4 and everything starting to work we ended up looking at this post https://answers.laserfiche.com/questions/184977/Workflow-11-SDK-Script-unable-to-add-reference-to-DocumentServices and were able to browse to it and move everything up to 11. 

Here is the final version of the script using 110:

namespace WorkflowActivity.Scripting.SDKScript2
{
    using System;
    using System.Collections.Generic;
    using System.ComponentModel;
    using System.Data;
    using System.Data.SqlClient;
    using System.Text;
    using Laserfiche.RepositoryAccess;
    using Laserfiche.DocumentServices;
    using System.IO;

    /// <summary>
    /// Provides one or more methods that can be run when the workflow scripting activity is performed.
    /// </summary>
    public class Script1 : RAScriptClass110
    {
        /// <summary>
        /// This method is run when the activity is performed.
        /// </summary>
        protected override void Execute()
        {
            // Get Path to Windows Folder for Exports
            String exportFolder = (String)GetTokenValue("DestinationPath");
            DocumentInfo doc = (DocumentInfo)this.BoundEntryInfo;
            DocumentExporter docExporter = new DocumentExporter();
//            String exportPath = System.IO.Path.Combine(exportFolder,GetTokenValue("ForEachEntry_CurrentEntry_ID") + "-" + GetTokenValue("ForEachEntry_CurrentEntry_Name") + "." + ".tif");
            String exportPath = System.IO.Path.Combine(exportFolder, doc.Name + ".tif");
            docExporter.PageFormat = DocumentPageFormat.Tiff;
            docExporter.ExportPages(doc, doc.AllPages, exportPath);
        }
    }
}

We are looking into sFTP transfer now so onto another problem. Thank you all for your assistance.

Hi Amir,

I am looking to achieve something similar. A script to export documents to a Windows folder.

Would you mind sharing the tokens that you used in the "Assign Token Values"

Thanks in advance

Jonathan

You could achieve the same outcome with ease using the Workflow Activity Bundle. There is a File Export to Windows activity included in the bundle, plus many other useful activities.

More info here:
https://marketplace.laserfiche.com/details/210806/Workflow-Activity-Bundle

Downloadable here:

https://licensing.nostello.com/Home/WcaInfo