Delta Uplaod Debugging problem

Hi Gurus,
i did try to load data in to 2lis_03_bf with Delta Upload,but it's showing me error and then i pressed the Debugger option in Info package screen and i pressed the Short Dump and i have set some Break points and i have run it.After that i deleted all Break points.
Now the Problem is when i click on InfoPackage,the ABAP RUn time errors screen is displaying.I want to come out from Debugging screen.
Please help me any one?
thanks in advance.
Regards

Hi
After going to ABAP Debugger screen go to the standard menu and select debuguing off
that might help you
Regards
Ajay
Assign points if useful

Similar Messages

JApplet debugging problem

Hi there all:
I'm having a problem with debugging a JApplet. I created a new workspace, project and applet and didn't make any changes to anything. When I try to debug the applet, I get these messages:
System Error: java.security.AccessControlException: access denied (java.lang.RuntimePermission modifyThreadGroup )
System Error: java.lang.Object java.lang.Class.newInstance0()
System Error: java.lang.Object java.lang.Class.newInstance()
System Error: java.applet.Applet sun.applet.AppletPanel.createApplet(sun.applet.AppletClassLoader)
System Error: void sun.applet.AppletPanel.runLoader()
System Error: void sun.applet.AppletPa
System Error: nel.run()
System Error: void java.lang.Thread.run()
If I change the object from a JApplet class to an Applet class, I can debug just fine.
Anyone know what's going on here?
Thanks
Jeff

