System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown
Good Day,
We have this error since we upgraded from 6.1.0.0 to 7.0.2.0 of Password Vault Manager
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Data.SqlClient.TdsParser.TryReadPlpUnicodeChars(Char[]& buff, Int32 offst, Int32 len, TdsParserStateObject stateObj, Int32& totalCharsRead)
at System.Data.SqlClient.TdsParser.TryReadSqlStringValue(SqlBuffer value, Byte type, Int32 length, Encoding encoding, Boolean isPlp, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.TryReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.TryReadColumnInternal(Int32 i, Boolean readHeaderOnly)
at System.Data.SqlClient.SqlDataReader.TryReadColumn(Int32 i, Boolean setTimeout, Boolean allowPartiallyReadColumn)
at System.Data.SqlClient.SqlDataReader.GetString(Int32 i)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.cca8119a110bebd9f7c66a9b8aa671a9c(IDataReader cb8306497615195e4d2b0b196997bb844, List`1 c956c86e3e516742fdb9aca7e24607786)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.cca8119a110bebd9f7c66a9b8aa671a9c(IDbCommand c469787a81372d641f189d46c8cbb1738, List`1& c8b9dc1f68940a43e7cd099cb1e4646fe, Byte[]& c9bd301a2fd1db0ad012d647646537ec1, Int32& c0d10ab04b5b18d594b7605de6eda18b5)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetConnections()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.ca4799bebd8b706f34eea94a778843b55(BaseConnectionDataSource c01af917dca3518ff73ed69848f95f91a)
Not sure what to do to fix this
Thanks
Helder
All Comments (8)
How many entries do you have?
David Hervieux
1465 connections is that what you're looking for?
Do you get the error if you try the old version?
David Hervieux
Works A1 with 6.1.0.0. No issue!
Hi,
I've just released a new version. Could you give it a try on one machine?
Regards
David Hervieux
Yes thanks for this new version. I just replied to your email with the sad results that the error still exists.
I still will redo a test on another machine just to validate.
Thanks
Could you send the error message with the Send Error Report?
David Hervieux
Small update on the forum in case this happen to anyone else.
I was able to find some incorrect/corrupted data in my database. So when the database was migrate to the newer version
the garbage was already there. Generating the out of Memory issue.
Using the Performance Profiling I identified the possible cause, then delete the data directly on SQL Server.
Now the database loads with no error or crash.
I'm still testing to validate everything but this looks good.