Issues with SSIS PACKAGE

  • Hi All,

    It seems a simple issue but we are not figuring out exactly what it is?

    We have two servers A and B

    B server is replicate of A server and run on one cluster mode.

    ssis package resides on Server A doing the job on Server B and our datasources are as follow as

    <!-- [if gte mso 10]> <mce:style> FILE "S:\Databse1\SSIS\XYZDataMArt\FullLoad.dtsx" /CONNECTION Helios;

    "\"Data Source=A;Initial Catalog=DATABASE1;Provider=123;Integrated Security=SSPI;Auto Translate=False;\"" /

    CONNECTION "localhost.ConfigDB";"\"Data Source=A;Initial Catalog=ConfigDB;Provider=123;Integrated Security=SSPI;Auto Translate=False;\"" /CONNECTION Staging;"\"Data Source=B\Reporting;Initial Catalog=DATABASE2;Provider=123;Integrated Security=SSPI;Auto Translate=False;\"" /CONNECTION Trans;"\"Data Source=B\Reporting;Initial Catalog=DATABASE3;Provider=123;Integrated Security=SSPI;Auto Translate=False;\"" /CHECKPOINTING OFF /REPORTING E

    and the Job was scheduled than it runs for 10 mins and throws an error:

    <!-- [if gte mso 10]> <mce:style>

    Executed as user: internal\XYZ. ...0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 09:48:51 Error: 2010-11-11 09:49:34.20 Code: 0xC0202009 Source: XYZ Connection manager "localhost.ConfigDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error: 2010-11-11 09:49:55.30 Code: 0xC0202009 Source: XYZ Connection manager "localhost.ConfigDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error: 2010-11-11 09:50:37.41 Code: 0xC0202009 Source: XYZ Connection manager "localhost.ConfigDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ". End Error Error: 2010-11-11 09:50:58.51 Code: 0xC0202009 Source: FullLoad Connection manager "localhost.ConfigDB" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005... The package execution fa... The step failed.

    Thanks,

    KKK

  • This error is the key component:

    "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online."

    The account replication is running under apparently can't see the other server. I'd try logging directly into the box under the replication account and see what visibility it has to the other node.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Thanks for reply!!!

    I checked everything it has the same permissions(dbo.) exactly what server A and B.

    Thanks,

    kumar

  • Craig is correct in that this is a network connection/visibility error.

    However I'm not clear. You say two servers, and also mention a cluster. Are these both in a cluster? Are there multiple instances? Is this from a cluster to a non-clustered instance? It's not really clear what your setup is.

  • I mean both server A and B are in Cluster Node.

    Thanks,

    kumar

  • kkishore1010 (11/11/2010)


    I mean both server A and B are in Cluster Node.

    Thanks,

    kumar

    Whoa, it sounds like you are running a two node cluster and Server A is the primary and Server B is the secondary. In that case server B will NEVER be available when server A is running. Please explain your setup in a bit more detail. Are these machines in the same cluster? Are you running more than one SQL server on each node?

    CEWII

  • You really need to learn some terminology as you'll get confused, confuse us, and possibly make a big mistake.

    A cluster is 2 or more servers combined with shared storage that can act as one instance through a virtual instance.

    Each server that is a part of the cluster is a node.

    You should have zero need to replicate between nodes as the storage is shared, so there is no data movement. You could potentially have an active /active cluster, where each side has separate instances that are live and responding to requests, but that would not be replication between the nodes, that is between named instances.

    Please provide in more detail exactly the setup and what you want to accomplish. It should take more than a few sentences to describe this.

  • kkishore1010 (11/11/2010)


    I mean both server A and B are in Cluster Node.

    Thanks,

    kumar

    Yeeps. I missed that. I blame a lack of coffee. Elliot and Steve are correct (as usual) :). You shouldn't need to replicate between nodes unless you're replicating between different instances in the same active/active cluster.

    I'll bow out to their experience, I haven't done much work with active/active. Though I'll be happily watching along. 🙂


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

  • Thanks everyone!!!

    I mean you people understand what i am talking, I am purely into development team i dont much idea with DBA things.

    We are running these packages across the main server. Please let me know if you have the answer or if you ever come across this scenario.

    Thanks,

    kumar

  • I think we have a bit of a language barrier here, but we don't understand what you mean. "Running packages across a server" doesn't mean anything to us. You need to explain in more detail what is happening, or what you want to happen.

  • Package is resides in file system and trying to excute the ssis package that have connections string as i indicate on first post of this forum.

  • :w00t::w00t::w00t:

  • The first post if very unclear about what connections are being made to what.

    You are trying to be too brief in asking questions and explaining your setup. We cannot, and likely will not, help if you cannot provide more details in a clear manner.

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply