At the very least, this should be good for a laugh, although it's no longer
funny to me...
I'm using VB6 code to compile and COM+ application that listens for RDS
calls to it. The client application does the normal
Dim myObj As Variant
Dim varObj as Variant
Set myObj = CreateObject("RDS.Dataspace")
myObj.InternetTimeOut = 60000
Set varObj = myObj.CreateObject(COMAPPNAME & "." & ClassName,
SERVERNAME)
intReturn = varObj.myFunction(string, string, string, ADODB
Disconnected
Recordset)
When the server name does NOT have http: attached to it, one call succeeds
and one almost duplicate call fails.
When the server name DOES have http: attached to it, one call fails and
one
call succeeds.
This works for both DNS names (simple) and IP addresses, but not full
domain
Internet DNS names when happening locally.
Anything happening from off-server fails altogether, though the client
believes that it's not the firewall.
The COM+ application is running as a domain administrator and RDS is (it
seems) active. Adding the ADCLaunch Key for the object and public class
made
it start working (as described above).
Has anyone seen any scenarios like this before? Is there something else
to
do? This solution works fine on all of the development and cold test
servers
we have.
--------------------------------------
P.E.B.C.A.K.
Problem Exists Between Chair And Keyboard
|
