447
I am on General Entry window, on test (TWO1 ) database. When open window get error The server principal "User1" is not able to access the database "TWO" under the current security context
Why is that so, I am on test company TWO1 and not on production company TWO, why is it giving me TWO database message?
User has no access to Company TWO.
when window open, there is 0 in General Entry number field and message pops Please enter a general entry number.
Any idea? Any Solution?
If you were to enter a transaction into TWO1 do you see it in TWO1 or TWO or both? Do you see both company databases in SSMS?
Try running in SSMS
select cmpanyid,cmpnynam,interid from dynamics..SY01500
What does this yield? I have never made a test company of the test company. I wonder if the -1 for the cmpnydid is causing an issue?
One thing I notice is that you are saying that you are in a Test company database called TWO1 and the error is saying TWO. Did you recently restore the live company over this test company? If so, you may want to take a look at the steps in this article, especially step 6. It may just be setup to call TWO in the tables still.
Nicole
I'm wondering if it is a matter of GP thinking the user has access to a company database while SQL doesn't, or vice versa? Though, if you're able to login to the company database, it would seem both GP and SQL show correctly that this user is a 'user' under that company database and has access.
You can verify by looking at the SY60100 table for this user and then in SQL Server Mgmt Studio, look under 'Users' under this company database and make sure the user exists there as well.
If you remove the user from having access to this company database, via the User Access window in Dynamics GP, then add access back, do you get any errors? If not, does that resolve this error messsage?
Thanks
I would start by checking that DYNSA is the owner of the TWO1 database. How did you create this database? Did you do a forced restore using the backup of TWO over TWO1? Did you then run the script to correct the INTERID?
DEXSQL
stmt(13144816):*/
BEGIN DECLARE @stored_proc_name char(30) DECLARE @retstat int DECLARE @param3 int DECLARE @param4 tinyint DECLARE @param5 int set
nocount on SELECT @param3 = 0 SELECT @param4 = 0 SELECT @param5 = 0 SELECT @stored_proc_name =
'TWO1.dbo.glGetNextJournalEntry' EXEC @retstat = @stored_proc_name 1, 1048, @param3 OUT, @param4 OUT,
@param5 OUT SELECT @retstat, @param3, @param4, @param5 set nocount on END
/*
/*
SQLSTATE:(08004) Native Err:(916) stmt(13144816):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]The server principal "User1" is not able to access the database "TWO" under the current security context.*/
/*
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (