tag:blogger.com,1999:blog-3930375442497799514.post3140044984052765414..comments2008-07-15T11:53:59.775-07:00Tom Puleohttp://www.blogger.com/profile/10697521511530638404noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3930375442497799514.post-1325477400513557522008-07-15T11:53:00.000-07:002008-07-15T11:53:00.000-07:002008-07-15T11:53:00.000-07:00I don't have any experience with the x64 servers, but it would seem to me that you could debug a 32-bit process remotely if was running in 32-bit mode on the server. I seem to remember there being a "program files" and a "program files (x86)" folder on the servers...something like that. Good luck figuring this out. If you find a solution, I'd love to know about it.Tom Puleohttp://www.blogger.com/profile/10697521511530638404noreply@blogger.comtag:blogger.com,1999:blog-3930375442497799514.post-25194147019892640362008-07-15T11:21:00.000-07:002008-07-15T11:21:00.000-07:002008-07-15T11:21:00.000-07:00Hi,<BR/><BR/>Our server is running on x64; I shared the (x86) folder for the remote debugger on the server and followed all steps till I saw the refreshed processes on the server in my x86 visual studio debugging windows for attach to process; however, when I attempt to attach a process, w3wp.exe of Type 64, it can't due to the machine architecture conflict; is it possible to debug from a x86 machine on target x64 remote machine?أحمدhttp://www.blogger.com/profile/15960270072810029831noreply@blogger.com