teeChart6.ocx Hangs IIS in ASP application.
Re: teeChart6.ocx Hangs IIS in ASP application.
This leaves us in a bit of a dillemma because we moved to version 7.0.1.4 to resolve the paged pool memory exhaustion problem. Now this customer has resolved their hang, but has reintroduced the previous problem. Do you think you will be able to identify what the change was between 7.0.1.1 and 7.0.1.4 that reintroduced the hang characteristic which was present in teeChart 6? It would be great if we could get a patched 7.0.1.4 ocx.
Re: teeChart6.ocx Hangs IIS in ASP application.
Hello,
Thanks, that's useful to know. There were several changes through v7.0.1.1. to v7.0.1.4. (ie. http://www.steema.com/files/activex/pub ... elease.txt). Would it be possible to test versions 7.0.1.2 and 7.0.1.3 for us to limit further the modifications made? Is the earlier problem that the client is experiencing with version 7.0.1.1. paged pool memory exhaustion? How do the symptoms show up for that?
Regards,
Marc
Thanks, that's useful to know. There were several changes through v7.0.1.1. to v7.0.1.4. (ie. http://www.steema.com/files/activex/pub ... elease.txt). Would it be possible to test versions 7.0.1.2 and 7.0.1.3 for us to limit further the modifications made? Is the earlier problem that the client is experiencing with version 7.0.1.1. paged pool memory exhaustion? How do the symptoms show up for that?
Regards,
Marc
Steema Support
Re: teeChart6.ocx Hangs IIS in ASP application.
Marc,
Sorry for the slow reply. Somehow I missed the email notification.
>>There were several changes through v7.0.1.1. to v7.0.1.4. (ie. http://www.steema.com/files/activex/pub ... elease.txt). >>Would it be possible to test versions 7.0.1.2 and 7.0.1.3 for us to limit further the modifications made?
I will check with the customer to see if they are willing to do this.
>>Is the earlier problem that the client is experiencing with version 7.0.1.1. paged pool memory exhaustion? How do the symptoms show up for that?
We did have serveral customers that ran into the paged pool memory exhaustion (PPM) with version 7.0.1.1 (but I don't think this customer was one of them). The symtom that was always reported with PPM was an explicit storage error on the browser. The PPM problem was never associated with a web server hang.
Dave
Sorry for the slow reply. Somehow I missed the email notification.
>>There were several changes through v7.0.1.1. to v7.0.1.4. (ie. http://www.steema.com/files/activex/pub ... elease.txt). >>Would it be possible to test versions 7.0.1.2 and 7.0.1.3 for us to limit further the modifications made?
I will check with the customer to see if they are willing to do this.
>>Is the earlier problem that the client is experiencing with version 7.0.1.1. paged pool memory exhaustion? How do the symptoms show up for that?
We did have serveral customers that ran into the paged pool memory exhaustion (PPM) with version 7.0.1.1 (but I don't think this customer was one of them). The symtom that was always reported with PPM was an explicit storage error on the browser. The PPM problem was never associated with a web server hang.
Dave
Re: teeChart6.ocx Hangs IIS in ASP application.
The customers response to testing the 7.0.1.2 and 7.0.1.3 versions is:
Since we have been unable to reproduce this problem anywhere except our production environment, I am unwilling to try this. I do not have the time or resources right now to handle any troubleshooting and cannot take further impact to our production environment at this time of the year.
Re: teeChart6.ocx Hangs IIS in ASP application.
Marc,
What is the status of this issue?
Thanks, Dave
What is the status of this issue?
Thanks, Dave
Re: teeChart6.ocx Hangs IIS in ASP application.
Hello Dave,
There were several changes between v7.0.1.1. and v7.0.1.4, some of which should not have any bearing on this issue but there is one area relating to COM ObjRelease that may be relevant. Changes were made before 7011 that caused problems for some application types, and were then corrected (largely removed) for v7.0.1.2. Knowing test results for 7012 would help us understand to what extent those changes were relevant.
We could build a v7.0.1.4 to test changes for your environment, but then tests would need to be made; is there any non-production environment available, that closely mimicks the customer environment, in which to be able to make those tests? If the customer is not experiencing problems with v7.0.1.1 then perhaps, as version 7 is no longer subject to on-development, might it be satisfactory to leave the customer at that version?
Regards,
Marc
There were several changes between v7.0.1.1. and v7.0.1.4, some of which should not have any bearing on this issue but there is one area relating to COM ObjRelease that may be relevant. Changes were made before 7011 that caused problems for some application types, and were then corrected (largely removed) for v7.0.1.2. Knowing test results for 7012 would help us understand to what extent those changes were relevant.
We could build a v7.0.1.4 to test changes for your environment, but then tests would need to be made; is there any non-production environment available, that closely mimicks the customer environment, in which to be able to make those tests? If the customer is not experiencing problems with v7.0.1.1 then perhaps, as version 7 is no longer subject to on-development, might it be satisfactory to leave the customer at that version?
Regards,
Marc
Steema Support