| Author |  Topic  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 22 March 2013 :  12:27:22     
 |  
                      | Below are some error messages I am receiving after being moved to a new server along with some replies from hosting. I am trying to get them to see that  an image uploaded last week prior to the move will not upload now.  And, they are blaming the Snitz files.  I've explained that my files worked fine prior to the move but after their persistence in my asking the Snitz developers, that's what I am doing.  What should I tell these guys?! 
 All of these error messages were received when trying to upload a 1.5mb file.  However; I received the same error with a 875kb file. A small 35kb file loads instantly.  (The server timeout for attachments is set at the default 9900 seconds.)
 
 Internal Server Error
 The server encountered an internal error or misconfiguration and was unable to complete your request.
 
 Hosting reply:  I tried changing the 'maxRequestLength' and 'executionTimeout' for your domain in the web.config file.
 
 However, this did not make any changes to the issue.
 
 ____________________
 
 
 The connection was reset
 
 The connection to the server was reset while the page was loading.
 
 Hosting reply:  The connection time-out error that you are receiving is not due to upload limit.
 
 This happens because the script tries to upload the image and it waits for a certain period of time and the script itself times out.
 
 I have increased the connection time-out value of asp pages for your domain to 300 seconds [5 minutes ].
 
 However this didn't fix the issue. I have looked into the code of your website and I could see several values inside the code which is the cause of the timeout.
 
 
 _______________________________
 
 
 Another hosting reply in regard to trying to upload the same image:  Currently we are facing a "Connection timed out" error instead of an 'Internal server error' while uploading files.
 
 I have edited the website configuration file by adding the 'sessionState timeout' and 'maxRequestLength' similar to that mentioned in the following URL.
 
 http://stackoverflow.com/questions/6435409/error-101-neterr-connection-reset-the-connection-was-reset
 
 However, these changes have not made any changes to the issue. So I have reverted back all the changes.
 
 Also, as mentioned by our previous tech, I noticed so many codes related to the 'Server TimeOut' in the file "outputFile.asp".
 
 Please discuss the same with the forum software developer as we have limited support for such issues. Moreover, the forum software developer could assist you better than us for such issues.
 
 ___________________
 
 
 Another error message when trying to upload the same image.  It took TEN minutes to receive this error message:
 
 
 The connection was reset
 
 The connection to the server was reset while the page was loading.
 
 The site could be temporarily unavailable or too busy. Try again in a few moments.
 
 They suggested I allow them to move me to a new server because they could never get the email to work for the forum and claimed this new server had better ASP support.  Well, the email works but now all of this!
 
 Other than changing hosting, any other suggestions?
 
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  | 
              
                | AnonJrModerator
 
      
 
                United States5768 Posts
 | 
                    
                      |  Posted - 22 March 2013 :  12:36:09       
 |  
                      | Semi-random question, did the permissions get moved as well? Theoretically if it was a permissions problem it would be giving you a permissions-related error message, but sometimes it's worth investigating other problem areas. |  
                      |  |  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 22 March 2013 :  13:07:56     
 |  
                      | If the directory wasn't given the proper permissions no files could be uploaded, right?  Very small files can be uploaded without problems.
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  
                      |  |  | 
              
                | AnonJrModerator
 
      
 
                United States5768 Posts
 | 
                    
                      |  Posted - 25 March 2013 :  10:57:23       
 |  
                      | That's correct - if the directory wasn't given the proper permissions, no files would be uploaded. 
 How small is "very small", and have you tried different sizes to figure out where the script stops uploading?
 |  
                      |  |  | 
              
                | HuwRForum Admin
 
      
 
                United Kingdom20611 Posts
 |  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 25 March 2013 :  11:43:15     
 |  
                      | I did try to determine at what point the script stops uploading.  However; I am now receiving the following error message, at times, when just trying to refresh whatever page I happen to be on while on one of the forums.  So, obviously, it's not limited to times when uploading an image.
 
 And then, at times, it's an "Internal Server" error message I receive. I always (since the move) get the "Internal Server" error message when I am in the profile area and click to upload an avatar.
 
 
 The connection has timed out
 
 The server is taking too long to respond.
 
 The site could be temporarily unavailable or too busy. Try again in a few moments.
 
 
 All of my files worked fine prior to hosting moving me to the new server.  So, don't you think that means it's definitely a hosting problem with the new server?
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  
                      |  |  | 
              
                | HuwRForum Admin
 
      
 
                United Kingdom20611 Posts
 |  | 
              
                | HuwRForum Admin
 
      
 
                United Kingdom20611 Posts
 |  | 
              
                | HuwRForum Admin
 
      
 
                United Kingdom20611 Posts
 |  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 25 March 2013 :  12:05:55     
 |  
                      | quote:Originally posted by HuwR
 Would be interested to see what they think is the cause
  
 
 I don't think they have a clue, Huw!
  
 So very  frustrating to say the least!
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  
                      |  |  | 
              
                | CarefreeAdvanced Member
 
      
 
                Philippines4224 Posts
 | 
                    
                      |  Posted - 25 March 2013 :  20:36:20     
 |  
                      | The issue is that the FileSystemObject is not enabled on the server.  The web host is incompetent.  I told them (through Ma) precisely what was necessary to enable it - and they claimed to have followed the instructions -- but it's not working.  To test this, I wrote the following little program and instructions for her to run.  When she ran it, guess what?  She still got the "Internal Server Error (500)" page result. 
 
 quote:The FSO System stands for "File System Object" - it's what allows you to programmatically read/write files on a hard drive over the web.  Edit the first line of code below to reflect a folder in your forum with write permission granted to the IUSR account, save the code as "fsotest.asp" to your root forum folder, then run it from your browser.  If it creates a link which opens a new text file saying "Test File" on one line, then the FSO system is working.  If you still get the "Internal Server Error (500) message, then the FSO system is NOT working.
 
 Very simply - here's how it works:
 
 Line 1 defines the folder and file name you wish to create or write to.
 Line 2 tells it to open access to the file read/write utility in IIS (provided that it's enabled and the directory has write permissions for the IUSR account).
 Line 3 defines the file path name as related to the physical location on the hard drive where the forum folder is stored.
 Line 4 checks if the file already exists.
 Line 5 -7 tells it to either append to an existing file or create a new one, depending on the result of line 4.
 Line 8 tells it to write a single line of text to that file.
 Lines 9-11 close access to the file and to the file read/write utility.
 Line 12 creates a hyperlink to the new file to check if it worked (assuming that error reporting to the browser is disabled, you'll need a method of verification).
 
 
 
 |  
                      |  |  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 26 March 2013 :  01:06:42     
 |  
                      | 
 I can hardly wait to hear what they say about that, Carefree.  It's already been over a week now since the move!
 
 
 I shouldn't be surprised that I am having problems with their Horde email, too.  Receiving this error message below.
 
 There was an error sending your message: unable to connect to smtp server localhost:25
 
 
 I don't know how companies like this stay in business!
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  
                      |  |  | 
              
                | CarefreeAdvanced Member
 
      
 
                Philippines4224 Posts
 | 
                    
                      |  Posted - 26 March 2013 :  04:01:41     
 |  
                      | They end up getting lots of free advice from people like us, just enough to claim they're "improving" to their victims (aka customers). |  
                      |  |  | 
              
                | MaGrahamSenior Member
 
     
 
                USA1297 Posts
 | 
                    
                      |  Posted - 26 March 2013 :  12:17:32     
 |  
                      | I sure do feel victimized  in many ways!
 
 
 |  
                      | "Do all the good you can, by all the means you can, in all the ways you can, at all the times you can, to all the people you can, as long as ever you can." -  John Wesley
 |  
                      |  |  | 
              
                | Doug GSupport Moderator
 
      
 
                USA6493 Posts
 | 
                    
                      |  Posted - 26 March 2013 :  19:34:31     
 |  
                      | If you're on a shared server it's not unusual for fso to be disabled.  Allowing the fso object can open some security issues in a shared environment. 
 Also turn off friendly error reporting in your web browser and perhaps you'll see more detailed error info.
 
 |  
                      | ======
 Doug G
 ======
 Computer history and help at www.dougscode.com
 |  
                      |  |  | 
              
                | CarefreeAdvanced Member
 
      
 
                Philippines4224 Posts
 | 
                    
                      |  Posted - 27 March 2013 :  03:07:23     
 |  
                      | My browsers definitely have "friendly error reporting" disabled, yet I get the same pages that she does.  Her browser isn't the issue, the host has set it to "custom error messages", hence the 500 pages.  I wrote her step-by-step instructions to pass on to them, hopefully they'll follow them. |  
                      |  |  | 
              
                
                |  Topic  |  |