Am I the only one having problems with Win13?
Is it working fine now after an IIS reset but I’m afraid this will be happen again.
Could you please let us know what’s the problem on that server? Seeing the threads at the forum, it has seem to give a lot of problems already.
Thank you very much.
Win13 had an error that one of the techs restarted IIS to resolve, IIS had not been restarted in some time.
[QUOTE=Stephen]
Win13 had an error that one of the techs restarted IIS to resolve, IIS had not been restarted in some time.
[/QUOTE]
Stephen, I’m having problems with this server since yesterday. Right now I’m still getting connection reset errors.
Could you please explain what is going on?
I am using it with no issue, can you please let me know your domain. I will check the pool and monitor the code in that pool.
Sure, I’ll send you a PM.
Just to let you know, I created a new account that went to Win18, I uploaded a zip file there on a test folder and uncompressed it in less than 1 minute from the WebShell application.
The same test on my current account at Win13 never finished, the file uncompressing process always took several minutes and hanged up with a connection reset message. So, I believe there is something inherently wrong with that server.
Could just be different PHP memory limits, I gave win17 and win18 some higher limits 
Win13 is on the default 8MB, win17 and win18 have been moved to 16MB
If you think that explains why in Win18 it took less than a minute and at Win13 more than 10, that’s ok. I find it hard to understand, but could you update Win13 to 16MB aswell and I do the test?
I sent you a PM with my domain.
Thank you very much.
If it times out it explains, asked you some questions via PM and will see what I get
win13 IS at its fastest point possible going to be a bit slower than win15/16/17/18/19 and soon win20, as they are all (except win16 it is Xeon), AMD Opteron servers with u320 SCSI raid arrays, Win13 is SATA. We have moved to the new platform just for this reason We spent more per server for everyone to have better service. For a while we went with SATA following reviews, specs etc saying how comparable it was to SCSI, but in our own testing it is simply not close. I am not going to continue on this topic, I think you are capable of understanding that
[QUOTE=Stephen]
If it times out it explains, asked you some questions via PM and will see what I get
win13 IS at its fastest point possible going to be a bit slower than win15/16/17/18/19 and soon win20, as they are all (except win16 it is Xeon), AMD Opteron servers with u320 SCSI raid arrays, Win13 is SATA. We have moved to the new platform just for this reason We spent more per server for everyone to have better service. For a while we went with SATA following reviews, specs etc saying how comparable it was to SCSI, but in our own testing it is simply not close. I am not going to continue on this topic, I think you are capable of understanding that
[/QUOTE]
I’m capable of understand that, but I’d like to add something. The problem was not an application timeout but a connection reset. I really don’t know if it’s the same, but the error was a connection reset window in Firefox and not a timeout error from the server application.
I have not seen that, even with the issues before.
but thanks for the info.
I gave you the info for why your site is timing out on webshell and having problems on win13.
Just as a FYI for others, check your FTP Quota(NOT your disk quota they are different).
[QUOTE=Stephen]
I gave you the info for why your site is timing out on webshell and having problems on win13.
Just as a FYI for others, check your FTP Quota(NOT your disk quota they are different).
[/QUOTE]
Right on! It seems that was it. At least I hope so…