Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Visual Studio problems... Any help...

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
Hi everyone.
I'm having some problem with my Visual Studio 6.0 . For some reason, since today I'm unable to do anything with it:
I cannot open new projects, refresh or synchronize old ones, add new files or save changes.
It keeps saying that it can't connect to the server and asks to check whether FP Extentions are installed or not.

My machine has W2K Advanced Server, IIS 5.0 with FPExtensions 2000 installed.

I'm able, though to run web applications or stand-alone pages, existing on a server, w/out any problems. I use for that purpose DNS name of my server,localhost or 127.0.0.1(which is same thing as localhost).
But whenever I try to do anything in Visual Studio, the server becomes inaccessible. It for sure was OK a couple of days ago and I didn't do anything with the server.

Does anyone know what could be the reason for this misbehavior? Maybe my Visual Studio is already celebrating Labor Day? I don't know.

Thank you in advance.
 
I use Visual Interdev 6 to.
i had this problem to on the same sistem.
So what i did was (a lot of...)
1. Reinstall IIS(web server, ftp server, mail server)
2. If not work, try then to get Service pack 2 for W2K AS
3. if not work try to get the latest patch of Visual Studio 6 (mine is service pack 6) it's good SP4 or 5.This solve all my problems with Interdev.
4. If u have the seccond CD from Your Visual Studio 6 Kit, try to instal Server Components again.

________
George, M
 
When it happened to me, I just reinstalled FP Extensions. That fixed it...

penny.gif
penny.gif
 
Hi, guys!
Thank you for your responses. Basically, I,ve done everything that there could've been done, starting with reinstallation of FP Extensions. Even tried step-by-step instructions from numerous Microsoft's KB articles regarding this "behavior by design", as they call it. And there're lots of reasons for that error. The only action that really helped, was reinstallation of IIS Services and Visual Studio itself.
So, thank you guys again. Now I'm back in business.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top