BizTalk 2013 CU2 + ESB : Failed to update resources in the application - biztalk

Recently upgraded to BizTalk 2013 CU2 and installed ESB.
This has had some side effects as we can no longer deploy without getting a database FK reference error.
Any one seen this before?
Here is the error when we try to deploy a new assembly to the DEV environment.
TITLE: BizTalk Server Administration
Failed to update resources in the application.
ADDITIONAL INFORMATION:
Failed to add resource(s). (mscorlib)
Change requests failed for some resources. (Microsoft.BizTalk.ApplicationDeployment.Engine)
BizTalkAssemblyResourceManager failed to complete end type change request. (Microsoft.BizTalk.ResourceManagers)
Removal of the assembly failed. Make sure that all items in the assembly you are trying to remove fulfill the following conditions:
Pipelines, maps, and schemas are not being used by Send Ports or Receive Locations in the same or referenced application(s).
Roles have no enlisted parties.
Database Error:
The DELETE statement conflicted with the REFERENCE constraint
bts_receiveport_transform_foreign_transformid. The conflict occurred
in database "BizTalkMgmtDb", table "dbo.bts_receiveport_transform",
column 'uidTransformGUID'. The DELETE statement conflicted with the
REFERENCE constraint "fk_bt_mapspec_bts_item". The conflict occurred
in database "BizTalkMgmtDb", table "dbo.bt_MapSpec", column 'itemid'.
The DELETE statement conflicted with the REFERENCE constraint
"bts_receiveport_transform_foreign_transformid". The conflict occurred
in database "BizTalkMgmtDb", table "dbo.bts_receiveport_transform",
column 'uidTransformGUID'. The statement has been terminated. The
statement has been terminated. The statement has been terminated.
(mscorlib)
I ran a SQL trace and found that this is the SP that breaks when it tries to delete from table dbo.bt_MapSpec.
exec dpl_DeleteAssembly
#Guid=N'00000000-0000-0000-0000-000000000000',#Name=N'theassemblynamegoeshere',#VersionMajor=1,#VersionMinor=0,#VersionBuild=0,#VersionRevision=0,#PublicKeyToken=N'89e32fae0caf808e',#Culture=N'neutral',#Type=N'2',#NoSchemasVerify=0

Related

Biztalk Cannot process EDIFACT file

I'm new in processing EDIFACT files. I want to process a EDIFACT file of type D:01B INTFSTA. I searched for schema in BizTalk server, created orchestration and deployed in BizTalk server. While processing the file I get the following error.
Error encountered during parsing.
Error: 1 (Miscellaneous error)
70: Cannot locate document specification because multiple schemas matched the message type "http://schemas.microsoft.com/BizTalk/EDI/EDIFACT/2006#EFACT_D01B_IFTSTA".
Error: 2 (Miscellaneous error)
71: Transaction Set or Group Control Number Mismatch
Error: 3 (Miscellaneous error)
29: Invalid count specified at interchange, group or message level
.
The sequence number of the suspended message is 1.
There is no other application using the same schema (D:01B INTFSTA).
Please help.
Most likely you have the schema deployed more than once in your BizTalk environment. In the BizTalk console, go to "All Artifacts", select "Schemas" and list alphabetically. There, search for EFACT_D01B_IFTSTA in the Root Name column. You will find that it is deployed in another application most likely.
A good practice around deploying EDI schemas btw, is to update the namespace to include the name of your trading partner. More than 1 of your trading partners may use the schema in different ways or have customizations in it. This approach lets you handle this situation.
The suggested namespace would, for example, be http://schemas.yourcompany.com/partners/yourtradingpartner
Most likely, the schema is not deployed. Check the Schemas node of the All Artifacts Application.
2&3. You test EDIFACT instance is invalid. Did you cut and paste it together? That would cause the mis-matches.
Note, it's a better practice to change the Target Namespace on the EDI schemas to something specific to the app which uses them.

ORA-14102: only one LOGGING or NOLOGGING clause may be specified

While importing an oracle schema from dump file, i am getting below error while creating tables.
ORA-14102: only one LOGGING or NOLOGGING clause may be specified.
I see the above error while creating tables from the dumpfile for several tables.
How to enable or disable LOGGING/NOLOGGING at schema level before i start import?
When performing an Oracle database export with the expdp of Oracle 11gR2 (11.2.0.1) and then importing it into the database with impdp, the following error messages appear in the import log file:
ORA-39083: Object type INDEX failed to create with error:
ORA-14102: only one LOGGING or NOLOGGING clause may be specified
This is a known Oracle 11gR2 issue. The problem is that the DBMS_METADATA.GET_DDL returns invalid syntax for an index created. So, during the index creation, both the NOLOGGING and LOGGING keywords are visible in the DDL. Download and apply Patch 8795792 from Oracle to resolve this issue.

BizTalk error Schema Not Found

I'm receiving an HL7 2.3 ORU schema. I've configured the appropriate party to use a schema namespace of "http://mycompany.ca/application/HL7/2X/2.3/1"
I've built my custom HL7 Schema, ad set the targetNamespace to "http://mycompany.ca/application/HL7/2X/2.3/1", and ensured it has a root element of "ORU_R01_23_GLO_DEF".
I've deployed the schema to biztalk by importing it, then running the msi.
I can see that my BIzTalk application has the schema in it, and I can see that the MSI installed the schema on the drive.
When I send an HL7 to my receive location, I get an error in the evenlog:
Error happened in body during parsing
Error # 1
Alternate Error Number: 301
Alternate Error Description: Schema http://mycompany.ca/application/HL7/2X/2.3/1#ORU_R01_23_GLO_DEF not found
Alternate Encoding System: HL7-BTA
From this, I can tell that the party resolution worked correctly, but can't figure out why it can not find the schema.

Update table with WCF-SQL adapter

I have created an Orchestration where I am trying to fetch all the rows from the Request table with Created status. I want to update these rows with Completed status.
I wrote a SP to fetch all the rows with Created status and I am able to get these values in my orchestration (I tried sending these values to a flat file and I am able see the values in output file.)
I wrote another SP to update the status to Completed by passing the RequestID. I added Transform control to my orchestration to map RequestID received from select SP to RequestIDparameter in update SP. I compiled and deployed this project, but at runtime I am getting the following error:
There was a failure executing the send pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLTransmit,
Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" Source: "XML assembler" Send Port:
"LogPort" URI: "C:\Data\Log\%MessageID%.xml" Reason: Root element is
missing.
I guess I doing something wrong in the mapping. But I'm not sure how to do it in the right way. I am using BizTalk 2010, VS 2010 and SQL Server 2008. I would like to know how to do the following:
How to debug BizTalk project.
How to map results for select query with update procedure.

Entity framework activates trigger to other database: error

I have a ASP.NET web application which does some changes on a table in SQL Server 2008 R2.
On this table there is a trigger that does updates on another table in another database on the same database server.
When saving the changes I'm having the following error:
- The error message: The underlying provider failed on Commit.
- InnerException: This SqlTransaction has completed; it is no longer usable.
Also allowing the database user to connect to the other database isn't working.
Somebody knows how I can make this work?
The trigger is not related to Entity Framework.
The trigger fires when changes are made to the table irrespective of where that change came from.
This is probably a rights issue, the system is attempting to make the change to the second database with the security context that was used to connect to the first database. It the change that was caused by the trigger fails, then everything in the same transaction will fail.
Since you are accessing 2 databases in a transaction, you are using MSDTC, make sure that it is started and that you have rights to it.

Resources