Get SQL Line Number of Error (And Stored Proc Name)


is there way stored proc name , line number of error when there sql error in stored proc (when using wcf-custom adapter in sendport).  example, i'm getting below.  know stored proc sendport calling, might call many sub-stored procs. seems biztalk capture entire sql error info , display back.

neal


system.data.sqlclient.sqlexception (0x80131904): string or binary data truncated.
the statement has been terminated.

server stack trace:
   @ system.runtime.asyncresult.end[tasyncresult](iasyncresult result)
   @ system.servicemodel.channels.servicechannel.sendasyncresult.end(sendasyncresult result)
   @ system.servicemodel.channels.servicechannel.endcall(string action, object[] outs, iasyncresult result)
   @ system.servicemodel.channels.servicechannel.endrequest(iasyncresult result)

exception rethrown @ [0]:
   @ system.runtime.remoting.proxies.realproxy.handlereturnmessage(imessage reqmsg, imessage retmsg)
   @ system.runtime.remoting.proxies.realproxy.privateinvoke(messagedata& msgdata, int32 type)
   @ system.servicemodel.channels.irequestchannel.endrequest(iasyncresult result)
   @ microsoft.biztalk.adapter.wcf.runtime.wcfclient`2.requestcallback(iasyncresult result)



in sql there's no easy way of getting column information, can refer post below:

http://social.msdn.microsoft.com/forums/en/transactsql/thread/ec184168-ddd1-4df5-b2c7-c6671b602a3d

randy aldrich paulo

mcts(biztalk 2010/2006,wcf net4.0), mcpd | my blog


biztalk message archiving - sql , file
automating/silent installation of biztalk deployment framework using powershell >
sending idocs using ssis



BizTalk Server  >  BizTalk Server Adapters and Adapter Pack



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

hi , background: for our customer, having a  2 biztalk , 1 sql setup of environment. [biztalk server 2013 azure vms provisioned azure gallery, sql server 2012 azure vm ]. in current configuration, there no high availability or disaster recovery plan set. want implement dr , possibly ha configuration on these servers. i have few questions regarding same. please let me know thoughts on same. currently writing log files (log shipping files) mounted/attached drive same sql server. how move these log files across secondary site since shared storage not supported. in case of sql server crash, losing log files since reside on same server. please share options on how can move these periodically between datacenters. for hosts pop3, ftp need host clustering (which requires biztalk machines present on windows cluster traditionally), please let know how achieve in azure scenario thanks , regards, ujjwal devarapalli -ujjwal you can refer article, issue azure vm lo...
Read more

How to send non-standard Content-Type header ?

hello, my custom client developed send custom content-type header "xyz" (with out "/"). message gone in lcs 2005. after have upgrade lcs 2005 ocs 2007 r2 in test environment. custom client not able send same custom content-type in ocs 2007 r2 used possible send in lcs 2005. below cut ocs 2007 r2 accessedge log file. tl_warn(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de7 (sipstack,ccontenttypeheader::parse:contenttypeheader.cpp(118))( 00000000036249f0 ) exit - media-type syntax error in getting "/" tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de8 (sipstack,csipmessage::parseallheaders:sipmessage.cpp(6408))( 0000000003566a50 ) exit. failed while parsing header. tl_error(tf_component) [0]0f68.0bb4::11/08/2010-06:02:51.546.00000de9 (sipstack,csiprequest::validateinboundheaders:siprequest.cpp(1391))( 0000000003566a50 ) exit - failed while parsing header. returned 0xc3e93f51(sipproxy_e_invalid_content_type_header)...
Read more