How to debug dynamic calls

Hi Gurus,
Can any one tell me how to debug dynamic calls?
The scenario is:
I know the message that is getting fired from a message class.
I didnot find its usage from the where-used list, as it says - possible dynamic calls.
How do i know, from where this message is getting fired?
Pls suggest.
Thanks, Rashmi

Hi,
Just try this
In the new debugger Breakpoints --> Breakpoint at --> Breakpoint at Statement
give MESSAGE
This will set break point at all message statement. Execute till you get the message
Regards

Similar Messages

How to add dynamically called files to a teststand workspace?

I am using TestStand 4.1.1 and LabVIEW 8.6.1 to try and install dynamically called VI's into a TestStand workspace. I am following the instructions on pp. 14-8 through 14-10 in the TestStand Reference Manual (May 2008) edition. So far I have not been successful, and the instructions are not clear. For example, I cannot see in the instructions anywhere that I am supposed to add my test sequence. Should the test sequence already be loaded in the project before this set of instructions is followed? Could someone clarify this set of instructions for me?
Then when I get a successful build, I would like to try out the deployment and installation on a target computer. Please provide a detailed and clear set of instructions on how this can be accomplished.
Also, is there anyway to do this without building an installation? Originally I just wanted to create the deployment without an installation. But please explain both ways.
Thank you.
epsilon-delta

Epsilon,
What are you using dynamically called VI's for? Are you adding dynamic VI's to LabVIEW, or to TestStand? If you are calling from TestStand, you don't need to do anything, the deployment utility will do all of the work for you. The section on adding dynamically called files to a workspace listed in the Test Stand Reference Manual is a mini-tutorial, and not exactly step by step instructions. All you need to do to add dynamically called VI's is to add them to your workspace file, and make sure the TSW is saved before you build your deployment. The example right before that one, covers how to deploy from a TSW, and mentions that you need to add your sequence file to the project that is in the workspace.
The steps needed to deploy a sequence is as follows:
1. Create a new workspace file
2. Right click on the workspace file and select "Add a project"
3.
Right click the project and select add additional files (here you
should add your sequence file and any files that are dynamically called
(e.g. VIs))
4. Go to Tools --> Deploy TestStand System
5. Check "Deploy Files from TestStand Workspace File"
6. Select the appropriate file path where you saved the workspace file
7. Add in a path for the location you want to store your deployable image (for instance your desk top)
8.
Go to the distributed files tab and select "yes" to analyze the source
files [here you will find all the files you chose to include with your
distribution, this is automatically populated from the workspace and
its dependencies), if you are deploying and plan on using a User
Interface and not the TestStand Sequence Editor, here you would need to
include the UI as well
9. If you were making an installer, you
could check the "Create installer" box under installer options and
specify a location. Also here you could click on the drivers and
components box to add additional driver installation (only if you are
building an installer)
10. Click on build status, then build
You can also reference the same manual 14-7 through 14-8 which goes through an example deployment, and installation on a target computer.
After you build your installer, copy the files to the target computer and run the setup.exe to install to the new computer, what problems do you have? Do you get errors, and if so can you take screenshots of them?
If you do not wish to create an installer, and you already have a user interface installed, and the TestStand engine on your target machine, you can just copy all of your files to the target machine, and run them normally. We generally recommend building installers, so that any missing dependencies on the target system could be installed, and the TestStand deployment tool takes care of pulling out all the needed files for you (except for the dynamiclly called ones, which is why you need to add them yourself). If you want you can use the deployment tool to create an image and then move that image to the target computer. The image should have all of your non-dynamic files included, but still requires that your system have all needed components installed. Please let me know what part of the deployment, installation process you are having errors, and we can help you troubleshoot. I always recommend trying to deploy a very simple example sequence with no code modules, if you are having problems. This is always a good troubleshooting tip that will help to determine if the problem is with one of your systems, or with your specific sequence file.
Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

How to check if internal table exists in dynamical called subroutine ?

Hi,
in a dynamically called subroutine i'm using a internal table, but in some calls this table is not exist.
How can i check in the code whether the internal table exist or not ?
regards,
Hans

In Horst Keller's blog /people/horst.keller/blog/2005/05/27/abap-geek-10--everything-functions-150-but-how my issue is talked about :
All other parameters are handled in a way as they were declared as global data objects in the top include of the function group, that can be used only during the execution of the function module: They are visible throughout the function group but you can access them only while the function module is active. If you access such a parameter and the respective function module is not executed, you get the runtime error GETWA_NOT_ASSIGNED (Why? Well, technically thos guys are represented via field symbols which are valid only during the runtime of the function module).
The code is in SD pricing. Sometimes the code is called from function module PRICING_BUILD_XKOMV or PRICING_SUBSCREEN_PBO where TKOMV is defined as globalized parameter.
And sometimes it is called from function module PRCING_CHECK where TKOMV is NOT defined as parameter.
In the call of last function the dump occures on the ASSIGN statement :
     data: ls_tkomv like line of tkomv,
              lv_tablename(30) type c value 'TKOMV[]'.
    field-symbols: <lfs> type any table.
     assign (lv_tablename) to <lfs>.
     if <lfs> is assigned.
Any suggestions to solve the issue ?
regards,
Hans

How to Debug Functional Module called via RFC?

Hi Experts,
     Please, can someone explain to me how to debug functional module that is called via RFC? Thanks in advance.
