Bill,

 

Install the server normally, but make sure you run the installer in XP-SP3
compatibility mode. Start it up and read the witangoevents.log to ensure
that the server is running properly.

 

Now, in IIS 7.5. Open the IIS Manager.

 

You have to make sure that you have the ISAPI module installed, this isn't
by default. You should see feature controls for Handler Mappings and ISAPI
and CGI Restrictions - if not, use the Windows features to install "ISAPI
Extensions"

 

Open the ISAPI and CGI Restrictions (on the server) and add one for Witango
- the default path is: 

C:\Program Files\WitangoServer\5.5\PlugIns\witango55_iis.dll

And check the "Allow extension path to execute" option. (I called mine
"Witango")

 

Next, open the Handle Mappings (on the website) and add an entry for *.taf
for the same path.

 

Now, under the Application pool, click on the default pool and open the
advanced settings. Change the parameter "Enable 32-bit applications" to
True. (this is probably only necessary if your Windows 7 is 64-bit)

 

Restart the website or IIS and you should be good.

 

I really should've taken better notes when I set this up myself last week.
I'm now completely converted over Windows 7 and have both the studio and the
server running without any showstoppers (although there are a few annoying
interface issues). If this still leaves you hanging, let me know what error
you get.

 

Robert

 

PS. If you try to install the studio, again be sure to run the installer in
XP-SP3 mode and if you system is like mine, you'll be missing 4 ddls which
you'll have to drag over from your old system - if you are running windows 7
64-bit these go in the SYSWOW64 folder, otherwise right into the system32
folder.

 

 

From: Bill Downall [mailto:[email protected]] 
Sent: Tuesday, April 13, 2010 4:33 PM
To: Witango-Talk
Subject: Witango-Talk: Witango Dev Server on Win 7 laptop / IIS 7.5

 

Please help! I'm trying to get Witango Development Server 5.5.020 running in
IIS on a Windows 7 laptop. 

 

I have a "Handler Mapping" named Witango, for the 4 Witango file extensions.

 

I have tried in a "Classic mode" application pool named Witango, and in the
DefaultAppPool "Integrated"

 

If I put in an ISAPI FILTER pointing to witango55_iis.dll, I get an error
500, Calling GetProcAddress on ISAPI filter
"c:\inetpub\wwwroot\scripts\witango55_iis.dll" failed. If I remove the ISAPI
FILTER, and just have the Handler Mapping, then it tries to save a TAF file
to disk. If I have a MIME type associated with Witango Studio, then it
suggests opening the file in Witango Studio. 

 

The Witango Service is running, and the witango logs don't show anything
unusual. No license errors or anything like that.

 

I'm sure it's something minor, in (this vastly changed since 6.0) IIS 7.5. 

 

Thanks for any pointers.

 

Bill

 

 

 

 

 

 
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to