RVTools Returning Parsing Error

Hello,

Do you get the same error message when you try to use RVTools outside RDM like in a command line prompt?

Could you please verify that there is no extra space charater in front of after the Host parameter value?

Best regards,

Good morning, Erica.

When I do command line, it works fine:

rvtools -s vCENTER -u USERNAME -p PASSWORD -c ExportAll2xlsx -d c:\temp -f test.xlsx

I have verified there are no extra characters. As I mentioned before, it worked two or three versions back. Nothing has changed, and I did a simple "Open Session", and I now get the error.

I upgraded from v4.3.1 to v4.3.2 this morning, and still get the same issue.

Hello Chuck,

Thank you for information.

We will test this and will keep you posted.

Thank you for your patience.

Best regards,

Hello Chuck,

One of our QA team specialist has been able to reproduce your issue.

A ticket has been submitted to our engineering team and once a fix will be available, we will post it here.

Thank you for your patience.

Best regards,

Thank you, Erica.

Sorry to keep bringing bugs to your group's attention. At least didn't have to do a remote session for this one.

Looking forward to turning my Trial in to a full-blown version in the next couple days and keep reporting issues I encounter.

Have a great Christmas!

Hello Chuck,

We are in fact unable to reproduce your issue other than when a space character exist in the host name, no matter where it is located (beginning, in the middle or at the end). Most of the solutions found online mentioned about that space character.

What mode are you using?



Best regards,

Erica,

I literally just created this entry, which mirror the rest.

I created a hosts file entry for TEST, just to make sure there was in fact nothing wrong with the entry.

I still get the exact same error message.

So now I have re-typed the correct URL(s) in three entries that worked perfectly fine in prior versions, as well as recreate them from scratch with the same information to make sure there were no extra characters anywhere. I did nothing more than double click the entry to export an RVTools Report like I have done in all other versions of RDM that has worked in the past.


An updated note. I just swapped the URL entry for the IP of the vCenters that worked previously.

Same error with regards to parsing.
.

Hello Chuck,

Thank you for your feedback.

That's odd as we can't reproduce this problem.

Do you encounter the same error message when you try to use the Default instead of exporting the file to start the RVTools application?

Do you have any relevant error messages in Help - Application Logs?

Best regards,

Good morning, Erica.

Yes, I do. Any and all options that are available all give the same results.

I installed the latest version on a new VM I stood up, installed RVTools 4.3.2 and RDM v2022.3.27.0. Nothing else exists on this machine.

Configured RDM for use with RVTools.

Manually created an entry.

Same results.

Hello Chuck,

Thank you for your feedback.

Could you please open the Profiling dialog in Help - Profiler and set the Debug level to 1?



Then try to run the RVTools session.

Do you get anything relevant? If so, please send me the result. You can hide any sensitive information prior to publish it.

Once finished, please set the Debug level back to 0.

Best regards,

Erica,

There was only one quick line written to anything on that screen.

I added the Marker at the start of the RVTools session:

Hello Chuck,

Thank you for your feedback.

I think it would be easier to troubleshoot this issue in a support session. I will create a ticket on your behalf and send you a link to book the support session.

Best regards,

Erica,

Thank you to you and your colleague for the support session this morning.

Going on what the thought was regarding complex passwords and the RVTools plug in, I decided to play around a bit.

I downloaded and installed, one by one, the previous versions of RDM as found on: Download Previous Versions - Remote Desktop Manager (devolutions.net). Once I exhausted all those versions, I installed the latest version available.

Just as the thought was, for each and every version, if I used a simple password (P@ssw0rd1234!), the plug in worked as it should.

Then I started playing with the Tools > Password Generator which is what I use with the following settings:


It looks as if the 1st character of the password is a certain character, it will give the parsing error.

Most characters worked, but a couple I found that did not were ", `, and ~.

If the password started with those characters, no matter the length, it would fail.

Most others worked perfectly such as {, (, : all worked fine.

I did not try all special characters, as I figure this would give your Dev department somewhere to start with.

Hope they can get to the bottom of the reason.

Have a great rest of the week, and thank you again for your time.

Hi Chuck,

Thank you for the detailed information.

As mentioned during the call, we are able to reproduce the behaviour with only adding a '\' in the password.

A note has been added in the internal ticket.

Once a fix will be available, we will post it here.

Thank you very much for your patience.

Best regards,

Hello,

We've investigated the issue, and as it turns out, the problem is linked to how RVTools handles received credentials. While you can input characters such as "\" directly in the main window of RVTools, they can't receive passwords with such characters from outside commands.

From what I understand, if you wish to keep such special characters as part of your password patterns, there is an application provided in the RVTools program directory that is used for Password Encryption (you can find out more in their documentation PDF online, page 105). We haven't been able to test it out, but as I understand it, you could paste a password in (with special characters), and receive an encrypted password back that you could use in the entry instead.

If you do decide to use their password encryption tool, please let us know if it fixes the problem for you. If it does, we'll add a help topic and a link in the entry to help clarify things for the future.

Regards,