asked on

SSIS Manifest Deployment fails

Hi,

I had a working SSIS package deployment and suddently it's not working. I'm running SSIS as administrator when I build the SSIS package and get the error below when I run it from my MS Explorer window (double click).

As a test I created a new SSIS package with 1 data flow task; built it and tried to deploy from the manifest. This too failed with the error below.

TITLE: Package Installation Wizard
------------------------------
You need to specify the full path to a SSIS deployment manifest file.

Thanks for any help you can lend me.

Todd

Todd_Fields

ASKER

Other interesting information. When I changed the deployment folder to my C: drive and not a network drive, the manifest deployment works. The IT team says that there has been no permissions changes within the network directory structure.

Todd_Fields

ASKER

For lack of an option, I'm leaving the manifest deployment and going to DTSUTIL:

echo on

DTUtil /FILE "I:\_Finance\FinPlan\DW\Source Code\ODS ETL\D2 Operations\D2 Operations\bin\Deployment\D2 Ops Data Load.dtsx" /DestServer MAY /COPY SQL;"D2 Ops Data Load"

pause

Let me know if you think there is a downside to doing this.

Thanks,
Todd

Ved Prakash Agrawal

Can you rebuild the SSIS package and create menifest file again and tried if this working fine.

Let me know if the error are same.

Todd_Fields

ASKER

I tried a new package called DW TEST with a simple control flow. This generated a Manifest file and still get the error message.

I've run BIDS as Administrator and without and get the same error.

Todd_Fields

ASKER

Here is my PATH setting:

PATH=C:\Program Files (x86)\Common Files\Fujitsu\COBOL;C:\Windows\SYSTEM32
C:\Windows;C:\Windows\SYSTEM32\WBEM;C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0\;
C:\PROGRA~2\COMMON~1\FUJITSU\COBOL;C:\Program Files (x86)\Common Files\Macola Shared;
c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;
c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;
c:\Program Files\Microsoft SQL Server\100\Tools\Binn\;
c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;
c:\Program Files\Business Objects\BusinessObjects Enterprise 12.0\win32_x86;
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\

Todd_Fields

ASKER

I gather that using the import option from within Management Studio would allow me to get around this?

Todd

ASKER CERTIFIED SOLUTION

Todd_Fields

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial