Desaware Home
Products    Purchase    Publishing    Articles   Support    Company    Contact    
Support
Product FAQ
Licensing System
CC Factory
Event Log Toolkit
Gallimaufry
IniFile Tool-5M
LineGraph-5M
NT Service Toolkit
OneTime Download
SpyWorks
StateCoder
StorageTools
VBX Legacy
VersionStamper
Downloads
Documentation
Professional Services

 

bluebar
Contact Desaware and order today

bluebar
Sign up for Desaware's Newsletter for the latest news and tech tips.

NT Service Toolkit Support

Frequently Asked Questions - Remote Automation

  1. How do I raise events from service objects to clients that are accessing the service remotely?
  2. My Service was working fine, but after I recompiled my Service EXE, I cannot remotely access the exposed objects.
  3. Creating client objects seem to result in memory leaks.
  4. Trouble creating client objects in Terminal Server.

1. How do I raise events from service objects to clients that are accessing the service remotely?

Refer to the article Raising Events from Remote DCOM Objects using the NT Service Toolkit


2. My Service was working fine, but after I recompiled my Service EXE, I cannot remotely access the exposed objects.

Be sure that you also recreate the VBR file and distribute that along with your new Service EXE file when you recompile your Service EXE. Each time a Service EXE is created, the Service Configuration Wizard creates a new GUID for the exposed objects.


3. I am exposing a client object from my service, this seems to result in a memory leak when they are created.

Be sure you are using the latest service template file, then rebuild your Service EXE to fix this problem.

Another thing you might be seeing is the initial thread pool allocation. Exposing the client object for creation has a little overhead the first time, the overhead size is dependent on the thread pool size specified.

You can also contact Desaware and we can email you the latest files.


4. My Service is attempting to create an instance of another object but is getting an error. I am running in Terminal Server.

This may be a result of a documented Microsoft issue with DCOM and Terminal Server. For more information and a possible solution, please refer to:

http://support.microsoft.com/support/kb/articles/Q187/1/46.ASP


 
Products    Purchase    Articles    Support    Company    Contact
Copyright© 2012 Desaware, Inc. All Rights Reserved.    Privacy Policy