Permission related problem

Marco Baracco

April 26, 2018 09:33

None

Hi all

i'm running Jet Professional, free version.

I have upgraded Jet to the last available version, and i've set the Office 2016 updates the correct way to avoid slowness issues

From every single workplace i have updated, if i run the Report with my user it updates correctly, no problem at all.

Any other user on the same pc, same jet settings, gets the error you can find below.

The connection type is direct to rhe SQL database, and it uses a different dedicated user, then i suppose the logged on user should not change anything in updating the report.

Any idea? thanks a lot!

An unexpected error has occurred:

System.Data.SqlClient.SqlException

in System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

in System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

in System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

in System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

in System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

in System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

in System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

in System.Data.SqlClient.SqlConnection.Open()

in Jet.Data.Ado.SqlDataSource.<LoadFields>d__27.MoveNext()

in Jet.Data.Ado.AdoDataSource.a(Object A_0, FieldsRequestedEventArgs A_1)

in Jet.Data.TableInfo.OnFieldsRequested(FieldsRequestedEventArgs e)

in Jet.Data.TableInfo.get_Fields()

in Jet.Data.Nav.NavSqlDataSource.ad()

in Jet.Data.Nav.NavSqlDataSource.f()

in Jet.Data.Nav.NavSqlDataSource.LoadTables()

in Jet.Data.Nav.NavDataSource.a(Object A_0, TablesRequestedEventArgs A_1)

in Jet.Data.DataSourceSchema.OnTablesRequested(TablesRequestedEventArgs e)

in Jet.Data.DataSourceSchema.get_Tables()

in Jet.Data.Nav.NavDataSourceSchema.get_Tables()

in Jet.Data.Nav.NavSqlDataSource.c(IQuery query)

in Jet.Data.Nav.NavSqlDataSource.ExecuteQuery(IQuery query)

in Jet.JetDispatcher.a(du A_0, IJetDataSource A_1)

in Jet.JetDispatcher.a(du A_0, Boolean A_1)

in Jet.JetDispatcher.b(d4 A_0)

in Jet.JetDispatcher.a(du A_0)

in Jet.JetDispatcher.e(du A_0, String A_1)

in Jet.JetDispatcher.e(Object[] A_0)

Date Votes

3 comments

0

Harry Lewis April 26, 2018 14:17

Hello Marco -

It appears that you are using Jet Express for NAV with Windows Authentication (current user) for the first authentication parameter in the Data Source Settings > Authentication tab.

In order for users to utilize the Dynamics NAV 2013 and later (SQL Server) data source with Windows Authentication (current user), the user must be added to the root security of the SQL Server Management Studio and mapped to the NAV 2013-2017 database with db_datareader permission and a public role.

You can do that or you can use a proxy user to gain db_datareader access to the database.

You can either create one SQL Server user with db_datareader access or create one Windows AD user with db_datareader access (e.g. one of your database administrator's AD accounts).

In the Jet Data Source Settings, switch to either SQL Server Authentication or Windows Authentication (other user) and enter the appropriate credentials.

If you review the following screenshots you will see the method that the Jet Reports Technical Support team recommends for configuring the authentication parameters for the Dynamics NAV 2013 and later (SQL Server) data source.

Comment actions Permalink
0

Marco Baracco April 26, 2018 14:34

Hi Harry

thanks for your reply

The strange thing here is that Jet is properly configured to use "Windows Authentication (Other users) " , with a user who has all the needed permissions on the database, and who was working fine till yesterday .

Now it looks like jet is not authenticating with the user i have set up but it uses the logged in user to query the db instead

Comment actions Permalink
0

Harry Lewis April 26, 2018 14:43

All settings for Jet Express are stored on a user-by-user basis (in %appdata%):

Since you are able to refresh the report, but others are not, you may want to have one of the users (who is *not* able to refresh the report) log in so that you can check their data source settings.

Edited by Harry Lewis April 26, 2018 16:12

Comment actions Permalink

Please sign in to leave a comment.