Asking for help and/or suggestions here.
I am trying to configure IIS 7.0 (Vista, WinServer 2008) to work with 
WAA1GATE.ISA.  The setup is completely different from that for IIS 6.0. 
Now, in addition to "ISAPI and CGI Restrictions" (formerly "Web Service 
Extension"), there are "Handler Mappings" and "Modules", which I do not 
comprehend.  I imagine the solution is a couple of setup entries, but I have 
not hit upon the magic words.  I learned yesterday Alaska-Software does not 
have a clue about how to handle this.  They would like me to fund their 
research.  I thought, why not ask the smart people myself?  Any constructive 
suggestions into this issue will be most appreciated.
Many thanks,
Bruce Anderson

Hi, Bruce. Thanks for raising this. Kind of surprising that this 
compatibility with current IIS has not been addressed. I was considering a 
new waa-based project on the assumption that this compatibility was there, 
but if not then i have to reconsider.

In a previous post, I believe i mentioned that I finally got the exe version 
of the gateway working with iis 7 after a lot of grief, but ran out of time 
and could not spend any more time trying to get the [preferred] isa version 
working.

lcc.



Unfor
"Bruce Anderson" <banderson@graphical-db.com> wrote in message 
news:33ad2927$282d9063$b34@news.alaska-software.com...
> Asking for help and/or suggestions here.
> I am trying to configure IIS 7.0 (Vista, WinServer 2008) to work with 
> WAA1GATE.ISA.  The setup is completely different from that for IIS 6.0. 
> Now, in addition to "ISAPI and CGI Restrictions" (formerly "Web Service 
> Extension"), there are "Handler Mappings" and "Modules", which I do not 
> comprehend.  I imagine the solution is a couple of setup entries, but I 
> have not hit upon the magic words.  I learned yesterday Alaska-Software 
> does not have a clue about how to handle this.  They would like me to fund 
> their research.  I thought, why not ask the smart people myself?  Any 
> constructive suggestions into this issue will be most appreciated.
> Many thanks,
> Bruce Anderson

Through a friend of a friend, I managed to connect to a member of the 
Microsoft team which developed IIS 7.0, and he has been helping me through 
the WAA setup.  We made good progress.  After employing his two semi-secret 
configuration lines, I have it "kind of working".  However, WAA1SRV.EXE 
immediately blows up on a socket read error when the first POST arrives:
    e:operation: Socket read error
    e:thread: 3
    CGICHANNEL:COMPLETECONNECT(188)
    BEGINTRANSACT(440)
    SERVEJOB(282)
    SERVEJOBPROTECTION(208)
I have sent the error file and the CFG files to Andreas Herdt asking if this 
is something Alaska-Software can fix or even point to the area that needs to 
be researched.  My guy at Microsoft is standing by, waiting for the next 
task.
Alaska's response...they have told me I need to renew my professional 
subscription, price: US$1,489.00.  And then they can talk about it.
I have offered to sell Alaska-Software the heretofore unknown configuration, 
direct from my inside source at Microsoft, price: US$ 1,489.00. My offer 
expires at close of business today.
We shall see.

Hello Bruce,

> Alaska's response...they have told me I need to renew my professional 
> subscription, price: US$1,489.00.  And then they can talk about it.

Why am I not surprised about Alaska's business behaviour? It's the mindset 
of the software architect that is showing up here. (Andreas Herdt has 
nothing to do with it).

It is interesting to see that the price for the professional subscription 
renewal has raised from $US 1,029.00 (2004) to $US 1,489.00 (2008). That's a 
remarkabale price increase of around 45% within four years only. Is Alaska's 
software bound to the oil price? Wondering...

WAA is distributed for free since its first day. Alaska's request for a $US 
1.489 purchase prior to technical support on a free product is more than 
questionable. Looks like the days of a free WAA are gone. Maybe it's time to 
change ...

Regards,
--
Hannes

http://www.knowleXbase.com

PS: If you want me to take a close look at your problem, please respond via 
private mail.


"Bruce Anderson" <banderson@graphical-db.com> schrieb im Newsbeitrag 
news:1493916e$7d292a1a$167@news.alaska-software.com...
> Through a friend of a friend, I managed to connect to a member of the 
> Microsoft team which developed IIS 7.0, and he has been helping me through 
> the WAA setup.  We made good progress.  After employing his two 
> semi-secret configuration lines, I have it "kind of working".  However, 
> WAA1SRV.EXE immediately blows up on a socket read error when the first 
> POST arrives:
>    e:operation: Socket read error
>    e:thread: 3
>    CGICHANNEL:COMPLETECONNECT(188)
>    BEGINTRANSACT(440)
>    SERVEJOB(282)
>    SERVEJOBPROTECTION(208)
> I have sent the error file and the CFG files to Andreas Herdt asking if 
> this is something Alaska-Software can fix or even point to the area that 
> needs to be researched.  My guy at Microsoft is standing by, waiting for 
> the next task.
> Alaska's response...they have told me I need to renew my professional 
> subscription, price: US$1,489.00.  And then they can talk about it.
> I have offered to sell Alaska-Software the heretofore unknown 
> configuration, direct from my inside source at Microsoft, price: US$ 
> 1,489.00. My offer expires at close of business today.
> We shall see.
>