New answers tagged

0

This is possibly caused by insufficient permissions on the Business Data Connectivity Service. Go to the Central Administration website and go to Manage service applications. Click on the Business Data Connectivity Service and check its permissions.


0

Actually the problem is solved there was problem with name of the database table name in the stored procedure. Just passed name dw.TimeSheet_FK which was database table name instead of dbo.information, the problem was solved then.



Top 50 recent answers are included