I still receive this message. I also dropped it in the Microsoft BizTalk ESB Toolkit forum. I got response and it pointed me to the tracing possibilities. I’m using the ESB Toolkit for a while now, but didn’t use this feature. If you really get stuck with problem solving, then this is a nice feature to use. Dwight Goins blogged about this. (note: it didn’t gave me the information I needed, but I think it still will help me in the near future).
Monthly Archives: October 2009
Presentation about Healthcare and BizTalk Accelerator for HL7
Last week I gave a presentation at the BTUG (NL), and I really enjoyed it. The presentation can be found here (note: it is Dutch). If you need more information or in English then please contact me.
SOA Manifesto
Last week some clever people set up the SOA Manifesto. The people involved in this are international known speakers / evangelists from different companies and are in one way or another competitors to each other when it comes to products and licenses (sales). Therefore it is good to see that there is a manifesto where the whole community can work with, but more important to create business value to our customers. I would encourage you to watch the presentation, or read the manifesto (clear and easy to understand).
Error while deploying to BAM
On my new virtual machine BizTalk Server and all features are installed, including Business Activity Monitoring. But somehow some security settings are not set correctly. To solve this problem I made the service account DBO on the BAMPrimaryImport database, that did the job.
So, what was happening. While deploying it is using some service and it is not using my own account. I receive the next message in the EventLog (MSSQLServerOLAPService):
OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object ‘bam_RegNonHL7MsgVw_ChangeToHL7Progress_RTATable’, database ‘BAMPrimaryImport’, schema ‘dbo’.; 42000.
and (BamManagementUtility):
Microsoft.BizTalk.Bam.Management.BamManagerException: The BAM deployment failed. —> Microsoft.AnalysisServices.OperationException: OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object ‘bam_RegNonHL7MsgVw_ChangeToHL7Progress_RTATable’, database ‘BAMPrimaryImport’, schema ‘dbo’.; 42000.
Server: The operation has been cancelled.at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Process(IMajorObject obj, ProcessType type, Binding source, ErrorConfiguration errorConfig, WriteBackTableCreation writebackOption, ImpactDetailCollection impact)
at Microsoft.AnalysisServices.Server.Process(IMajorObject obj, ProcessType processType, Binding source, ErrorConfiguration errorConfig, WriteBackTableCreation writebackOption, XmlaWarningCollection warnings, ImpactDetailCollection impactResult, Boolean analyzeImpactOnly)
at Microsoft.AnalysisServices.Server.SendProcess(IMajorObject obj, ProcessType processType, Binding source, ErrorConfiguration errorConfig, WriteBackTableCreation writebackOption, XmlaWarningCollection warnings, ImpactDetailCollection impactResult, Boolean analyzeImpactOnly)
at Microsoft.AnalysisServices.ProcessableMajorObject.Process(ProcessType processType, ErrorConfiguration errorConfiguration, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.ProcessableMajorObject.Process(ProcessType processType)
at Microsoft.BizTalk.Bam.Management.Olap2008Helper.CreateRtaCubes(Database db, XmlNode cubeNode)
at Microsoft.BizTalk.Bam.Management.Olap2008Helper.CreateOlapInfrastructure(Boolean realTimeOnly)
at Microsoft.BizTalk.Bam.Management.Olap2008Helper.CreateOlapInfrastructure()
at Microsoft.BizTalk.Bam.Management.ViewModule.Create(XmlDocument defXmlDoc)
at Microsoft.BizTalk.Bam.Management.WorkerModule.DispatchOperation(OperationType operation, XmlDocument defXmlDoc)
at Microsoft.BizTalk.Bam.Management.BamManager.ProcessOneBamArtifactType(BamArtifactType bamArtifact, OperationType operation)
at Microsoft.BizTalk.Bam.Management.BamManager.ManageInfrastructure(OperationType operation)
at Microsoft.BizTalk.Bam.Management.BamManager.Deploy()
— End of inner exception stack trace —
at Microsoft.BizTalk.Bam.Management.BamManager.Deploy()
at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.HandleDeployAll()
at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.DispatchCommand()
at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Run()
at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Main(String[] args)
Did I gave too much access to this service account? Or what access level should I set for the Service Account in SQL Server on the BAMPrimaryImport?
BizTalk Server 2009 Live Demo and HOLs VPC Image
Microsoft has published a VPC on its site with BizTalk Server 2009 and six hands-on labs (HOLs). The HOLs focus on integration with SharePoint Server 2007 and Windows Workflow (.Net 3.5). You can get it here. (note: a high-end laptop / system is recommended 
)
Article in Software Release Magazine (NL)
Mijn artikel over BizTalk Accelerators en met name over de HL7 Accelerator in de zorg is verschenen in de Software Release Magazine (een IT blad in Nederland). Het artikel kunt u hier vinden. Wilt u meer weten, dan kunt u natuurlijk altijd contact met me opnemen.
(ENGLISH)
My article about BizTalk Accelerators and especially about HL7 Accelerator in the Healthcare appeared in the Software Release Magazine (an IT magazine in the Netherlands). You can find the article over here. Note: it is a Dutch article. Let me know if you are interested in BizTalk Server Accelerators and HL7.
Cheers Gerben
“Body schema is missing” (2)
In my last post I blogged about this message. After fixing the input files, I still received this message. After some digging I noticed that the MessageType was empty (from ‘http://schemas.microsoft.com/BizTalk/2003/system-properties’). This field is used by the pipeline component BTAHL7 2.X Assembler. This field is not promoted because I’m using a generic Orchestration for routing HL7 messages via the ESB Itinerary to the MLLP Adapter (see earlier post about using a static port in an ESB Itinerary). In this Orchestration I’m receiving and sending System.Xml.XmlDocument for the message header, body and z-segment (MultiPart message). It is also not possible to write in this MessageType property, because it is read-only (in an Orchestration).
After the Orchestration the message is routed to a send pipeline and there I found another context property I can use: DocSpecType in ‘http://HL7Schemas.HeaderPropertySchema’:
I created a custom pipeline component for setting the MessageType property and setting this value:
This component is used as early as possible:
By creating the properties I can reuse this component in the future.
"Body schema is missing"
When you are working with HL7 schemas and you receive this message, then you should have a look at your incoming message. Probably it doesn’t match your Xsd. In my case it had to do with elements which don’t match the enumeration defined in the tablevalues_25.xsd (my input elements were empty). The BTAHL7 2.X Assembler is using the schemas for creating the Xml file, but also for validating. It really has nothing to do with your schema if it is deployed or not (in my case).
There was a failure executing the send pipeline: "BTAHL72XPipelines.BTAHL72XSendPipeline, BTAHL72XPipelines, Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "BTAHL7 2.X Assembler" Send Port: "SendPortMLLP" URI: "ip-address:port" Reason: Body schema is missing
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
