Forum Replies Created
-
Posts
-
Thank you.
If we will work with X12 270/271 file, then what kinds os pipeline we will use.
We have write any custom pipeline for this or we can use our flat file disassember for this.Can we receive X12 270 file directly from HIPPA Accelerator, we we will write any custom Adapter.
Please let me know as soon as possible.
Thanks,
Anand kumarBTW I have tired adding <xs:whiteSpace value="preserve"/> annotation but it doesn't work. Seems BizTalk just ignores it.
Naveen,
If you mark "Enable routing for failed messages"
in your send port properties and a message occasionally failed to
deliver, it will not get suspended. Instead, BTS will create a
cloned message, add failure-specific properties and try to publish this
message. If publishing succeeds, BTS discard the original message.So,
if your error handler subscribe this kind of messages and send them to
another port or wherever you will never have suspended messages for
that particular reason.P.S. To enable routing for failed
messages use Administration console, not Visual Studio. And be sure to
subscribe error messages.Nick
what do you mean by push value? what value are u talking about here..? Are u using the smtp send adpater to send the email? I came across this php listing while trying to answer your q coz it is very interesting. .net framework also has libraries for smtp so may be you can use something like this. http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/473810
http://geekswithblogs.net/sureshg/archive/2006/02/14/69456.aspx
http://support.microsoft.com/kb/899191/
Says this is because your invoker, Biztalk is not authenticating with the DTC participant(in this case the db server), it also contains a way to fix this as modifying the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC
Value name: AllowOnlySecureRpcCalls
Value type: REG_DWORD
Value data: 1value data to 0, although setting this value to 0 could have security implications that are beyond the scope of this blog :DD..just kidding.
I have come across this "failed to execute sql error" Microsoft should do something to provide more info in the error message. In your case it looks like some problem with the DTC which is running on the biztalk machine, are u using a transaction shape in your orchestration? Depending on the serialization(transaction serialization not object serialization) mode this error can occur even when select is used.
As you must be knowing every application has an application domain. The adapter will be loaded by the biztalk service and hence your config information should be in the config file for the biztalk service.exe file.
That would be BTSNTsvc.exe.config, in Program Files/<biztalk directory> I searched google for btsntsvc.exe.config and found a lot of blogs..here is one http://www.masteringbiztalk.com/blogs/jon/PermaLink,guid,6e4b84db-d15f-45e9-b245-08b1eb6c4def.aspx
-Mahesh
Yeah so you can use my solution, create a secondary transport which will always be available(a file folder on local can never be unavailable). Wonder why you have a requirement like that.
Thanks Nick,
But what I want to achieve is that, when a send port or an adapter fails to send a message to the destination ( due to destination unavailability) after the stipulated retries the messages gets suspended. I dont want the message to get suspended. How can this be handled using custom pipelines or custom adapters?
Naveen
Thanks Nick,
But what I wanted to achieve is that, when a send port or an adapter fails to send a message to the destination ( due to destination unavailability) after the stipulated retries the messages gets suspended. I dont want the message to get suspended. How can this be handled using custom pipelines or custom adapters?
Naveen
After I posted this yesterday, I was doing some testing, and was able to see the raw data of a suspended message in BT Admin. Still I do not know if I can see the raw data of successful messages.
mike
Thanks, do you have any idea where I can set the permissions for the IPC Port?
I know if you write a custom .NET 2.0 application you can set the permissions in the application config file, but I can't find where I can set the permissions as I don't have a config file.
Well the good news is that I managaed to get this working!! It seems the 403 message may have been misleading?
I started playing with the file – reducing it's size and then upping it until I hit problems. When it reached 48K I got "Chunked encoding upload is not supported on the HTTP/1.0 protocol."
Official Microsoft reason for the problems: You cannot disable HTTP chunked encoding in BizTalk Server 2004.
Explanation: Microsoft BizTalk Server uses chunked encoding in HTTP transport when the message size is more than 48 KB. Sometimes, you may not want to use chunked encoding. For example, you may have to disable the chunked encoding when the other end of the HTTP transport cannot receive chunked encoding.
Solution: Either stop production of files larger than 48K, or install Service Pack 2 and then make some amendments to the machine registry to enable larger files through —
After you install the fix, you must add the DisableChunkEncoding registry value to disable chunked encoding for outbound requests and responses to inbound requests. The registry value is a DWORD type. To disable chunked encoding, set the registry value to 1. By default, the registry value is 0.
For outbound requests, you must add this registry value under each registry key that matches this pattern:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{Host instance GUID}For inbound requests, you must add this registry value under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc 3.0\HttpReceive
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
As i said – good news is that it now works fine for large files!!
blems: You cannot disable HTTP chunked encoding in BizTalk Server 2004.
Explanation: Microsoft BizTalk Server uses chunked encoding in HTTP transport when the message size is more than 48 KB. Sometimes, you may not want to use chunked encoding. For example, you may have to disable the chunked encoding when the other end of the HTTP transport cannot receive chunked encoding.
Solution: Either stop production of files larger than 48K, or install Service Pack 2 and then make some amendments to the machine registry to enable larger files through —
After you install the fix, you must add the DisableChunkEncoding registry value to disable chunked encoding for outbound requests and responses to inbound requests. The registry value is a DWORD type. To disable chunked encoding, set the registry value to 1. By default, the registry value is 0.
For outbound requests, you must add this registry value under each registry key that matches this pattern:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc{Host instance GUID}For inbound requests, you must add this registry value under the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BTSSvc 3.0\HttpReceive
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
This will obviosuly switch off chunk encoding rather than increase the 48k limit.
As i said – good news is that it now works fine for large files!!
Thanks Richard,
I think my problem falls in the category of Service Oriented Scenario Architecture. By accident i run into your webcast "Biztalk Server 2006: End to End Scenarios" that gave some light to face this problem.Thanks so much guys for your help. I am still wonder why MSDN does not provide detailed info about it. But having you guru guys supporting us is very,very helpful.
-DiegoUcedo
