Hello All,

A while back someone on this list was asking about some Win 2003
server problems with FlashComm. It seems that when we upgraded to Win
2003, certain features of some apps went south and some of the
browsers (FireFox, Safari, Opera) would not work with some of the apps.

This problem has cropped up again on an app that works in everything
except Windows 2003. I get an error in the application.asc: line 99

TypeError:Client.__RESPONSE__ has no properties.

(In the SS code application.asc is loaded.) Line 99, just in case you
don't recall, reads:

99    client.__RESPONSE__[listener.__LID__] = true;

Were it not for the fact that the app works fine testing it in other
environs, I would not be concerned, but the app only fails in Windows
2003.

TIA for any ideas where to solve this problem.
Bill


bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

I've had no such experiences and I currently run Win2K3 with the
agh-tech server
a

> Hello All,
>
> A while back someone on this list was asking about some Win 2003
> server problems with FlashComm. It seems that when we upgraded to Win
> 2003, certain features of some apps went south and some of the
> browsers (FireFox, Safari, Opera) would not work with some of the apps.
>
> This problem has cropped up again on an app that works in everything
> except Windows 2003. I get an error in the application.asc: line 99
>
> TypeError:Client.__RESPONSE__ has no properties.
>
> (In the SS code application.asc is loaded.) Line 99, just in case you
> don't recall, reads:
>
> 99    client.__RESPONSE__[listener.__LID__] = true;
>
> Were it not for the fact that the app works fine testing it in other
> environs, I would not be concerned, but the app only fails in Windows
> 2003.
>
> TIA for any ideas where to solve this problem.
> Bill
>
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

aYo,

So, you're saying that you're not running into any problems with the
Win 2003 server. On most of my apps that I use on the Win 2003
server, I'm not either.

However, with this particular app, I am. Moreover, it's only the Win
2003 server and all others work fine.

Do you have any idea as to why that may happen only on Win 2003?

Thanks,
Bill

On Jun 26, 2005, at 9:31 AM, _a wrote:

> I've had no such experiences and I currently run Win2K3 with the
> agh-tech server
> a
>
> 
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>

bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

Bill,
Have you tried capitaLising the  client.
If the method was set as a prototype then I guess *client *would throw
up errors because* Client* is the correct class designate. On the other
hand it may be that  *client* was sent to the application.onConnect
method as *Client *and you have set the variable to *client.
*I have not seen the code so I'm fishing here, funny though that it
works wel in the test environment.

a
**

> aYo,
>
> So, you're saying that you're not running into any problems with the
> Win 2003 server. On most of my apps that I use on the Win 2003
> server, I'm not either.
>
> However, with this particular app, I am. Moreover, it's only the Win
> 2003 server and all others work fine.
>
> Do you have any idea as to why that may happen only on Win 2003?
>
> Thanks,
> Bill
>
> On Jun 26, 2005, at 9:31 AM, _a wrote:
> 
>
> bill sanders | www.sandlight.com | bloomfield, ct | 860-242-2260
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]

aYo,

It works in both the test environment (Windows XP + Apache server)
and on a Linux server. It's pretty well isolated to the Windows 2003
server -- also I checked to make sure that all of the test
environments and the versions of FCS are the same.

As I said initially, some others on this list were having certain
issues that are peculiar to the Win 2003 server, and I'm wondering if
they have found any way to make the appropriate fixes.

Thanks,
Bill

PS: In your room.

On Jun 26, 2005, at 9:56 AM, _a wrote:

> Bill,
> Have you tried capitaLising the  client.
> If the method was set as a prototype then I guess *client *would
> throw up errors because* Client* is the correct class designate. On
> the other hand it may be that  *client* was sent to the
> application.onConnect method as *Client *and you have set the
> variable to *client.
> *I have not seen the code so I'm fishing here, funny though that it
> works wel in the test environment.
>
> a
> **
>
> 
>
>
> =-----------------------------------------------------------
> Supported by Fig Leaf Software - http://www.figleaf.com
> =-----------------------------------------------------------
>
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcomm
>


=-----------------------------------------------------------
Supported by Fig Leaf Software - http://www.figleaf.com
=-----------------------------------------------------------

To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcomm

[ Post a follow-up to this message ]