Answered by:
MBAM 2.5 SCCM Integration Setup - The operation failed

Question
-
I'm trying to install the SCCM Part of MBAM and get the following message.
I do the setup on the SCCM Central Site where the SSRS is Installed and running.
SCCM 2012 R2 CU4 on Windows Server 2008 R2 with SQL Server 2008 SP4.
Does the setup write any logs where more information can be found what was going wrong?
Kind regards Stefan Somogyi
- Edited by SSOMOGYI Tuesday, May 19, 2015 1:18 PM
Tuesday, May 19, 2015 1:00 PM
Answers
-
This can happen due to MBAM 2.5 incompatible with SQL Components.
MBAM 2.5 supports SQL Server 2008 R2 and above for SQL features.
- Proposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Unproposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Proposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Marked as answer by SSOMOGYI Friday, May 22, 2015 6:41 AM
Tuesday, May 19, 2015 5:57 PM
All replies
-
You can check the MBAM Setup Logs in :
Event Viewer - Application and Service Logs - Microsoft-Windows-MBAM Setup.
- Proposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:01 PM
Tuesday, May 19, 2015 3:11 PM -
Thanks for the hint to the log. I have found the following:
Unexpected Configurator error. Description: Exception thrown from feature provider. Exception: System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: The Value expression for the text box ‘textbox30’ refers to the field ‘KeyProtectorId’. Report item expressions can only refer to fields within the current dataset scope or, if inside an aggregate, the specified dataset scope. at Microsoft.ReportingServices.WebServer.ReportingService2005Impl.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings) at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, Warning[]& Warnings) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.SqlServer.ReportingServices.ReportService2005.ReportingService2005.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties) at Microsoft.Mbam.Setup.Common.CmIntegration.Implementors.CmReportingServicesManager.DeployReport(IReportingServicesProxyWrapper serviceProxy, String reportNameToPublish, XDocument reportContent, String cmFolder, String subFolder, String reportFolder) at Microsoft.Mbam.Setup.Common.CmIntegration.Implementors.CmReportingServicesManager.DeployReports(CMVersion cmVersion, String reportsFilesPath, ReportingServicesInformation reportingServicesInfo, DeployReportParameters additionalInfo, CultureInfo desiredCulture, String subfolderName) at Microsoft.Mbam.Setup.Common.CmIntegration.CMObjects.CreateCmReports() at Microsoft.Mbam.Setup.Common.ActionItem.Run() at Microsoft.Mbam.Setup.Common.ActionItemQueue.Run() at Microsoft.Mbam.Setup.Common.CmIntegration.CmIntegrationProvider.Enable(IProgress`1 progress, CancellationToken cancellationToken, CmIntegrationConfiguration configuration) at Microsoft.Mbam.Setup.Common.FeatureProviderBase`1.<>c__DisplayClass34`1.<InvokeAsync>b__33() at System.Threading.Tasks.Task`1.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mbam.Setup.Common.FeatureProviderBase`1.<InvokeAsync>d__36`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mbam.Setup.Common.FeatureProviderBase`1.<>c__DisplayClass2.<<EnableAsync>b__0>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Microsoft.Mbam.Setup.Common.FeatureProviderBase`1.<EnableAsync>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mbam.Setup.Configurator.CMUIFeatureModel.<EnableTransacted>d__4.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mbam.Setup.Configurator.BatchTaskModel.<>c__DisplayClass5.<<Commit>b__1>d__7.MoveNext()
Any Idea what was going wrong?
Kind regards Stefan Somogyi
Tuesday, May 19, 2015 3:52 PM -
This can happen due to MBAM 2.5 incompatible with SQL Components.
MBAM 2.5 supports SQL Server 2008 R2 and above for SQL features.
- Proposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Unproposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Proposed as answer by Prithwi321Microsoft employee Tuesday, May 19, 2015 6:00 PM
- Marked as answer by SSOMOGYI Friday, May 22, 2015 6:41 AM
Tuesday, May 19, 2015 5:57 PM