Posts: 13
Threads: 5
Joined: Jun 2018
Reputation:
0
When anyone with admin access is logging into visionapp it is taking approx 5-10min then the error log is filling up with the following error, over 300lines in the error per admin that logs in.
We are running Vision App 2018 11.0.6064.1
Message:
Object reference not set to an instance of an object.
Stacktrace:
---------------------------
at CloudAdminCommon.Helper.LogHelper.GetChangeDetails(String resourceId, List`1 parameter)
How would i go about tracing this error to correct the issue?
I have already ran the Data Optimizer and Fixed any issues it threw up.
Any help would be great,
thanks
Chris
Posts: 11,194
Threads: 101
Joined: Aug 2006
Reputation:
204
Is the program working afterwards? The only idea I have is that the working directory is set to another location (not the program directory) - else you should get not that error?!?
Did you try to delete the error log? Same behavior? Or you can try to delete the layout Tools=>Reset Layout - but I think it should be the working dir...
Regards/Gruss
Oliver
Posts: 11,194
Threads: 101
Joined: Aug 2006
Reputation:
204
Could you try it with the latest version? And did you check the working dir???
Regards/Gruss
Oliver
Posts: 13
Threads: 5
Joined: Jun 2018
Reputation:
0
installed the latest version on my test server still same, Object reference not set to an instance of an object error.
Not sure what you mean for me to check with the working directory? What do you need me to check.
If I open say the working directory for ping in ext app, it goes to the correct directory that vision app is installed in, is that what you mean?
Posts: 11,194
Threads: 101
Joined: Aug 2006
Reputation:
204
if you open ASGRD by a link just open the link and you find the working diectory - but if it is working afterwards it should be the right working dir
Regards/Gruss
Oliver
Posts: 13
Threads: 5
Joined: Jun 2018
Reputation:
0
no its the correct directory, double checked that when installing the new version also.
are they are deeper logs that I can log at in the DB?
Posts: 11,194
Threads: 101
Joined: Aug 2006
Reputation:
204
I read your answer and have a new suggestion :-)
Did you activate one or more "Extensions"? Or perhaps only some persons that are using the same database? I think that is causing this issue - because an extension dll is not loaded (because it is not activated) a type could not be loaded…
We will fix that with the next version...
Regards/Gruss
Oliver
Posts: 13
Threads: 5
Joined: Jun 2018
Reputation:
0
We are all using the same DB. I do have KeePass active but the error was happening before this. We have over 20 thousand connections in our DB.
Just thinking on what you are saying. Could it be there are a few connections in there that only the admins have access to that are causing the issue and that's why its fine for everyone else but admin are the only ones getting the error.
Posts: 11,194
Threads: 101
Joined: Aug 2006
Reputation:
204
No believe me - I can reproduce - if any user has an extension module active and configured it and any other user now opens the ChangeLog - the error occur and the error log entry is written...
Regards/Gruss
Oliver
