Dcom working on the client(suppose to work work on the server)
-
I have build a dcom that update data on a db. the dcom sits on the server and so is the db. i'm registering the server as : "\\computer_name\dcom.exe" /regserver some how, the dcom who suppose to work on the server is working on the client, so he search for the db on the client and not over the server. what should i do? any code will be great, i can send the code to you. please .. i'm so :confused: . thanks, /// (.)_(.) oOO(.)OOo
-
I have build a dcom that update data on a db. the dcom sits on the server and so is the db. i'm registering the server as : "\\computer_name\dcom.exe" /regserver some how, the dcom who suppose to work on the server is working on the client, so he search for the db on the client and not over the server. what should i do? any code will be great, i can send the code to you. please .. i'm so :confused: . thanks, /// (.)_(.) oOO(.)OOo
> i'm registering the server as : > "\\computer_name\dcom.exe" /regserver This does not tell COM to instantiate the COM server on computer_name, but rather to retrieve the disk file that houses the server from computer_name. COM does so and then instantiates the COM server on the local machine using the bits from the disk file located on computer_name. The quickest way to achieve what you want is to register the COM server locally, then use dcomcnfg to modify the registration for instantiating on computer_name. The soundest way to achieve what you want is to use CoCreateInstanceEx() to create the COM server and directly tell COM to instantiate the COM service on computer_name. This way, your configuration can't be botched after installation by misuse of dcomcnfg. It would be a good idea to study any indroductory DCOM text book for details. Also search MSDN for dcomcnfg and CoCreateInstanceEx.
-
I have build a dcom that update data on a db. the dcom sits on the server and so is the db. i'm registering the server as : "\\computer_name\dcom.exe" /regserver some how, the dcom who suppose to work on the server is working on the client, so he search for the db on the client and not over the server. what should i do? any code will be great, i can send the code to you. please .. i'm so :confused: . thanks, /// (.)_(.) oOO(.)OOo
Hi Hush, You may be registering the exe on your machine rather than the remote machine. You need to run "dcom.exe /regserver" from the client and FROM the server. This can not be done remotely (as far as I know?). I have come across this problem often enough to include the following code in the remote classes to tell me where it is running. // *************************************************************************** //DESCRIPTION: // Return the machine name of the machine running this code. //PARAMS: // *pbsrtMachine Name returned here //RETURN: // Standard HRESULT //CREATED: // 1-2-2001, 16:51:31 by john@mctainsh.com // *************************************************************************** STDMETHODIMP CWhereAmI::GetMachine(BSTR *pbstrMachine) { ATLTRACE( _T("CWhereAmI::GetMachine(%p)\n"), pbstrMachine ); ATLASSERT( pbstrMachine ); USES_CONVERSION; //Get my name DWORD dwComputerNameLength = MAX_COMPUTERNAME_LENGTH + 1; TCHAR szComputerName[MAX_COMPUTERNAME_LENGTH + 2]; if( GetComputerName( szComputerName, &dwComputerNameLength ) ) szComputerName[dwComputerNameLength] = NULL; else _tcscpy( szComputerName, _T("Unknown") ); *pbstrMachine = SysAllocString( T2W( szComputerName ) ); return S_OK; } --------------------------------------------------- I have a note on DCOM remoting at http://www.mctainsh.com/COM/SmartPtr3.aspx The hardest thing I find is getting security correct. Let me know how you get on... Have a great day! http://www.mctainsh.com