Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
BaseItemGet Error
#21
(05-12-2017, 11:53 AM)mkeeves Wrote:
(05-12-2017, 11:11 AM)DevOma Wrote: Which user have the problems? Just a name, I will find it :-)

I will e-mail you the username. I have had another user with the same error this morning. In his instance we saw that there was a favourite which had been orphaned (showing a red X next to a personal favourite in the GUI). The user deleted this favourite object, closed and opened the application, and the error went away.

I have tried the same for the first user, but this has not resolved the issue.

Sorry for not replying to this thread sooner. After having the newer version packaged up by our desktop team (2017 Patch 2), and installing this for 2 users with the issue, it seems that the issue is resolved, and the users are no longer getting errors when logging in.
Reply
#22
Getting the Error BaseItemGet again, followed by LogsAdd when opening ASG Remote Desktop 2018 patch 1 64 bit.

I have run through the data optimizer as a full admin. I have done a reset layout, and a reset quick connect history, but the issue persists.

We have an AD sync set up, and I have just realised that there some machines which got deleted from the domain. These no longer appear in the connections folder, however there are some shared favourites which have been created for these objects which now appear like so:
[img]data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGcAAAAsCAYAAAB43qZWAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAVlSURBVHhe7ZlfaFNXHMe/+dM/tlWcDl/EtaMP+uDYUAQdDFqsW0LXtXZhQzt9SYRayny5WUHYQF+20shg+iAsgU2s4kw7OxrsukKjg86HVlsIQ8Ha5E1FmYKKMYlnv3Nzb/7t3vTeDm7zcD5wcv7c3y+55/7O73fPyc/GCAgqErtSCyoQYZwKxrBx3vtmEo09gytuC8xjyTuHGykxPKD0BEYx5TkqN6em0FVfjz/DYaRevVJGgUw6jZnRUXxWV4e5SEQZhTDMSuGeY4S3Dn4n17OTk8xTV8eunzjBjm/dyq5dvMhSySRLp1Lsr8uX2cCmTWxk7172RW0tmxsfl3Xe/fp3uRaYw7DnqKv/ZFcX+o8dQ0Mmg679+/GHJOEGecvslSuI9PWhbccOOJ8/h7u5GUMej6zzz+ItuS4mCr/NBn9U6crwMT99riJRP2zuEBKlbT30ZIzoLoPpsPbV+fOIDA8j9fQpkg8e4JN9+zB+9Ch+PXIE7Tt3Ao8ewfb4Mf5eWsKX587JOuXCWmDQ5AQSIbj/56TL0jIEdtWLRqW7mhg2jrr6d3d0oPPUKYxduoTaly/hePIEn+/Zg0+3bEF6YQGOu3cxv7iI9lAIuzo7ZR393ZqEoCeMM6vqKpWL6bDmcDqxm0Lbx6dP4xd66TsePoQjFkM9GWm93Y65Fy/wEXnWru5uOKurZR3tsJal2Uvf26odyhIhN2wU+uQix78EQr0+TEz40FTqPTyMqLK8yNdJ3l0cOqN+G9wh0tSUlwX0w5SWvEwYvZrjeYrmoiNTip0Lc/RqlcLVz16/ho1K5tkzZO7dw3oywpu0e1tXVYUaGncqcirld2st6A/GMMgfWCH0MJrCHsRpp0/vRkyjlR4q4D0bhMsVRLw09PBwpMjK8tt95JGN8A5ICERU60QRCUgY8JKmprwipkU5+QnAE8+P92rN5fZATjdO0eI/MhrYuTBHr1ZRV3+ats58A/DbgQPo3rgRDbW1cJIh15FHvdHQgI7Nm3H98GHMkwyX5Sx3CG0k79nuO1PkPdFIAC5PW84ALe0SJm4vKT1tuFfIK5NKa0AZbGmHFIhkvzsaQSzYT8shi6Z8GXTlXR60KTeqdZ98Lgi05nSbfBPLzoVjOqzdGBvDSE8P3qezDP8hfrb5MZHA93fuyO2Mw4EPNmzA1KFDuEWynHJhLYvqPYtK3zw8bLSSf/FFxcu0pFxQvps7TzQSg0d5ivry2piVL8UVjOd05TKkLhF9TO/WfiCv2EbvljRtpVNkjNH79+GiXZn7wgX8TCEumUwiSaHtnZoanCVZTvmwliXrPT7kFzytwPBULjbLnrTtbaWnTf56AosxpUk0tnkQi/gRieVXOEdPXg8j8lr3Kc+lIDLI75/iM4Q2ZEVD5A6hdLA8WF3NfqqpYcftdjZTcAi9SYfQb6uq2NW1a1kfXV8oewidZhIk+ixgWqJYmh+LB108tmaLpI5yPT5Wopsbz5ecCouzoAuMVq/S5+jI83twBUmjpF1OvnBc/dEi3ZK5FIyXw7BxCuEn/wNr1rAZMgY3jAo30OzICPPSNdUwHNWwAnMY/uOTh7X5kx8qPYEVmD6EciOZTReobYE5LEkZCFaGYc8RWI8wTgVj6pyz0ncNbwvMY8k7hxvJyEFUUIzpfwg4Ik1tEdxzjCDS1NZj2HPU1S/S1CXoyRjRXQbTYU2kqa3DsHHU1S/S1NZhOqyJNHWJvIxIU4s0dWmtoq5+kabWkBdp6vLop5FFmlqkqRVEmloeE2lqTUSa2hoM//HJw5pIU1uL6UMoN5LZdIHaFpjDkpSBYGUY9hyB9QjjVDDCOBWMME4FI4xTsQD/At+dk+x1RH9jAAAAAElFTkSuQmCC[/img]

