As Scott said Witango/Tango2000 defaults to System Account permissions. Another way is...
Go to the folder that the dll is installed in and add "System" the list of permissions for folder and files within. Ben Johansen - http://www.pcforge.com Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm Latest downloads & List Archives @ http://www.witango.ws -----Original Message----- From: [EMAIL PROTECTED] [mailto:owner-witango-talk@;witango.com] On Behalf Of Scott Cadillac Sent: Friday, November 01, 2002 8:00 AM To: Multiple recipients of list witango-talk Subject: Re: Witango-Talk: Com Object registration Hi Chuck, If an ASP page can work with the COM, but Witango can't - I might suspect it's a permissions thing. Witango does not automatically inherit the same IIS permissions that ASP have. Try boosting the "Tango 2000 Server" Service permissions. In Windows Services properties dialog for "Tango 2000" check the 'Log on' Account. By default it is the 'Local system account' - try an Admin account of some sort. Hope this helps. Cheers.... ----- Original Message ----- From: "Chuck Lockwood" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Friday, November 01, 2002 8:31 AM Subject: RE: Witango-Talk: Com Object registration > Hey Ben, or anyone else that wants to chime in: > > The t4handlers.ini looks correct. > [COM] > ShortName=COM / DCOM Objects > SupportsScanning=0 > ServerPath=C:\RBTI\RTango2000\W3hcm100.dll > > DLL registration went ok, tried moving the DLL's and registering them in > various places. > My clients system guy wrote a quick ASP app to test, and that works. So the > DLL registration seems to be ok as far as ASP in concerned. Which really > stinks, because they love to blame everything on Witango! > > I'm trying to avoid a try this, try that exchange with the my clients system > guy, so I need a checklist of things that may be causing the problem. > > How does the objects.ini fit in? At all? > Would tango require a reboot after COM registration? (ASP didn't) > Any other system switches that may be the issue? > > Thanks, again and again and again ..... > > Chuck Lockwood > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > LockData Technologies, Inc. > 309 Main Avenue, Hawley, Pa 18428 > 570-226-7340 ~ Fax: 570-226-7341 > [EMAIL PROTECTED] ~ www.lockdata.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:owner-witango-talk@;witango.com]On Behalf Of Ben Johansen > Sent: Thursday, October 31, 2002 6:22 PM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: Com Object registration > > > Hi Chuck, > > No, you don't need a line for each dll > > I just had to change the current ServerPath= line > > FROM > ServerPath=.\W3hcm100.dll > TO > ServerPath=c:\PVSW\Tango2000\W3hcm100.dll > > I really think it has to do with Windows permissions and security. There > was a web hack called "dot walking" and there were fixes published which > closed this hole > > I also made sure the the COM dll file was installed in the same folder > on both dev and productions machines > > Did you use the REGSVR32 program to register the dll? > > > Ben Johansen - http://www.pcforge.com > Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm > Latest downloads & List Archives @ http://www.witango.ws > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:owner-witango-talk@;witango.com] On Behalf Of Chuck Lockwood > Sent: Thursday, October 31, 2002 2:56 PM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: Com Object registration > > Thanks Ben, > > >I had to setup ServerPath=c:\folder\folder\dllfile.dll > > Does each specific DLL need to be listed here? Or just the path? > Neither is on my dev platform, but they work?? > > Is there any documentation about the objects.ini and the t4handlers.ini > anywhere? > > (I know, so many questions)! > > Thanks again, > > Chuck Lockwood > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > LockData Technologies, Inc. > 309 Main Avenue, Hawley, Pa 18428 > 570-226-7340 ~ Fax: 570-226-7341 > [EMAIL PROTECTED] ~ www.lockdata.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:owner-witango-talk@;witango.com]On Behalf Of Ben Johansen > Sent: Thursday, October 31, 2002 5:14 PM > To: Multiple recipients of list witango-talk > Subject: RE: Witango-Talk: Com Object registration > > > Ok, > > In your t4handlers.ini on the server. > Check to see if the ServerPath is using physical path instead of .\ path > I had to setup ServerPath=c:\folder\folder\dllfile.dll > From ServPaht=.\dllfile.dll > > Give this a try. > > Ben Johansen - http://www.pcforge.com > Authorized Witango Reseller http://www.pcforge.com/WitangoGoodies.htm > Latest downloads & List Archives @ http://www.witango.ws > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:owner-witango-talk@;witango.com] On Behalf Of Chuck Lockwood > Sent: Thursday, October 31, 2002 1:05 PM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: Com Object registration > > On my development machine (win 2000), I installed and registered a com > object and was able to access it in the editor and the completed taf > works > perfectly. There is no reference to the com object in the t4handler.ini > > On the production machine (win 2000), there is no editor installed, the > com > object registration worked, but the taf will not find it! "Cannot > access > handler. The specified object instance could not be created." > > Am I missing a needed step when the editor is not installed? Do I need > to > do something in the t4handler.ini? > > Thanks for any and all guidance, > > Chuck Lockwood > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > LockData Technologies, Inc. > 309 Main Avenue, Hawley, Pa 18428 > 570-226-7340 ~ Fax: 570-226-7341 > [EMAIL PROTECTED] ~ www.lockdata.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