Best Regards,
Aleksandar

Hi Laxman,
   First of all thank you very much for giving attention to my post. Ok, I am trying to debug function module in RM-CA (FICA), function module is called by CRM system (via RFC) and in addition all this chain is triggered by WebClient.
     I have user that can login on the CRM as well as on RM-CA (ECC 6.0) system, but those users are different (unfortunately I do not have administration permission so I cant change profiles of my users but I can ask for it). I can without any problem debug calls that come from WebClient, so setting an external break point in CRM system I can catch whatever I want but when process comes to point where actually call to back-end (RM-CA) takes place I simply cant get into functional module, that resides on RM-CA side. Actually what happens is that processing continues as was chosen NEXT STEP (F6).
     To resume, two systems and two different users. Where XCM user should be created? (on RM-CA system or CRM). Should I change something in Menu option Utilities -> Settings -> ABAP Editor tab -> Debugging tab, in field users? If you need any additional info please tell me.
Thanks again for your support.
Aleksandar

How to dynamically call and order program modules

Hey guys,
I have ‘x’ pieces of code (x could be 10’s or 100’s of modules).
I need to be able to dynamically call and run ‘y’ of them, but I need to be able to do it in parallel, and some of them might be in order.
For instance ‘A’, ‘B’ and ‘C’ need to run in parallel,
but 'D' needs data from 'A' and will run after 'A',
and 'E' needs to run after ‘D’,
and ‘F’ needs data from 'C' and will to run after ‘C’
So I have two questions.
How should I organize and order these dynamic calls?
and What method should I use to pass data along from one VI to another?

jcyth wrote:
[...]But when you thought of Teststand, did you have a specific feature of Teststand that you thought it would be a viable solution?
Since we will probably have the end user choose the modules required in this module operation, having a premade sequence editor might be nice
My point mentioning TestStand is that my feeling tells me that you are going to re-implement some very basic functions which are already included in TestStand.
To be honest: TestStand adds additional costs. You have to purchase licenses, you should get some training which takes time until getting payed off.
But on the other hand: You also need time to implement and test your self-made approach. Also: Does this project grow in the future? Do you need additional features in the (near) future?
Going into this will result in a break even in costs where you can say: if i take more time in my self-made approach, it is cheaper to go for TestStand right from the beginning.
TestStand is designed to be VERY flexible. But you have to get familiar to this flexibiity in order to get where you want. Therefore, i recommend you to collect some information before making the decision. Maybe you want to invite some sales guy from NI in order to present TestStand to you....
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to stop the vi dynamically called out?

Some vi was dynamically called out by the attached vi, may I know how to close it using the vi reference. Thanks
Solved!
Go to Solution.
Attachments:
PubSub_Start_VI_Dyn.vi ‏25 KB

hi turbot,
if that is running first abort that vi using invoke node and then use the property Node of that vi reference That is Front Panel Windowpen pass faulse value to close that vi. for more details check the attachment.
Regards,
Santhosh M
Attachments:
Close VI.vi ‏8 KB

How to edit a program dynamically called from another program

Hi all,
Can anyone help me in coding for a program which call's another
report dynamically from selection screen(for instance z_dynam_called)
and retreive the whole content of the dynamically called program(z_dynam_called)
into an internal table and replace the contents of the internal table with some new code and put it back in z_dynam_called and save it.
Thanks in advance.
Needful will be rewarded with points

Hi,
Follow this:
1) U can pass data from one program to another in a single login using SAP memory......
2) u can create a DBtable update dat table using ur first pgm and fetch from second program.....
3) U can pass the report output using EXPORT TO MEMORY addition and get it back using IMPORT FROM MEMORY..........
Eg:
Export the selected rows to the next program
EXPORT final TO MEMORY ID 'ABC'.
CALL TRANSACTION 'XXX'.
XXX is the tcode for the other program where u want to import the values.
In the second program
INITIALIZATION.
IMPORT the internal table from the first program
IMPORT final FROM MEMORY ID 'ABC'.
Thanks and Regards,
Reward If Helpful

How to dynamically call image in PDF for Acrobat ver 8.1 onwards?

Hi Experts,
I am using Web Dynpro Java. My requirement is to call the images dynamically on a PDF form. There are no of company code. I have to call different logos for different company codes/
We are now using Acrobat 8.1.1. Please refer following thread.
http://kb2.adobe.com/cps/405/kb405270.html
From Acrobat 8.*, we have to use some different method for dynamically calling the images. Earlier we were using the concept mentioned below to dynamically call images.
However this method is not applicable for Acrobat Reader 8.* onwards due to security reasons.
Click on the Layout tab and choose None for the Caption position.
u2022 Click on the Object, then the Binding tab and choose None for Default Binding.
u2022 Click on the Field tab, enter $record.SapOnlineShopUrl for the URL entry, and select Use Image Size for the Sizing field.
u2022 Click on the script editor and enter the following FormCalc script statement, which enables the dynamic integration of the image. Show: initialize Script: this.value.image.href = xfa.resolveNode(this.value.image.href).value; Language: FormCalc Run At: Client
write following code in wddoinit
try { String url = WDURLGenerator.getAbsoluteWebResourceURL( wdComponentAPI.getDeployableObjectPart(), "sap_online_shop.jpg"); wdContext.currentDataSourceElement().setSapOnlineShopUrl(url); } catch(Exception e) { throw new WDRuntimeException(e); }
Please let me know what is the alternate method for Adope ver 8.1.1
Regards,
Gary

