Multi vault search doesn't work any more in de latste versieon

Hi,

Sorry to hear about the issue you are encountering. May I ask you how many vaults you have in your server ? Also, do you use any particular filters that make you reproduce this behavior ?

Best regards,

Vincent Forest

no filter

17 vaults

the search was working before the update

now the hole functie search all vault is not working

and has to be disabled to work the search

and the search only works on a single vault

with all vaults enabled also the search on the current vault is not working

Hi,

I just want to make sure I understand your problem correctly. Are we talking about the Advanced search as per the first screen capture, or the search from the sidebar as per the second capture ?




For now, I haven't been able to reproduce, but we will investigate further to find what could be causing the issue and we will let to know if we need further information or if a fix is on the way.

Best regards,

Vincent Forest

both are not working

and for the search to work i have to slide tha all vaults off. and the it works voor current slected vault

a lot of error's are also being genertated



Error:

InvalidOperationException
- There was an error generating the XML document. at
System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object
o, XmlSerializerNamespaces namespaces, String encodingStyle, String id) at
Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToString(Object
value) at Devolutions.Server.Managers.Variables.VariableManager.ApplyVariables(ISessionContext
context, Boolean isUri, Boolean isAdhoc, Connection connection, Int32
nesting) at
Devolutions.Server.Business.Search.ConnectionSearchEngine.<>c__DisplayClass15_0.<GetConnections>g__ApplyVariables|0(Connection
c) at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext() at
System.Linq.Enumerable.WhereEnumerableIterator`1.ToArray() at
Devolutions.Server.Business.Search.ConnectionSearchEngine.GetSearchResults(SearchEngineParameters
parameters) ------------------------------------------ ArgumentException -
'', hexadecimal value 0x13, is an invalid character. at
System.Xml.XmlUtf8RawTextWriter.WriteElementTextBlock(Char* pSrc, Char*
pSrcEnd) at System.Xml.XmlUtf8RawTextWriter.WriteString(String text) at
System.Xml.XmlWellFormedWriter.WriteString(String text) at
System.Xml.Serialization.XmlSerializationWriter.WriteElementString(String
localName, String ns, String value) at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write535_Connection(String
n, String ns, Connection o, Boolean isNullable, Boolean needType) at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write775_Connection(Object
o) --- Default





Source:

System.Private.Xml

Hi,

Thanks for providing us with this information, it will help us find the problem quicker.

I will let you know once there's a fix available.

Best regards,

Vincent Forest

Could you go to Reports => Diagnostic then to the 'Entries' tab and see if you have any entries with 'Deserialization error' ?




It may be possible you have entries somewhere with bad data that is causing the issue.

Let me know if you find anything there,

Best regards,

Vincent Forest

no errors are soon

no errors in report diagonstic


by a search with all vault on these error are generated

InvalidOperationException - There was an error generating the XML document.

at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
at Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToString(Object value)
at Devolutions.Server.Managers.Variables.VariableManager.ApplyVariables(ISessionContext context, Boolean isUri, Boolean isAdhoc, Connection connection, Int32 nesting)
at Devolutions.Server.Business.Search.ConnectionSearchEngine.<>c__DisplayClass15_0.<GetConnections>g__ApplyVariables|0(Connection c)
at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.ToArray()
at Devolutions.Server.Business.Search.ConnectionSearchEngine.GetSearchResults(SearchEngineParameters parameters)

------------------------------------------

ArgumentException - '', hexadecimal value 0x13, is an invalid character.

at System.Xml.XmlUtf8RawTextWriter.WriteElementTextBlock(Char* pSrc, Char* pSrcEnd)
at System.Xml.XmlUtf8RawTextWriter.WriteString(String text)
at System.Xml.XmlWellFormedWriter.WriteString(String text)
at System.Xml.Serialization.XmlSerializationWriter.WriteElementString(String localName, String ns, String value)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write535_Connection(String n, String ns, Connection o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write775_Connection(Object o)

If you try the advanced search, while filtering in a single vault at a time, is there any vault that returns the same error when searching for entries within it, or do they all works separately and only crash when you specifically search through all of them at the same time ?

Best regards,

Vincent Forest

if you switchs all vaults off

the search is working for selected vault

if all vaults are on

search is not working at all even not for the current selected vault

I think you have an entry in one of your vault that contains bad data that cannot be serialized. What we need to do next to resolve this issue is to try and find that particular entry.
To do that, we will proceed that way :

• Go to the advanced search screen
• In the 'Include vaults' filter, select only one vault at a time
• Include another filter, this one could be anything, to trigger the search. For simplicity, I suggest using the filter 'Name' 'Contains' 'a'
• I will need you to repeat this process for every vault that you have ( 1 vault at a time, for all of your 17 vaults ) or until you get the error while you try to search in a vault, then we will know in which vault the faulty entry is.
• Here is what it should look like

Let me know if you need further help, and let me know if you find in which vault the search crashes. Thank you for your cooperation.

Best regards,

Vincent Forest

i identified the vault where there occured on

also test a multi search over all the vault except the on with error

the multi search is working then

how do i proceed???

That's great news, we are getting closer to the source of the issue!

How many entries is there in that vault ?

Are you able to go browse that vault and the entries in it normally or does it crashes when trying to do so ?

there are 1753 Entries

i can browse but error are generated when a browse the vault

i can't op the vault in RDM the i get these errors

ystem.Net.WebException: Unexpected exception
at Devolutions.Server.ApiWrapper.RDMSWebClient.RunSynchronous[T](Task`1 task)
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.<>c__DisplayClass96_0.<GetData>b__0()
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.RetryAction[T](ExecuteActionDelegate`1 action, String label)
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.ExecuteAction[T](ExecuteActionDelegate`1 action, ExecuteActionLogMode logMode)
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSWebApiClient.GetData(String proxyConnectionCacheID, Byte[] version, String repositoryID, Boolean getSensitive)
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.GetDataSourceSettings(String repositoryID)
at Devolutions.RemoteDesktopManager.Business.DataSources.RDMSConnectionDataSource.GetDataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadDataSourceSettingsFromDataSource(ConnectionEngine engine)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.ValidatePoliciesPart1(ConnectionEngine engine, Boolean hasChanged)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadConnectionsFromDataSource(ConnectionEngine engine, Boolean hasChanged)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadConnections(BaseConnectionDataSource dataSource)

