Hi all....I have a problem hopefully someone can point me in the right direction.
Background first:
1. I've installed IssueVision locally on my pc and everything works perfectly.

2. I've installed IssueVision on a network server (Win 2k3, II6) and everything works perfectly.

3. I've pointed my local IssueVision project setup files ("http://xxxxxxx/IssueVisionWeb/IssueVisionServices.asmx, ect) to this server and everything works fine.

So, I begin more to start modifying...
4. I completely rebuild the entire IssueVision app to a new name; let's call it ProjectX. I did this to simulate an entire new smart app built on the IssueVision framework. So my new local app config points to
http://localhost/ProjectXWeb/ProjectXServices....) ect. As you see the name of IssueVision has changed as mentioned above. All procedural logic remains the same though. I test this new project build and everything works perfectly.
*** NOW THE ISSUE ***I move the project web folder from point 4 to the server, and remap my local pc config files to point to it. When I try to connect it simply throws an error "Server not responding".

I figure it has something to do with the way the DLL's are registered on the server? I created and installed a copy of my 'ProjectX' Web project on this server, and even went as far as registering the DLL located in it's BIN directory. No luck.

I have zero issues with SQL Authentication, IIS setup issues ect..that is for sure ruled out.
Anybody know how to deploy a "freshly named IssueVision" on a server?!