How to debug RFC

hi
could anybody suggest me how to debug RFC
thank you
kalyan.

Hello Kalyan,
What do you mean by debug RFC? RFC can be tested using SM59 transaction code.
Regards
Arif Mansuri

Similar Messages

How to Debug RFC Enabled FM ?

Hello All,
         I want to debug an RFC Enabled FM.
I've written a small Test program to check this.
DATA: eenumber           LIKE     bapip2001-pernr,
      subtype           LIKE     bapip2001-subty,
      objectid           LIKE     bapip2001-objps,
      lockindicator     LIKE     bapip2001-sprps,
      validitybegin     LIKE     bapip2001-begda,
      validityend           LIKE     bapip2001-endda,
      recordnumber     LIKE     bapip2001-seqnr.
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL
EXPORTING
    employeenumber          = eenumber
    subtype                 = subtype
    objectid                = objectid
    lockindicator           = lockindicator
    validitybegin           = validitybegin
    validityend             = validityend
    recordnumber            = recordnumber
* IMPORTING
*   RETURN                  =
*   START                   =
*   END                     =
*   ABSENCETYPE             =
*   ABSENCEDAYS             =
*   ABSENCEHOURS            =
*   NAMEOFABSENCETYPE       =
IF sy-subrc <> 0.
WRITE:/ 'UNsuccessful'.
ENDIF.
When a Break Point is kept at the above FM and When I press F5 the cursor is going into the FM .
But when I specify the Destination in the Call Statement as :
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL' DESTINATION 'SID_010'
EXPORTING
    employeenumber          = eenumber
    subtype                 = subtype
    objectid                = objectid
    lockindicator           = lockindicator
    validitybegin           = validitybegin
    validityend             = validityend
    recordnumber            = recordnumber
* IMPORTING
*   RETURN                  =
*   START                   =
*   END                     =
*   ABSENCETYPE             =
*   ABSENCEDAYS             =
*   ABSENCEHOURS            =
*   NAMEOFABSENCETYPE       =
The control is not going into the FM.
Can any one tell me how to debug the FM within a different system ?
Regards,
Deepu.K

Hi Deepu,
Your function module is at other system and you are calling it at some other system.
I hope you know on which system your function module exists.
First debug your coding at your system where you are calling this RFC Function Module and go to that point where your function module starts, now check the export data here
And
go to that system where this function module exists and give the same export data there and debug this Function Module at that system.
Reward points, if helpful,
Sandeep Kaushik

How to debug RFC connection?

I have got an error when SAP execute RfcOpenEx.
How to debug RfcOpenEx and setup breakpoint?
Thanks for your help
Marty

Hi,
in fact the conection from SAP to the destination works using SM59. but the system reply with a connection using RfcOpenEx but this function fails because there is a mixup with the parameters maybe a wrong type.
I will try to debug from the tcode COOPC1 when I start a subscription.
Thanks
Marty

How to debug RFC connection using RfcOpenEx?

Hi,
I use COOPC1 to test a RFC connection and this transaction uses RfcOpenEx which fails.
How can I debug this connection?
Best regards
Marty

Hi,
in fact the conection from SAP to the destination works using SM59. but the system reply with a connection using RfcOpenEx but this function fails because there is a mixup with the parameters maybe a wrong type.
I will try to debug from the tcode COOPC1 when I start a subscription.
Thanks
Marty

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 debug Adaptive RFC

hi folks,
How to debug an adaptive RFC connection and plz leave some idea about the Bapi_Input and Bapi_output structures
thanks in advance
nikhil

Hi
If you want to debug the backend then put and external breakpoint in the abap code.
make your jco connect to a single instance
login using the user which is configured for jco.
For the front end
put a break point in your code before you call the execute method on the RFC and after it and use the debug perspective to evaluate the values.
Regards
Ayyapparaj

How to debug a RFC function when the user is non-dialog type? Please help!

hi Experts,
I am calling a RFC FM residing in B from R/3 system A.
R/3 A -
Call FM residing in B----
> R/3 B
The user attached to the remote destination is a non-dialog type.
I cannot change the user type of this user.
Therefore how to debug the RFC FM in System A?
Are there any alternatives?
Please help
Thanks
Gopal

in your RFC FM, code an endlees loop.
something like:
data: gv_x type xfeld value 'X'.
do.
if gv_x = space.
exit.
endif.
enddo.
now you can catch the mode in TA SM50, go in it, change gv_x to space and debug what is coming further.

How to debug a failed shopping cart transfer to ECC in classic mode

