Hello Rick and everyone,
Some of the users of our website are getting a COM Server Execution Error during the server method call indicating that a specific variable is not found.
But we can brows the same pages without any issue on the same browsers and similar environments! So it was too hard to replicate the issue but finally we got it and it's like after clearing the history everything goes back to normal also we don't get the error if we brows it in "Chrome Incognito" mode for instance.
We have had these line in our template pages since the first day so we assume No Caching should be taken care of!

<!-- Added: No caching -->
    <meta http-equiv="cache-control" content="no-cache" />
    <meta http-equiv="cache-control" content="no-store" />
    <meta http-equiv="cache-control" content="must-revalidate" />    
    <meta http-equiv="cache-control" content="max-age=0" />
    <meta http-equiv="cache-control" content="post-check=0" />
    <meta http-equiv="cache-control" content="pre-check=0" />
    <meta http-equiv="pragma" content="no-cache" />
    <meta http-equiv="expires" content="-1" />
    <%
        Response.AddForceReload()
    %>

Also, when I click on the “Com Server Execution Error” on the Admin page, I see this message:

The Com server threw an exception during the server method call: wwmaint.wcdllerrorlog c:\wconnect7\classes\wwmaint.prg Error in line 789 Class definition WWRESPONSESTRINGNOBUFFER is not found. 1733

Would you think these two could be related. And how can I fix the second error any ways?

And I don't know if this can be related or not but the only thing I've done recently is that I've updated Webconnect 7.0 to the latest version on the development area but not on the live machine.

I do appreciate your ideas on these.
Thanks,
Kathy

The DLL log error has been fixed in recent versions... you maybe seeing a difference between your live and dev versions.

The other issue - not sure, but I'd think the problem here is that you're getting different values based on the cached behavior.

+++ Rick ---

This is really helpful.
Thank you so much Rick.

Sorry Rick,
For updating our live web server we assume that we should just replace all the w*.dll files on the website with the latest version.
And everything else should be taken care of by the normal update.
Could you please confirm?
Thanks.

The wwMaint log issue is a FoxPro server issue in the wwMaint.prg library. That was fixed but in order to see that you need to build your app and redeploy it.

In general for server updates you should replace

• web\bin\webconnectionmodule.dll (or wc.dll if you're using ISAPI)
• deploy*.dll from \wconnect*.dll

The latter are all the .NET and wwipstuff related DLLs and while they rarely change it's a good idea to update them when you update Web Connection versions.

+++ Rick ---