empz's questions

We are about to get a new Windows 2008 R2 Server for development, testing and also as a "showroom" for clients.

We will need to deploy all kind of applications (ASP.NET, PHP and Ruby on Rails for instance). Fortunately, IIS 7.5 is already capable of serving ASP.NET and PHP files.

• For Ruby on Rails what would be the best approach?
• Is it possible to have IIS to serve RoR files under port 80? (we have just 1 ip)
• If not, how would you setup things to avoid having to explicity type :port in URL?
• Is it possible to make use of IIS URL redirection to pass some requests to apache (port 81) so it can process the RoR requests with clean url (without :81). How?

Sorry if this question is already asked, but I didn't found some clear facts about it.

Thank you so much!

My client has just got a new dedicated server running Win2008 (we had 2003 before), II7, etc. I started setting a little ASP.NET 2.0 web application we have. Running on its own AppPool 2.0.

The problem is that when I browse the site root (locally or remotely), I get 404 because the url now points to http://domain/default.php, when it should be default.aspx.

Yes, I've checked the Defaults Documents settins for the website and I deleted everything but default.aspx (default.php was not even listed).

To finish, I'll say that if I navigate to http://domain/default.aspx, the site works perfectly and I can follow links without problem.

Any idea why is this happening? Or at least where I should start looking?

Thanks!

UPDATE

• I've already tried resetting IIS.

• I've checked the web.config looking for some default.php, nothing found. It's the same web.config copied from the old server which has not this problem. In fact, there is default.aspx being explicity declared on the web.config as follow:

  <system.webServer>
      <defaultDocument enabled="true">
          <files>
              <clear />
              <add value="default.aspx" />
          </files>
      </defaultDocument>
  </system.webServer>
  

• The problem seems to happen only with that website. The default website root resolves well to its default document (iisstart.htm)

I have a dedicated server running windows 2003 server and Visual SVN Server 2.0.8.

I'm trying to configure it to send email notifications on commit. So I found this article on Visual SVN site.

It says I have to edit the Post-commit hook and set it to the following:

"%VISUALSVN_SERVER%\bin\VisualSVNServerHooks.exe" ^
commit-notification "%1" -r %2 ^
--from <from-email> --to <to-email> ^
--smtp-server <smtp-server>

Of course I've replaced the variables there.

The problem is when someone commits something, the svn client throws the following error:

post-commit hook failed (exit code 1) with no output.
VisualSVNServerHooks: Error resolving case of '<path-to-repository>'

The commit process runs with no problems, I mean it does commit the files. But it won't send any email notification. If I remove the post-commit hook, then I don't get the error (and of course I don't get any notification).

Manually running the VisualSVNServerHook.exe using cmd.exe with the following code works fine (sends the email).

"%VISUALSVN_SERVER%\bin\VisualSVNServerHooks.exe" commit-notification ^
<path-to-repository> -r <some-revision_number> ^
--from <from-email> --to <to-email> ^
--smtp-server <smtp-server>

Could you help me out with it? The error doesn't tell too much =S

Thank you!

EDIT: Ok... so I've tried replacing %1 and %2 with static values (using the actual repository path and some existing revision number), just as I tested using cmd.exe. But it didn't work. So I went further and I replaced the entire hook with a simple call to C:\hook.bat, same error. It seems no matter what I put on the hook, it won't work.

we have a dev server. First we had SQL 2000 (default instance), when SQL 2005 came out, we installed it as a named instance. Nowadays we barely use the SQL2000 instance, but this is the default. We would like the SQL2005 to be the default instance and make the 2000 a named one. Is this even possible?

Thank you!

Ok, first of all, I've already googled a lot about this problem, but didn't found any solution... I've searched here and on ServerFault, but didn't found anything, so I end up posting this question here (don't really sure if it goes here or in ServerFault, sorry).

So here's the deal: We have a Windows 2003 Server running without problems. We have been using Visual SVN Server as our Subversion server and it worked great until now. We take some vacations for a couple of weeks so we didn't use the SVN at all. Today, when I tried to commit something I got:

Server sent unexpected return value (403 Forbidden) in response to OPTIONS request for [repository url]

We use TortoiseSVN as our svn client, but the problem seems to be on the server. We tried creating a new repository and import new files, same error. We tried accessing the SVN server from the server itself through RDC and trying to checkout something by console (svn checkout) and others commands too.... everything leads to that error.

Some people said it was a case-sensitive problem on the URL... but that's not our case... I've double-checked the URLs and they are fine... (anyway they were stored on the Tortoise history, so that didn't change).

One particular point to say is that there are people out there having the same problem that are not using Visual SVN (which is really just a easy way to set up a Subversion server in 2 clicks, it's not something different from any Subversion server). So I don't know if the problem is actually the Visual SVN itself.

We're lost... Any helpful information will be really appreciated.

EDIT/SOLUTION: I had a wrong entry on the authz file. It was trying to give permission to a deleted group (I think VisualSVN didn't delete the entry on authz but it did delete the group), so I deleted the entry and it's working now.

Thank you