Hi Gary,
First you upload the image in SAP through se78.then write the below code in your adobe form interface.
data : v_object type TDOBJECTGR value 'GRAPHICS',
        v_id type TDIDGR value 'BMAP',
        v_btype type TDBTYPE value 'BCOL',
        V_FIELD TYPE XSTRING.
V_NAME = 'ZW_DEVMAN_LOGO'.
CALL METHOD cl_ssf_xsf_utilities=>get_bds_graphic_as_bmp
EXPORTING
p_object = v_object " 'GRAPHICS'
p_name = v_name " Name of the logo as in se78
p_id = v_id " 'BMAP'
p_btype = v_btype " 'BCOL' ( whether the image is in color or black and white )
RECEIVING
p_bmp = v_field
EXCEPTIONS
not_found = 1
internal_error = 2
OTHERS = 3.
g_logo = v_field.
Declare g_logo as xstring in global data.
In context of the form make one graphic element with field g_logo and mime type BMP.It will work.
Regards,
Simi A M
Edited by: amsimi on Jan 26, 2011 5:30 AM

How to debug a smartform?

I am facing deffficulty.. while debugging the my smartform.
this is called in e-recruitement portal.. i tried with smartform_trace and break-point and all.
how to do this?
Please help me.
Thanks

Hi
DEBUG Smartform:
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
Read More here.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Re: How to Debug a Smartform
Debug of smartform and sapscript.
Debugging SmartForms
LOGO on Smartform
1) In Smart Forms Editor, In left pane, right Click any Page (say Page1) and select Create -> Window, Give it a name and Description (Say Window1)
2) Right Click on Window (Window 1) and select Create -> Graphics, Give it a name and description
3) In general Attributes, Select Name, get search help (F4) , you will find a list of pictures
4) Select any picture and set its Resolution in DPI
5) Press F9 to open Smart Forms Builder, Select window (Window1) and In Output options window set, size and position of the Logo
6) Set any other parameters if required, save and activate.
7) If there is only 1 Window in the forms, set it as Main Window in general attributes.
8) Use TCode SE78 to upload new pictures and logos.
look at Thread Dynamic Graph in smartforms
Refer the links also -
Re: Dinamic Graph in smartforms
How to get file perperties in Unix server

VI Profiler on dynamic called VI archiecture

I have a question about debugging to put to the Gurus out there.
My architechure is this, Event driven Producer, which queues Data into the Primary Consumer Loop. Primary consumer Loop performs an action and Queues information into the Secondary consumer Loop which updates the front panel GUI.
The Primary consumer calls test VIs dynamically using a call by Ref node function.
I have a very simple test VI which I am repeatedly calling which is outputing the time since the whole test sequence started (in ms) to the Front panel.
For debugging I have put a conditional disable around the dynamic call function, and I can change it to call the test VI directly.
VI profiler is telling me that the execution of my run a test VI which does the dynamic call takes 0ms. This can't be true.
The results from VI profiler would indicate that I could run 20 tests in about 1 second, but it's taking me about 10 seconds.
I do 10 display updates (via property nodes to change the active row, colours and contents of a multicolum listbox) per test.
Any ideas how I should be debugging where the time is being lost? - VI profiler is not helping enough.
Cheers
James

James W wrote:
Ben wrote: Use the VI itself to time how long it takes by getting the time before and after.
Opening a dynamic VI takes time. Load ahead of time use it and when done close it.
1) Def FP updates (to shut of screen updates), hide the MCLB, update it, un-hide, un-defer. passing data directly to the MCLB via terminal is fastest but can't do color stuff without property nodes.
2) Pre-load
Ben
1)
And here comes the killer...
If I defer FP updates, the code runs slower!!! not faster.
If I change the MCLB from Synchronous to Asynchronous using the drop down menu before I run it has no effect on the run time.
If I change the MCLB from Synchronous to Asynchronous at runtime using at property node (not meant to do this), I get error 1073 and the GUI stops updating (sometimes while redrawing the screen half way down), but wiping over the FP window 10 seconds later shows the code has run significantly faster.
2) How do you preload 120 different tests all with the same VI pattern (generated from the same template) and ensure you have the correct VIs in memory without running them? (and producing loads of errors - these tests all logs any errors they produce to files)
I asked for the Guru's I didn't think I was going to the the Knights so fast!! Thanks Ben
Lacking Guru's you'll have to settle for me for now.
If the defer makes it go slower the issue may indeed be the FP updates since the defer forces an extra update when set.
Is is slower if do the next two steps of hiding updating and un-hiding?
If you toss all MCLB code does it run fast enough to make you believe it is the GUI update that is hitting you?
Can you post image of your code as png or jpg?
How much data is in the MCLB?
This cloud has links to LabVIEW_Performance threads. Not sure if any of those threads ring a bell.
Please show us the code to get the most out of us.
Not sure about Q#2 but I would open them and keep a ref to each in array so that they are loaded when I need to run them.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

How to debug DAQ VIs (problem with data)

