php.ini set up problem

Paul Herber wrote:
> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
> wrote:
>
>
>>Hi,
>>
>>I am very new to PHP I am having php.ini problems. I am working in XP
>>with IIS and have php installed as an ISAPI. I am trying to change
>>values in my php environment like 'upload_tmp_dir',
>>'upload_max_filesize'. I have scanned my computer and the only php.ini
>>file on the machine is in C:\Program Files\PHP. If I change entries in
>>that php.ini file and run phpinfo() it appears that the values are not
>>getting updated. This is still true after I start and stop the IIS server.
>>
>>Also the phpinfo() reports my path to the php.ini file is c:\windows,
>>but there is no php.ini file in that directory. If I copy the php.ini
>>file to c:\windows and restart the server, then php breaks.
>
>
> What do you mean by 'php breaks'? What does/doesn't it do?
> The fact that putting the php.ini file in c:/windows affects operation
> certainly proves that that is the correct place for it. Put a standard
> php.ini file here then sort out problems from there.
>
>
>
Thanks

I put the standard file that came with the install there. So it should
not have been corrupted but who knows. So I agree it looks like it was
going through its list of places to find the php.ini file and found
somthing in the windows directory. I seem to have gotten PHP to now read
the php.ini file (atleast partially) in the windows directory by doing a
php uninstall and a reinstall of php. This time I put it in a C:\PHP
directory as opposed to the installer default c:\Program Files
directory. Seems like other people have it working in Program Files.
When it was not workin I would get a short message in my browser that
said somethin like it could not make the reference call, no error
number. Sorry, I can not remember the exact message.

Thanks
Mike

mike wrote:
> Paul Herber wrote:
>
>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>> wrote:
>>
>>
>>> Hi,
>>>
>>> I am very new to PHP I am having php.ini problems. I am working in XP
>>> with IIS and have php installed as an ISAPI. I am trying to change
>>> values in my php environment like 'upload_tmp_dir',
>>> 'upload_max_filesize'. I have scanned my computer and the only
>>> php.ini file on the machine is in C:\Program Files\PHP. If I change
>>> entries in that php.ini file and run phpinfo() it appears that the
>>> values are not getting updated. This is still true after I start and
>>> stop the IIS server.
>>>
>>> Also the phpinfo() reports my path to the php.ini file is c:\windows,
>>> but there is no php.ini file in that directory. If I copy the php.ini
>>> file to c:\windows and restart the server, then php breaks.
>>
>>
>>
>> What do you mean by 'php breaks'? What does/doesn't it do?
>> The fact that putting the php.ini file in c:/windows affects operation
>> certainly proves that that is the correct place for it. Put a standard
>> php.ini file here then sort out problems from there.
>>
>>
>>
> Thanks
>
> I put the standard file that came with the install there. So it should
> not have been corrupted but who knows. So I agree it looks like it was
> going through its list of places to find the php.ini file and found
> somthing in the windows directory. I seem to have gotten PHP to now read
> the php.ini file (atleast partially) in the windows directory by doing a
> php uninstall and a reinstall of php. This time I put it in a C:\PHP
> directory as opposed to the installer default c:\Program Files
> directory. Seems like other people have it working in Program Files.
> When it was not workin I would get a short message in my browser that
> said somethin like it could not make the reference call, no error
> number. Sorry, I can not remember the exact message.
>
> Thanks
> Mike

Now I remember:

The remote procedure call failed

Mike

mike wrote:
> Paul Herber wrote:
>
>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>> wrote:
>>
>>
>>> Hi,
>>>
>>> I am very new to PHP I am having php.ini problems. I am working in XP
>>> with IIS and have php installed as an ISAPI. I am trying to change
>>> values in my php environment like 'upload_tmp_dir',
>>> 'upload_max_filesize'. I have scanned my computer and the only
>>> php.ini file on the machine is in C:\Program Files\PHP. If I change
>>> entries in that php.ini file and run phpinfo() it appears that the
>>> values are not getting updated. This is still true after I start and
>>> stop the IIS server.
>>>
>>> Also the phpinfo() reports my path to the php.ini file is c:\windows,
>>> but there is no php.ini file in that directory. If I copy the php.ini
>>> file to c:\windows and restart the server, then php breaks.
>>
>>
>>
>> What do you mean by 'php breaks'? What does/doesn't it do?
>> The fact that putting the php.ini file in c:/windows affects operation
>> certainly proves that that is the correct place for it. Put a standard
>> php.ini file here then sort out problems from there.
>>
>>
>>
> Thanks
>
> I put the standard file that came with the install there. So it should
> not have been corrupted but who knows. So I agree it looks like it was
> going through its list of places to find the php.ini file and found
> somthing in the windows directory. I seem to have gotten PHP to now read
> the php.ini file (atleast partially) in the windows directory by doing a
> php uninstall and a reinstall of php. This time I put it in a C:\PHP
> directory as opposed to the installer default c:\Program Files
> directory. Seems like other people have it working in Program Files.
> When it was not workin I would get a short message in my browser that
> said somethin like it could not make the reference call, no error
> number. Sorry, I can not remember the exact message.
>
> Thanks
> Mike

