Geeks With Blogs
Solution Architecture, Strategy eCommerce and Omni Channel Thought at the end of the day January 2005 Entries
MSMQT Delivered Not Consumed
You can tell I'm doing alot of documentation today. Here is another quick tip. If you get a “Delivered not consumed” message in HAT sending a message using MSMQT (I think this will be the same with MSMQC) this means that your message did not reach the MSMQ Queue for some reason. Either the Server name / Queue name is wrong or the server is not available ......

Posted On Wednesday, January 19, 2005 2:52 PM

Siebel web service returns the wrong value if an error occurs in Siebel
In BizTalk 2004 you will end up with a dehydrated orchestration if the Siebel web service would fail. The reason is that the return error type mentioned in the WSDL is not returned. Instead, and depending on the type of error, HTTP error in this case, you see something like this in the event log The adapter "SOAP" raised an error message. Details "Client found response content type of 'text/html;charset=UTF-8', but expected 'text/xml'. The request failed with the error message: -- <html><head><... ......

Posted On Wednesday, January 19, 2005 2:14 PM

Gotcha!! Integrating with Siebel Web services using Biztalk 2004 SOAP
Siebel consultants use a wizard to build Web service WSDLs from their integration objects. One thing to watch out for is the value for ElementFormDefault in the WSDL. Sometimes (Not sure why) they will generate the WSDL and will have the following line: xsd:schema xmlns:xsdLocal0="http://www... targetNamespace=http://www.... xmlns:xsd="http://www.w3.or... Which is fine but then the return value you get ......

Posted On Wednesday, January 19, 2005 2:03 PM

BizTalk 2004: The DBLookup functoid produces the wrong results under load
Ok, let's keep the blogging momentum going. Here is something to consider if you want to use the DBLook functoid in BizTalk 2004. The DBLookup functoid produces the wrong results under load. Despite installing the Rollup version, as well as Q884887. Still there seems to be an issue with the DBLookup functoid returning either empty or the wrong results under load (200+ messages). The most recent hotfix looks good (Q888309), but I don’t think it will be included in SP1. You would have to get ......

Posted On Tuesday, January 18, 2005 2:09 PM

What is in BizTalk 2004 SP1
This is what I believe is going to be included in SP1 Of BizTalk 2004, I'm sure there will be more 811250 FIX: You experience high CPU utilization and no timeout exceptionwhen using a timed scope in orchestration813845 BizTalk Server 2004 rejects reliable receipts from BizTalk Server2000 and from BizTalk Server 2002814041 BizTalk Server may fail persisting state to the database and mayend the orchestration instance821934 FIX: BizTalk Server 2004 rejects BTF receipts in CoordinatedUniversal Time (Greenwich ......

Posted On Tuesday, January 18, 2005 11:13 AM

Copyright © Tamer Shaaban | Powered by: