500 internal server errors after using Vault

Krillan · Post by **Krillan** » Fri Nov 05, 2004 12:28 pm

After I started using Vault for my source control, all of my web projects, at one point or another (typically after a reboot) fail to run. When VS.NET 2003 tries to open a web project under source control, it gives me a 500 internal server error. I can't even go into IE and run the ASP.NET application. It's as if it can't compile, possibly due to permissions on the project files that Vault has messed around with. Anyone else get this type of problem? My boss received the same errors after he started using Vault too, so I'm positive it's an issue with Vault.

What's funny is that after this error and clicking "OK", the web project still loads in the Solution Explorer as if everything's fine, and I edit it as normal, no issues. But the issue comes up when I want to actually RUN the application. IIS has hissy fits with the application and I get 500 internal server errors.

Thanks in advance. I attached a screen shot of the error.

Krillan · Post by **Krillan** » Fri Nov 05, 2004 2:03 pm

This problem is fixed (temporarily, as it will happen again after a reboot) by doing the following:

iisreset /stop
net user ASPNET /delete (optional)
aspnet_regiis -i
iisreset /start

After this, the error doesn't occur anymore. But once I restart I'm sure it will occur again and again. Odd as heck.