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 www.microsoft.com 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 http://support.microsoft.com/?id=231951 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.
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.