|
|
Posted by shimmyshack on 03/06/07 17:09
On Mar 6, 2:39 pm, "Steve" <no....@example.com> wrote:
> "LiquidEyes" <n...@liquideyes.net> wrote in message
>
> news:45ed73d4$1_1@mk-nntp-2.news.uk.tiscali.com...
> |> have you tried it using forward slashes
> |
> | Thanks for the suggestion, however I tried that and it made no difference.
> | As far as I'm aware, it's okay to use backslashes in php.ini (in fact the
> | comments seem to suggest this is correct).
> |
> | > the Apache manual
> | > specifically states that all slashes in the conf should face forward,
> |
> | Indeed, all the paths in my httpd.conf file do use forward slashes.
> |
> | Any more ideas? I'm completely stuck at the moment. :(
>
> usually it's to do with directory/file permissions on windows servers. does
> IUSR_<computer name> have permissions to wrx the extension dir and the
> dll's?
if you're running apache but not as a special user, have you checked
that the module version is consistent with the version of php you are
running,
you might for instance have decided to run php as a module and might
have chosen to run a later version...
If I were you I would grab filemon from sysinternals on the microsoft
site and run it while apache is trying to load the extnesion, if you
can see that the paths are correct in filemon - that apache is getting
module and yet you still get the erro, then perhaps it is a version
clash.
At least you can get odd errors like this when you use a newer module
than the version of php you are running, or vice versa etc..
Navigation:
[Reply to this message]
|