Thursday, May 01, 2014

NS$BAMAlert causing unhandled exception FileNotFoundException in a new BizTalk installation

Working thorough the creation on new BizTalk 2010 dev virtual

On start-up of the virtual machine, I was getting a prompt to start a new instance of Visual Studio to debug an unhandled FileNotFoundException from nsservice.exe.

System event log shows a couple of errors relating to NS$BAMAlerts failing to start

Opened up the SQL Server 2005 Notification Services Command Prompt and ran ...
    nscontrol listversions
which shows the instance is BAMAlerts and version is 9.0.242

So then ran ...
    nscontrol status -name bamalerts
which shows NS$bamalerts (VIRTUAL) service is not running

Then see if repair helps ...
    nscontrol repair -name bamalerts -database bamalertsnsmain -schema dbo
but get error ...
The type initializer for 'Microsoft.SqlServer.NotificationServices.Common.DatabaseObject' threw an exception.

Is this another issue with the problem with SMO being updated by the SQL 2008 R2 Reporting Services SharePoint 2010 Add-in?

So uninstalled the add-in, reinstalled the SQLServer2005_XMO_x64.msi, and eureka, the NS$BAMAlerts service started up OK  ... once I'd given the right SQL Server login permissions to the account I'd set-up for running the various services

0 Comments:

Post a Comment

<< Home