Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Connection Failed when running bulkops

I'm getting a connection failed when running my first SF_BulkOps operation

--- Starting SF_BulkOps for Account Load
18:15:47: Run the DBAmp.exe program.
18:15:47: DBAmp Bulk Operations. V2.20.6 (c) Copyright 2006-2015 forceAmp.com LLC
18:15:47: Upserting Salesforce using Account (Load / LG-CRC) .
18:16:03: Error: Unable to open SQL Server Source with SQLNCLI.
18:16:03: Connection string is SERVER=Load;DATABASE=LG-CRC;Trusted_Connection=Yes;Packet Size=4096
Source: Microsoft SQL Server Native Client 10.0
Description: Login timeout expired
Source: Microsoft SQL Server Native Client 10.0
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.
Source: Microsoft SQL Server Native Client 10.0
Description: Named Pipes Provider: Could not open a connection to SQL Server [53].
Source: Microsoft SQL Server Native Client 10.0
Description: Invalid connection string attribute
18:16:03: Error: DBAmp.exe was unsuccessful.
18:16:03: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe upsert Account Load "LG-CRC" "SalesForce Backups" "SALESFORCE" "CRC_Cust_Numb__c" " "
--- Ending SF_BulkOps. Operation FAILED.
Msg 50000, Level 16, State 1, Procedure SF_BulkOps, Line 143
SF_BulkOps Error: 18:15:47: DBAmp Bulk Operations. V2.20.6 (c) Copyright 2006-2015 forceAmp.com LLC18:15:47: Upserting Salesforce using Account (Load / LG-CRC) .18:16:03: Error: Unable to open SQL Server Source with SQLNCLI.18:16:03: Connection string is SERVER=Load;DATABASE=LG-CRC;Trusted_Connection=Yes;Packet Size=4096Source: Microsoft SQL Server Native Client 10.0Description: Login timeout expiredSource: Microsoft SQL Server Native Client 10.0Description: 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.Source: Microsoft SQL Server Native Client 10.0Description: Named Pipes Provider: Could not open a connection to SQL Server [53]. Source: Microsoft SQL Server Native Client 10.0Description: Invalid connection string attribute

Not sure which side is having connection issues or how to fix it at the moment.
1 person has
this question
+1
Reply
  • Your SQL instance appears to be configured to not accept the client connection:

    "Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. "

    Ask you SQL dba to configure to accept remote connections over named pipes.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Any other advice? I have named pipes enable, firewall port 1433 is open and tcp is also enable. I'm not sure what I am missing.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Can you post the messages from the latest run ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • I'm pretty much getting the same error message as before.

    --- Starting SF_BulkOps for Account Load
    11:21:26: Run the DBAmp.exe program.
    11:21:26: DBAmp Bulk Operations. V2.20.6 (c) Copyright 2006-2015 forceAmp.com LLC
    11:21:26: Upserting Salesforce using Account (Load / LG-CRC) .
    11:21:43: Error: Unable to open SQL Server Source with SQLNCLI.
    11:21:43: Connection string is SERVER=Load;DATABASE=LG-CRC;Trusted_Connection=Yes;Packet Size=4096
    Source: Microsoft SQL Server Native Client 10.0
    Description: Login timeout expired
    Source: Microsoft SQL Server Native Client 10.0
    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.
    Source: Microsoft SQL Server Native Client 10.0
    Description: Named Pipes Provider: Could not open a connection to SQL Server [53].
    Source: Microsoft SQL Server Native Client 10.0
    Description: Invalid connection string attribute
    11:21:43: Error: DBAmp.exe was unsuccessful.
    11:21:43: Error: Command string is C:\"Program Files"\DBAmp\DBAmp.exe upsert Account Load "LG-CRC" "SalesForce Backups" "SALESFORCE" "CRC_Cust_Numb__c" " "
    --- Ending SF_BulkOps. Operation FAILED.
    Msg 50000, Level 16, State 1, Procedure SF_BulkOps, Line 143
    SF_BulkOps Error: 11:21:26: DBAmp Bulk Operations. V2.20.6 (c) Copyright 2006-2015 forceAmp.com LLC11:21:26: Upserting Salesforce using Account (Load / LG-CRC) .11:21:43: Error: Unable to open SQL Server Source with SQLNCLI.11:21:43: Connection string is SERVER=Load;DATABASE=LG-CRC;Trusted_Connection=Yes;Packet Size=4096Source: Microsoft SQL Server Native Client 10.0Description: Login timeout expiredSource: Microsoft SQL Server Native Client 10.0Description: 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.Source: Microsoft SQL Server Native Client 10.0Description: Named Pipes Provider: Could not open a connection to SQL Server [53]. Source: Microsoft SQL Server Native Client 10.0Description: Invalid connection string attribute
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Hi Matt Jakachira,

    Did you get a resolution to this issue? I am having a similar issue so was interested in what steps you took to solve.

    Kind regards

    Dan
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Is the name of your SQL Server instance "Load" ?

    SQL Server is saying that it cannot find a sql instance with that name.

    Did you change the network name of this server to be different than the SQL Instance name ? Can you see if Select @@SERVERNAME returns a different value than SERVERPROPERTY('SERVERNAME') ?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated

  • Thanks Bill,

    @@SERVERNAME and SERVERPROPERTY

    I should clarify that my problem was only related to the part of the error message:

    Msg 50000, Level 16, State 1, Procedure SF_BulkOps, Line 143
    SF_BulkOps Error

    We resolved by containing a TRY and CATCH section around our upsert operation.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated