Information générale
Catégorie:
COM/DCOM et OLE Automation
Titre:
The DLL doesn’t get activated by the client
I’m having a very strange problem.
I’ve created a DLL (VFP7) which I put in a server (W2000Svr) folder, together with vfp7t.dll and TLB and VBR files. The DLL doesn’t use the MTXAS.APPSERVER.1 object.
Then, using the Control Panel, I’ ve created an Application under:
Component Services-Computers-My Computer-COM+ Application.
The dll is then called from a client computer by and .EXE (still located in a server folder, accessed through a mapped drive). The .EXE uses the CreateobjectEX() function, to retrieve data via ODBC and return it in XML format.
Everything seems good and the application does his job.
From time to time the server needs to be restarted. When restarted, the EXE does no more activate the DLL and, of course, no data is returned.
It becomes necessary (simply) to access the control panel of the server, then scroll down AdministrativeTools-Component Services-Computers-My Computer-COM+ Application. Drill down MyApplication. From this time on, all of the clients in the network are able to run the exe and access the data.
The settings of the application are those suggested by default:
- Security: Perform access check at the process and component level. Authentication level for calls: PACKET. Impesonation level: IMPERSONATE
- Identity: Interactive user – the current logged on user
- Activation: Server application
- Advanced: 3 Minutes until idle shutdown
The settings of my dll inside the Application are:
- Security: Enforce component level access chechs
- Activation: Enable Just in time activation; Component supports events and statistics
- Concurrency: Required
Can someone tell me what to try to avoid the problem?
TIA
Bruno Maddalozzo
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement