Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Only admins can connect with 2019?
#1
Hi

We use a central DB to work with ASGRD. I just installed 2019 x64 and upgraded the DB. When I try to open 2019 as an admin (admins in ASG's permissions, not "run as admin" in windows) it works with no issues, however, if anyone else tries they get stuck at "Loading Data".

Now I've run some tests, it doesn't even matter if I assign all permissions to "Everyone else", they still get stuck at "Loading Data". You must be an ASG admin to be able to open 2019.

Everyone can still open 2018 and connect to the DB without issues, the issue only occurs when opening 2019.
Reply
#2
Ok - we run it with users in several security groups without any issues - but we will check that immediately...
Regards/Gruss
Oliver
Reply
#3
We can't reproduce the issue - is it possible that you send us a backup of your database? So we could try to login into that database and try to find the issue - we have planned a Patch for the next days and would like to solve that issue too

asg.rd@asg.com - if the SQL backup file is more than some MB you should put it on any transfer share and send me the link (can be done also via private message here)
Regards/Gruss
Oliver
Reply
#4
Also can you run the Data Optimizer to see if there are any hidden objects that might result in that error?
Regards/Gruss
Oliver
Reply
#5
Hi

After going through our InfoSec I was allowed to send you a DB privately. It's been pretty much emptied but the issue still exists on it so it should be good enough.

Can you give me an email address so I can send you this DB privately?
Reply
#6
Please send it to asg.rd@asg.com
Regards/Gruss
Oliver
Reply
#7
I have restored your test database and can reproduce the issue - now it should be easy to find the reason and fix it
Regards/Gruss
Oliver
Reply
#8
Ok I think I found it - there was one entry in the database that referenced itself - that was not handled by code (and I don't know how it was possible to put these values into the database)

Try to run the following SQL command

DELETE FROM Items WHERE ItemId = ParentItemId

Of course you can first see what the result would be with

SELECT FROM Items WHERE ItemId = ParentItemId

In the test database I have from you only one entry was invalid - but perhaps there will be more?!?
Regards/Gruss
Oliver
Reply
#9
Thanks for the reply, seems in our DB it was only that same entry that popped up in the query, I deleted it and now it seems to be working for everyone.

Thanks a lot Oma.
Reply




Users browsing this thread: 1 Guest(s)