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).

---

<%
strPath="uploads/testfile.txt"
Set objFSO = Server.CreateObject("Scripting.FileSystemObject")
FilePath=Server.Mappath(strPath)
If objFSO.FileExists(FilePath) Then
    Set objTextStream = objFSO.OpenTextFile(FilePath, 8) '    Appending
Else   
    Set objTextStream = objFSO.OpenTextFile(FilePath, 2) '    Writing (Creation)
End If
objTextStream.WriteLine("This is a test.")
objTextStream.Close
Set objTextStream = Nothing
Set objFSO = Nothing
Response.Write "<a href=""" & strPath & """>Test File</a>"
%>

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!

quote:

---

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.

---

quote:

---

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?

---