I have been pulling my hair out for a few days here. Here is my problem. I have a site running IIS, Win 2k, MS-SQL 2k
I am using ODBC functions to connect to the database. It works fine on my local machine (same config except I have XP pro) But when I put it into clients machine it has some strange issues which i have never seen before.

If a page takes a long time to execute it craps out and only displays half the page. It is definately random where it stops because it will serve up varrying amounts of HTML everytime I hit refresh. SOmetimes it will even display the entire page. I checked php.ini for the timeout settings. The seemed normal. When the page loads it normally takes a maximum of 5 seconds to fully load, definately not approaching the 60 second timeout. Also I checked IIS settings and they were all at the defaults from installing IIS fresh. I also checked this on varrying internet connections and machines, so it is not an issue with my internet or browser.

    Heads up to anyone using IIS.

    I had a function which utilized the split function Http://www.php.net/split

    If you pass split an empty string with PHP on a windows machine it will throw a "memory could nto be read" error. I added an empty string check in the code and my page started being displayed normally.

    Also I read in another forum that you should always initialize any associative arrays before using them on windows

    example:

    $ar=array();

    as this can cause that same "memory could not be read" error. I did this also.... damn I hate windows:mad:

      Write a Reply...