Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / General MS InfoPath Questions / December 2004

Tip: Looking for answers? Try searching our database.

Unable to attach to application ...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Greg Poirier - 20 Dec 2004 17:26 GMT
I am unable to debug a VS.Net InfoPath project that uses managed code (C#
via the VSTO SDK).

Searching MSDN on this problem turns up a few suggestions about relaxing
permissions on some system resources, which I have done to no avail.  I also
reviewed Min Park's blog on the subject(s):
http://blogs.msdn.com/mkpark/articles/86872.aspx.

When attempting to start an InfoPath project in debug mode, I receive the
error: "Unable to attach to application 'Microsoft Internet Explorer'
(PID:xxxx) on machine 'YYYYY'. If I choose the continue option, I get
"Unable to attach to machine'. (At present, the InfoPath app is published to
a shared folder on my machine only.)

Attempting to attach the debugger directly to the InfoPath process does not
work when selecting the 'common language runtime' option; this results in
'Unable to attach to process'' message. Selecting the 'native' option only
works when attaching, but of course my breakpoints are not honored

FWIW,  I have .NET frameworks 1.0, 1.1, and 2.0 installed side-by-side.

Any suggestions would be appreciated.
virgul - 22 Dec 2004 13:01 GMT
Is your toolkit for infopath correct install and when you have install
office sp1 have you first uninstall infopath instal the sp1 and
reinstall infopath.
Greg Poirier - 31 Dec 2004 21:34 GMT
I was able to fix this problem by following the advice from
http://blogstogo.com/dotnet2/archive/2004/12/14/554.aspx.
It is interesting to note, that before finding this help, I had first tried
removing the .NET Framework version 2.0, but the problem still persisted.

Rate this thread:






 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.