Reputation: 549

Could not find a part of the path in 'C:\' at line 0

I am stuck with an error on Script Task in SSIS package. I could found similar questions but they are different from my scenario.

Build the Script and which was failed with following error (for Error list please refer following image):

Severity Code Description Project File Line Suppression State Error Could not find a part of the path 'C:\Users\name\AppData\Local\Temp\2\Vsta\166f3f6a0a3b4d2b9bce8275652e86c5_out'.
ST_e39a74fadbb04a8088f3dcc732f67cf0 C:\Users\name\AppData\Local\Temp\2\Vsta\SSIS_ST140\VstagyjdfDg98EOThQux2q_T5A\VstaFGRuzNpZdEeMuG1swXzy5g\mscorlib 0

Error List:

I can understand this error that File not found in the path. OK. I can change path, but it shows line: 0. When I click the error I have following notification.

Message:

So, now my questions are,

where this path is exist in the project? how to resolve this error?

Note:

I am using following version VS Code.

Microsoft Visual Studio Community 2019 Version 16.9.1 VisualStudio.16.Release/16.9.1+31105.61 Microsoft .NET Framework Version 4.7.03062

File name *_out in error is changed for each time build.

Thanks,

Pugal.

Upvotes: 4

Answers (4)

Cᴏʀʏ

Reputation: 107498

A workaround was posted on the VS marketplace:

Click “Edit Script” to open the project in VS

Right click on the project in solution explorer, and click “Open Folder in File Explorer”

In the file explorer, open the csproj or vbproj file with any text editor

Find the two element, change the value to .\bin\Debug\ and .\bin\Release\ separately, or you can simply remove them

Save the csproj or vbproj and reload the project

Now you can try to rebuild the project in VS

The instructions aren't super clear but I found that simply commenting out the OutputPath nodes in the two configuration PropertyGroups did the trick.

For example:

  <PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <Optimize>false</Optimize>
    <!-- <OutputPath>.\bin\Debug\</OutputPath> -->
    <EnableUnmanagedDebugging>false</EnableUnmanagedDebugging>
    <DefineConstants>DEBUG;TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
    <DebugSymbols>false</DebugSymbols>
    <Optimize>true</Optimize>
    <!-- <OutputPath>.\bin\Release\</OutputPath> -->
    <EnableUnmanagedDebugging>false</EnableUnmanagedDebugging>
    <DefineConstants>TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
  </PropertyGroup>

Upvotes: 2

Subbu

Reputation: 2205

Update: There is now fixed in Visual Studio 2019, But the fix is to install the latest version of Visual Studio for Applications.

https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects

There is a regression in VS 2019 16.9 that will cause script task/component not work properly when editing script. VSTA team has released a new version to work around this issue. Please install latest version 3.12.1 to fix the issue, or you can keep on version 3.12 and manually download and install the latest version of VSTA 2019 here.

Old: As per below, this is broken in Visual Studio 2019 16.9

https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects

There is a regression in VS 2019 16.9 that will cause script task/component not work properly when editing script. Please do NOT upgrade to 16.9 currently. If you have already upgraded to 16.9, please rollback to 16.8 or earlier version if you are using script task/component.

So, try with the latest available 16.8.x version. https://learn.microsoft.com/en-us/visualstudio/releases/2019/history#installing-an-earlier-release

You could also vote for this item

https://developercommunity2.visualstudio.com/t/SSIS-script-task-do-not-build/1354064