What happened when I went to Windows 7

I have recently purchased a new PC with Windows 7 Pro. My previous PC had Windows XP Media Edition (don't laugh it worked :) ) Which is exactly my point my app in VS2010 that consumed an intranet web service worked fine on the XP machine buut when I moved it over to the Win7 machine I keep getting an error from the web service that simply says "Unknown". I am trying to find out from the web service creator what that means but my point is that I do not understand why changing PC's and OS's should make a difference. This is not the only software though. I have 3 separate ASP.NET softwares that consume the web service and none of them that were (and still do) working in the XP function in the Win7. I have disabled my firewall to see if it was blocking for some reason.

AND when I publish them to the Windows 2008 server, I get the same error. If that helps?

Not to sound stupid, but I don't get it.

UPDATE:

I took the code for the Hello World app that I created new on the Win7 PC in VS2010 that gave me the error above and I transferred it to the XP PC.

IT RAN FINE!:mad::confused:

I am new to the Win7 realm, is there something I am over looking?

Could there be something incorrect in my settings?

Is this the correct forum even?

ANOTHER UPDATE:

I published the code that functioned on my XP laptop to the Windows 2008 server host. It gave me the "Unknown" exception again.

My Win7Pro laptop is 64-bit but my XP laptop and the Win2K8 server are 32-bit. Is there something else maybe with the way newer OS's work with calling a web service?
:confused:

Hey,

The first major difference between the OSes is that one would be using IIS 5.0, and the other will be using IIS 7.0/7.5. When you say you publish the site, are you actually publishing to IIS? If so, which version of the .Net Framework are you using?

Gary

I publish to the FTP then copy the file to folder assigned in the IIS7 web site source. I am using .NET framework 4.0 on the Win2K8 server. That is the target framework in the web.config file also.

I also have the Windows Authentication enabled and am using the ASP.NE 4.0 application pool if that helps.

Have you configured the application pool that is running your application to use the correct version of the .Net Framework?

Gary

Application Pool = ASP.NET v4.0 which is assigned the .NET 4.0 framework

If you get an "Unknown Exception" from a component that previously worked on XP but doesn't work on Windows 7 64 bit then it's a an issue of a component not being able to run in the 64 bit environment. To fix this, open your IIS Manager, select an Application Pool which your application is running under, right click on it and select ADVANCED SETTINGS. Make sure the option "Enable 32-bit Applications" is set to TRUE.

Serge,

My Windows 7 laptop is 64 bit but I do not know how to change anything in the ASP.NET Development Server with relation to an application pool. Any ideas on how to do that?

Also, the Windows 2008 Server is 32-bit so that should not apply which is why I am really surprised that these apps are not running there. I suppose also that the fact that it is 32-bit is the reason I could not find the setting to enable it.

Jason

UPDATE:

On my Windows 7 64-bit laptop, I checked the "Enable 32-bit applications" setting but still no dice. I do not think that affects the ASP.NET Development server but I could be wrong.

I am more concerned about why the app will not work on the 32-bit Win2K8 server in IIS7.

Could there be a difference in the way the communication to the web service works? That is where the failure occurs when I try to execute a call to the web service the "Exception: Unknown" is the result. I will get someone on their side to check the logs to see if there is a clue.

Any other thoughts please ...... :confused:

ANOTHER UPDATE:

I talked with Microsoft today about IIS7. No help. Now upon their suggestion I will try ASP.NET team.:cry:

Hey,

Although you have a 64bit OS, Visual Studio itself, and hence the Development Server within it, is a 32 bit application, so there is no need to enable 32 bit support within it. It is already running as a 32 bit process.

Gary