'An internal error has occurred' message launching RPD tcp/udp service

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

When launching an rdpproxy service only from one user desktop they get this error

Cause

In the rdpproxy service definition, i see there is not path in mstsc launch 

 

usually path is C:\Windows\system32\mstsc.exe /f  /v:<Local IP>:<First Port> 

Resolution

To use the mstsc command from the command line in Windows, you need to ensure that the path to mstsc.exe is included in your system's PATH environment variable. The typical location for mstsc.exe is in the Windows System32 folder, which is often already included in the PATH. If it's not, you'll need to manually add the path.  

 

Here's how to check and modify the PATH environment variable: 

 

1. Check if the path is already included: 

 

• Open Command Prompt (or PowerShell).
• Type echo %PATH% and press Enter.
• Look for the following path in the output: C:\Windows\system32 (or C:\Windows\SysWOW64 if your system is a 64-bit version). If this path is present, mstsc should work without specifying the full path.  
   

2. Add the path if it's missing: 

 

• Open the System Properties: You can do this by right-clicking on "This PC" (or "My Computer") and selecting "Properties". Alternatively, search for "System" in the Start Menu.
• Go to Advanced System Settings: Click on "Advanced system settings".
• Open Environment Variables: In the "Advanced" tab, click on "Environment Variables".
• Edit the PATH Variable: Find the "PATH" variable in either the "User variables" or "System variables" section (usually in the "System variables" section). Select it and click "Edit".
• Add the path: In the "Variable value" field, add the full path to the mstsc.exe executable. This is typically C:\Windows\system32 (or C:\Windows\SysWOW64 for 64-bit systems). You can simply add a semicolon (;) at the end of the existing path, then add the new path, like this: ...;C:\Windows\system32.
• Click OK: Click "OK" on all the open windows to save the changes.
• Test: Reopen Command Prompt (or PowerShell) to ensure the changes take effect. You should now be able to use the mstsc command without specifying the full path. 

 

After you add the path it should work from cmd.. running mstsc directly without c:\windows\system32