I got the new installation to break. The old installation was in the
c:\Program Files\PHP\ directory. When I placed the php.ini file in the
c:\windows directory PHP broke. I was getting an error message that
said "The remote procedure call failed "

When I reinstalled I installed to the c:\PHP\ directory. I placed the
php.ini file back in C:\windows and all was well. Then I noticed using
phpinfo() that the extension_dir was set to C:\Program Files\PHP, which
was now a none existant directory. So I changed the value in php.ini to
point to C:\PHP, the new directory. PHP immedialy choked again giving
the same "The remote procedure call failed " errors. When I changed the
extension_dir back to C:\Program Files\PHP, al was well again.

Im not sure what is going on but I think something is wrong with the
extension directory. If php makes a call to an existing extension
directory it dies. However if the directory does not exist, then it lives.

Just a guess anyway. However, the scripts I have written are so simple
I am not sure why php would look in the extension directory anyway.


Mike

Jerry Stuckle wrote:
> mike wrote:
>
>> mike wrote:
>>
>>> Paul Herber wrote:
>>>
>>>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>>>> wrote:
>>>>
>>>>
>>>>> Hi,
>>>>>
>>>>> I am very new to PHP I am having php.ini problems. I am working in
>>>>> XP with IIS and have php installed as an ISAPI. I am trying to
>>>>> change values in my php environment like 'upload_tmp_dir',
>>>>> 'upload_max_filesize'. I have scanned my computer and the only
>>>>> php.ini file on the machine is in C:\Program Files\PHP. If I change
>>>>> entries in that php.ini file and run phpinfo() it appears that the
>>>>> values are not getting updated. This is still true after I start
>>>>> and stop the IIS server.
>>>>>
>>>>> Also the phpinfo() reports my path to the php.ini file is
>>>>> c:\windows, but there is no php.ini file in that directory. If I
>>>>> copy the php.ini file to c:\windows and restart the server, then
>>>>> php breaks.
>>>>
>>>>
>>>>
>>>>
>>>> What do you mean by 'php breaks'? What does/doesn't it do?
>>>> The fact that putting the php.ini file in c:/windows affects operation
>>>> certainly proves that that is the correct place for it. Put a standard
>>>> php.ini file here then sort out problems from there.
>>>>
>>>>
>>>>
>>> Thanks
>>>
>>> I put the standard file that came with the install there. So it
>>> should not have been corrupted but who knows. So I agree it looks
>>> like it was going through its list of places to find the php.ini file
>>> and found somthing in the windows directory. I seem to have gotten
>>> PHP to now read the php.ini file (atleast partially) in the windows
>>> directory by doing a php uninstall and a reinstall of php. This time
>>> I put it in a C:\PHP directory as opposed to the installer default
>>> c:\Program Files directory. Seems like other people have it working
>>> in Program Files.
>>> When it was not workin I would get a short message in my browser that
>>> said somethin like it could not make the reference call, no error
>>> number. Sorry, I can not remember the exact message.
>>>
>>> Thanks
>>> Mike
>>
>>
>> I got the new installation to break. The old installation was in the
>> c:\Program Files\PHP\ directory. When I placed the php.ini file in the
>> c:\windows directory PHP broke. I was getting an error message that
>> said "The remote procedure call failed "
>>
>> When I reinstalled I installed to the c:\PHP\ directory. I placed the
>> php.ini file back in C:\windows and all was well. Then I noticed using
>> phpinfo() that the extension_dir was set to C:\Program Files\PHP,
>> which was now a none existant directory. So I changed the value in
>> php.ini to point to C:\PHP, the new directory. PHP immedialy choked
>> again giving the same "The remote procedure call failed " errors. When
>> I changed the extension_dir back to C:\Program Files\PHP, al was well
>> again.
>>
>> Im not sure what is going on but I think something is wrong with the
>> extension directory. If php makes a call to an existing extension
>> directory it dies. However if the directory does not exist, then it
>> lives.
>>
>> Just a guess anyway. However, the scripts I have written are so
>> simple I am not sure why php would look in the extension directory
>> anyway.
>>
>>
>> Mike
>>
>
> Well, to start with, which extensions are you attempting to load?
>
Jerry,

