BizTalk 2013 R2 and EDI correlations sets.
"Failed to initialize the correlation property name"
More detail:
Inner exception: Failed to initialize the correlation property name: ISA06 namespace: http://schemas.microsoft.com/Edi/PropertySchema from message: MessageFinal271V1.
The following correlation failed:
EDI.ST01, EDI.ISA06, EDI.ISA08
This correlation set succeeded.
EDI.ST01, EDIOverride.ISA06, EDIOverride.ISA08
I was doing this is a BizTalk Expression:
MessageFinal277V1(EdiOverride.ISA06) = MessageIn276V1(EDI.ISA08);
MessageFinal277V1(EdiOverride.ISA08) = MessageIn276V1(EDI.ISA06);
This solved the problem.
Thursday, June 11, 2015
Friday, March 20, 2015
The external credentials in the SSO database are more recent.
I got the following error when adding Trading Partner information in the BizTalk console.
Software I was using:
BizTalk 2013 R2
SQL 2014
SSO AUDIT
Function: SetConfigInfo
Tracking ID: 7e95dcb7-088f-4b8a-aa6a-57a3141132f0
Client Computer:local (mmc.exe:6916)
Client User:
Application Name: {6d186731-31d0-45d6-a773-7a7f9f516138}
Error Code: 0xC0002A40, The external credentials in the SSO database are more recent.
Or
SSO AUDIT
Function: GetConfigInfo ({5DDE9C84-BF89-47FF-8F19-4862FE3F0FA8})
Tracking ID: 51cb5a98-a60a-4481-9631-c47f6d6ea68f
Client Computer:local (BTSNTSvc.exe:14568)
Client User: BiztalkDev
Application Name: {56B82475-ED73-456B-9F68-1F4599F11E01}
Error Code: 0x80090005, Bad Data.
Local server name removed.
replacing the stored procedure in the SSO database ([dbo].[ssox_spStoreXp2]) seem to solve this problem. I got this SQL stored procedure from MS. See download:
Download:
Software I was using:
BizTalk 2013 R2
SQL 2014
SSO AUDIT
Function: SetConfigInfo
Tracking ID: 7e95dcb7-088f-4b8a-aa6a-57a3141132f0
Client Computer:
Client User:
Application Name: {6d186731-31d0-45d6-a773-7a7f9f516138}
Error Code: 0xC0002A40, The external credentials in the SSO database are more recent.
Or
SSO AUDIT
Function: GetConfigInfo ({5DDE9C84-BF89-47FF-8F19-4862FE3F0FA8})
Tracking ID: 51cb5a98-a60a-4481-9631-c47f6d6ea68f
Client Computer:
Client User: BiztalkDev
Application Name: {56B82475-ED73-456B-9F68-1F4599F11E01}
Error Code: 0x80090005, Bad Data.
Local server name removed.
replacing the stored procedure in the SSO database ([dbo].[ssox_spStoreXp2]) seem to solve this problem. I got this SQL stored procedure from MS. See download:
Download:
https://sites.google.com/site/biztalkcsharpandsql/SSOPatch.sql?attredirects=0&d=1
Thursday, February 19, 2015
IsGeneratedAck="true" in X12 999(X12_5010_999).
This property appeared in my 999 XML from the EDISend port IsGeneratedAck="true"
I had a SOAP message that contained a EDI 270. In the orchestration when I sent it out I got a 999 that I needed to put back in the SOAP message to return to sender. This property appeared on the XML root node.
Hey some days you gotta cheat. I converted the 999 XML to a string and removed the property that was giving us grief.
the IsGeneratedAck="true" Was not in any schema I could find.
This solved the problem and the XML loaded to X12_5010_999 without an issue.
Good Coding
Kent
This property appeared in my 999 XML from the EDISend port IsGeneratedAck="true"
I had a SOAP message that contained a EDI 270. In the orchestration when I sent it out I got a 999 that I needed to put back in the SOAP message to return to sender. This property appeared on the XML root node.
<ns0:X12_999_Root IsGeneratedAck="true">
<ns0:ST>
<ST01>999</ST01>
<ST02>0065</ST02>
<ST03>005010X231A1</ST03>
</ns0:ST>
<AK1>
<>
Hey some days you gotta cheat. I converted the 999 XML to a string and removed the property that was giving us grief.
String2
= MQXMLRec.OuterXml;
String2
= String2.Replace("IsGeneratedAck=\"true\"","");
MQXMLRec3
= new System.Xml.XmlDocument();
MQXMLRec3.LoadXml(String2);
the IsGeneratedAck="true" Was not in any schema I could find.
This solved the problem and the XML loaded to X12_5010_999 without an issue.
Good Coding
Kent
Tuesday, December 30, 2014
BizTalk Pipeline Components with code projects
Examples
Rename files
Archive Files
Zip files
To download use the link below each project.
Code my be less than pretty
Recently I have been writing some BizTalk pipeline components. One I modified some other person's code. I will try to make them Zipped files that you can download.
1. KNTrename - This component will rename files. It works on send and receive locations. It has a filter to rename files that match the filter. The filter can be ignored. The project has a lot of macros and you can add your own. KNT stands for "Kent Named This".
https://sites.google.com/site/biztalkcsharpandsql/KNT.BizTalk.Pipelines.Components.Rename.zip?attredirects=0&d=1
2. SAB - This is the archiving software from codeplex, I did not write it. However I fixed the dates to include the zero in from the month and day "01" instead of "1".
https://sites.google.com/site/biztalkcsharpandsql/SAB1.zip?attredirects=0&d=1
3. Stm.ZipEncoder - this will ZIP large files - I rewrote this component to use ZipArchive in .NetFramework 4.5. It must be compiled in Visual Studio 2013, I did not try it in 2012, I know it does not work in VS 2010 because you cannot use 4.5 in 2010. On this one be sure to add the reference to WindowsBase located at "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\WindowsBase.dll"
https://sites.google.com/site/biztalkcsharpandsql/Stm.ZipEncoder.zip?attredirects=0&d=1
Documentation:
https://sites.google.com/site/biztalkcsharpandsql/KNTrenamePipelineDocumentation.docx?attredirects=0&d=1
https://sites.google.com/site/biztalkcsharpandsql/StmZipEncoder.docx?attredirects=0&d=1
I hope someone finds this useful. Let me know at val1329@gmail.com
Thursday, January 30, 2014
Shareing BizTalk Applications artifacts. Especially pipeline. When I go to redeploy I get the following error.
The DELETE statement conflicted with the REFERENCE constraint
"adm_ReceiveLocation_fk_Pipeline". The conflict occurred in database
"BizTalkMgmtDb", table "dbo.adm_ReceiveLocation", column
'ReceivePipelineId'.
The statement has been terminated."
To fix this you can delete and the associated BizTalk applications. Load the MSI and then reload the other applications. I will copy the needed artifacts , in the other application and give them a different name.
The DELETE statement conflicted with the REFERENCE constraint
"adm_ReceiveLocation_fk_Pipeline". The conflict occurred in database
"BizTalkMgmtDb", table "dbo.adm_ReceiveLocation", column
'ReceivePipelineId'.
The statement has been terminated."
To fix this you can delete and the associated BizTalk applications. Load the MSI and then reload the other applications. I will copy the needed artifacts , in the other application and give them a different name.
Subscribe to:
Posts (Atom)