After removing these objects, I am no longer getting any errors when opening ASG. This to me seems like a bug - would you agree?

This was probably less of a problem before shared favourites, but we are now extensively using shared favourites across multiple teams. We can also have a high turnover of domain servers due to environments being spun up and down. It would be great if the favourite kept a reference to the original object, so that when the original object is removed that any favourites are removed from the database also.
Reply
#23
Could you add the image again? It's only a big char string currently...

I will check that afterwards - you can set the delete option in your sync to "Show image instead of deleting the connection" - perhaps that helps as a workaround...
Regards/Gruss
Oliver
Reply
#24
Ah, sorry, I do not have the image any more. It was a red cross next to 'unavailable' I believe.

I do want unavailable items to be removed when they are not available in the sync, but thanks for suggesting the workaround.
Reply
#25
Ok
Regards/Gruss
Oliver
Reply
#26
(13-03-2018, 03:21 PM)DevOma Wrote: Ok

Would you agree this is a bug? Or do I need to request this as a feature?
Reply
#27
Screenshot:



[Image: ASGCapture.PNG]

The UI loads after this error, but is unresposive.
Reply
#28
Which version do you use?
Regards/Gruss
Oliver
Reply
#29
@mkeeves - will be fixed in next version!
Regards/Gruss
Oliver
Reply
#30
(14-03-2018, 01:40 PM)DevOma Wrote: @mkeeves - will be fixed in next version!

Thanks for the quick response as usual!

I am again getting the BaseItemGet error, followed by the LogsAdd error. The application log shows the errors also:

An error occured on executing an sql statement
BaseItemGet
 
An error occured on executing an sql statement
BaseItemGet
There is already an open DataReader associated with this Command which must be closed first.
 
---------------------------
 
at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader()
at CloudAdminDataAccess.SqlDataAccessor.BaseItemGet(Guid itemId, Guid userId)

________

An error occured on executing an sql statement
LogsAdd
 
An error occured on executing an sql statement
LogsAdd
There is already an open DataReader associated with this Command which must be closed first.
 
---------------------------
 
at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at CloudAdminDataAccess.SqlDataAccessor.LogsAdd(LogItem logItem)
Reply
#31
Sh...! I will have a new try to find the piece of code that causes this error...
Regards/Gruss
Oliver
Reply
#32
(27-03-2018, 10:07 AM)DevOma Wrote: Sh...! I will have a new try to find the piece of code that causes this error...

One of my colleagues found that this error was again caused by an orphaned favourite. I know that you have implemented some code to resolve prevent this from happening in the new version (patch 3), we just haven't been able to upgrade to that version yet. I guess the new version might prevent the issue occuring, as when a connection is deleted it will also remove associated favourites (although I don't know if this will happen across multiple users, or when the object is deleted via a sync). However if the issue already exists because the connection has been deleted using an old client then it would be useful if it was not a manual process to clean this up. Perhaps the Data Optimizer could be used?
Reply
#33
Ok - then the fix might help you soon :-)

DataOptimizer might be a good idea - problem currently is that a user can't delete a personal favorite of another user - but the new code should prevent this to result in an error... but with next database change there should be another clean up function for the data optimizer...
Regards/Gruss
Oliver
Reply
#34
In my opinion I think users have Trenbolone problems with their saved layouts, I think they should try tools layout etc
Reply
#35
@mkeeves: Do you use Permissions? We found a bug with active permissions and restricted users - currently we have a private fix for that and it will be released with the next version… perhaps that solves your issue too
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)