When I installed php the installer gave me the option to load a list of
extensions, I just loaded everything. So my C:\PHP\ext directory is
packed with .dll files. I do not know exactly what php uses, but right
now I probably do not need any of them. All I know is that if I change
the extension_dir from c:\Program Files\PHP\ext (a non-existant
directory) to C:\PHP\ext (an exsisting one) simple PHP scripts die with
"The remote procedure call failed " errors.

I also noticed that the include_path was also wrong so I changed it to
..;c\PHP\PEAR ( again I am not any were near to using PEAR stuff yet).
This change did not seem to break php.

Mike

mike wrote:
> mike wrote:
>> Paul Herber wrote:
>>
>>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>>> wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> I am very new to PHP I am having php.ini problems. I am working in
>>>> XP with IIS and have php installed as an ISAPI. I am trying to
>>>> change values in my php environment like 'upload_tmp_dir',
>>>> 'upload_max_filesize'. I have scanned my computer and the only
>>>> php.ini file on the machine is in C:\Program Files\PHP. If I change
>>>> entries in that php.ini file and run phpinfo() it appears that the
>>>> values are not getting updated. This is still true after I start and
>>>> stop the IIS server.
>>>>
>>>> Also the phpinfo() reports my path to the php.ini file is
>>>> c:\windows, but there is no php.ini file in that directory. If I
>>>> copy the php.ini file to c:\windows and restart the server, then php
>>>> breaks.
>>>
>>>
>>>
>>> What do you mean by 'php breaks'? What does/doesn't it do?
>>> The fact that putting the php.ini file in c:/windows affects operation
>>> certainly proves that that is the correct place for it. Put a standard
>>> php.ini file here then sort out problems from there.
>>>
>>>
>>>
>> Thanks
>>
>> I put the standard file that came with the install there. So it should
>> not have been corrupted but who knows. So I agree it looks like it was
>> going through its list of places to find the php.ini file and found
>> somthing in the windows directory. I seem to have gotten PHP to now
>> read the php.ini file (atleast partially) in the windows directory by
>> doing a php uninstall and a reinstall of php. This time I put it in a
>> C:\PHP directory as opposed to the installer default c:\Program Files
>> directory. Seems like other people have it working in Program Files.
>> When it was not workin I would get a short message in my browser that
>> said somethin like it could not make the reference call, no error
>> number. Sorry, I can not remember the exact message.
>>
>> Thanks
>> Mike
>
> I got the new installation to break. The old installation was in the
> c:\Program Files\PHP\ directory. When I placed the php.ini file in the
> c:\windows directory PHP broke. I was getting an error message that
> said "The remote procedure call failed "
>
> When I reinstalled I installed to the c:\PHP\ directory. I placed the
> php.ini file back in C:\windows and all was well. Then I noticed using
> phpinfo() that the extension_dir was set to C:\Program Files\PHP, which
> was now a none existant directory. So I changed the value in php.ini to
> point to C:\PHP, the new directory. PHP immedialy choked again giving
> the same "The remote procedure call failed " errors. When I changed the
> extension_dir back to C:\Program Files\PHP, al was well again.
>
> Im not sure what is going on but I think something is wrong with the
> extension directory. If php makes a call to an existing extension
> directory it dies. However if the directory does not exist, then it lives.
>
> Just a guess anyway. However, the scripts I have written are so simple
> I am not sure why php would look in the extension directory anyway.
>
>
> Mike
>

Well, to start with, which extensions are you attempting to load?

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

