Business Process Integration » BAM

Error while deploying to BAM

Gerben van Ophuizen — Wed, 28 Oct 2009 12:16:07 +0000

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?

Error deploying definition to BAM

Gerben van Ophuizen — Mon, 23 Mar 2009 06:00:00 +0000

I created a BAM Activity Definition in Excel 2007: SomeView.xml. This file can be deployed with BM like:

BM deploy-all -definitionfile:SomeView.xml

In the DOS-box I received the output:

Deploying Activity… Done.
Deploying View… ERROR: The BAM deployment failed.
OLE DB error: OLE DB or ODBC error: Cannot open database “BAMPrimaryImport" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘bam_rta_SomeView’, Name of ‘bam_rta_SomeView’.
Server: The operation has been cancelled.

On the Internet I couldn’t find this message in conjunction with the BAMPrimaryImport database. When looking in the EventLog I saw the next Informational message:

After adding this account to the BAMPrimaryImport database with the right access, it worked all fine:

Deploying Activity… Done.
Deploying View… Done.
Deploying Security… Done.

Did I missed something during installation, or is it because I used BizTalk Server 2009 Beta?

Why restrictions on BAM View- and other names?

Gerben van Ophuizen — Mon, 23 Mar 2009 06:00:00 +0000

I’m working on a demo PC for our company. In one of the scenarios I’m using BAM. I didn’t use it for a quiet long time. Also with BizTalk Server 2009 Beta BAM is still a powerful tool for generating near real-time management information.

But why am I restricted to 18 characters for the BAM View name or Measure name?

A colleague of my who is a BI specialist doesn’t recognize this with SQL Server Analysis Services. So SQL Server has not this kind of restriction.

Error installing ‘exception handling BAM tracking’ for the ESB Guidance (CTP)

Gerben van Ophuizen — Mon, 23 Mar 2009 06:00:00 +0000

I posted recently a problem with BAM: “Error deploying definition to BAM”. With the ESB Guidance 2.0 (CTP version from January) I received the same message, but then for the database BAMStarSchema. After adding the SQL Service account to the right security group I received another error:

Using ‘BAMPrimaryImport’ BAM Primary Import database on server ‘WIN2008′…

Deploying Activity… Done.
Deploying View… ERROR: The BAM deployment failed.
Server: The operation has been cancelled.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘ExcByApplication_ExcDatetime’, Name of ‘ExcByApplication_ExcDatetime’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Year’ attribute of the ‘ExcByApplication_ExcDatetime’ dimension from the ‘BAMAnalysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
The following system error occurred: Unspecified error .
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘bam_ExcByApplication’, Name of ‘bam_ExcByApplication’.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘ExcByApplication_ExcDatetime’, Name of ‘ExcByApplication_ExcDatetime’ was being processed.
… etc …

After inspecting my machine I find out that I was missing BAMAnalysis. After reconfiguring BizTalk again, it worked fine. Note: to trigger to create the BAMAnalysis was to rename it to another name, and then back to BAMAnalysis.