Posts: 40
Threads: 15
Joined: Feb 2018
Reputation:
1
21-02-2019, 09:58 AM
(This post was last modified: 21-02-2019, 10:01 AM by ILA.)
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.
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
Ok - we run it with users in several security groups without any issues - but we will check that immediately...
Regards/Gruss
Oliver
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
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
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
Also can you run the Data Optimizer to see if there are any hidden objects that might result in that error?
Regards/Gruss
Oliver
Posts: 40
Threads: 15
Joined: Feb 2018
Reputation:
1
24-02-2019, 04:05 PM
(This post was last modified: 24-02-2019, 05:47 PM by ILA.)
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?
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
Please send it to asg.rd@asg.com
Regards/Gruss
Oliver
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
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
Posts: 11,127
Threads: 100
Joined: Aug 2006
Reputation:
202
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
Posts: 40
Threads: 15
Joined: Feb 2018
Reputation:
1
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.