I am trying to debug (and understand) the attached VI. I’m not asking anyone to analyze/debug it, since it is far more than an example; I am new to these forums and feel like asking such a thing would be inappropriate.
I would like advice on how to debug it. I am also going to describe my problem to see if the cause may be obvious to someone.
The outputs of the "Angle Calc" sub-vi are fed into a state machine. The state machine actuates outputs to move a motor and measures changing angles. It first moves up/down, then left/right. The attached VI is called by a top-level VI and the front panel is not usually open. For some reason, when the front panel is opened, it behaves differently when it is called. The behavior only changes for the right/left movements.
Here's where I'm hoping someone can point out some better debugging methods for me.
I have been using the Express Write to LVM File VI and the Convert to Dynamic Data function to write acquired data to text files for analysis after the acquisition has completed. Are there better methods recommended for doing this? I wish I could run through the code while recording the execution and then step through a playback of it!
As for the specific problem I am having...
In the "Right Find Stall" case, the signal wired from the "Angle Calc" VI (array size 100) is connected to a Max/Min Array function. When I log the data coming from the Min/Max function, I see an alternation between valid data and 0 (i.e. 12.2, 0, 13.3, 0, 14.0, 0, 14.5, 0...). When I log the data being fed into the Min/Max function I do not see 0s.
A guess of mine is that the array is empty and therefore no data is logged but Min/Max returns a 0 (not sure why this would happen). I also have no idea why this would ALWAYS happen with the front panel opened. I have seen the effect with the front panel closed, but never to the same degree; usually just a seemingly random zero or two but not a pattern of every other point...
Thanks all,
Dave
Attachments:
Functional_Test.vi ‏2710 KB

Angle_calc receives array controls in and passes array indicators out. It performs a trig function and a bit of multiplication.
I'll check out the Write to Spreadsheet File VI, haven't used it in the past. If it will allow me to write text out that'll be enough reason for me to stop using the Express VI.
I've used Execution Highlighting and stepping before but with the data acquisition by the time the application makes it around to the next read the DAQ card has sampled a ton of data and the data coming in is no longer useful (a different state should be active by then).
I do think the problem is related to the computer slowing down with the front panel open. I've logged the 'backlog' number of the Read function and found that the number in there is greater than 0 much more often when the VI's front panel is open and that I've seen relations between the 0s that I discussed earlier and the backlog going above 0 (usually the scan after a non-0 backlog seems to be a problem).
I need to familiarize myself with the DAQ basics, the buffer, backlog, and relation to sampling rate, etc.
In a simple VI I just wrote, I noticed that if I increased the sampling rate high enough, data being acquired into a chart cuts-out on a regular basis; instead of a smooth line, I see small dashes or dots of data (spaces in between). I don't understand this- I would expect data to be lost but not "no data" to be read in. I think understanding what is happening here would be helpful.

WHERE AND HOW IS DEBUGGING USED ?

WHERE AND HOW IS DEBUGGING USED ? PLEASE GUIDE ME WITH EXAMPLES.
REWARD POITS GUARENTEED !!

Hi,
check these...
ABAP DEBUGGING
http://help.sap.com/saphelp_webas620/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9cbb7716-0a01-0010-58b1-a2ddd8361ac0
Debug Program scheduled Background
Re: Debugging Report which is scheduled in background
3 types update,normal and system debugging
check this for update debugging
If you set "Update Debbugging" you can debug the codes which works in update tusk.
SAP std often runs the routine (function or form) to update the database in update tusk mode, these routine start as soon as a commit work is done.
The commit is called at the end of the program, so you can't debug them by "normal debbugging" because it ends as soon as the program ends
or----
All the database updates are performed by the update work processes by calling the functions/subroutines in update tasks.
These tasks are executed after a commit work is reached in the application. By default you cannot debug these functions.
TO debug these u need to explicitly activate update debugging.
for system debugging check the below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/5f0640555ae369e10000000a155106/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
For debugging tutorial:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://www.sapdevelopment.co.uk/tips/debug/debughome.htm
http://www.sap-basis-abap.com/sapab002.htm
System Debugging
If you set this option, the Debugger is also activated for system programs (programs with status S in their program attributes). When you save breakpoints, the System Debugging setting is also saved.
Update Debugging
Update function modules do not run in the same user session as the program that is currently running in the ABAP Debugger. These function modules are therefore not included in debugging. Only if you select the Update Debugging option can you display and debug them after the COMMIT WORK.
Normal Debugging
Normal debugging is the one we do it by the normal dynamic break points or by /H or by using stattic break points.
You can switch to diffferent debuggin modes while processing.
BREAKPOINT
In the source code we set the Break-point there by clicking the stop button, the system will stop there when you execute the program.
Watchpoint
For watchpoints, we need to give some condition and when this condition is satisfied, program will stop
example : if you want to debug only
for matnr value 100 than set watch point
matnr = 100. when value reaches 100 than
program stops at that point.
more at
http://help.sap.com/saphelp_nw04/helpdata/en/c6/617cdce68c11d2b2ab080009b43351/content.htm
check these documents as well
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/abap-runtime-tools/the%20new%20abap%20debugger%20-%20an%20introduction.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/f720ea47-0801-0010-f7a3-bd37d44fee8d
here r some links for debugging...
Go through these threads for more information on debugging,
1) debugging
2) debugging
3) Debugging
4) Debugging
some more links .....
Introduction: http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
A PDF file to know knowledge about Debugging
Some more links:
http://www.sap-basis-abap.com/sapab002.htm
Debug Background Programs: http://www.sapdevelopment.co.uk/tips/debug/debug_backjob.htm
Debugger: http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
Cheers
VJ

