can't open VS .NET projects... pls help :(

[pgrimes]

I am running two servers (one for development and one for
live apps), both are identical. Running IIS 5.0 Win 2k
Pro with SP2. I have frontpage server extensions, .net
framework, and a full version of Visual Studio .NET
installed on each server. On my development server,
everything is working fine. On the other server, I am
unable to create new projects, nor can I open a project
that I move from the develop. server. When I try to open
it, I get the following message:

Unable to open Web project 'cpthandler/processUploads'.
The file path 'G:\WebServer\cpthandler\processUploads'
does not correspond to the
URL 'http://LocalHost:/cpthandler/processUploads'. The
two need to map to the same serer location. HTTP Error
404: Object Not Found

"G:\WebServer" is my root web directory on both systems.

Also, when I try to create a new project on the
development server, I get the same message. In this case,
it gives me the option to "Retry using a different file
share path" (which, does nothing if I choose another path)
or to "Try to open the project with FrontPage Server
Extensions".

I have been trying to resolve this for 2 days now. I have
reinstalled the front page server extensions, I have
reinstalled IIS, and I have reinstalled Visual
Studio .NET. Nothing is working, I just keep getting
those same messages.

And just to let you know, one project that (the first one
I moved from the develop. server to the other) worked fine
until I reinstalled VS .NET. Now nothing will open/run
with it.

Please help,

Paul Grimes

[pgrimes]

*bump*

[Cander]

http://msdn.microsoft.com/library/de...nwebserver.asp

[Edneeis]

Is this a type-o or exactly what it says:

.... 'http://LocalHost:/cpthandler/processUploads'....

If so you may need to edit the paths in the config and other files, also is there anything different about the IIS setup that would effect the path?

Can you browse to the webforms using that path ('http://LocalHost:/cpthandler/processUploads')?

[pgrimes]

Thanks for the replies.

Is this a type-o or exactly what it says:

.... 'http://LocalHost:/cpthandler/processUploads'....

Edneeis,

I'm pretty sure that was a typo. In any case, I uninstalled IIS (again), installed some microsoft update, then reinstalled IIS.

http://msdn.microsoft.com/library/d...onwebserver.asp

Cander,
Thanks for the link, but I had already seen that and it didn't work. I would browse to a location and get the same error message.


If anyone else has this problem, Here is what someone suggested on http://msdn.microsoft.com/newsgroups/default.asp

A friend of mine had this problem. We spent all day yesterday trying to fix
it including rebuilding the whole machine. Here is what he thinks finally
fixed it. I can't guarantee this is the fix because we did a lot of other
things before it.

1) uninstall IIS

2) reinstall IIS

3) Repair Visual Studio .NET Framework (Uninstall .NET platform)





To reinstall .NET Framework

For Visual Studio .NET DVD, insert the DVD, and then on the Start menu
choose Run:

<DVD Drive>:\wcu\dotNetFramework\dotnetfx.exe /t:c:\temp /c:"msiexec.exe
/fvecms c:\temp\netfx.msi"

For Visual Studio .NET CDs, insert the Visual Studio .NET Windows Comp

Mike Sneen

[pgrimes]

Is this a type-o or exactly what it says:

.... 'http://LocalHost:/cpthandler/processUploads'....

If so you may need to edit the paths in the config and other files, also is there anything different about the IIS setup that would effect the path?

Can you browse to the webforms using that path ('http://LocalHost:/cpthandler/processUploads')?

Aha... no, that isn't a typo. I am able to open new projects, but when I try to open an existing project. It has 'http://LocalHost:/cpthandler/processUploads' in the error message. Where can I change that? I looked in machine.config, but LocalHost isn't specified in there.

[Cander]

so did you get it working with the re-isntalling stuff?

[pgrimes]

so did you get it working with the re-isntalling stuff?

Partially... I can open new projects now, but not existing ones.

[Cander]

hmmph...

God I hate Visual Studio

[pgrimes]

hmmph...

God I hate Visual Studio

YA

[Edneeis]

If its the colon that is messing things up near the localhost then I believe it gets that information from the solution file stored in the common projects folder (because for web apps the rest is stored in the root of IIS). If you open it with notepad you should see the address and be able to correct it.

[pgrimes]

F@#$

I guess going to lunch destroys vs .net. I went to lunch and came back. I restarted the server and am back at square one again. I can't open existing or new web projects/applications. When I try to open an existing project, the colon shows up after localhost. When trying to open a new project, the colon isn't there.

I really don't want to have to format and reinstall win2k.

[pgrimes]

Ok, I found out what is causing the problem. These
messages occur when I change the home directory for IIS.
How can I fix this. I cannot use C:\Inetpub\wwwroot\ as
my root directory. When I change the root directory to a
location on my G:\ drive, I get the errors I mentioned
earlier. How do I fix this?????????????? I've been
wasting time on this for days.


ps.
Am I the only one experiencing major downtime w/ vbforums.com?

Paul

[Edneeis]

As long as the local path still corresponds to the web path then it should still work. For instance if your IIS root is G:\ and your VS project is WebApp1 then the WebApp1 folder should be G:\WebApp1 and the web path http://localhost/WebApp1. There should also be another WebApp1 folder whereever the default location for your VS Projects are and in that will be just the solution file(s). You will probably have to go and open up the solution file and edit the path in Notepad (see prev. post). Did you try that?

Also you could set it up to remote debug and just open the project on the machine where it will end up from the test or dev machine.

[pgrimes]

Ya, I tried to edit all the files in notepad... every reference to 'localhost' was correct (didn't have the ':' in there, etc.). Although I really don't want to bend and work around this problem (it would be nice to fix it), I have to get back to work, i've been stuck with this problem for a while and it's slowing me down.

So, I'm not famililar with remote debugging. Do you have any quick starter tips/links on that?

For now I guess I'll just stick my servers root in 'Inetpub/wwwroot'.

Thanks for the replies, and if anybody runs into this problem and solves it, please post solution

[Edneeis]

If the two machines are networked then I can create a project on the server from my developer machine. Instead of using the localhost address just enter the address it will use on the server. If VS.NET or at least the remote debugging features are installed then you can just work with the project as if it was on your machine. You may need to change some of the .NET framework security settings if it doesn't let you remote debug, a quick search for whatever error pops up at the MS website will tell you how (or it might give you instructions right on the page).

[pgrimes]

I seem to have gotten it working for good now.

When I create a new project, I replaced localhost with my machines ip address, then in the internet options security settings, I added my ip address as a 'trusted site'. Now I am able to open new projects :0). I still can't open projects that I move from the other server, but... I just create new projects and copy and paste the code into the new one (and call it the same thing).

So... this is manageable enough for me.

Thanks a ton for all the replies fellas

Paul