error 0x80131500

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › error 0x80131500

Viewing 1 reply thread
  • Author
    Posts
    • February 1, 2006 at 9:06 AM #12775
      community-content

        hi

        we are using a orchestration which contains many sql adapters we connect to diff databses using these adapters one db is situated on same machine as biztalk and other is connected through a vpn on a remote server.

        we have prepared a binding file for same when we deploy the application the ports are created but we get a binding exception as follows

        Failed updating binding information. BindingException: Could not validate TransportTypeData or Address properties for Primary Transport of Send Port ‘IdeaToDms_19UpdateIdea’. Exception from HRESULT: 0x80131500

      • February 2, 2006 at 4:55 AM #12776
        community-content

          hi

          i had not used integrated security it was set as false in connectionstring

          and i used actual password and not the ***

          and i executed stored procedure in sql analyzer with userid and password and it ran well

          should i use sp1 as time to connect to remote db has been extended in sp1

          • February 2, 2006 at 4:57 AM #12777
            community-content

              i looked for error code on net and found that error comes when time to execute sql statement is more

              • February 1, 2006 at 5:45 PM #12778
                community-content

                  Failed updating binding information. BindingException: Could not validate TransportTypeData or Address properties for Primary Transport of Send Port ‘IdeaToDms_19UpdateIdea’. Exception from HRESULT: 0x80131500

                  I just put added this to my blog (http://nealwalters.blogspot.com)

                  Here are some steps:

                  1) If you are using client-network utility – make sure that it is set up properly on the target machine.

                  2) If you are using non-integrated security, there will be a password=******** in the binding file, you will need to change this to the real password for the target system.

                  3) It’s often a security or logon issue; have your security people or database admins added the userid to the target system, had it been granted the necessary security to actually run the stored proc. My suggestion is to logon SQL Query Analyzer with the desired userid/password, and try to run the stored proc or SQL command. Once you get error eliminated here, then redeploy.

                  Neal Walters
                  http://Biztalk-Training.com – 3 CD/ROM Videos

          • Author
            Posts
          Viewing 1 reply thread
          • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.