Me again. Was doing some searching on the net about this one since I've gotten no response.
Found this at Inprise (Borland) about a debugging problem with JBuilder3 (I assume that the base of jdev is still JBuilder).
http://community.borland.com/article/0,1410,19739,00.html
To quote from their document--------
Question:
I can't seem to debug Applets with JBuilder3 Standard. If I attempt to debug my Applet
I recieve the following error:
java.security.AccessControlException: access denied (java.lang.RuntimePermission
modifyThreadGroup )
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:195)
at java.security.AccessController.checkPermission(AccessController.java:403)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
Why?
Answer:
In a nutshell this is an installation problem with JBuilder3 Standard edition.
The install for JBuilder3 Standard did not provide the file 'DebugApplet.policy'.
To resolve this problem download the file from the following URL:
http://www.borland.com/devsupport/jbuilder/downloads/DebugApplet.policy
After you have downloaded the file, copy the file to your JBuilder3\bin directory.
This will fix the problem.
You can also cut and paste the following:
(NOTE: create the file DebugApplet.policy in your JBuilder3\bin directory)
//DebugApplet.policy
// These policy permissions are needed for the AppletViewer used by sun.tools.debug.
grant {
permission java.lang.RuntimePermission "accessClassInPackage.*";
permission java.lang.RuntimePermission "modifyThread";
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.net.SocketPermission "*", "accept, connect, listen, resolve";
permission java.util.PropertyPermission "appletviewer.version", "read";
permission java.io.FilePermission "<>", "read";
permission java.security.AllPermission;
Could this be a problem in JDev3 too?
Jeff
null

K7n2 delt ilsr instabilty problem update

have a k7n2 delta ilsr have an issue where it is unstalble ie get bsod at welcom etc at 400 fsb ie 200 setting in bios will run at 166 in safe mode the 3200 cpu is reconised as at 2.39 ghz it should be 2.2 ghz if i run cpucz it says the multiplier is *12 is this a motherbord fault have updated bios too 7.8 latesed have tried diff make of memory power supply but i think the problem is looking me in the face in the fact that the cpu is reconised as 2.39 ghz and the muilt is *12 i think it should be * 11 can any body help regards bazer

yes has latesd bios    AMD Athlon(tm) XP 2700+ here is some info pc wizard 2005
Codename :   Barton
Revision :   A2
Technology :   0.13µ
CPU ID :   6.A.0
CPU IDEx :   7.A.0
Features :
VME - Virtual Mode Ext. :   Yes
DE - Debugging Extension :   Yes
PSE - Page Size Extension :   Yes
TSC - Time Stamp Counter :   Yes
MSR - Model Specific Registers :   Yes
PAE - Physical Address Extension :   Yes
MCE - Machine Check Exception :   Yes
APIC - Local APIC Built-in :   Yes
SEP - Fast System Call :   Yes
MTRR - Memory Type Range Reg. :   Yes
PGE - Page Global Enable :   Yes
MCA - Machine Check Architecture :   Yes
PAT - Page Attribute Table :   Yes
PSE36 - 36-bit Page Size Extension :   Yes
PSN - Unique Serial Number :   No
DS - Debug Trace & EMON Store :   No
ACPI - Software Clock Control :   No
SS - Self Snoop :   No
TM - Thermal Monitor :   No
HTT - Hyper-Threading :   No
SBF - Signal Break on FERR :   No
MON - Monitor/Mwait :   No
DSCPL - CPL qualified Debug Store :   No
TM2 - Thermal Monitor 2 :   No
CID - Context ID :   No
EST - Enhanced SpeedStep Tec...   No
NX Bit - No-execute Page Protec...   No
VMX - Vanderpool Technology :   No
Miscellaneous :
FPU - Co-processor Built-in :   Yes
CX8 - CMPXCHG8B :   Yes
CX16 - CMPXCHG16B :   No
CMOV - Conditionnal Move Inst. :   Yes
CLF - Cache Line Flush :   No
FXSR - Fast Float Save & Restore :   Yes
DAZ - Denormals Are Zero :   No
MMX Technology :   Yes
SSE Technology :   Yes
SSE2 Technology :   No
SSE3 Technology :   No
X86-64 Technology :   No
AMD MMX Technology :   Yes
3DNow! Technology :   Yes
Extended 3DNow! Technology :   Yes
3DNow! Pro Technology :   Yes
SMP - MP Capability :   No
Power Status :
Voltage Control :   No
Frequency Control :   No
Thermal Sensor Built-in :   Yes
Addressing Information :
Physical Addressing max. :   34-bit
Linear Addressing max. :   32-bit
Mainboard Upgradebility :
Socket/Slot :   Socket A
Upgrade interface :   ZIF Socket
Supported Speed :   2200 MHz (or more)
Supported Voltage :   1.6V
al Information :
Performance Rating :   PR-3300 (estimated)
Real Frequency :   2164.89 MHz
Multiplier :   12x
Front Side Bus Information :
FSB Frequency :   180.4 MHz
Bus Speed :   360.8 MHz (DDR)
Initial Frequencies :
Frequency :   2000 MHz
FSB Frequency :   166 MHz
Control Clock Frequency :
Type :   None
Thermal Information :
Core Power :   63.42 W (estimated)
Resistance :   0.46 °C/W (estimated)
Processor Performance Information :
Throttle Mode AC :   None
Throttle Mode DC :   Adaptive
Current Configuration :   None
Throttle :   2164 MHz
CPU Throttle Temperature :   60°C
CPU Shutdown Temperature :   100°C
eneral Information :
A0 (RAS 0) :   256 (Single Bank)
A1 (RAS 2) :   256 (Single Bank)
A2 :   Empty
Memory Controller Information :
Memory Controller :   Standard, EDO
Number of connectors :   3
Max. Module Size :   32 MB
Max. Memory Size :   96 MB
Supported Speed :   70ns, 60ns
Supported Voltages :   5v
Error Detection Method :   8-bit Parity
Error Correction Capability :   Unspecified
Current/Supported Interleave :   1-way/1-way
Chipset Information :
Type :   DDR-SDRAM PC2900
Frequency :   180 MHz
FSB/RAM Multiplier :   1/1x
Channels :   Dual
ECC Diagnostic :   No
CAS Latency (tCL) :   3 clocks
RAS to CAS (tRCD) :   3 clocks
RAS Precharge (tRP) :   3 clocks
Cycle Time (tRAS) :   8 clocks
Information SPD EEPROM (A0) :
Manufacturer :   Samsung
Part Number :   M3 68L3223ETM-CCC
Serial Number :   F6016243
Type :   DDR-SDRAM PC3200 (200 MHz)
Size :   256 MB (1 rows, 4 banks)
Module Buffered :   No
Module Registered :   No
Width :   64-bit
Error Correction Capability :   No
Max. Burst Length :   8
Refresh :   Reduced (.5x)7.8 µs, Self Refresh
Voltage :   SSTL 2.5v
Supported Frequencies :   166 MHz, 200 MHz
CAS Latency (tCL) :   2.5 clocks @166 MHz, 3 clocks @200 MHz
RAS to CAS (tRCD) :   3 clocks @166 MHz, 3 clocks @200 MHz
RAS Precharge (tRP) :   3 clocks @166 MHz, 3 clocks @200 MHz
Cycle Time (tRAS) :   7 clocks @166 MHz, 8 clocks @200 MHz
Information SPD EEPROM (A1) :
Manufacturer :   Samsung
Part Number :   M3 68L3223ETM-CCC
Serial Number :   F6056193
Type :   DDR-SDRAM PC3200 (200 MHz)
Size :   256 MB (1 rows, 4 banks)
Module Buffered :   No
Module Registered :   No
Width :   64-bit
Error Correction Capability :   No
Max. Burst Length :   8
Refresh :   Reduced (.5x)7.8 µs, Self Refresh
Voltage :   SSTL 2.5v
Supported Frequencies :   166 MHz, 200 MHz
CAS Latency (tCL) :   2.5 clocks @166 MHz, 3 clocks @200 MHz
RAS to CAS (tRCD) :   3 clocks @166 MHz, 3 clocks @200 MHz
RAS Precharge (tRP) :   3 clocks @166 MHz, 3 clocks @200 MHz
Cycle Time (tRAS) :   7 clocks @166 MHz, 8 clocks @200 MHz

Remote Delta link setup problem with Bean / Access Service

Hello,
I am trying to setup Remote Delta Link (RDL) between two portals. (Both portals same version - EP 7.0 EHP1 SP 05 - are in the same domain)
I already have the Remote Role Assignment working without any issues.
The following have been done successfully:
1. Same user repository has been setup for both the portals
2. Setup trust between producer and consumer (SSO working fine)
3. Producer added and registered succesfully on consumer
4. Permissions setup on producer and consumer
4. pcd_service user with required UME actions setup
I am able to see all the remote content in the Consumer portal.
When I try to copy the remote content and paste it as local content, I am getting the following error:
Could not create remote delta link to object 'page id'. Could not connect to the remote portal. The remote portal may be down, there may be a network problem, or your connection settings to the remote portal may be configured incorrectly.
After increasing the log severity, I am able to see the following in Default Trace:
com.sap.portal.fpn.transport.Trying to lookup access service (P4-RMI) for connecting to producer 'ess_int' with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
com.sap.portal.fpn.transport.Unable to lookup access service (P4-RMI) with information: com.sap.portal.fpn.remote.AccessServiceInformation@31c92207[connectionURL=hostname.mycompany.com:50004, shouldUseSSL=false, RemoteName=AccessService]
AbstractAdvancedOperation.handleDirOperationException
[EXCEPTION]
com.sap.portal.pcm.admin.exceptions.DirOperationFailedException: Could not retrieve the bean / access service to connect with producer
Could not retrieve the bean / access service to connect with producer
Like you can see above, there is some bean / access service which is not retrieved successfully. I am not sure if this is a permission problem on the consumer.
I have checked that the P4 ports are configured correctly (standard - not changed) and I am able to telnet from producer to consumer (and vice versa) on the P4 port.
I am stuck at this point and am not able to find any information on this.
I would really appreciate if some one can point me in the right direction.
Thank you for reading.
- Raj

Hi Raj,
Please check your config of the P4 port on the producer. Is it really 50004 (check SystemInfo of the producer)?
I do think there's a problem with the P4 communication since RDL requires P4 connection.
Do you have load balanced consumer-producer connection? Please refer to this blog for further details
Little known ways to create a load balanced Consumer Producer connection in a FPN scenario
Regards,
Dao

MSI K7N2 Delta ILSR Memory problems

I'm trying to burn in a system in a 50 deg C (122 deg F) room for a minimum of 12 hours. The main system components are as follows:
Motherboard: MSI K7N2 Delta ILSR
CPU: AMD Athlon XP 2800+
Memory: 2x512 OCZ PC3200 EL
My problem is that the burn-in software continues to freeze up during the memory test. I've already contacted the software manufacturers and the software is stable. It's a problem with the way the motherboard handles the memory. I've tried putting the memory in dual channel configuration and changing the timing settings in the BIOS. The SPD settings are 2.5-3-3-7. Right now I have them at 3-4-3-8. It's a lot more stable than it was under the default settings but it still freezes up sometime after 7 hours. Unfortunately, I wasn't around when it froze so I don't know exactly how long it lasted. I can say that after 7 hours, it wasn't showing any slowdown in performance. If anyone could think of anything else I might be able to do to get the system stable, I would greatly appreciate it.

Thanks for the suggestions. The CPU FSB is 200, so it's already matched up there. And we have a ton of fans already. There are two in the front, 4 inside and 1 on the back. It's a custom case, 2u high. The power supply is oversized and more than adequate to provide the required power. I have four of these units running right now. Two with 2x512 sticks and two with 1x1024 sticks. For each combination, the memory clock speed for one is 166 and 200 for the other. I have been loosening up the memory timings trying to get the system stable, but it still isn't. If the power supply is good, and I'm unable to cool the system anymore due to limititions within the case, is there anything you can think of to stabilize the system. Maybe other settings in the BIOS or suggestions on how to go about getting good timings for the memory. Thanks.

MSI K7N2 Delta-ILSR MB Problems, Need Help ASAP!! PLEASE

Ok I just got this motherboard (MSI K7N2 Delta) Yesterday and after getting it setup I began overclocking the Processor (an AMD Athlon XP Barton Mobile 2500+) I was at 11x 215 1.750V Perfectly. I moved to 216 it started to seem unstable so I pushed the VCORE up to 1.775 and tried 217. It couldn't boot so I dropped it back down and decided ok 208 and a 11.5 multi might get me past the 2.4 mark which I was looking for. Well when I changed the Multi. to 11.5 and said save the system just sate as the flashing y for save. I could not change it to n I had already pushed enter So i firgured great and left it alone for a few minutes, nothing so I reset it. Now it refuses to boot/post. It spinds the fans the HD's the Network port is going but I get no picture. I have cleared the CMOS using the jumper I have removed the battery and power for over an hour and I still get nothing. I am assuming this is a BIOS error but I am not sure what to do to fix it. Does anyone here kno maybe, something I have yet to try something I can do? I would hate to RMA it and have to wait on newegg. Hell the thing is a day old. So please any idea's are welcome I have this posted on the Hard Forums as well but I am hopinh this forum may be more popular with getting help as no one is helping over there. Thanks!

Hi,
Cross: Just in case you are doing something wrong there's a clear CMOS guide here, follow it to the letter (and don't forget to put the FSB jumper to SAFE beforehand - there's a note about it in the guide).
How To Clear the CMOS
Your system board or CPU maybe not be dead yet - I had a similar problem with one of my boards and I tried everything - to cut a long story short I eventually got it working!!!
Btw, If you can't boot or get into the BIOS put your other CPU in (clear BIOS again after fitting!), so that you can prove whether your motherboard is working correctly!
Good luck! I'm off ta bed!
Axel

Sun Studio Debugging problem

Hello
I need help configuring the Sun studio debugger to work in fedora 8. The project is loaded from a make file, compiles fine, and runs fine. However, I can not place break points, and when I start the visual debugger, it gives a message box titled progress, and hangs on saying: starting debugger: /lib/libc.so.6
Running from the command line gives me:
$dbx <my program>
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.6' in your .dbxrc
Reading <my program>
Reading ld-linux.so.2
Reading libm.so.6
Reading libmpich.so.1.1
Reading libpthread.so.0
Reading librt.so.1
Reading libc.so.6
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: warning: unknown location expression code (0xe0)
dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
I have another problem in debugging an mpi problem in another installation of Sun Studio on Solaris 10 on a Sun machine. The visual debugger is working fine there, however, I need to debug with mpirun
to decide the number of processors, because by default it loads the application on one processor. Iwill need to do this as well later on the linux machine I am using now, which doesn't even start the debugger on a sequential code so far.
I appreciate your help a lot.
Thank you very much in advance.
Manal

mhelal wrote:
Hi
Thank you for your reply. you said 2 problems,Yes, basically I meant these two:
1. dbx: warning: unknown location expression code (0xe0)
2. dbx: panic: "ThreadAgent::setup_helper"(): Assertion (ta_td_agent) failed - "thread.cc":2674
First one should be fixed in dbx itself, but the second looks like an incompatibility between Fedora's libc and dbx; unless distros in "supported" list upgrade to the same version of libc, dbx can't be changed to match it.
In other words, I'm sorry to say that you will probably not succeed in using dbx on Fedora 8 for the time being.

Debug problem using JDK 1.2.2

Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks

I had this problem earlier today. I deleted the old workspace, created a new one, added my projects in again, recompiled and things were fine. Every now and then my workspaces seem to corrupt and I have to do this, although I don't always get the "can't debug class message"
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Bill:
Hello,
I set up remote debugging in J-Dev 3.1.1.2 and was using it successfully for several days.
I then did some local debugging on a servlet that was compiled using 1.1.8 JDK. Now none of my servlets that are compiled under 1.2.2 can be debugged either locally or remotely. I get a message telling me that the class cannot be debugged.
Can anyone offer suggestions on what could be wrong?
Thanks <HR></BLOCKQUOTE>
null

Debug problem in JDeveloper 3.0

Has anybody come across a problem when debugging an application that causes JDeveloper to go into an infinite loop (until my machine runs out of memory) when a breakpoint is hit.
This only seems to happen on certain files
I've removed JDeveloper 2.0. I've reinstalled JDeveloper 3.0. I've recreated my workspace and project from scratch but I still get the problem.
My project has ~1200 files.
I've also noticed that sometimes the breakpoint is hit and the application being debugged will be paused but JDeveloper does not gain control (i.e. the 'step', 'step into' etc. buttons are still disabled). This is possibly related to the above problem.

Has anybody come across a problem when >debugging an application that causes >JDeveloper to go into an infinite loop >>(until my machine runs out of memory) when a >breakpoint is hit.This is not a known issue but if anyone has a reproducable test case then we'll be happy to follow it up.
Thanks,
Arun

Java debugging - problems with standard input

Hi
I hope somebody can help me with this problem.
I'm developing a Java app that reads from the standard input. I use System.in.read() to do that. When I debug it, I use the Standard I/O window instead of the Run Log window to pass in values, but nothing happens (i.e. the line following the read() is never reached). I also tried to run the app and then attach the debugger to use the Run Log window as standard input, with the same result. If I add a breakpoint before the call to read(), the debugger pauses the execution, so I suppose the breakpoints are OK.
In the executable Info window, Debugging tab, I use the pseudo terminal with the Java debugger.
So my question is: how can I enter values from the standard input in debugging mode?

I believe that you are seeing these problems because we have found the
current versions of RMI found in the JDK to be inherently unscalable -- we
do not listen for them. As you noticed, we recommend that you use our
packages for now, and then do the simple change that you found if you decide
that you do not like WLS. (If you do decide that you do not like us, please
definitely let us know why you chose the way you did!)
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Tim Dawson" <[email protected]> wrote in message
news:397b8cc2$[email protected]..
We're developing a J2EE application on NT using WLS 5.1, SP3, but we don't
want to be tied to any particular J2EE server, so we're making sure that
none of our code is weblogic specific.
In keeping with this philosophy, I created an RMI service that used the
standard java.rmi.* imports instead of weblogic.rmi.* and used thestandard
RMIC compiler rather than the weblogic.rmic compiler.
Unfortunately, I couldn't get the system to work. I kept getting
"java.rmi.MarshalException: Error marshaling transport header; nested
exception is: java.io.EOFException" whenever I'd call Naming.lookup().
Of course, when I did the search & replace with java.rmi.* with
weblogic.rmi.*, and switched from the standard rmic to weblogic.rmic,
everything started working just fine. This is the ONLY change I made!
Has anyone else run into similar problems?
Tim Dawson
Sr. Software Architect
is.com

Debugging problem, in inbound function module.

Hi Experts,
              R/3 system is receiving data through an IDOC called WPUUMS[sales data]. It has been seen that when this data is posted in R/3 through XI the data gets reflected in WE02 / WE05, and is similar to when a manual entry is done the transaction WPUK. But the difference is , when manual idoc generation is done, it is updating correct data in database, but when same data is posted from XI, it is updating data base with in correct data!
   what I cant get to understand is in both the cases, IDOC is posted, and same data is there in the DATA records, but database is getting upated with diff data.
    Also , when I am putting a break point on the inbound function module IDOC_INPUT_POS_SALES_ACCOUNT, it is not hitting the break-point but idoc gets generated successfully with status records like
53 Application Document posted
62 Idoc Passed to application
64 Idoc ready to be transferred to application
50 Idoc added.
Also , i want to know, wether these messeges come step by step or randomly, because, why is the messege 62, before messege 64.
Lastly when I am taking the same IDOC and trying the same in WE19, then it hits the break-point function module IDOC_INPUT_POS_SALES_ACCOUNT successfully.
Experts, comments pls.!
Regards,
Arnab.

Hi,
You are supposed to read the ststus messages from bottom to top. So the actual sequence is:
50 Idoc added.
64 Idoc ready to be transferred to application
62 Idoc Passed to application
53 Application Document posted
Which is correct.
And it is correct that the system bypasses any breakpoint in the background mode. So when the IDoc is coming from XI the posting FM IDOC_INPUT_POS_SALES_ACCOUNT is called in background and so the breakpoint is not called.
Only way to debug the problem is via transaction WE19 in Debug mode.
Regards,
Prakash Pandey

Debugging problems on iPad

I have two applications, and 4.7 installed in two different PCs (64 bits one and 32 bits the other one).
In one PC (32 bits) both apps can be tested with no problem at all. In the other one (64 bits) I debugged one of them once, but now I can't debug any of them.
Problem description: device is there and connected, debug begins, says it's installing and seems to finish it well. It waits for me to initiate the app, but the app is not there. No app for debugging in the iPad.

Hi,
A similar issue has been logged and is being tracked. Please refer to below bug for more description.
http://bugs.adobe.com/jira/browse/FB-33478
Workaround: Even though ipa is not installed on the device, ipa will be generated in the specified output folder(bin-debug).Using iTunes install the ipa on the device and launch the app to make a debugger session.
Let me know if you require more information.
Thanks,
Sanjay

Debug problem

I installed the sneak preview Enterprise portal on my machine. Yesterday i was able to debug my portal application. But today i wasn't. This problem was after the moment I deleted the old portal application.
Can someone tell my how i can fix this problem
Message was edited by: Edward Kust

It could be that your IP address has changed?! In this case, the Developer Studio/Eclipse might not be able to find the portal anymore. I had the same problem, and the strange thing about it is that IE still connects to the portal.

Smartform debugging problem

Hi Experts,
How to debug smartform in quality. can anybody explain me....
Thanks
rajesh

dear
Do one thing apply the breakpoint in smartform where u r getting the problem and execute directly u will come to that point .
Else execute u will get long string name in function module screen :
Goto to the display mode and then put the break point
this will also do
thanx
-ankit

M-Audio Delta 1010LT driver problems with 10.4.6

I'm having problems with the M-Audio drivers for my Delta 1010LT sound card under 10.4.6. Specifically, I'm getting frequent kernel panics if I try to play sound through the card when I boot up in the morning after the computer has been shut down during the night. I've tried using not only the current version of the Delta driver (2.0.5), but also 2.0.4, 2.0.3, and 2.0.1.
Recently, after being very frustrated with this problem, I requested and received a replacement card from the vendor, since both I and M-Audio Tech Support suspected that I might have a defective card. I have to admit that there seems to be some progress. At least for the time being, I have a working setup for Pro Tools M-Powered 7.1 with driver version 2.0.5 and Mac OS 10.4.6. However, I'm finding that I'm still experiencing frequent kernel panics if I try to play sound through the card (any sound application causes a problem, not just PTMP) when I boot up my computer in the morning. (BTW, I probably wouldn't have this problem if the driver would allow my computer to sleep! But that's another story . . .)
I do have a workaround (at least, it seems to be a workaround, though my past experience leads me to believe that it could cease to be one at any moment): immediately upon starting up, I reinstall the driver. Then everything seems to be OK—unless the system freezes (which it does frequently, and which it didn't before I installed the 1010LT), in which case more often than not I get a kernel panic upon rebooting and have to install the driver again.
Since when it does work, it works very well, I don't think that the problem is with my machine. (I've tried switching slots several times, which does not seem to have an effect.) But something is still clearly not right.
BTW, through a process of trial and error, I've determined that there seems to be a conflict, at least on my system, between the M-Audio Delta drivers (all versions) and Intego VirusBarrier X 4 (and, I think, also ClamXav). I assume, though I can't support the assumption, that they may conflict with other anti-virus software as well. With Mac OS X viruses beginning to appear, this is a serious problem that I think should be addressed very soon!
I'd be interested to hear if other users with Delta 1010LT cards have had similar problems under 10.4.6. I've seen a large number of such items involving 10.4.3 and 10.4.4, but there appear to be few reports of such difficulties with 10.4.6.
MDD dual 1.25 GHz Power Mac Mac OS X (10.4.6)

I finally gave up and ordered a Firewire 410, which works beautifully. Too bad that I wasted $200 on a card that I couldn't use, but . . .

Delta Uplaod Debugging problem

Similar Messages

Maybe you are looking for