Re: PHP on NT Problem: "Resource id #1file opened.."
| From: | Rasmus Lerdorf | Date: | Tue, 27 Jun 2000 18:37:18 +0000 |
| Subject: | Re: PHP on NT Problem: "Resource id #1file opened.." | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-3393@lists.php.net to get a copy of this message | ||
Sounds like you left some debug code in your script. If you put this:
echo $fp;
echo "file opened"
Then that is what you would see.
-Rasmus
On Tue, 27 Jun 2000, Waldo L. Jaquith wrote:
> Folks,
>
> A client of mine (a Fortune 500 that sees PHP as a test case) has installed
> PHP on their brand-new NT4 box. I don't know (sorry, I can't get in touch
> with somebody who knows) what version, but I assume it to be 4.0.0, as it
> was just installed this week.
>
> A very simple program that we've written (forces the browser to download a
> text file as a TSF for use in Excel) isn't working on the new server. When
> the form data is submitted (a date range), the following is printed:
>
> ----
> Resource id #1file opened..
> Warning: Cannot add header information - headers already sent by (output
> started at F:\wwwroot\orders\index.php3:70) in F:\wwwroot\orders\index.php3
> on line 100
>
> Warning: Cannot add header information - headers already sent by (output
> started at F:\wwwroot\orders\index.php3:70) in F:\wwwroot\orders\index.php3
> on line 101
> ----
>
> I'm certainly familiar with the warnings. It's "Resource id #1file
> opened.." that worries me. "#1file"? ".."? An error with typos in
> it has
> all the signs of a Microsoft error. I assume that the warnings are the
> result of this line being echoed.
>
> So the question is, what the heck is causing this error? (Or is it an
> error?) I've got an @ in front of the fopen, so that should shut it up, in
> case this is some weird idle remark being made by NT. I'm not quite sure of
> what to do, but the client wants an answer now. The obvious ("It's a
> Windows error, we can't help you") won't help them, and it won't help us.
> No matter what is causing the problem, they'll see it as a PHP problem, and
> we can't have that.
>
> Anybody have any ideas? I've run out of resources. Thanks, folks.
>
> Best,
> Waldo
>
> Waldo L. Jaquith
> < waldo@munkandphyber.com >
> < 804/979.2980 >
> // Munk & Phyber
> // 110B Second Street NE
> // Charlottesville, VA 22902
>
>
>