I am trying to perform a remote debug over the internet, however, I receive the following error.
Error
Debugger Assertion Failure: "!"mkapistream::openConnection()""
in ..\win32src\rproxy.cpp at line 298
OK
Details >>
I have opened up the default PAServer port i.e. 64211, as well as the remote debugger port i.e. 64447 on my router and, can confirm that they are available from an external source.
I have tried with both Delphi XE3 which is my development environment as well as with a trial version of the new Delphi 10.3, however, both versions of Delphi throw the exact same error.
This error occurs, when I try using the Load Process|Remote and Attach to Process|Remote.
If I attempt the exact same process over a LAN connection everything works as expected, it only seems to be over a WAN which the problem occurs.
Below are my environment details:
Windows 10 - Version 1607 (OS Build 14393.2608)
Delphi XE3 Update 2 Enterprise - Version 17.0.4770.56661
PA Server (paserver.exe) - Version 17.0.4770.56661
Remote debugger (rmtdbg170.exe) - Version 17.0.4770.56661
and
Delphi 10.3 Architect Trial - Version 26.0.32429.4364
PA Server (paserver.exe) - Version 26.0.32429.4364
Remote Debugger (rmtdbg260.exe) - Version 260.1810.29.29349
I have also registered both libraries bordbk170.dll and bordbk170N.dll for Delphi XE3 as well as bordbk260.dll and bordbk260N.dll.
If I set up an VPN connection, I can remote debug over the WAN connection, but it seems as if the remote debugger just cannot resolve the cons over a straight WAN connection.
So, my question is the following:
Can one remote debug a Delphi application over a WAN connection?
You probably need to find out what port the remote debugger is looking for and redirect that using port forwarding on your local router to your PC
Related
In Delphi 10.4.1 I'm trying to build an Android application that connects to an instance of Interbase running on my laptop (which I can connect to remotely from my desktop). I get the exception:
Project Project6.apk raised exception class EIBNativeException with message '[FireDAC][Phys][IBLite]Unable to complete network request to host "192.168.1.58".
Failed to locate host machine.
Undefined service gds_db/tcp.'.
Connection Parameters:
Database=192.168.1.58:C:\Users\Public\Documents\Embarcadero\Studio\21.0\Samples\data\employee.gdb
User_Name=sysdba
Password=masterkey
DriverID=IB
Everything works fine if I connect to a local database, or run the app on Windows.
I've seen this demonstrated in XE7 (https://youtu.be/XAZQfYzvxHc?t=1384), but can't get it to work in 10.4.1.
What am I doing wrong?
If InterBase on your Windows machine is running on default instance 'gds_db', then it is probably using TCP socket on port 3050. Try changing your Android application's Database URL to the following so it includes the target 3050 port number. I am assuming that it is not automatically able to resolve 'gds_db' name on Android since the TCP socket service name is not defined on Android. On Desktop platforms like Windows, Linux, macOS, the InterBase installer updates the system services file to provide the translation of 'gds_db' name to 3050. Just providing a TCP socket port number is a failproof way to target an endpoint without need for name resolution.
Database=192.168.1.58/3050:C:\Users\Public\Documents\Embarcadero\Studio\21.0\Samples\data\employee.gdb
I have a COM+ application consisting of a client DLL and many middle-tier DLLs.
The application gets run by using an MSC application file.
When I am in die IDE and run my client DLL, I have the following run parameters to launch, run and debug my client DLL (this works great):
The theory is that I should be able to debug my middle-tier by running the DLL with the following parameters (I get the ProcessID from my COM+ Application in Component Services):
Once it is running, I should then be able to start my client MSC application and that should allow me to attach and debug my middle tier. I have seen this working before.
Running my Client DLL from the IDE or as an MSC application works without issues but when I try to debug my middle-tier, as described above, I get a "The RPC server is unavailable" error.
I am running everything locally so I am not sure what server it is referring too.
I have also made sure the following services are up-and-running:
DCOM Server Process Launcher, Remote Procedure Call (RPC) and RPC Endpoint Mapper
Any idea what else could cause this error or what server it is trying to connect too?
It turns out there were more than 1 version of the DLLs registered on my pc. I inherited the pc from a previous employee and noticed some install files of the application on the C drive (all my stuff is on the E drive). I ran the uninstall procedure on the C drive that also unregistered some DLLs and my RPC problem was resolved.
I have some delphi applications with connection to Firebird database by FireDAC technology. It works fine, but after Windows 10 update 1803, cannot connect to database when I call application stored in network path (example: \comp1\share\myapp.exe or Q:\myapp.exe, Q: is mapped server path). Error status is 335544721 with illegal parameter.
The same build of application stored on local path works fine. Can anybody help Me?
I've got the same problem!! The reason is the Firebird version 1.5.x (maybe 2.5 too?). Windows Update 1803 blocks the communication between client and server. The only solution is to migrate to Firebird 3.0.x (or to uninstall the update - not a really good option).
I had the same problem with my delphi application I developed a couple years ago, after an update to windows 10 in one of my machines it suddenly drops the connection to the firebird server (2.50 in superserver mode) installed on a windows 7 host, while my other hosts (win xp, win 2003, win 7 and 8.1) connects normally, when I ping or telnet to the server adresse from win10 (telnet 192.168.1.X 3050) the connection establishes, I have tried everything like enabling Smbv1 and disabling v2 and v3, run it under a VM (win 7) machine inside win10 I was surprised to not being able to connect too, then I realised that it wasn't a network hardware configuration problem, but for unexplained reasons WINDOWS DEFENDER, I just disabled it and then my app was able to connect.
And don't rely on firebird's returned error messages they don't discribe the real issue, and can mislead you.
I forgot to mention that I did enabled some services before disabling win defender, wich were disabled after windows update 1803:
Set both Function Discovery Services to Automatic and Start Them
SSDP Discovery set to automatic.
UPnP Device Host set to automatic.
I have a Cordova-Ionic application on Visual Studio (Microsoft Visual Studio Community 2015, Version 14.0.25123.00 Update 2). I am able to run the app on my android phone and all is good. I want to test the app by also running it on an iPhone/iOS simulator.
I have OS X El Capitan (version 10.11.6) running as a VM on virtual box. I have been following this guide (https://taco.visualstudio.com/en-us/docs/ios-guide/) to try to test the app on apple devices. I have installed version 0.12.9 Node.js and Xcode Version 8 Beta 4. I have also installed xcode command line tools, remote agent, homebrew. I have tried running 'remotebuild test' in a terminal and it executes successfully, ending with 'taco-remote test passed.' However, this is where the problems start.
To attempt to use secure remotebuild, i run 'remotebuild certificates reset' and then 'remotebuild certificates generate' in the terminal. I see
host: noyolks-iMac.local
port: 3000
PIN: 121422
I then run 'remotebuild'. On visual studios on my windows machine, I then go to tools -> options -> tools for apache cordova -> iOS configuration. I set 'Enable remote iOS processing' to 'true', 'host' to 'noyolks-iMac.local', 'port' to '3000', 'secure mode' to 'true', 'security pin' to '121422'. However, when i press ok, i see the following error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
I try using the IP instead in place of the host name as suggested in the guide. On OS X, i go system preferences -> network. I then see '10.0.2.15' under IP address. I go back to my windows machine. I try '10.0.2.15' in place of the 'host'. When i press ok, i see the following error popup 'An error occurred trying to acquire certificate from https://10.0.2.15.'.
Please note, I ensured that all the above was done within the 10 minutes window before the security pin expires.
Following the guide, I then tried to start the remote agent without secure mode. I run 'remotebuild --secure false'. Once again on visual studio on my windows machine, i try host 'noyolks-imac.local' first (with 'port' to '3000', 'enable remote iOS processing' to 'true', 'secure mode' to 'false') and i get the error popup 'Unable to connect to remote iOS build server. Underlying exception: The remote name could not be resolved: 'noyolks-imac.local''.
Once again, running without secure mode, i instead use the ip address in place of the host '10.0.2.15'. I get the error popup 'Unable to connect to remote iOS build server. Underlying exception: Unable to connect to the remote server'.
I have also tried a similar procedure using a friends mac book pro and have not been able to get this to work. Any help would be appreciated and please do feel free to ask for any other information you might need.
Thanks.
I'm an idiot. The problem was that I couldnt even ping my El Capitan VM. Changing the network adapter settings in virtualbox to 'bridged adapter' solved this.
Alright, I was tasked to develop a Windows Service that listens to a directory for files that are dropped in it, read them, delete them and print out a report.
I installed the service on my work laptop (Win 7 x86) and a test machine (XP x86) under a User account at first. It would do everything as it should except the print the report. No errors, nothing. Then I made it run under Local System and it produced a "No printers found" exception.
Converting the app to a Console Application and running on these machines gave the desired result. OK, so now I was assuming that there are security "stuff" involved.
Then I installed the service on a Server 2008 x64 machine (under Local System) and it just worked. Can anybody explain to me why this is happening? Why does the service allow printing from Server OS but not from a Desktop OS or am I missing something very obvious?
I'm guessing that the printers are installed locally on the server but installed as network printers on the desktop. Local System only have access to local printers.