Welcome to WebmasterWorld Guest from

Forum Moderators: coopster & jatar k

Message Too Old, No Replies

Remote Document Root with 5.3.1

9:04 pm on Sep 22, 2011 (gmt 0)

Junior Member

10+ Year Member

joined:May 31, 2006
votes: 0

Hello all,

I've got a unique problem that I'm hoping someone can help me with. It's specific enough that my GoogleFoo is failing me.

We have a requirement to use MSSQL databases from Linux servers, so we need the MSSQL library and, to my knowledge, cannot use the new SQLSRV library. Additionally all of our programs are written with MSSQL functions so changing over would be a pain, though possible if absolutely needed.

I'm also trying to get Apache on Windows 7 to use a remote location (shared drive) as my document root. This is so other developers have access to my code and we have backup jobs running on those drives.

PHP 5.3.1 allows me to use MSSQL, but I get an error when I browse to localhost, "No such file or directory in Unknown on line 0"

PHP 5.3.5 forces me to use SQLSRV, but it works great with my remote document root.

I've read that 5.3.1 doesn't like remote or soft Windows links, which is why the remote doc root fails. Is there anyway to have a remote document root AND use MSSQL functions? Both are requirements but I'm starting to think they're mutually exclusive. I've used the convention "//remotedrive/myfolder/www" and I've used "P:/www" where P is mapped to "//remotedrive/myfolder". Neither work, and "P:/www" gives me an error on Apache start saying the doc root must be a folder. The other way starts Apache ok, but I get that error I noted above.

Apache is running as my domain user in both instances.

11:45 am on Oct 6, 2011 (gmt 0)


WebmasterWorld Administrator coopster is a WebmasterWorld Top Contributor of All Time 10+ Year Member

joined:July 31, 2003
votes: 3

I won't be able to offer much help with Windows OS administration. I use *nix servers.

However, have you considered using a version control system so you can share the code throughout the shop as well as remotely? You checkout the repository you want to work with and you have your own local copy for development and testing then commit and merge code changes with your peers and other developers.