I have a workflow defined in Visual Studio and it resides on both a development server and a production server. The workflow runs fine on the development but gives me a error in the production server. I'm certian the workflow is fine since it runs on the first server. So I decided to run it in debugger in order to find some idea as to where the "smoking gun" resides on the production server.
When I bring up Visual Studio, attch the process id and sttempt to set the firsty breakpoint, I expect to see a solid dot to the left of the selected line. Instead, I see a clear dot and the following message : THE BREAKPOINT WILL NOT CURRENTLY BE HIT. NO SYMBOLS HAVE BEEN LOADED FOR THIS DOCUMENT. (I have attached a screen print in a WORD document to this description.
How and where do resolve this? What symbol table is it expecting to find?
I appreciate any help and leads you can provide.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Okay - let me answer your question this way and hopefully, I will give you what you are looking for.
I go to Debug, select Attach to Process amd hunt down the w3wp.exe processes. There are usually three there to choose from. I select the one with type "Workflow, T-SQL, Managed, x64". This particular process also has the most memory use when viewed in the Task Manager.
The other two w3wp.exe process are of the types "Script, T-SQL, Managed, x64" and simply "T-SQL, Managed, x64".
There resources available to show how to debug remote applications:
Remote Debugging in Visual Studio .Net
http://parthasarathi.netfi
Bob
For a while, I thought we were really on to something here.
As the site you referenced recommended, I checked the production server and the Machine Debug Manager (MDM) was not installed. We installed it (it lists in the Services page as "Visual Basic Remote Debugger"). Then I attempted another debug session and I got the following error at the time I tried to attach the process:
R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.
I looked up that error and it suggested that I rebuild my application with a manifest. The required information would then be passed on into the .dll file. Since the .dll was imported directly from our development server (where debugging works fine), I double-checked that server as well. The MDM was not installed there either. That seemed to imply it wasn't needed for us.
Just to verify, we installed it on the test server and it made no difference there - debugging continued as normal.
So I went back to the production server and stopped the MDM and restarted it. I even took the extra step of re-installing my application again with this new Network Service running. Same results (the R6034 error). As one other attempt, I stopped the MDM and tried to attach the process and this time it worked, but I still get the original problem where I see the clear dot next to the breakpoint and the message, "THE BREAKPOINT WILL NOT CURRENTLY BE HIT. NO SYMBOLS HAVE BEEN LOADED FOR THIS DOCUMENT" (just as you see in the original attached WORD doc).
Whew...
Okay - now I am getting the clear circle and error message on the development server as well. My earlier test there may have been invalid, I don't know. I did rebuild and install the application there but when that was done in the sequence of events I can't clearly define.
Let's just say that the installation of MDM failed to do the trick.
Any other thoughts on this one?
This may be a clue as to what is happening...
As I stated in my post (2/20 at 4:13 PM), I select the process to attach as the one that uses the most memory in the Task Manager and that one generally has a type of "Workflow, T-SQL, Managed, x64". Now this process no longer says "Workflow" as part of it's type, simply "T-SQL, Managed, x64".
In the "Attach to:" selection box in the "Process to Attach" option, I have asked to attach to Workflow Code, so I am GUESSING that this may be a "piece of the puzzle" as to why the breakpoints aere not being recognized.
Thoughts?
First off, I apologize for not posting in such a long time.
I broke down and called Microsoft on this and they have done a lot if investigation but have not come up with an answer yet. the path they have been going down involves the fact that our development system is a 32-bit machine and our production system system is a 64-bit machine. They installed some 64-bit debuggers and have been installing other system files as well.
Now it is a mut point because of other "quirky" errors we are getting in the application, we have decided to re-deploy our application on a 32-bit server instead. There have just been too many problems (besides this debugging issue) that we can't resolve. We feel this is our best option.
That probably makes this debugging issue a dead issue since we are debugging fine on our 32-bit system.
I appreciate your help and interest on this problem.
Business Accounts
Answer for Membership
by: TheLearnedOnePosted on 2008-02-20 at 12:09:37ID: 20941348
Are you running in the Debug or Release configuration?
Bob