The below list of potential errors are found in the 2D Map after the NSM MDB has been upgraded from SQL 2008 to SQL 2012 as a result of the MDB Migration procedure not being followed correctly:
Warning: The procedure resolves the above listed errors but the changes may not be dynamic and closing/opening of 2D Map is always required for the changes to be observed. The procedure contains modification of the SQL query on the SQL 2012 machine - before proceeding further, it is recommended to take backup of the existing MDB and restore the original MDB back if the issue is not resolved
Open the SQL Management Studio on the SQL 2012 MDB machine with NSM installed and navigate as below:
if(update(severity)orupdate(status_no))
if(( 1 in(select acknowledge from deleted))and( 1 in
select acknowledge from inserted)))
begin
select 80001
raiserror 80001 'Update severity or status_no failed Since one of acknowledges is on(1). '
rollbacktransaction
return
end
raiserror 80001 'Update severity or status_no failed Since one of acknowledges is on(1). '
raiserror ('Update severity or status_no failed Since one of acknowledges is on(1). ',80001,1)
if(update(class_name)orupdate(uuid))
begin
select 80002
raiserror 80002 'Do not allow to update uuid of an object,
the transaction failed. '
rollbacktransaction
return
end
raiserror 80002 'Do not allow to update uuid of an object,
the transaction failed. '
raiserror ('Do not allow to update uuid of an object, the transaction failed. ',80002 ,2)
.
.
.
if(update(severity)orupdate(status_no))
if(( 1 in(select acknowledge from deleted))and( 1 in
select acknowledge from inserted)))
begin
select 80001
raiserror ('Update severity or status_no failed Since one of acknowledges is on(1). ',80001,1)
rollbacktransaction
return
end
(update(class_name)orupdate(uuid))
begin
select 80002
raiserror ('Do not allow to update uuid of an object, the transaction failed. ',80002 ,2)
rollbacktransaction
return
end
.
.
.
Note: Please revert back the changes if the issue is not resolved