Hello,
I am using SRM 5 in classic mode, connected to ECC 6.0.
I have an error message in the administrator monitor that tells me a transfer a shopping cart to ECC has failed.
"Shopping cart 1000000123: Error creating the follow-on document"
(Message is BBP_PU 367)
This is located in the "local errors" section of the administrator monitor.
The follow on doucment will be a PO in ECC.
This message does not tell me the cause of the problem therefore I need to retrnsmit the cart and debug to find the error message that is being returned from ECC.
I have browsed the forum and there are various answers about debugging but but have not found exact instructions on how to debug, and it is now always clear on whether the instructions apply to classic or extended classic.
I have seen reference to the method in note 539978 that creates test data with FBGENDAT for the ECC BAPI. However this method does not seem suitable for a production system because it will interfere with all shopping carts being transferred while the shoppign cart with the problem is being debugged.
Therefore I would like to debug in SRM just for the shoppign cart with the problem.
Hopefully this thread will become the defintiive poitn of reference for debuggin a classic shopping cart transfer to ECC in SRM 5.
I propose to use function module BBP_PD_SC_TRANSFER to transfer the shopping cart again by entering the shopping cart GUID.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possbile to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
Your help would be appreciated,
Reagrds

Hi Paul,
a small correction to Dishas comment:
The class CL_BBP_BS_ADAPTER_PO_CRT_470_1 is used for the backend release 4.7, so it is not relevant for you. Instead of this, you have to take the CL_BBP_BS_ADAPTER_PO_CRT_ERP10 and method CREATE_DOCUMENT. This is the last step, before the SRM calls the backend system.
From the alert "local errors" I suppose, that there is an error in the SRM customizing (in case the error message comes from the backend system, you get the message into the "Backend Application error").
Typical customizing error, when e.g. the number range of the purchase REQUISITION is not correctly customized (in case the prerequisits for a PO are not fulfilled, the system tried to create a purchase requisition). See the note 1173815 regarding this problem.
Back to your questions:
The activating of the FBGENDAT was a good idea, but I would give here two hints:
- I case of production system you can use only the "Mode B".
- Activate the FBGENDAT only for a short term:
-- at first set the breakpoint in the method CREATE_DOCUMENT (as above described)
-- execute the BBP_PD_SC_TRANSFER
-- you will be stopped at the breakpoint.
-- Now you can activate the FBGENDAT in the backend
-- go on with F8 in the debugger in the SRM system
-- >>> test data will be filled in the backend system (BAPI_PO_CREATE1)
-- deactivate the FBGENDAT
You can do this in one min. and the worst what can happen is that you have 2-3 test data in the BAPI_PO_CREATE1 additionally to the erronous SC.
Question 1) Can this error message be returned by checks in SRM before the BAPI is called in ECC? If so, where do I place a breakpoint to find the error determined by the checks in SRM?
- Maybe... Places for setting breakpoints
-- FM "BBP_PD_MSG_ADD"
-- System command "RAISE"
-- FM "META_BAPI_DISPATCH" (typical problem, see above, and also the note 1173815)
Question 2) If the system is getting as far as calling the BAPI in ECC, is it possible to find the error message passed back from ECC by this approach, given that the actual transfer is carried out by the spooler?
- Yes, you can find the message in the:
-- Test data of the BAPI_PO_CREATE1, if you have activated the FBGENDAT
-- In the method CREATE_DOCUMENT if you "comes back" from the RFC call from the backend
Question 3) If this approach is valid, in which method/function module do I need to place a breakpoint, at which statement is the error message passed back to SRM from ECC?
- see above, CL_BBP_BS_ADAPTER_PO_CRT_ERP10 method CREATE_DOCUMENT
Kind regards,
Peter

Debugging RFC Calls

I was going thru the Blog
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
I am not understanding what Michal is trying to say? Would some one explain me please.
I understand that when we are talking to an RFC and error occurs how XI is going to handle.
Thanks

Thanks Michal.
Just I have listed what I have understood, please correct me. (I got confused with your naming conventions)
1) Existing RFC    : RFC-OLD (XI calls RFC_OLD)
2) Copy            : RFC-OLD_Copy
3)                 : Delete the function code in RFC-OLD
4)                 : RFC-OLD Calls RFC-OLD_Copy
DATA: queue_name like TRFCQOUT-QNAME.
*setting the queue name
queue_name = 'DEBUG_QUEUE'.
    call function 'TRFC_SET_QUEUE_NAME'
      exporting
        qname              = queue_name
      exceptions
        invalid_queue_name = 1
        others             = 2.
    if sy-subrc <> 0.
    endif.
*call the new function in the background *and passing all the parameters from the old RFC! *so we'll be able to debug the RFC with correct *parameters
CALL FUNCTION 'RFC-OLD_Copy'
in background task
destination 'NONE'
as separate unit
TABLES
    TABLESAMPLE       = TABLESAMPLE.
*remember about the commit work
Commit Work.
Endfunction.

How to debug crm programs

hi abapers i need to know how to debug the crm programs.

