Remotable(?) .WSCs over DCOM twixt NT 4.0 & 98SE angst... 
Author Message
 Remotable(?) .WSCs over DCOM twixt NT 4.0 & 98SE angst...

OK, it's an NT domain/intranet with all Win 98SE stations + DCOM98 and
RPCSS.EXE running!

Identical VBScript 5.5 components properly registered on NT Server and
client.

DCOMTEST thingy from MS checks out OK, both ways.

In a test script/HTA, CreateObject("Component.MyComponent", "myserver")
works fine calling from
98(COM as client) --> NT(COM as server).  Going the other way I get

 0x1AD, "ActiveX component can't create object."

Event log pops up a Type 10006, "DCOM got error "Server execution failed "
from..."

"Have read documentation until brain hurts", etc.  I understand that the
server app must
be running on a Win9x machine before a client can connect to it, but...

Question: how exactly does one keep a .WSC scriptlet ...'running'???  Huh?

Immense gratitude in advance.

Jeff Morris




Sun, 11 May 2003 03:00:00 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. VB 4.0 32-bit & NT 4.0 compatibility

2. VB 4.0 32-bit & NT 4.0 Compatibility

3. NT 4.0 File Security & VB 4.0

4. Communication 'twixt client & server

5. AdobePS 5.0 for NT 4.0 & Linotronic output

6. GradienrtFill & AnimateWindow in 98SE

7. WSH on NT 4.0 Server without IE 4.0 (5.0)

8. System Tray & NT 4.0

9. Installation Diff between 95 & NT 4.0

10. MSCOMM32.OCX & NT 4.0 Workstation

11. User & GDI Resources in Win95 / NT 4.0

12. Two NT 4.0 problems : GetModuleHandle (&Crystal)

 

 
Powered by phpBB® Forum Software