ISAPI Webinator on IIS 5 issue

Post Reply
jon-paul
Posts: 15
Joined: Wed Jul 21, 2004 12:36 pm

ISAPI Webinator on IIS 5 issue

Post by jon-paul »

Hi guys!

I've been trying to implement the latest Webinator on IIS 5 (production server) but the dll does not seem to want to load (red arrow in IIS). Obviously calls to port 10700 aren't functioning either. The Error in the event log:
---------------------
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 14
Date: 12/7/2006
Time: 11:22:22 AM
User: N/A
Computer: IS07106
Description:
The HTTP Filter DLL C:\WINNT\system32\inetsrv\TexisISAPI.dll failed to load. The data is the error.
For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
Data:
0000: 7e 00 00 00 ~...

---------------------------
I've been successful in implementing it under IIS6 in my development environment.

I've done just about everything but remove everything and reinstall. I was installing over a previous 5.1 version (non isapi, obviously). CGI portion works fine under IIS 5 - so I'm still afloat.

Any ideas as to what I can do?

Thanks!
User avatar
John
Site Admin
Posts: 2622
Joined: Mon Apr 24, 2000 3:18 pm
Location: Cleveland, OH
Contact:

ISAPI Webinator on IIS 5 issue

Post by John »

First thing is to get the port 10700 working. Are there any messages in the monitor.log file that would indicate problems?
John Turnbull
Thunderstone Software
jon-paul
Posts: 15
Joined: Wed Jul 21, 2004 12:36 pm

ISAPI Webinator on IIS 5 issue

Post by jon-paul »

here's the last couple lines...

--------------

200 2006-12-07 11:21:41 (824) Texis Monitor version 05.00.1092695634 starting
200 2006-12-07 11:21:41 (824) Generating default Webinator license
200 2006-12-07 11:21:41 (824) Starting Dispatcher in the function SVmain
200 2006-12-07 11:21:41 (824) Got Handle 1413784 in the function ServiceMain
200 2006-12-07 11:21:41 (804) Database Monitor on E:\Program Files\Thunderstone Software\texis\testdb starting
200 2006-12-07 11:21:41 (824) Contacting license server
200 2006-12-07 11:21:41 (824) Successful reply from license server
200 2006-12-07 11:21:44 (824) Got Message 1 in the function ServiceHandler
200 2006-12-07 11:21:45 (804) Database Monitor on E:\Program Files\Thunderstone Software\texis\testdb exiting
200 2006-12-07 11:21:45 (824) Started Dispatcher in the function SVmain
200 2006-12-07 11:21:45 (824) Texis Monitor exiting
200 2006-12-07 11:22:05 (1932) Texis Monitor version 05.01.1160077904 starting
200 2006-12-07 11:22:06 (540) Database Monitor on E:\Program Files\Thunderstone Software\texis\testdb starting
200 2006-12-07 11:25:24 (1208) Database Monitor on E:\Program Files\Thunderstone Software\texis\default\db1 starting
000 2006-12-07 11:30:33 (1932) Cannot find file E:\Program Files\Thunderstone Software\htdocs\ requested by 192.168.100.50: No such file or directory
000 2006-12-07 11:30:37 (1932) Cannot find file E:\Program Files\Thunderstone Software\htdocs\ requested by 192.168.100.50: No such file or directory
000 2006-12-07 11:30:49 (1932) Cannot find file E:\Program Files\Thunderstone Software\htdocs\ requested by 127.0.0.1: No such file or directory
200 2006-12-07 11:31:24 (1208) Database Monitor on E:\Program Files\Thunderstone Software\texis\default\db1 exiting

-------

I'm starting to think a uninstall/reinstall is in order just to clear up any confusion from the previous install...
User avatar
jason112
Site Admin
Posts: 347
Joined: Tue Oct 26, 2004 5:35 pm

ISAPI Webinator on IIS 5 issue

Post by jason112 »

7e means a dll that TexisISAPI depends on wasn't found.
I'm willing to bet it's the updated C runtime (msvcr71.dll), although a free dependency walker can tell you for sure (http://www.dependencywalker.com/)

Try copying the "msvcr71.dll" file from webinator's installation directory into your windows\system32 folder and see if that helps. If not, the dependency walker will be needed to see exactly what isn't found.


the fact that port 10700 isn't listening is a separate issue (and also needs resolved, that's what TexisISAPI talks to). Are there things uncommented in the [Httpd] section of the "texis.cnf" file in your installation directory?
jon-paul
Posts: 15
Joined: Wed Jul 21, 2004 12:36 pm

ISAPI Webinator on IIS 5 issue

Post by jon-paul »

Looking through the dependency walker, it's barking about MSVCP71.DLL...It CAN find msvcr71.dll just fine...

Doing a search for that file on the system reveals it's tied to a CISCO SECURITY AGENT which we have installed and I'm now guessing that it's blocking the TexisISAPI.dll from working.

I'll check with my infrastructure team and see if I'm right.
User avatar
jason112
Site Admin
Posts: 347
Joined: Tue Oct 26, 2004 5:35 pm

ISAPI Webinator on IIS 5 issue

Post by jason112 »

not at all, texisisapi.dll actually depends on msvcp71.dll itself, which it can't find. There have been occasional random reports of people missing this file, despite the fact that all our boxes here seem to have it. What OS & service pack are you running?

I'm guessing msvcp71.dll exists somewhere else on your
file system? Try copying it into your system32 folder.
jon-paul
Posts: 15
Joined: Wed Jul 21, 2004 12:36 pm

ISAPI Webinator on IIS 5 issue

Post by jon-paul »

Okay...

Windows Server 2000 sp4

Found the file in the Cisco Security Agent folder (go figure) and copied it over the system32 and restarted IIS...

Everything's working now!

It's a Christmas miracle!! :)

Thanks guys! Always a pleasure getting support from ThunderStone!
User avatar
jason112
Site Admin
Posts: 347
Joined: Tue Oct 26, 2004 5:35 pm

ISAPI Webinator on IIS 5 issue

Post by jason112 »

Ok, our win2k sp4 boxes already had that file, and the other customer with this problem was on a 2k3 sp1 box. We'll try tracking down some information from Microsoft to let us determine when we can depend on he file being present, and we'll adjust the installer accordingly.

Glad to hear it's working.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

ISAPI Webinator on IIS 5 issue

Post by mark »

Sounds like Cisco includes that dll for that very reason, it can't be relied on to exist.
Post Reply