Jerry Stuckle wrote:
> mike wrote:
>
>> Jerry Stuckle wrote:
>>
>>> mike wrote:
>>>
>>>> mike wrote:
>>>>
>>>>> Paul Herber wrote:
>>>>>
>>>>>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am very new to PHP I am having php.ini problems. I am working
>>>>>>> in XP with IIS and have php installed as an ISAPI. I am trying to
>>>>>>> change values in my php environment like 'upload_tmp_dir',
>>>>>>> 'upload_max_filesize'. I have scanned my computer and the only
>>>>>>> php.ini file on the machine is in C:\Program Files\PHP. If I
>>>>>>> change entries in that php.ini file and run phpinfo() it appears
>>>>>>> that the values are not getting updated. This is still true after
>>>>>>> I start and stop the IIS server.
>>>>>>>
>>>>>>> Also the phpinfo() reports my path to the php.ini file is
>>>>>>> c:\windows, but there is no php.ini file in that directory. If I
>>>>>>> copy the php.ini file to c:\windows and restart the server, then
>>>>>>> php breaks.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> What do you mean by 'php breaks'? What does/doesn't it do?
>>>>>> The fact that putting the php.ini file in c:/windows affects
>>>>>> operation
>>>>>> certainly proves that that is the correct place for it. Put a
>>>>>> standard
>>>>>> php.ini file here then sort out problems from there.
>>>>>>
>>>>>>
>>>>>>
>>>>> Thanks
>>>>>
>>>>> I put the standard file that came with the install there. So it
>>>>> should not have been corrupted but who knows. So I agree it looks
>>>>> like it was going through its list of places to find the php.ini
>>>>> file and found somthing in the windows directory. I seem to have
>>>>> gotten PHP to now read the php.ini file (atleast partially) in the
>>>>> windows directory by doing a php uninstall and a reinstall of php.
>>>>> This time I put it in a C:\PHP directory as opposed to the
>>>>> installer default c:\Program Files directory. Seems like other
>>>>> people have it working in Program Files.
>>>>> When it was not workin I would get a short message in my browser that
>>>>> said somethin like it could not make the reference call, no error
>>>>> number. Sorry, I can not remember the exact message.
>>>>>
>>>>> Thanks
>>>>> Mike
>>>>
>>>>
>>>>
>>>> I got the new installation to break. The old installation was in the
>>>> c:\Program Files\PHP\ directory. When I placed the php.ini file in
>>>> the c:\windows directory PHP broke. I was getting an error message
>>>> that said "The remote procedure call failed "
>>>>
>>>> When I reinstalled I installed to the c:\PHP\ directory. I placed the
>>>> php.ini file back in C:\windows and all was well. Then I noticed
>>>> using phpinfo() that the extension_dir was set to C:\Program
>>>> Files\PHP, which was now a none existant directory. So I changed the
>>>> value in php.ini to point to C:\PHP, the new directory. PHP
>>>> immedialy choked again giving the same "The remote procedure call
>>>> failed " errors. When I changed the extension_dir back to C:\Program
>>>> Files\PHP, al was well again.
>>>>
>>>> Im not sure what is going on but I think something is wrong with the
>>>> extension directory. If php makes a call to an existing extension
>>>> directory it dies. However if the directory does not exist, then it
>>>> lives.
>>>>
>>>> Just a guess anyway. However, the scripts I have written are so
>>>> simple I am not sure why php would look in the extension directory
>>>> anyway.
>>>>
>>>>
>>>> Mike
>>>>
>>>
>>> Well, to start with, which extensions are you attempting to load?
>>>
>> Jerry,
>>
>> When I installed php the installer gave me the option to load a list
>> of extensions, I just loaded everything. So my C:\PHP\ext directory is
>> packed with .dll files. I do not know exactly what php uses, but right
>> now I probably do not need any of them. All I know is that if I change
>> the extension_dir from c:\Program Files\PHP\ext (a non-existant
>> directory) to C:\PHP\ext (an exsisting one) simple PHP scripts die with
>> "The remote procedure call failed " errors.
>>
>> I also noticed that the include_path was also wrong so I changed it to
>> .;c\PHP\PEAR ( again I am not any were near to using PEAR stuff yet).
>> This change did not seem to break php.
>>
>> Mike
>>
>
> First thing is to get rid of all of the extensions. You can do that in
> your php.ini file. Then once you get it working, add in only the ones
> you need.
>
> Some of the extensions require external files, i.e. MySQL requires the
> MySQL client libs. That's probably why your installation didn't work
> when you moved your php.ini file.
>
Thanks Jerry,

I commented out all the extensions and changed the extension_dir back to
c:\PHP\ext restarted the server and all is well now. I will have to
learn what each extension does. From the titles it looks like some may
be useful. Eventually I will give learning MySQL a shot so I can bring
those back in then.

