1

I have configured my computer for remote debugging: I have the Visual Studio solution and projects on my development computer and the testing is about to happen on a remote testmachine.

On the testmachine, the entire installation procedure has been executed, and everything is working fine. The remote debugger is launched, the options mention no authentication being needed, allowing any user to debug. This is working fine. On the development machine, I've prepared everything for remote debugging, and indeed, starting the application on the remote machine is working fine, as can be retrieved from the following screenshot:

Debugging screenshot

I can confirm that the mentioned process ID (11176) is indeed the PID of the corresponding process on the remote testmachine.
On the development machine, there is no process with that process ID.

The following line is giving an access violation:

ILicPtr lic = ILicPtr(CLSID_Lic);

That pointer is defined in a *.tlh file, as follows: _COM_SMARTPTR_TYPEDEF(ILic, __uuidof(ILic));

The value of CLSID_Lic equals {07BA438E-D124-4A78-892F-125B0FC5A98A} and is found in the registry of the testmachine, at following locations in registry:

HKEY_CLASSES_ROOT\Company.License.BusinessRules.Lic\CLSID => Default
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{07BA438E-D124-4A78-892F-125B0FC5A98A}
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Company.License.BusinessRules.Lic\CLSID => Default
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{07BA438E-D124-4A78-892F-125B0FC5A98A}
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{07BA438E-D124-4A78-892F-125B0FC5A98A}

For your information: if I try to run the application on the testmachine without debugging, everything works fine.

What's wrong with that line and how can I get over this?

3
  • 2
    ILicPtr(CLSID_Lic) would fall down to _com_ptr_t::CreateInstance which in turn use COM's CoCreateInstance (src is in Microsoft Visual Studio\18\Professional\VC\Tools\MSVC\14.50.35717\include\comip.h or similar) and possibly OleRun (does your object implements IRunnableObject?) and that's it. After that it can be a proxy stub problem. Do you have a custom one? When it works, is it running in-process or out-of-process? Commented Feb 6 at 14:54
  • Wow6432Node - so it's registered as a 32-bit object - is that what it should be? Commented Feb 6 at 15:33
  • @500-InternalServerError: yes, that's correct. Commented Feb 9 at 8:47

0

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.