bm.exe deployment common errors and resolutions

Admin uses BAM Manager command line utility bm.exe to manage the dynamic SQL and OLAP tracking infrastructure.  bm.exe does many things for you during the deployment of a Xml or XLS file -- creating SQL tables, indexes, triggers, views, stored procs, OLAP cubes, DTS packages, SQL and OLAP security roles etc.  I compiled some of the common errors into this thread.  Let us know if you encountered other errors and need help.  We'll try to resolve that for you.

1. Many "fnGetString" or "Unable to get resource string" popup error dialogs or "Old Format or Invalid Type Library" error in the command line output.
Cause & Resolution: This is a known issue and has been addressed in BizTalk Online Documentation . To work around this problem, you can either install the Office Multilingual User Interface (MUI) pack which can be found on or change your locale to US-EN just for the duration of the deployment.

2. "Unable to connect to the registry on the server <servername>, or you are not a member of the OLAP Administrators group on this server."
Cause & Resolution: first, make sure you have SQL2000 SP4 installed on your Analysis Server. Second, you need to have the admin priviledge to deploy OLAP cubes to your Analysis Server.  Check out this KB article to make sure you have all the necessary permissions.

3. "Queryinterface for interface DTS.CustomTask failed".
Cause & Resolution: You're missing either SQL SP3 or SQL client tools or both.  Install both should make this error go away.

4. "Error compiling hidden module: Utility".
Cause & Resolution: You're missing some dependency files.  Make sure your files meet the following minimum version requirement.  The requirement is also documented at BizTalk Admin Guide.

Excel.exe  10.0.4524.0
stdole2.tlb  3.50.5014.0
mso.dll  10.0.4219.0
fm20.dll 2.1.7017.1
msado15.dll  2.71.9030.0
msxml4.dll  4.0.9406.0 (SP1)

Some user reported they have multiple versions of ADO on their machines and don't know which one is actually being referenced by Bam.xls.  In that case, close bam.xls, go to the directory and run Regsvr32 msado15.dll,  then reopen Bam.xls.

5. "Invalid object name 'dbo.bam_<...>_ActiveAliasView' "

This is a known issue.  It's due to the naming confliction among Alias, Duration, measures, dimensions or dimension levels.  Check your view, make sure all Alias, Duration, Dimension, dimension levels and Measures names are unique.  In BizTalk 2006, bm.exe will spit out more descriptive error messages.

Comments (13)
  1. PBR says:

    Thanks for the information…nice to see someone concentrating on this part of BizTalk Server…

  2. Invalid object name ‘dbo.bam_ManagerView_ViewLoanProcess_ActiveAliasView’.

    Can’t figure out what the problem is and couldn’t find any useful help/info.



  3. Chun says:

    Hi Saravana,

    Thanks for raising the issue. I updated my original post w/ error #5. Let me know if you have additional questions.



  4. Hi Chun ,
    <br>I’ve got a very strange error : Syntax error expecting ‘,’ . : HIDDEN something like this. What I did to solve this is the run the repair option in Add Remove Programs of Microsoft Office 2003 :)).
    <br>Cheers ,

  5. Patrick says:

    Hi Chun,

    unfortunately I can’t get BAM to run.

    I did a lot and I can deploy all staff. I get the *_LiveData.xls-File but whenever I open it it fails with:

    Some of the Pivottables could not be actual because the connection to the BAM- or OLAP-Databases con not be opened.

    Do you have any idea, what is missing here?

    My Configuration is BTS 2004 in german, AS with SP4 and I also installed the KB 831950 for SQL Server.

    Thanks a lot and keep on blogging!

    Best reagrds


  6. chunyu says:

    Patrick, first make sure you can connect to the SQL and Olap servers specified in the configuration Xml.  second, try to pump in some data either via the orchestration or manually.  Due to pivot table limitation, live data BAM xls file can’t connect to blank table.

    Hope this helps.

  7. Patrick says:

    Hi Chun,

    thanks for your help and for the good tip with the "empty tables"…

    Now, there is a data format question for a duration. In the Duration-Object you have a begin and an end with each DateTime-Fields. Next step ist than to get the aggregation-types Max, Min, Average. In our Business Case we get as example 0,001227083 as AverageDuration.


    Now the question: Is there a clear definition of the datatype and how could we transform it so seconds or milli seconds?


    Thanks again and best regards


  8. chunyu says:

    Patrick, for each duration, bm.exe creates two datatime fields (one for begin, the other for end point) in the underlining sql table. and in the public sql view, which is exposed to users, we create a float datatype that simply calcualte the time diff and always convert that to a fix time unit (it’s either day or second, i couldn’t remember on top of my head since i wrote that code more than 2 years ago).  

    For the sake of consistency, we made conscious decision to use a fix time unit for all durations. the other option is to always convert to user specified time unit (day, hour etc.) The drawback of that is user would have no clue what the numeric value for the duration stands for when she look at sql view w/o the xml file by her side.

    after understanding this, you should be able to convert the duration to whatever unit you choose in your own app that queries the BAM view.

  9. Failed to deploy BAM says:

    I have sql server named XYZSQLSVR that contains BAMArchive, BAMPrimaryImport databases. I also have sql analysis server named XYZ that contains BAMAnalysis, BizTalkAnalysisDb databases. These two are on the same machine (computer) named XYZ thats running windows XP service pack 2. I am getting the following error:



    Failed to deploy BAM start schema database

    sql server does not exist or access denied

    Please help me. Appreciated.

  10. chunyu says:

    You may have forgotten to specify the star-schema database. Check your BAMConfiguration.xml to see whether BAMStarSchema entry is missing.

Comments are closed.

Skip to main content