mike wrote:
> Jerry Stuckle wrote:
>> mike wrote:
>>
>>> mike wrote:
>>>
>>>> Paul Herber wrote:
>>>>
>>>>> On Sun, 09 Mar 2008 02:38:08 GMT, mike <spammesillt@junkmail.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I am very new to PHP I am having php.ini problems. I am working in
>>>>>> XP with IIS and have php installed as an ISAPI. I am trying to
>>>>>> change values in my php environment like 'upload_tmp_dir',
>>>>>> 'upload_max_filesize'. I have scanned my computer and the only
>>>>>> php.ini file on the machine is in C:\Program Files\PHP. If I
>>>>>> change entries in that php.ini file and run phpinfo() it appears
>>>>>> that the values are not getting updated. This is still true after
>>>>>> I start and stop the IIS server.
>>>>>>
>>>>>> Also the phpinfo() reports my path to the php.ini file is
>>>>>> c:\windows, but there is no php.ini file in that directory. If I
>>>>>> copy the php.ini file to c:\windows and restart the server, then
>>>>>> php breaks.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> What do you mean by 'php breaks'? What does/doesn't it do?
>>>>> The fact that putting the php.ini file in c:/windows affects operation
>>>>> certainly proves that that is the correct place for it. Put a standard
>>>>> php.ini file here then sort out problems from there.
>>>>>
>>>>>
>>>>>
>>>> Thanks
>>>>
>>>> I put the standard file that came with the install there. So it
>>>> should not have been corrupted but who knows. So I agree it looks
>>>> like it was going through its list of places to find the php.ini
>>>> file and found somthing in the windows directory. I seem to have
>>>> gotten PHP to now read the php.ini file (atleast partially) in the
>>>> windows directory by doing a php uninstall and a reinstall of php.
>>>> This time I put it in a C:\PHP directory as opposed to the installer
>>>> default c:\Program Files directory. Seems like other people have it
>>>> working in Program Files.
>>>> When it was not workin I would get a short message in my browser that
>>>> said somethin like it could not make the reference call, no error
>>>> number. Sorry, I can not remember the exact message.
>>>>
>>>> Thanks
>>>> Mike
>>>
>>>
>>> I got the new installation to break. The old installation was in the
>>> c:\Program Files\PHP\ directory. When I placed the php.ini file in
>>> the c:\windows directory PHP broke. I was getting an error message
>>> that said "The remote procedure call failed "
>>>
>>> When I reinstalled I installed to the c:\PHP\ directory. I placed the
>>> php.ini file back in C:\windows and all was well. Then I noticed
>>> using phpinfo() that the extension_dir was set to C:\Program
>>> Files\PHP, which was now a none existant directory. So I changed the
>>> value in php.ini to point to C:\PHP, the new directory. PHP immedialy
>>> choked again giving the same "The remote procedure call failed "
>>> errors. When I changed the extension_dir back to C:\Program
>>> Files\PHP, al was well again.
>>>
>>> Im not sure what is going on but I think something is wrong with the
>>> extension directory. If php makes a call to an existing extension
>>> directory it dies. However if the directory does not exist, then it
>>> lives.
>>>
>>> Just a guess anyway. However, the scripts I have written are so
>>> simple I am not sure why php would look in the extension directory
>>> anyway.
>>>
>>>
>>> Mike
>>>
>>
>> Well, to start with, which extensions are you attempting to load?
>>
> Jerry,
>
> When I installed php the installer gave me the option to load a list of
> extensions, I just loaded everything. So my C:\PHP\ext directory is
> packed with .dll files. I do not know exactly what php uses, but right
> now I probably do not need any of them. All I know is that if I change
> the extension_dir from c:\Program Files\PHP\ext (a non-existant
> directory) to C:\PHP\ext (an exsisting one) simple PHP scripts die with
> "The remote procedure call failed " errors.
>
> I also noticed that the include_path was also wrong so I changed it to
> .;c\PHP\PEAR ( again I am not any were near to using PEAR stuff yet).
> This change did not seem to break php.
>
> Mike
>

First thing is to get rid of all of the extensions. You can do that in
your php.ini file. Then once you get it working, add in only the ones
you need.

Some of the extensions require external files, i.e. MySQL requires the
MySQL client libs. That's probably why your installation didn't work
when you moved your php.ini file.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================