Microsoft BizTalk Server

(Kerrey's view with BPI Products)

Browse by Tags

Tagged Content List
  • Blog Post: BizTalk Error: Could not find stored procedure

    SYMPTOMS The SQL Adapter may fail and you may receive an error message that is similar to the following: ------------------- Error details: HRESULT='xxxxx' Description="Could not find stored procedure 'sp_xxxxx". as below: This problem may occur when there is no SP in Database or you changed...
  • Blog Post: Change IP Address on BizTalk Server

    Change IP Address of the BizTalk boxes is supported except below senarios: 1, If the server has the MSMQ adapter, in which case the server needs to be reinstalled( http://support.microsoft.com/kb/836487 ) 2, If you are using IP Addresses anywhere in your configuration instead of of server names (eg...
  • Blog Post: Business Rule常见错误

    症状:调用Rule/Policy后,无法得到结果,或处理的消息没有如期的结果 原因: 1,首先在Orchestration Designer中,检查有没有指定需要传递的参数(消息) 2,在Business Rule Composer中检查Document Type值,是否与Message的namespace匹配 3,如果Fact用到数据库,还需要检查Database binding type得值
  • Blog Post: BizTalk Error: HIS Adapter Error

    When you try to insert/update data into DB2 through HIS Adapters, an error encountered. Error details: RTI1L01 ?BPCSUSRFV6?3 in *N not valid for operation. SQLSTATE: 55019, SQLCODE: -7008 As Below: Resolutions: 1, Check each piece of data again the schema, the problem might be that when...
  • Blog Post: BizTalk Error: Can Not Enable Receive Location

    Issue: When you refesh Application after enable the Receive Location, you find the Receive Location is still in Disable status. Resolution: Check the configuration of Host / Host Instance, you may use a restrict user account.
  • Blog Post: BizTalk Error: The published message could not be routed

    Error Message: The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration or send port has not been enlisted, or if some of the message properties necessary for subscription evaluation have not been promoted. Please use the Biztalk...
  • Blog Post: BizTalk Error: Microsoft.RuleEngine.dll Not Found

    Instead of the path "<installation Drive>:\Program Files\Microsoft BizTalk Server 2006", sometimes Microsoft.RuleEngine.dll is located "<installation Drive>:\Program Files\Common Files\Microsoft BizTalk". After that, you should check if "Rule Engine Update Service" been started correctly...
  • Blog Post: Error BEC2004: hexadecimal value 0x00, is an invalid character

    Error BEC2004: hexadecimal value 0x00, is an invalid character This error may occur when you try to validate an instance in BizTalk, especiall your incoming file is a flat file. Solution: Make sure your input file(Flat file) is saved by Unicode encoding. It's a simply way to resove this error.
  • Blog Post: Error BEC2004: Unexpected data found while looking for: '\n\r'

    Error BEC2004: Unexpected data found while looking for: '\n\r' This maybe encountered when you Validation Instance for a flat file. Solution: 1, Check your flat file(always an input file), there maybe BLANKS before 'return line', so make sure the file is a coreect one; 2, Modify your Schema...
Page 1 of 1 (9 items)