Thursday, December 4, 2014

NAV 2013 R2 - Navision Client Crash for a Set of Users after Upgrade.

Hi all,

After Upgrade from NAV 2009 to NAV 2013 R2, one of my customer Reported that some of its users are unable to access the Windows Client.

This post list down the discussion what we had and how we were able to resolve the issue.

Issue -
Some of the users when trying to Connect to Database were getting Below error Message and Navision Windows Client was getting crashed.

Discussion -
1. After Discussion with Customer it was found that not all but some specific users are getting this issue.
2. I created a new user, assigned the basic role to it and tried Login into Windows Client. (Works OK).
3. One by one i started assigning Roles to New user same to that of the User who was unable to Login.
4. After applying 5 Permission Set, it got Crashed.

Understanding -

1. There is Something wrong with the Fifth Permission Set.

Action -
1. Tried Opening the Permission Set in Windows Client with a Super User.
2. Unable to Open the Permission and Client Crashed with Below Error.

Microsoft Dynamics NAV
Exception of type 'Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLTypeMappingException' was thrown.

Cause -

The Permission set contain a permission with Security Filter in NAV 2009.

In earlier version of Navision and in table permission set , security filter was updated by the field name and but in new version of Navision it is updated by Field Number.

Resolution -

1. Delete the Specific Permission From SQL -

**REPLACE ALL Parameter within <> with actual Values.

USE [<Database Name>]
select * from Permission where [Role ID] = '<ROLE NAME>' AND [Object Type] = 0

Delete from Permission Where [Role ID] = '<ROLE NAME>' AND [Object Type] = 0 AND [Object ID] = OBJECT ID

2. Manually Creating the above role again in NAV 2013 R2.

Hope this post will help you, if you ever face this issue.

Saurav Dhyani

No comments:

Post a Comment

Popular Posts