02:19:27 PM
3HL0UOHLG
The application path determines where wc.dll is loaded from. IOW, if you're accessing wc.dll directly and not via script map the application's Web path determines where wc.dll and wc.ini will be read from.
If you use script maps then that doesn't matter - wc.dll/.ini can live anywhere for that as long as the script entry points at it.
+++ Rick ---
Never mind -- ha, ha
there is a wwwroot\wconnect\wc.ini folder and I changed that. My cas9000Server wc.ini is in the wwwroot\jkt9000\wconnect\ folder. Seems odd, though, that it would use the wrong wc.ini file????
Kevin
I guess I installed webConnection 5 on this machine also and it seems to be trying to fire up the wcDemo app instead of the 4x cas9000Server app. They are in separate folder in wwwroot with their own wc.dll -- but there seems to be a cross mis-firing!
Does this explain it any better?
Kevin
Server1: ClassID for wcDemo.wcDemoServer not found. Err code = 800401f3: Invalid class string
I tried to run my machine in com mode today and I am getting this error. It has run in com mode just fine before -- it is a Vista machine. I am not sure where the "wcDemo.wcDemoServer" is coming from -- the server name should be webjkt9000.cas9000Server.
I did try and do the /regserver thing again -- no help, though.
Any insights would be helpful (incites, too).
Kevin
West Wind Technologies
Making waves on the Web
from Maui, Hawaii