Hi, and sorry for the delay.

We now need to find which particular entry in that vault is causing the issue. To do that, we will proceed with RDM by doing these steps

• In the bottom right corner, click on the bug icon to enable and pop the profiler screen;
• Then, you will need to go in the right tab, which is called 'Debug'
• After that, please select only 'Load connection detailed' in the list, or even easier, just right 256 in profiler level.
• Then, keep that screen open and force a refresh in your vault that contains the faulty entry, then you should see all your entries one by one in the profiler, and we should see which one is causing the issue

Please note that it may take a while to load and write all of them since you have 1753 entries in that vault. Just let the process go until it is over. If you can't find the information, you can just use the copy button on the bottom right corner of the profiler screen, and send me the result in private message and I will look at them for you.



Best regards,

Vincent Forest

i can't open the vault in RDM

the following error is being displayed



i can only open the vault in the web interface of devolution server

Same issues here with DVLS 2023.3.5.0 and RDM 2023.3.20.0
Web is working but also throwing the same error.
RDM can't connect at all to that specific vault.
On Reports -> Diagnostic -> Entries there is no Entrie with an Deserialization Error.
I also reseted Server Cache but still the same issues.

Error:

InvalidOperationException - There was an error
generating the XML document. at
System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o,
XmlSerializerNamespaces namespaces, String encodingStyle, String id) at
Devolutions.RemoteDesktopManager.Managers.SerializationManager.SaveObjectToString(Object
value) at
Devolutions.Server.Managers.Variables.VariableManager.ApplyVariables(ISessionContext
context, Boolean isUri, Boolean isAdhoc, Connection connection, Int32 nesting)
at Devolutions.Server.Business.Search.ConnectionSearchEngine.<>c__DisplayClass15_0.<GetConnections>g__ApplyVariables|0(Connection
c) at System.Linq.Enumerable.SelectArrayIterator`2.MoveNext() at
System.Linq.Enumerable.WhereEnumerableIterator`1.ToArray() at
Devolutions.Server.Business.Search.ConnectionSearchEngine.GetSearchResults(SearchEngineParameters
parameters) ------------------------------------------ ArgumentException - '­',
hexadecimal value 0x1F, is an invalid character. at
System.Xml.XmlUtf8RawTextWriter.WriteElementTextBlock(Char* pSrc, Char*
pSrcEnd) at System.Xml.XmlUtf8RawTextWriter.WriteString(String text) at
System.Xml.XmlWellFormedWriter.WriteString(String text) at
System.Xml.Serialization.XmlSerializationWriter.WriteElementString(String
localName, String ns, String value) at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write535_Connection(String
n, String ns, Connection o, Boolean isNullable, Boolean needType) at
Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write775_Connection(Object
o) --- Default

Source:
System.Private.Xml

Kind regards

As mschulpen stated we can't profile that Vault:

Hello to both of you,

Thank you for your feedback. We are positive that we found the source of the issue and are working on a fix as quickly as possible, we will release a version as soon as it is fixed. In the meantime, if you really need to use that vault, I would advice you rollback to the previous version while we are working on the fix. It should be available soon and I will keep you updated.

Best regards,

Vincent Forest

Hi Vincent
When will the fix be available? ETA?
When I go back to the last version I also need to downgrade 50 RDMs.
Kind regards,

Hi,

We hope we will be able to deploy a new version today containing the fix, if we are not able to make it, it should be in the next few days at most.

Thanks for your patience while we fix the issue,

Best regards,

Vincent Forest

Hi Vincent
I solved the problem by myself.
@mschulpen you can follow my solutions path, maybe it works for you too.
Go to Reports -> Diagnostics -> Entries and press Export to CSV on the lower left side.
Open the CSV in Notepad++ and use following settings to find the special character:



The one error that made the deserialization fail is following character:


Kind regards,

Hi Jannisroth, no this not working for it still doesn't find any error's

@vincent when do you thank the fix is avaible ??

Hi,

Thank you @jannisroth for the potential fix in the meantime. Sorry it did not work for you @mschulpen. We are working on deploying a new version containing the fix. If everything goes smoothly, it should go out today or tomorrow.

Thanks for you patience,

Best regards,

Vincent Forest

Hi
@mschulpen as you can see in your error message the Character you are looking for is not \x1f (0x1F) your is \x13 (0x13).
But probably just wait for your fix.
Kind regards

Looks like the update fix the probleem and search is working and no errors are generated at the moment

Hi,

Glad to hear the new version is solving the issue, thanks for your patience and feedback!

I will now close this topic as it is resolved, don't hesitate to reach to us if there is anything else !

Best regards,

Vincent Forest