Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Catastrophic failure calling client
Message
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01142442
Message ID:
01142474
Views:
7
Rick,
What do you mean by "explicit reference to the client"?
>Catastrophic Failure usually means the server proxy has disconnected or otherwise lost in some way. It's essentially the generic remote error that COM uses.
>
>Callbacks may not work the same way as on a local machine - you need to make sure the server has an explicit reference to the client. Two way communication over DCOM is very tricky to get right.
>
>+++ Rick ---
>
>>I am getting the following:
>>OLE error code 0x8000ffff: Catastrophic failure.
>>when a remote server does callback to the client.
>>Here is the callback method:
>>
>>
>>LPARAMETERS toMachine
>>LOCAL lcSql
>>
>>TEXT TO lcSql TEXTMERGE NOSHOW
>>	usp_UpdateReadings '<<toMachine.ReadFromScanner.pcLastReading>>',
>>	<<toMachine.pnMachineRegistrationId>>, <<toMachine.pnUserId>>
>>ENDTEXT	
>>IF This.mExecuteSqlCommand(lcSql, '', '') >= 1
>>	*!* Update client monitors with new read
>>	This.poCallingObj.mExecuteCommand(toMachine)
>>ELSE
>>	*!* If SQL has returned an error, dont call Client
>>ENDIF	
>>
>>Where This.poCallingObj has a referance to the client.
>>Any idea, please?
>>
>>Thanks
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform