Home/ Questions/Q 8919305
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T05:59:08+00:00

I have an SSIS package which gathers data from Oracle and puts it into

  • 0

I have an SSIS package which gathers data from Oracle and puts it into SQL. This package runs fine on the current server. However when I run the same package, which was exported to a file system, on another server it fails with the error ORA-1005 – null password given; logon denied.

I can connect to Oracle from the server and also to SQL. The weird thing is, if I navigate to the new server from the old server using windows explorer and run the package it works fine. It is only failing when executed from the new server, works fine when executed from the old server even though the file is on the new server.

Please can someone help as this is driving me nuts!

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    So from our little chat I’m guessing that SSIS packages lossing passwords for connections in the servers. You need to use config file for the connection string properties (with username and password included) and it will work probably.

    In your SSIS package

    1. SSIS->Package Configurations mark enable
    2. Add->Next-> Specify conf settings directly choose your location and name of config file->Save
    3. In tab Objects find your connection and expand->Properties_>Mark “ConnectionString”, “Name”,”Password”
    4. Next Next

    Sometimes configuration file too dont save password. So after creating configuration file go and open it with notepad. When you enter your pass and save, this should be done when package is closed.

    Example of config file(don’t copy create your own):

    <?xml version="1.0"?><DTSConfiguration><DTSConfigurationHeading>
<DTSConfigurationFileInfo GeneratedBy="dasdsa\dasdsa" 
GeneratedFromPackageName="Package" 
GeneratedFromPackageID="{53B24B50-B43F-4D51-AD15-44FC92896BCA}"
 GeneratedDate="27.11.2012 19:07:35"/></DTSConfigurationHeading>
<Configuration ConfiguredType="Property" 
Path="\Package.Connections[Oracle].Properties[Name]" ValueType="String">
<ConfiguredValue>YourName
</ConfiguredValue></Configuration><Configuration 
ConfiguredType="Property" Path="\Package.Connections
[Oracle].Properties[Password]"
 ValueType="String"><ConfiguredValue>**ENTERHEREPASS**</ConfiguredValue>
</Configuration></DTSConfiguration>

    2. Part. Why Agent Job fail executing package
    When transferring from one server to another
    There could be several problems:

    1. Need to set up right executing mode 64 or 32 bit http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
    2. Security set on package “ProtectionLevel” can do bad things
    3. Sql server Agent Job is running under the Owner rights which have no rights.
    • 0