How to debug the abap program ?

how to debug the abap program ?Can anybody explain me in details.

Hi
Debugger
This section of the ABAP Workbench documentation provides information on how to use the Debugger as a test tool for finding errors in the source code of an ABAP program.
Functional Overview
Use
The ABAP Debugger is an integrated test tool within the ABAP Workbench. You use it to check the program logic and to find errors in the source code of an ABAP program. In the Debugger, you can step through the source code of a program. The running program is interrupted after each step, allowing you to check its processing logic and the results of individual statements.
As of Release 6.10, you can also run Business Server Pages (BSP) in the debugging mode. You can also display and set breakpoints here. Business Server Pages can be displayed in the Object Navigator when you select an appropriate application under BSP Application.
Features
The Debugger provides an efficient means of identifying errors in ABAP programs. It contains the following functions:
Ways of starting the Debugger
Choosing different views
Choosing different execution options in the Debugger
Displaying source code in the Debugger
Setting and deleting breakpoints
Setting and deleting watchpoints
Stopping a program at a particular statement or event
Displaying and changing field contents at runtime
Displaying ABAP Objects and references
Displaying and positioning strings
Setting and deleting database locks
Opening the ABAP Editor, or Object Navigator
System settings and runtime warnings
Starting the Debugger
There are two possible strategies for starting the Debugger in the ABAP Workbench:
By setting breakpoints then running the program
By running the program in debugging mode.
Setting Breakpoints
A breakpoint is a signal in a specific line of the program source code. This signal indicates to the ABAP runtime processor to stop the program at the relevant line and start the ABAP Debugger. A distinction is made between static and dynamic breakpoints. For further information about the different types of breakpoints and how to use them, refer to Breakpoints.
Direct Processing
You can start the Debugger without previously having set breakpoints. This is the best procedure to use when you want to test a program right from the beginning. It is also a useful procedure if you are not overly familiar with the program and therefore are not sure where best to set breakpoints. You can start the Debugger as follows:
From the Object Navigator
Select a report or transaction and choose Program ® Test ® Debugging.
From the ABAP Editor
Choose Program ® Execute ® Debugging (or the Debugging pushbutton).
From any screen
Choose System ® Utilities ® Debug ABAP.
From any screen
Enter /h in the command field.
Display Modes in the Debugger
When you are debugging a program, there are various display modes that you can use. All of the display modes have the same structure. The top part of the screen displays an extract of the program source code. The bottom part displays the information specifically available in that display mode. There are also pushbuttons on the screen allowing you to switch to the most frequently-used display modes.
Display Modes Available Using Pushbuttons
Fields
The scrollable field display contains the contents of up to eight fields. The contents of the three most important system fields are always displayed. This is the default display mode in the Debugger. See also Processing Fields
Table
Displays the contents of an internal table. This mode allows you to display and edit the entries in an internal table. See also Processing Internal Tables
Breakpoints
A scrollable display containing up to 30 breakpoints. Next to each breakpoint is a counter. You can also delete breakpoints in this display. See also Managing Dynamic Breakpoints
Watchpoints
You can set a watchpoint for a field so that the program is interrupted whenever the value of that field changes. This display mode contains a list of watchpoints, the fields and programs to which they are assigned, the current values of the fields, and the conditions upon which the watchpoint is activated. See also Setting Watchpoints
Calls
This mode displays the current sequence of events, and the sequence of calls up to the current breakpoint. The last active call is displayed at the top of the list; previous calls are listed in reverse chronological order. When an event (for example, START-OF-SELECTION) concludes, it is deleted from the display.
Overview
This mode displays the structure of the program. It lists its events, subroutines, and modules, and shows which sections belong to which events. It also displays the section currently being processed.
Settings
This mode displays the current Debugger settings. You can change the settings by selecting or deselecting various options. For further information, refer to Settings and Warnings
Other Display Modes
You can access other display modes by choosing Goto ® Display data object.
Single field
Displays the contents and technical attributes of a field.
Structured
field
Displays the components of a structure, along with their contents and attributes. If you double-click a component, the system displays detailed information for it.
Strings
Display the content and current length of the string. You can also display part of the content by means of offset and length.
Internal table
Displays the type, line numbers and contents of an internal table.
Object
Displays the structure of an ABAP Object.
For further information on these displays, refer to Displaying Attributes and Displaying ABAP Objects
Checking System Programs for Errors
To check a program or program component that is part of the ABAP Workbench (for example, the Screen Painter), you must use the system Debugger. To start the system Debugger, choose System ® Utilities ® Debug System from any screen. To stop the system Debugger, choose Debugger ® Debugging off.
Displaying Program Attributes
You can display the attributes Fixed Point Arithmetic, System Program, and Unicode Checks of the program that has just been executed by choosing Goto ® Further Information ® Program Attributes.
Restarting the Debugger
If you choose Debugging ® Restart, debugging mode is stopped and the system takes you to the initial screen of the last transaction you called. If, for example, you started an ABAP program in debugging mode from transaction SE38 (ABAP Editor), choosing Debugging ® Restart will take you back to the screen titled ABAP Editor: Initial Screen. If you want to restart the program in debugging mode, choose Debugging.
Breakpoints
Apart from direct execution of an ABAP program in the Debugger, it is also possible to start the Debugger call by the exact setting of a breakpoint. This is achieved by setting one or more of these breakpoints in the program. A breakpoint is a signal at a particular point in the program that tells the ABAP runtime processor to interrupt processing and start the Debugger. The program runs normally until the breakpoint is reached.
There is also a special kind of breakpoint called a watchpoint. When you use watchpoints, the Debugger is not activated until the contents of a particular field change. For further information, refer to Watchpoints.
Breakpoint Variants
The Debugger contains different breakpoint variants:
Static
The BREAK-POINT statement in an ABAP program. Static breakpoints are not normally user-specific. However, you can make them user-specific.
Directly-set
dynamic breakpoints
Can be set in the ABAP Editor or the Debugger. Dynamic breakpoints are always user-specific, and are deleted when you log off from the R/3 System.
Breakpoints
at statement
The Debugger stops the program directly before the specified statement is executed.
Breakpoints
at subroutine
The Debugger stops the program directly before the specified subroutine is called.
Breakpoint at function module
The Debugger stops the program directly before the specified function module is called.
Breakpoint at method
The Debugger stops the program directly before the specified method is called.
Breakpoints at system exceptions
The Debugger stops the program directly after a system exception, that is, after a runtime error has been intercepted.
Static Breakpoints
Static breakpoints are not normally user-specific. Once a user has inserted the statement BREAK-POINT or BREAK name in an ABAP program, the system always interrupts the program at that point for that user or only for the user name. This procedure is only useful in the development phase of an application, when the program execution is always to be interrupted at the same place. For further information, refer to Static Breakpoints.
In HTTP sessions, a static breakpoint is skipped if you did not set additional dynamic HTTP breakpoints in the editor of a BSP page. Instead, a corresponding system log entry is written, which can be checked using transaction SM21.
Dynamic Breakpoints
Dynamic breakpoints are user-specific. Therefore, you should use them if you only want the program to be interrupted when you run it yourself, not when it is being executed by other users. All dynamic breakpoints are deleted when you log off from the R/3 System.
Dynamic breakpoints are more flexible than static breakpoints, because you can deactivate or delete them at runtime. They have the following advantages:
You do not have to change the program code
You can set them even when the program is locked by another programmer
You can define a counter that only activates the breakpoint after it has been reached
Special dynamic breakpoints are useful when you want to interrupt a program directly before a particular ABAP statement, a subroutine, or an event, but do not know exactly where to find it in the source code. Event here is used to refer to the occurrence of a particular statement, for example, or calling up a method. Special dynamic breakpoints are user-specific. You can only set them in the Debugger. For further information, refer to Dynamic Breakpoints.
In HTTP sessions, the system stops both at static and dynamic breakpoints if a dynamic breakpoint was set in the editor of a BSP page before program execution.
Lifetime and Transfer of Breakpoints
A static breakpoint remains intact as long as the BREAK-POINT or BREAK-POINT name statement is not removed from the source code. Without saving, dynamic breakpoints only remain intact in the relevant internal session. However, they are effective during the entire user session, if they are saved by choosing Breakpoints ® Save in the ABAP Debugger. For more details on the subject of sessions and user sessions, refer to Modularization Techniques in the ABAP keyword documentation.
If you call an HTTP session during a user session, only the HTTP breakpoints are loaded when the HTTP session is started. You activate HTTP debugging in the ABAP Editor by choosing Utilities ® Settings ® HTTP Debugging. Depending on the setting, the system then displays either the HTTP or standard breakpoints in the Editor.
If you call an update session during a user session, breakpoints that were defined beforehand in the calling processing unit are copied to the new update session, where they can be displayed under Breakpoints. If, in the ABAP Debugger, you check Update Debugging under Settings and then, for example, call the update module func using CALL FUNCTION func IN UPDATE TASK, a new window is opened in which you can debug this function module in the update session. All the breakpoints that were set in the calling processing unit can also be processed here.
Breakpoints at Statements
You can use this special kind of dynamic breakpoint to interrupt a program directly before an ABAP statement is processed.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at an ABAP statement:
1.Choose Breakpoint ® Breakpoint at ® Statement...
The following dialog box appears:
2.Enter the ABAP statement.
The system sets a breakpoint at all points in the program at which the ABAP statement occurs.
3.Choose ENTER.
The breakpoint applies to all lines containing the specified statement.
Result
The system confirms the breakpoint and adds it to the list in the display. When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Breakpoints at Subroutines
You can use this special kind of dynamic breakpoint to interrupt a program directly before a subroutine is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a subroutine:
Choose Breakpoint ® Breakpoint at ® Event/Subroutine.
The following dialog box then appears:
Enter the name of the subroutine before which you want to interrupt the program. By default, the Program field contains the name of the program that is currently active. The system sets a breakpoint wherever the specified subroutine occurs in the program code.
Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
Breakpoints at Function Module
You can use this kind of dynamic breakpoint to interrupt a program directly before a function module is called.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint for a function module:
Choose Breakpoint ® Breakpoint at ® Function module...
The following dialog box appears:
Enter the name of the function module before which you want to interrupt the program. The system sets a breakpoint wherever the specified event, module pool, or subroutine occurs in the program code.
Choose ENTER.
Result
If you entered a valid function module name, the system confirms that the breakpoint has been set. If the function module exists in the system, the new breakpoint is added to the display list.
Breakpoints at Methods
You can use this special kind of dynamic breakpoint to interrupt a program directly before a method is called.
Prerequisites
You must be already running the program in the debugger.
Procedure
To set a breakpoint for methods:
1. Choose Breakpoint ® Breakpoint at ® Method...
The following dialog box then appears:
2. Enter the name of the method and class before which you want to interrupt the program. A breakpoint is then set each time the specified processing block appears in the source code.
3. Choose ENTER.
Result
The system confirms the breakpoint. The breakpoint is added to the list in the display.
Breakpoints at System Exceptions
You can use this special form of dynamic breakpoint to interrupt a program immediately after a runtime error has occurred.
Prerequisites
You must already be running the program in the Debugger.
Procedure
To set a breakpoint at a system exception:
Choose Breakpoint ® Breakpoint at ® System exception.
Result
The system confirms the breakpoint. The breakpoint is added to the breakpoints displayed.
When a system exception is triggered, a warning triangle appears in the line containing the statement that caused it. If you double-click the warning triangle, the internal name of the runtime error appears.
Static Breakpoints
You should only use static breakpoints during the development phase of an application. You must remove them from your program before you transport it.
Setting Breakpoints
To set a static breakpoint, use the ABAP statement BREAK-POINT . Place the breakpoint in the line at which you want to interrupt the program.
program RSDEBUG_01.
if SY-SUBRC 0.
break-point.
endif.
When you run the program, the runtime processor interrupts it when the breakpoints occur. You can number your breakpoints to make them easier to identify ( BREAK-POINT 1, BREAK-POINT 2 ).
Static breakpoints are not normally user-specific. The program is, therefore, always interrupted as soon as the runtime processor reaches the line containing the breakpoint. The program is interrupted regardless of the user who executes it.
However, you can set user-specific static breakpoints using the BREAK statement followed by your user name. For example, if you use the statement BREAK SMITH , the program is only interrupted when user Smith runs it. Although user-specific breakpoints appear in the program code, they are not active when other users run the program. You should, however, be careful if an application is being used by several users with the same name.
Deleting Breakpoints
Since static breakpoints apply to all users, you must remove them from the program once you have finished testing it. In the ABAP Editor, you can find breakpoints quickly by choosing Utilities ® Global search. You can also use the Extended Program Check to find them.
If you do not remove static breakpoints from your program, they will be transported to your production system. This could cause serious problems in the production system.
Dynamic Breakpoints
You can set up to 30 dynamic breakpoints without changing the program code. Dynamic breakpoints can be set either in the ABAP Editor or directly in the Debugger.
Setting Dynamic Breakpoints in the ABAP Editor
You can set dynamic breakpoints in the ABAP Editor regardless of whether you are in display or change mode. You can also set breakpoints directly from within the Debugger at runtime. To set a dynamic breakpoint in the ABAP Editor:
Position the cursor on the line of the source code at which you want to set the breakpoint.
Choose Utilities ® Breakpoints ® Set or the Stop icon. The system confirms that the breakpoint has been set.
To display a list of all dynamic breakpoints in a program, choose Utilities ® Breakpoints ® Display. You can use this list to navigate to a particular breakpoint or to delete one or more breakpoints from the program.
Setting Dynamic Breakpoints in Debugging Mode
To set a dynamic breakpoint in the Debugger:
Position the cursor on the line in which you want to set the breakpoint.
Select the line by double-clicking it or choosing Breakpoint ® Set/delete.
The system sets the breakpoint, and displays a small stop sign to the left of the relevant line. If the line already contained a breakpoint, it is deleted.
When you finish your debugging session, the breakpoint is automatically deleted unless you have explicitly saved it.
Saving Breakpoints
If you want to leave the Debugger temporarily, you can save your dynamic breakpoints so that they are still active when you return to the Debugger within the same terminal session.
To save the breakpoints that you have set in the Debugger:
Choose Breakpoint ® Save.
The system saves all of the breakpoints that you have set in the current program. These breakpoints will remain active until you either explicitly delete them or log off from the system.
You can also delete breakpoints that you have saved:
By deleting individual breakpoints from the display and then saving again. In this case, only your selected breakpoints will be deleted.
By choosing Breakpoint ® Delete all. In this case, the system deletes all dynamic breakpoints.
Managing Dynamic Breakpoints
The ABAP Debugger provides a convenient user interface for managing breakpoints. To open the breakpoint display, choose Breakpoints, or, from the menu, Goto ® Control debugging ® Breakpoints.
Example
Functions
This display mode contains the following functions for breakpoints:
Breakpoint Display
The scrollable breakpoint display contains up to 30 dynamic breakpoints. For breakpoints that you set directly, the program name and line number at which the breakpoint occurs are displayed. For special breakpoint forms, the list displays the statements, events, subroutines, and module calls at which the relevant breakpoints are set.
Counter
In the breakpoint display, you can specify a counter. When you use a counter, the breakpoint is not activated until it has been reached a specified number of times. For example, if you enter 5 for the counter, the breakpoint is not activated until it is reached for the fifth time. After the breakpoint has been activated, it remains so, and the counter no longer appears in the breakpoint display.
Deleting Breakpoints
Position the cursor on the breakpoint that you want to delete, and either double-click the line or choose Breakpoint ® Set/delete. To delete all breakpoints, choose Breakpoint ® Delete all.
Activating and Deactivating Breakpoints
Position the cursor on the breakpoint that you want to activate or deactivate and choose Breakpoint ® Activate/deactivate.
Watchpoints
Like a breakpoint, a watchpoint is an indicator in a program that tells the ABAP runtime processor to interrupt the program at a particular point. Unlike breakpoints, however, watchpoints are not activated until the contents of a specified field change. Watchpoints, like dynamic breakpoints, are user-specific, and so do not affect other users running the same program. You can only define watchpoints in the Debugger.
Use
You set watchpoints in the Debugger to monitor the contents of specific fields. They inform you when the value of a field changes. When the value changes, the Debugger interrupts the program.
Features
You can set up to five watchpoints in a program.
See also Setting Watchpoints.
You can also specify the conditions on which a watchpoint is to become active.
You can specify logical conditions between up to five conditional watchpoints.
See Specifying a Logical Expression.
You can define watchpoints as either local or global. If you define a global watchpoint, it is active in all called programs. Local watchpoints are only active in the specified program.
You can change and delete watchpoints.
See Changing Watchpoints.
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables.
See Memory Monitoring with Watchpoints
Setting Watchpoints
If you want to interrupt a program when the contents of a field or structure change, use a watchpoint. You can set up to five watchpoints, including watchpoints for strings.
A watchpoint can be either local or global. Local watchpoints are only valid in the specified program. Global watchpoints are valid in the specified program, and also in all the other programs it calls.
Procedure
To set a watchpoint, start the Debugger and proceed as follows:
Choose Breakpoint ® Create watchpoint or the corresponding pushbutton. The Create Watchpoint dialog box appears:
Decide whether you want to set a local or global watchpoint.
Enter the program and the name of the field for which you want to set the watchpoint. In the Program field, the name of the program currently running is always defaulted.
If you want your watchpoint to be activated each time the contents of the field change, the definition is now complete, and you can return to the Debugger by pressing ENTER .
To create a conditional watchpoint, that is only activated when a particular situation arises, choose one of the following relational operators.
Operator
Meaning
<
Less than
<=
Less than or equal
=
Equal
<>
Not equal
=
Greater than or equal
Greater than
You can use the Comparison field option to specify whether the comparison is to be carried out with a value that you specify or with the contents of another field. Depending on your choice from step 6, enter a value or a field for the comparison.
Result
The system confirms the watchpoint and adds it to the list in the display. When you finish your debugging session, the watchpoint is automatically deleted unless you have explicitly saved it.
Specifying Logical Links
If you have more than one conditional watchpoint, you can specify a logical link between them:
OR
Only one of the specified conditions must be met
AND
All of the conditions must be met.
Changing Watchpoints
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list. The following dialog box appears:
Choose the pencil icon in the line containing the watchpoint you want to change.
Change the watchpoint attributes in the Create/Change Watchpoint.
Choose ENTER .
Deleting Watchpoints
You cannot delete watchpoints by choosing Breakpoint ® Delete or Breakpoint ® Deactivate/activate. Instead, proceed as follows:
Choose Goto ® Control debugging ® Watchpoints or the Watchpoints pushbutton to display the watchpoint list.
Choose the trashcan icon in the line containing the watchpoint you want to delete.
Memory Monitoring with Watchpoints
You can use watchpoints to display changes to the references of strings, data and object references, and internal tables. By placing an ampersand (&) in front of the object name, you can display the reference in question in hexadecimal format. With internal tables, you can also display the table header by placing an asterisk (*) at the beginning of the name.
&objectname
Displays the references of strings, internal tables as well as data and object references
*itab
Displays the table header of the internal table itab
Example
If a watchpoint is set for the object in question at runtime, the program is stopped as soon as the reference is changed. A short dump can be intercepted in this way to stop the program being terminated when the memory is overwritten.
Analyzing Source Code
The Debugger contains an extensive range of functions that help you to analyze the source code of a program. You can step through the source code of a program in four different ways. For further information, refer to Stepping Through the Source Code
For information about functions within the source code display, see Displaying the Source Code
There are also different display modes that provide various information and display the contents of individual fields, tables, and so on:
Reward if usefull