Hi Rockey,
IF u have the integration with CRM and R/3.Then u will use the Middle ware BADI's to copy the data from CRm to r/3 or R73 to CRM.
You can debug that that BADI and u can see where u are going wrong.
Mainly in CRM
we will have the FM's.Through this function modules we ill do evrything in the CRM.
CRM_ORDER_SAVE.
CRM_ORDER_MAINTAIN
CRM_ORDER_READ.
IF we want to get the Data from R73 to CRM. then you can write RFC'S toget the data.
There are so many ways are there.JUst put the breakpoints.In ur middle ware BADI's
then i hope it may help you.
Thanks

Debugging RFC

I just rolled out a new app and can't get he RFC call to work.   The trace file shows:
---> RFC MESSAGE/ERROR : 104
RFC_ERROR_SYSTEM_FAILURE
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
So I did a bit of messing around in SM59. The ONLY thing I would change in SM59 was
the program being called. I changed the called program than ran connection test. All these Unix programs are owned by the same user and have the same rights.
/usr/sap/DEV/SYS/exe/run/tp -> worked OK
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
copied 'tp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
/usr/sap/DEV/SYS/exe/run/sapftp -> worked OK
copied 'sapftp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
copied orignal tf80server.csh back
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
The timeout doesn't seem to be consistant what whatever program I put in. I even created a short shell script (called vince.sh) that only had:
   echo "hi"
   exit 0
/usr/sap/DEV/SYS/exe/run/vince.sh -> timed out
BUT copied 'tp' to 'vince.sh'
/usr/sap/DEV/SYS/exe/run/vince.sh -> worked OK.
So I don't think it is a TaxFactory issue but an internal SAP/RFC
issue. I am unsure how to debug further.
Suggestions?
Thanks!
HP-UX 11.31 Oracle 11.2.0.2 SAP 7.00 Kernel 278 Basis Support Pack 22

Though I would still like to know how to further debug RFC turns out it is a BSI issue. The tf80server executable turned out to be the point of failure.

How to debug extraction a datasource in ecc starting execution in bw ?

HI gurus,
how to debug extraction a datasource in ecc starting execution in bw ?
Thanks.

Hi,
In your issue i thick data source trace in BW is not possible but RFC is the main criteria here if it is correct data will comes to the bw automatically when ever info package triggers.
If you need to check the data source data in trace mode and it is not coming properly, then we need to check from RSA3 by executing with debug mode check box option.
Still need any clarification let me know.
Thanks & Regards,
Srinu.Rapolu

How to debug in SAP Netweaver Developers Studio?

Hi there,
I am trying to debug and slove my error in SAP NWDS.
I am building portal application->JSPDynPage
I am trying to debug the jsp code behind page, it doesn't realli give error message like the java beans does.
I am quite new to this and do not know how to set the function to test and debug this page can anyone provide any solution ?
I have have this prob pls refer to this link
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=192104">https://www.sdn.sap.com/irj/sdn/thread?threadID=192104</a>
Thanks loads
Quatre

Hi Quatre ,
-Select the breakpoints in your Dynpages /beans in ur project
-To debug u have to change the prespective to debug which u can find in
window/open prespective /Debug in NWDS
-Select the Run/Debug or the Debug icon in the toolbar.
-Fill the project name ,application name in the in the wizard opnend .
- Follow the debugging using the next step over F6 ,step return F7 keys .
These link may be helpful:
http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/def86ab54da5418a3575373934ca00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/31e24044b80b06e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/cffcb407c67842b122bd1296dc810f/frameset.htm
U can always find out the way in the PDK development /how to debug/
ie in NWDS /HELP /SAP WAS AS Documentation /SAP J2ee Enterprise Java Beans/Java development User Guide /Running and Debugging
Cheers,
Swathi Rao
Do offer pts:-)

How to debug web app with weblogic?

I wrote a web app that includes jsp files and some javabeans, then I put the jsp files to directory
mydomain\applications\DefaultWebApp
then I complied javabeans and put those classes to
mydomain\applications\DefaultWebApp\WEB-INF\classes
Then I start the weblogic,it runs very well.
I modified some javabean, complie them and put classes override the old classes,
but the web app can not find the new classes.
Any one know How to debug web app(with javabeans) in weblogic?
thanks!

how to config the hot deploy?
thxSorry, for this delay in responding. I had set notify me with email option in Watch This topic; but I never did get any email notification.
I use wls6.1; I think the process may be very similar to this in wls8.x. In wls6.1 (sp5), this is done via the -
Dweblogic.ProductionModeEnabled=False or
Dweblogic.ProductionModeEnabled=True
in the startup cmd/sh script. Out of the box, wls6.1 is set to Dweblogic.ProductionModeEnabled=False which automatically enables hot deploys.

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 RFC

Similar Messages

Maybe you are looking for