代码之家  ›  专栏  ›  技术社区  ›  Turpan

SSIS文件系统任务错误

  •  0
  • Turpan  · 技术社区  · 7 年前

    我用一个 foreach loop 容器内 File System Task . 这应该是移动和重命名多个文件。

    我使用了源和目标的几个变量;和文件名。似乎变量定义得很好。都指向一个V型驱动器。

    尝试运行包时,会出现错误:

    “[文件系统任务]错误:出现以下错误消息:“找不到文件”C:\Program Files(x86)\Microsoft Visual Studio 11.0\Common7\IDE\destination\u Filename。PDF名称。pdf'。"

    有人能帮忙吗?

    2 回复  |  直到 7 年前
        1
  •  0
  •   Prabhat G    7 年前

    该错误表示未对表达式求值。最好的调试方法是,在for-each循环中,放置一个 Script task (C#),传递变量并打印。要打印的脚本:

    public void Main()
    {
     string strMessage = Dts.Variables["User::test"].Value.ToString();
     MessageBox.Show(strMessage);
    
     Dts.TaskResult = (int)ScriptResults.Success;
    }
    

        2
  •  0
  •   Turpan    7 年前

    脚本任务:

        #region Help:  Introduction to the script task
    /* The Script Task allows you to perform virtually any operation that can be accomplished in
     * a .Net application within the context of an Integration Services control flow. 
     * 
     * Expand the other regions which have "Help" prefixes for examples of specific ways to use
     * Integration Services features within this script task. */
    #endregion
    
    
    #region Namespaces
    using System;
    using System.Data;
    using Microsoft.SqlServer.Dts.Runtime;
    using System.Windows.Forms;
    #endregion
    
    namespace ST_e5bcf69902754e9cb85594ea888a4d08
    {
        /// <summary>
        /// ScriptMain is the entry point class of the script.  Do not change the name, attributes,
        /// or parent of this class.
        /// </summary>
        [Microsoft.SqlServer.Dts.Tasks.ScriptTask.SSISScriptTaskEntryPointAttribute]
        public partial class ScriptMain : Microsoft.SqlServer.Dts.Tasks.ScriptTask.VSTARTScriptObjectModelBase
        {
            #region Help:  Using Integration Services variables and parameters in a script
            /* To use a variable in this script, first ensure that the variable has been added to 
             * either the list contained in the ReadOnlyVariables property or the list contained in 
             * the ReadWriteVariables property of this script task, according to whether or not your
             * code needs to write to the variable.  To add the variable, save this script, close this instance of
             * Visual Studio, and update the ReadOnlyVariables and 
             * ReadWriteVariables properties in the Script Transformation Editor window.
             * To use a parameter in this script, follow the same steps. Parameters are always read-only.
             * 
             * Example of reading from a variable:
             *  DateTime startTime = (DateTime) Dts.Variables["System::StartTime"].Value;
             * 
             * Example of writing to a variable:
             *  Dts.Variables["User::myStringVariable"].Value = "new value";
             * 
             * Example of reading from a package parameter:
             *  int batchId = (int) Dts.Variables["$Package::batchId"].Value;
             *  
             * Example of reading from a project parameter:
             *  int batchId = (int) Dts.Variables["$Project::batchId"].Value;
             * 
             * Example of reading from a sensitive project parameter:
             *  int batchId = (int) Dts.Variables["$Project::batchId"].GetSensitiveValue();
             * */
    
            #endregion
    
            #region Help:  Firing Integration Services events from a script
            /* This script task can fire events for logging purposes.
             * 
             * Example of firing an error event:
             *  Dts.Events.FireError(18, "Process Values", "Bad value", "", 0);
             * 
             * Example of firing an information event:
             *  Dts.Events.FireInformation(3, "Process Values", "Processing has started", "", 0, ref fireAgain)
             * 
             * Example of firing a warning event:
             *  Dts.Events.FireWarning(14, "Process Values", "No values received for input", "", 0);
             * */
            #endregion
    
            #region Help:  Using Integration Services connection managers in a script
            /* Some types of connection managers can be used in this script task.  See the topic 
             * "Working with Connection Managers Programatically" for details.
             * 
             * Example of using an ADO.Net connection manager:
             *  object rawConnection = Dts.Connections["Sales DB"].AcquireConnection(Dts.Transaction);
             *  SqlConnection myADONETConnection = (SqlConnection)rawConnection;
             *  //Use the connection in some code here, then release the connection
             *  Dts.Connections["Sales DB"].ReleaseConnection(rawConnection);
             *
             * Example of using a File connection manager
             *  object rawConnection = Dts.Connections["Prices.zip"].AcquireConnection(Dts.Transaction);
             *  string filePath = (string)rawConnection;
             *  //Use the connection in some code here, then release the connection
             *  Dts.Connections["Prices.zip"].ReleaseConnection(rawConnection);
             * */
            #endregion
    
    
            /// <summary>
            /// This method is called when this script task executes in the control flow.
            /// Before returning from this method, set the value of Dts.TaskResult to indicate success or failure.
            /// To open Help, press F1.
            /// </summary>
            public void Main()
            {
                string strMessage = Dts.Variables["User::test"].Value.ToString();
                MessageBox.Show(strMessage);
    
                Dts.TaskResult = (int)ScriptResults.Success;
            }
    
            #region ScriptResults declaration
            /// <summary>
            /// This enum provides a convenient shorthand within the scope of this class for setting the
            /// result of the script.
            /// 
            /// This code was generated automatically.
            /// </summary>
            enum ScriptResults
            {
                Success = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Success,
                Failure = Microsoft.SqlServer.Dts.Runtime.DTSExecResult.Failure
            };
            #endregion
    
        }
    }