Hi gurus how to debug the smartforms

hi gurus how to debug the smartforms

Hi
DEBUG Smartform:
1) One way to debug smartform is to debug the Function Module of that smartforms.
If you want to debug particular smartform node that the solution would be,
insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
2) SFTRACE can be used for debugging SMARTFORMS.
Read More here.
http://help.sap.com/saphelp_erp2004/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Re: How to Debug a Smartform
Debug of smartform and sapscript.
Debugging SmartForms
LOGO on Smartform
1) In Smart Forms Editor, In left pane, right Click any Page (say Page1) and select Create -> Window, Give it a name and Description (Say Window1)
2) Right Click on Window (Window 1) and select Create -> Graphics, Give it a name and description
3) In general Attributes, Select Name, get search help (F4) , you will find a list of pictures
4) Select any picture and set its Resolution in DPI
5) Press F9 to open Smart Forms Builder, Select window (Window1) and In Output options window set, size and position of the Logo
6) Set any other parameters if required, save and activate.
7) If there is only 1 Window in the forms, set it as Main Window in general attributes.
8) Use TCode SE78 to upload new pictures and logos.
look at Thread Dynamic Graph in smartforms
Refer the links also -
Re: Dinamic Graph in smartforms
How to get file perperties in Unix server

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug dynamic calls

Similar Messages

Maybe you are looking for