Connection test to the localhost

[crimsonread]

Hello!

I've just installed this module and try to test on the localhost. When I run Invoke-RemoteDesktopViewer -ServerAddress "127.0.0.1" -ServerPort 2801 -SecurePassword (ConvertTo-SecureString -String "urCompl3xP@ssw0rd" -AsPlainText -Force) in the example,

I have encountered Exception: Could not open a new session with error: "Exception calling ".ctor" with "2" argument(s): target computer denied access"

Anything that I should look for to solve issue?

OS: Windows 10

Thanks.

[DarkCoderSc]

Hello,

Can you please provide the following details :

• Exact version of PowerShell (use $host command)
• Both Viewer and Server command line ( don't forget to redact passwords )
• Verbose dump of both Viewer and Server
• Exact version of PowerRemoteDesktop

Thank you in advance

[crimsonread]

Hello,

Can you please provide the following details :

• Exact version of PowerShell (use $host command)
• Both Viewer and Server command line ( don't forget to redact passwords )
• Verbose dump of both Viewer and Server
• Exact version of PowerRemoteDesktop

Thank you in advance

Hi, Thanks for your reply.

• Exact version of PowerShell (use $host command) 7.2.1

• Both Viewer and Server command line ( don't forget to redact passwords )

When I run Invoke-RemoteDesktopServer, I cannot input any parameter. so the output is as below.

InvalidOperation: Cannot find the type for custom attribute 'ValidateFile'. Make sure that the assembly that contains this type is loaded.

• Exact version of PowerRemoteDesktop 3.1.0

By the way, when I use PowerRemoteDesktop version 2.0.0, it was okay to connect it.

[DarkCoderSc]

I was able to reproduce the error, I did not see that since I'm always testing as a PowerShell Script rather than PowerShell Module.

A hot-fix was released both on PowerShell Gallery and GitHub Repository, can you confirm everything is fine in your side ?

I will investigate more deeply why custom Validators are not successfully imported in this specific case.

Waiting for your reply before closing this issue.

Thank you

[crimsonread]

I was able to reproduce the error, I did not see that since I'm always testing as a PowerShell Script rather than PowerShell Module.

A hot-fix was released both on PowerShell Gallery and GitHub Repository, can you confirm everything is fine in your side ?

I will investigate more deeply why custom Validators are not successfully imported in this specific case.

Waiting for your reply before closing this issue.

Thank you

Hello!

The issue has been resolved with updated version from PowerShell Gallery. Thanks for your quick fix!