Sql Server Error while accessing Navision table

zoltero

Can any please help with this. :-k

When using Windows Authentication we get Sql Server Error while we accessing some tables in Nav. W1 40 SP2 with Sql Server 2005.

When log in as Database Server Authentication this error does not occur.

Get following message:
1088,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot find the object "name.dbo.table" because it does not exist or you do not have permissions.

SQL:
SET IDENTITY_INSERT "name.dbo.table" ON

Buba

In fact I've seen the same error with Nav version 4.0.2.22979 and Sql-Server 2005 both 32 and 64bit. Seems like you have to drop Windows login :bug: :evil:

zoltero

Really happy for your answer.. :-s
But I need to solve this problem..
Please any

DenSter

Ask your solution center for the latest update. There are some issues with security that have been resolved by new executables and dll's.

Waldo

Try a complete backup restore.
Try a complete security synchronisation.

Just a guess...

kine

Yes, best solution is to update your client to newest version.

zoltero

Hi have now tried to backup and restore. I am also using the last hotfix of the kernel. All this did not help. ](*,)
- Still more searching needs.

Waldo

Tried a complete security synchronisation?

kine

zoltero wrote:

Hi have now tried to backup and restore. I am also using the last hotfix of the kernel. All this did not help. ](*,)
- Still more searching needs.

What do you mean with the "last hotfix of the kernel"?

Buba

I have tried both the restore/backup and completly re-synchronizing options without any luck I will now try to use the release SP3 xp_ndo to check if this will help :?: [-o<

kine

I recommend to use the SP3 clients too.

Waldo

Definitally ... although they are not everywhere available yet.

Buba

Well the SP3 xp_ndo.dll did not solve this problem. :evil: Neither did a clean SP3 client :evil: So this must be a programming issue as far as I can see. I'll check with the programmer and tried to run a maximum test of the database to check if there is something there :?:

zoltero

We have found a work around for this problem. :whistle: \:D/
Every users have to be defined as SysAdmin in Sql 2005.
- Dissadvantage is that users get to much rights to the database. :-$

kine

I never had problem with SQL 2005 with the rigths. We are using the base rights as with SQL 2005 without problems (SP2 Update 1). Users are not members of the server role or haven't any extended permissions on the database. Strange.

TonyH

Have you tried playing with the Logins Schemas?

Buba

No! Tell me how... :?: