How to debug "vic-2fxo"'s dialer information?

who can tell the correct way to see the debug information about the vic-2fxo?
once i have used the command" debug dialer events" and " debug dialer packets" in the router. And I can initiate a successful call from remote phone to the Call manger through the vic-2fxo in the router. But I can see any debug information in the router either at the console or at the remote terminal.
Thanks
Sincerely

What debug information are you looking for. If you are using FXO for voip purposes then debug vpm would show you the voice port signaling events and debug vtsp all would show you debug of vtsp layer when it communicates with the ccapi layer. For voip you can turn on debug voip ccapi inout. There are other deugs that can give you much more verbose information if you want to read through the h225 and h245 messages.

Similar Messages

Putting PVDMs in NM-2V / VIC-2FXO / VIC-2FXS into DSP farm

I have a Cisco 2650XM router with an NM-2V module with one VIC-2FXO and one VIC-2FXS card in it. I'm very new to Cisco voice stuff and want to get started with it. I'm trying to pool the PVDMs on this router into a DSP farm so that they can be used in CME 4.1 with call conferencing / transcoding / VoIP calls between Cisco IP Communicator and Cisco VoIP physical phones but I'm having issues doing so. I believe I'm supposed to create a DSP farm by going into "voice-card X" mode and assigning them to the DSP farm?
I know that there are PVDMs present because they are listed when I do a "show voice dsp detail." I'm not sure if the PVDMs are present in the NM-2V module or actually on the VICs. Can someone offer advice?

Yeah, the only cards / modules that I have in the router are the NM-2V, VIC-2FXO, and VIC-2FXS. Here is the "show diag" output as well as some other ones that may be useful.
Press RETURN to get started!
*Mar 1 00:00:05.949: %LINEPROTO-5-UPDOWN: Line protocol on Interface VoIP-Null0, changed state to up
*Mar 1 00:00:25.281: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
*Mar 1 00:00:25.970: %SYS-6-CLOCKUPDATE: System clock has been updated from 00:00:25 UTC Fri Mar 1 2002 to 17:00:25 AZT Thu Feb 28 2002, configured from console by console.
*Mar 1 00:00:26.439: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to up
*Mar 1 00:00:27.873: %SYS-5-CONFIG_I: Configured from memory by console
*Jan 4 02:05:04.149: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C2600 Software (C2600-ADVENTERPRISEK9-M), Version 12.4(15)T14, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 17-Aug-10 05:40 by prod_rel_team
*Jan 4 02:05:04.153: %SNMP-5-COLDSTART: SNMP agent on host KINASE is undergoing a cold start
*Jan 4 02:05:04.322: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF
*Jan 4 02:05:04.322: %CRYPTO-6-GDOI_ON_OFF: GDOI is OFF
*Jan 4 02:05:05.435: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/0/0, changed state to up
*Jan 4 02:05:05.435: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/0/1, changed state to up
*Jan 4 02:05:05.439: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/1/0, changed state to up
*Jan 4 02:05:05.439: %LINK-3-UPDOWN: Interface Foreign Exchange Office 1/1/1, changed state to up
CNF-FILES: Clock is not set or synchronized, retaining old versionStamps
CNF files update complete (post init)
KINASE>en
KINASE#show diag
Slot 0:
C2650XM 1FE Mainboard Port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 3.0
PCB Serial Number FFFF
Part Number : 73-7755-04
RMA History : 00
RMA Number : 0-0-0-0
Board Revision : A0
Deviation Number : 0-0
Product (FRU) Number : C2650XM-1FE
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 03 6E 41 03 00 C1 0B FF FF FF 46 46 46
0x10: 46 FF FF FF FF 82 49 1E 4B 04 04 00 81 00 00 00
0x20: 00 42 41 30 80 00 00 00 00 FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Slot 1:
4 PORT Voice PM for C2600 Port adapter
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware revision 1.1 Board revision H0
Serial number 26333860 Part number 800-02491-02
FRU Part Number NM-2V=
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x00: 01 65 01 01 01 91 D2 A4 50 09 BB 02 00 00 00 00
0x10: 88 00 00 00 01 06 27 17 FF FF FF FF FF FF FF FF
0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF FF
VIC Slot 0:
FXO Voice daughter card (2 port)
Hardware revision 1.1 Board revision J0
Serial number 21522658 Part number 800-02495-01
Test history 0x0 RMA number 00-00-00
 Connector type Wan Module
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 0D 01 01 01 48 68 E2 50 09 BF 01 00 00 00 00
0x30: 98 00 00 00 00 07 22 01 FF FF FF FF FF FF FF FF
VIC Slot 1:
FXO Voice daughter card (2 port)
Hardware revision 1.1 Board revision J0
Serial number 22783161 Part number 800-02495-01
Test history 0x0 RMA number 00-00-00
 Connector type Wan Module
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 0D 01 01 01 5B A4 B9 50 09 BF 01 00 00 00 00
0x30: 98 00 00 00 00 11 16 01 FF FF FF FF FF FF FF FF
KINASE#sh voice dsp detail
DSP DSP DSPWARE CURR BOOT PAK TX/RX
TYPE NUM CH CODEC VERSION STATE STATE RST AI VOICEPORT TS ABORT PACK COUNT
==== === == ======== ========== ===== ======= === == ========= == ===== ============
C542 001 01 None 9.4.7 IDLE idle 0 0 1/0/0 NA 0 602/623
C542 002 01 None 9.4.7 IDLE idle 0 0 1/0/1 NA 0 593/590
C542 003 01 None 9.4.7 IDLE idle 0 0 1/1/0 NA 0 601/622
C542 004 01 None 9.4.7 IDLE idle 0 0 1/1/1 NA 0 593/590
KINASE#sh dspfarm
DSPFARM Configuration Information:
Admin State: DOWN, Oper Status: DOWN - Cause code: ADMIN_STATE_DOWN
Transcoding Sessions: 0(Avail: 0), Conferencing Sessions: 0 (Avail: 0)
Trans sessions for mixed-mode conf: 0 (Avail: 0), RTP Timeout: 600
Connection check interval 600 Codec G729 VAD: ENABLED
KINASE#config t
Enter configuration commands, one per line. End with CNTL/Z.
KINASE(config)#voice-card ?
<0-1> Voice interface slot #
KINASE(config)#voice-card 0 ?
% Unrecognized command
KINASE(config)#voice-card 0?
% Unrecognized command
KINASE(config)#voice-card 0?
% Unrecognized command
KINASE(config)#voice-card 0/?
% Unrecognized command
KINASE(config)#voice-card 0
 ^
% Invalid input detected at '^' marker.
KINASE(config)#voice-card 1
 ^
% Invalid input detected at '^' marker.
KINASE(config)#
KINASE(config)#voice-port 1/0/0
KINASE(config-voiceport)#?
Voice-port configuration commands:
battery-reversal Enable FXO battery-reversal detection
bearer-cap Specify the bear capability
busyout Configure busyout trigger event & procedure
comfort-noise Use fill-silence option
connection Specify Trunking Parameters
cptone Configure voice call progress tone locale
default Set a command to its defaults
description Description of what this port is connected to
dial-type Configure type of dialer for voice
disc_pi_off close voice path when disconnect with PI received
echo-cancel Echo-cancellation option
exit Exit from voice-port configuration mode
impedance Specifies the terminating impedance of the interface
input Configure input gain for voice
music-threshold Threshold for Music on Hold
no Negate a command or set its defaults
non-linear Use non-linear processing during echo cancellation
output Configure output attenuation for voice
playout-delay Configure voice playout delay buffer
pre-dial-delay FXO Pre-dial Delay
ring Number of rings
shutdown Take voice-port offline
signal The signaling type for the interface FXS or FXO
snmp Modify SNMP voice port parameters
station-id Configure station ID
supervisory Configure answer + disconnect supervision options
threshold Threshold [noise] for voice port
timeouts Configure voice timeout parameters
timing Configure voice timing parameters
translate Translation rule
translation-profile Translation profile
trunk-group Configure interface to be in a trunk group
voice-class Set voiceport voice class control parameters
KINASE(config-voiceport)#
Looks like the "voice-port" command works, but not the "voice-card" command.

VIC2-2FXO and VIC-2FXO

In my environment there is a PBX connecto VIC2-2FXO at router CISCO1751-V. I have an old PBX and when I change the card to VIC-2FXO(EOL), I have from from PBX e works fine. But if I return the new card VIC2-2FXO it doesn't work, even tone is missing. What a real difference between VIC-2FXO and VIC2-2FXO

Hi Almir,
The card is comatible with 1751-4V. The VIC2 cards are the new generation cards. Working wise they are no different. I checked the configs nd they looked kinda incomplete. Usually the FXO works with a "connection plar/trunk". Neither did I notice any voip dial-peers.
Sample config for call flow : (phone---pbx---vic2-fxo---router1--ip---router2---fxs--phone)
voice-port 2/0
cptone BR
connection plar 3000
dial-peer voice 100 voip
destination-pattern 3000
session target ipv4:p.q.r.s
dial-peer voice 1 pots
destination-pattern .T
port 2/0
The above config should be fine for inbound and outbound calls. If this doesn't work please send me the following-
1. Exact call flow eg
2. deb voice ccapi inout
3. debug vpm signal
4. debug vtsp events
5. debug vtsp session
Subhrojyoti

How to debug when you can't recreate error consistently

I have a simple illustrator-type application in which I draw rounded rectangles to a JPanel and then the user is able to move them around (the position and repaint is done in via the mouseDragged interface.
Sometimes, the application shuts down when I am dragging a box with this message:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
# An error report file with more information is saved as hs_err_pid3400.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
I checked the error report and it suggests the problem is within the PathFiller.WriteAlpha. The entire report is below. The problem I have is that if I restart the application and place boxes in the exact same locations as before, and try moving the one that caused the error, the error is not thrown.
I have no idea how to debug this as I can't even consistently reproduce. I just upgraded to the newest JDK (I think it was 7).
Thanks for any insight and help you can offer.
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
--------------- T H R E A D ---------------
Current thread (0x00acae38): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000007
Registers:
EAX=0x00a9c6b8, EBX=0x02e33930, ECX=0x00a9c6a4, EDX=0x00000001
ESP=0x0303f314, EBP=0x0303f328, ESI=0x00a35f1c, EDI=0xffffffff
EIP=0x6d236a0c, EFLAGS=0x00010286
Top of Stack: (sp=0x0303f314)
0x0303f314: 02e2865c 00a35f1c 02e33930 ffffffff
0x0303f324: 02e2865c 0303f34c 6d236ce8 02e33930
0x0303f334: 00a35f1c 02e33930 02e2865c 02e33930
0x0303f344: 00acaef8 02e34774 0303f378 6d2326be
0x0303f354: 02e33930 00a35f1c 02f13380 00000001
0x0303f364: 00000020 00000000 22fb02e8 22fad0d0
0x0303f374: 00acae38 0303f3a0 00b6a767 02f13380
0x0303f384: 0303f3b8 0303f3b4 00000001 00000020
Instructions: (pc=0x6d236a0c)
0x6d2369fc: 85 ff 89 7d f8 0f 84 16 01 00 00 eb 03 8b 7d f8
0x6d236a0c: d9 47 08 d8 15 50 c0 23 6d 8b 47 04 d9 55 fc 89
Stack: [0x03000000,0x03040000), sp=0x0303f314, free space=252k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [dcpr.dll+0x6a0c]
C [dcpr.dll+0x6ce8]
C [dcpr.dll+0x26be]
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
V [jvm.dll+0x86401]
V [jvm.dll+0xdb172]
V [jvm.dll+0x862d2]
V [jvm.dll+0x8602f]
V [jvm.dll+0xa0bcb]
V [jvm.dll+0x10bdad]
V [jvm.dll+0x10bd7b]
C [MSVCRT.dll+0x2a3b0]
C [kernel32.dll+0xb50b]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x000360c0 JavaThread "DestroyJavaVM" [_thread_blocked, id=696]
=>0x00acae38 JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
0x00ac5530 JavaThread "AWT-Windows" daemon [_thread_in_native, id=3396]
0x00ac50b0 JavaThread "AWT-Shutdown" [_thread_blocked, id=2656]
0x00ac3eb8 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1644]
0x00a6ef28 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=408]
0x00a6dc28 JavaThread "CompilerThread0" daemon [_thread_blocked, id=992]
0x0003fda0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1756]
0x00a42240 JavaThread "Finalizer" daemon [_thread_blocked, id=2156]
0x00a40d58 JavaThread "Reference Handler" daemon [_thread_blocked, id=328]
Other Threads:
0x00a3e460 VMThread [id=3024]
0x00a702a8 WatcherThread [id=1740]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 576K, used 20K [0x22a70000, 0x22b10000, 0x22f50000)
eden space 512K, 2% used [0x22a70000, 0x22a73220, 0x22af0000)
from space 64K, 12% used [0x22af0000, 0x22af2128, 0x22b00000)
to space 64K, 0% used [0x22b00000, 0x22b00000, 0x22b10000)
tenured generation total 1408K, used 435K [0x22f50000, 0x230b0000, 0x26a70000)
the space 1408K, 30% used [0x22f50000, 0x22fbcd10, 0x22fbce00, 0x230b0000)
compacting perm gen total 8192K, used 388K [0x26a70000, 0x27270000, 0x2aa70000)
the space 8192K, 4% used [0x26a70000, 0x26ad1170, 0x26ad1200, 0x27270000)
ro space 8192K, 67% used [0x2aa70000, 0x2afcd9f8, 0x2afcda00, 0x2b270000)
rw space 12288K, 46% used [0x2b270000, 0x2b813808, 0x2b813a00, 0x2be70000)
Dynamic libraries:
0x00400000 - 0x0040d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.exe
0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
0x6d730000 - 0x6d8c7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\client\jvm.dll
0x77d40000 - 0x77dd0000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x6d2f0000 - 0x6d2f8000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\hpi.dll
0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d700000 - 0x6d70c000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\verify.dll
0x6d370000 - 0x6d38d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.dll
0x6d720000 - 0x6d72f000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\zip.dll
0x6d070000 - 0x6d1d7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\awt.dll
0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\uxtheme.dll
0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
0x73940000 - 0x73a10000      C:\WINDOWS\system32\D3DIM700.DLL
0x6d2b0000 - 0x6d2ef000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\fontmanager.dll
0x74720000 - 0x7476b000      C:\WINDOWS\system32\MSCTF.dll
0x7c9c0000 - 0x7d1d5000      C:\WINDOWS\system32\shell32.dll
0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
0x773d0000 - 0x774d2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
0x5d090000 - 0x5d127000      C:\WINDOWS\system32\comctl32.dll
0x605d0000 - 0x605d9000      C:\WINDOWS\system32\mslbui.dll
0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.DLL
0x6d530000 - 0x6d543000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\net.dll
0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
0x6d550000 - 0x6d559000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\nio.dll
0x6d230000 - 0x6d253000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\dcpr.dll
VM Arguments:
java_command: writingplatform.Main
Launcher Type: SUN_STANDARD
Environment Variables:
CLASSPATH=C:\Program Files\Java\jre1.5.0_05\lib\ext\QTJava.zip
PATH=C:\Program Files\Microsoft DirectX 9.0 SDK (August 2005)\Utilities\Bin\x86;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\SSH Communications Security\SSH Secure Shell
USERNAME=Wanderer
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 2 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 1047764k(366012k free), swap 2518724k(2059484k free)
vm_info: Java HotSpot(TM) Client VM (1.5.0_07-b03) for windows-x86, built on May 3 2006 01:04:38 by "java_re" with MS VC++ 6.0

This is not your bug, it's Sun's. All you can do is to:
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
On the other hand, if you cannot afford to wait and just
want to find a quick workaround, you will at least need
to find a way to reproduce the bug with a reasonable
frequency. If you are absolutely unable to reproduce it,
just forget it, but still report it to Sun.

How to debug a report

how to debug a report
i am new to ABAP

Hi
ABAP Debugger
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 line of code that tells the ABAP runtime processor to interrupt the program at that 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.
Running a Program in Debugging Mode
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 useful if you do not know the program very well 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 program 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.
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 active of the program that has just been executed by choosing Goto  Further Information  Program Attributes.

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.
go to se38->give ur program name-.execute->give /h at command prompt->execute->now debugging will start->
f5-used for line by line debugging
f6-used for directly executing function modules or performs i.e. control won't go into that block.
f7-run to cursor
f8-direct executing.
fileds: here we can check fild values.
click fileds option and double click on the filed or type the filen name beside filed
tables : here we can check the data in the internal table.
click tables option and double click on the internal table.
Break points:
if you want to debug a particulr part you can use this.
place the cursor at any perform click breakpoint or double click on that line.it will be set.
if /h from report statement it will debug,so for debugging from particular point we will use break points.use f7 to traverse between multiple break points.
Watch-points: In some cases we need to check the data populated in the internal table for eample if we want to check the data of internal table record belongs to 100th vendor we will create watch point for this goto->breakpoints->create watch points->give filed itab-lifnr->=->100.
debugging procedure:
Use '/H' in the command line and execute the report/program, so that it goes to debugging mode
2. keep a hard coded break point in the code like BREAK-POINT and it stops there.
3.From the program Menu, Keep the Soft Break-points and do the debugging.
see the links
Refer to this thread
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.sappro.com/downloads/Settings&SystemAreas.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/frameset.htm
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=3187106
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=850453
https://forums.sdn.sap.com/click.jspa?searchID=2673672&messageID=1546485
https://forums.sdn.sap.com/click.jspa?searchID=2673628&messageID=2048883
http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
http://www.sap-img.com/abap/testing-and-debugging-abap-codes-functions.htm
Reward points if useful

How to debug adapter module in PI 7.1

Hello all,
I am trying to figure out how to debug adapter module in PI 7.1.
I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
The only option is to send debug information to log file. So in the module code like:
audit.addAuditLogEntry(key, status, message);
location.debugT(SIGNATURE, message);
I've read that for PI 7.0, you need to add log-configuration.xml to meta-inf. Is this still required for PI 7.1?
My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log? I can't see any of my log there.
For log in location, I guess I need to go to NWA, can you please share the path (navigation) in NWA to see the location?
Thanks
Jayson

> I guess runtime debugging ( switch AS java in debug mode and attach NWDS to the AS Java to debug as module is being executed) is not possible with adapter module. Please let me know if this is indeed possible and how to enable it.
It is possible for adapter modules as well. I know this from our developers
It should work like this:
/people/christian.drumm/blog/2008/09/30/debugging-java-mappings-using-sap-netweaver-developer-studio
> The only option is to send debug information to log file. So in the module code like:
> audit.addAuditLogEntry(key, status, message);
> location.debugT(SIGNATURE, message);
> My next question is how to read the log in audit log and in location. I've read that the audit log can be read in .../MessagingSystem/monitor/monitor.jsp, under which section of the page I can read the audit log?
In the RWB under Message Monitoring for Adapter, or try the shortcut
http://server:port/mdt

How to debug a run time error encountered while executing ZFunction Module

Hi all,
My requirement is to create a ZFunction Module that Generated a sales order
for multiple line items and works for both Variant Configurable material and a Normal Material.
I am using BAPI_SLSTRANSACT_CREATEMULTI in my Zfunction Module to create a
Sales order
My ZFunction Module works well if I give normal material as input.
It also works well and generates a sales order if I give all Variant Configurable materials as input.
But if I give both Variant Configurable material and a normal material it throws a run time error.
Can some one tell me what is wrong? can some one suggest me how to debug this run time error
Termination occurred in the ABAP program "SAPLCRM_CONFIG_OW" - in
"CONFIG_TO_CBASE".
The main program was "RS_TESTFRAME_CALL ".
In the source code you have the termination point in line 63
of the (Include) program "LCRM_CONFIG_OWF02".
Source Code Extract
Line SourceCde
| 33| LT_CUXI_CUPRT
| 34| LT_CUXI_CUVAL
| 35| LT_CUXI_CUVK
| 36| LS_CUXI_CUCFG.
37
| 38| PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.
39
| 40|* set config to cbase
| 41| CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'
| 42| EXPORTING
| 43| I_CFG_HEADER = LS_CUXI_CUCFG
| 44| I_ROOT_INSTANCE = CV_INT_OBJ_NO
| 45| I_LOGSYS = LV_LOGSYS
| 46| IMPORTING
| 47| E_ROOT_INSTANCE = CV_INT_OBJ_NO
| 48| TABLES
| 49| I_TAB_INSTANCES = LT_CUXI_CUINS
| 50| I_TAB_PART_OF = LT_CUXI_CUPRT
| 51| I_TAB_VALUES = LT_CUXI_CUVAL
| 52| I_TAB_VAR_KEYS = LT_CUXI_CUVK
| 53| I_TAB_RESTRICTIONS = LT_CUXI_CURES
| 54| EXCEPTIONS
| 55| INVALID_INSTANCE = 1
| 56| INTERNAL_ERROR = 2
57
OTHERS = 3. 58
| 59| IF SY-SUBRC <> 0.
| 60| if sy-msgno is initial.
| 61| MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
| 62| else.
|>>>>>| MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
| 64| WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
| 65| endif.
| 66| ENDIF.
67
| 68|ENDFORM. " CONFIG_TO_CBASE

Hey Amit...
Can I Create a Sales order for VC and Non VC items using BAPI_SLSTRANSACT_CREATEMULTI
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
Some one please help me u2026I am just stuggling to get this doneu2026
I dint find any posts that gives me information about this error.
CUX1 034 u201CNo root instance found in header datau201D
In the source code you have the termination point in line 63 of the (Include) program "LCRM_CONFIG_OWF02".

How to debug this error? trying to load excel file to Database

SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" starting.
Information: 0x4004300A at BuyerDedupe, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC001002B at PackageToLoadBuyerDedupe, Connection manager "Excel Connection Manager": The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine. For more information, see http://go.microsoft.com/fwlink/?LinkId=219816
Error: 0xC020801C at BuyerDedupe, Excel Source [2]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0209303. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at BuyerDedupe, SSIS.Pipeline: Excel Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at BuyerDedupe, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at BuyerDedupe: There were errors during task validation.
SSIS package "c:\users\asubedi\documents\visual studio 2012\Projects\Integration Services Project1\Integration Services Project1\PackageToLoadBuyerDedupe.dtsx" finished: Failure.
how to debug this issue?

Hi Arjunji,
The issue occurs because you have only 32-bit Microsoft ACE 12.0 OLEDB drivers installed, however, the package runs in 64-bit runtime mode which requires 64-bit drivers.
To avoid this issue, you need to either install the 64-bit
Microsoft Access Database Engine 2010 Redistributable or run the package in 32-bit runtime mode. To run the package in 32-bit runtime mode, in SSDT, you can set the Run64BitRuntime property of the IS project to False; in a SQL Server Agent job, you can
configure the SSIS Package Job step and check the “Use 32 bit run time” option.
In addition, please note that the 32-bit install file of Microsoft Access Database Engine 2010 Redistributable and the 64-bit one cannot be installed side by side on a single server. However, if your current ACE 12.0 OLE DB drivers are installed by 32-bit
Office suit, you can go ahead and install the 64-bit Microsoft Access Database Engine 2010 Redistributable.
Regards,
Mike Yin
TechNet Community Support

VOIP home lab with cisco 2620 and VIC-2FXO port

Hi all,
I m considering building a home lab for studying CCVP, the lab would be based on the follow components :
- CUCM 8.X (already installed)
- A couple of soft phones running in VMWARE with IP Blue and CIPC (they are already in place and registered with the CUCM)
- Cisco router 2620 with NM-2V and VIC-2FXO-M2 (for europe, I'm in France)
so here are my questions :
1/ it looks like the NM-2V comes with integrated DSP, so I should not need more DSP, I have got one PSTN analogic line only so I can make only one call at a time, please confirm
2/ my analog line comes via my home internet provider dsl box, i have already tried to connect an analog phone and it works, please confirm the router will be able to receive and place calls
thanks for your help, I m looking forward to begin my voice lab

1. Yes, the NM-2V has built-in DSP resources for up to four calls (max voice port density with two 1st generation VICs). You cannot add further DSP chips to the NM-1V/2V, nor would you need to for what it does. You have one PSTN phone line, thus you can only make one call at a time. If you had a second line you could use the other FXO port for a second concurrent call.
2. If the phone line works then it will work with the router to make and receive calls. As Gregory said, just configure dial peers for what you need to do.
Here is some info on the NM-2V:
http://www.cisco.com/en/US/products/hw/modules/ps2617/products_tech_note09186a0080094ac0.shtml

How to debug the update FM

Hi,
I am facing a problem with the debugging of the update FM. I have enabled the update debugging and the system says that update debuging is on . even though the control did not go into the FM.
Do i need to check in any other transaction . Please give me the details steps on how to see the what is happening in the update FM.
Full marks are guaranteed.
thanks
sankar

Hi
I have got a clue from SAP help on how to debug the update FM see the below information from SAP
When you debug a program that calls function modules using the IN BACKGROUND TASK addition, they are processed in a background work process (additional internal session). If you set the In background task: Do not process option, the system collects the function calls, but does not start the background work process. The Debugger assigns a transaction ID, which identifies the background work process uniquely. You can now start the Debugger for the background work process using transaction SM58. You can select the function module concerned here, and then execute it via the Edit menu.
I have done everything that is said above , but could not find any entries in SM58
any suggestions
thanks
sankar

Internal error - how to debug and fix

Hi Gurus
I am trying to enter data for a business partner using transaction BP. I am able to create the BP (person) however when I attempt to enter communication information, such as telephone number, I receive the following error message:
Internal error - access to IT_ADR2_L
Can anyone tell me how to debug this? Please include individual steps, as I am not a developer.
Any help greatly appreciated.
Thanks
Harrrry

Dear Harry
I think there are any permission issue better to talk basis team, because i has work in my side.

How to debug the workflow

dear friends,
please tell me how to debug the workflow, if you have time then you just see the workflow WS99900212 . in this i have done Leave Approver Notification . but i want to debug on that how to flow step by step .
please you tell me on same workflow , where i am going to take breakpoint.
Thanks in Advance for help.
Cheers.
Puneet.

You can try first of all to enable more logging. (I assume you are running release ERP 2005 since you are not saying what your release is.)
In the workflow builder, select menu item "Goto", "Basic data"
Select the "Version-dependent (current workflow version)" tab
Select the "Control" tab within the version-dependent subscreen
Select the "Performance optimization" tab within the control subscreen
Change the "Settings" drop-down value to "No restrictions on logging".
That will give you much more information in the workflow log. The description of this choice says "All the messages are logged. All runtime operations can be traced." As also noted: don't keep this setting in a production system.

How to debug a form module (Oracle 11G Forms) through URL

How to debug a form module (Oracle 11G Forms) through URL.
My server OS is Unix. So i could not able to do the Debug Forms from the Form Developer.
It is displaying a message that "Cannot find the module". Becuase the system is trying find out the module in Unix system instead of ma local system(Windows).
I need to debug ma module through URL.
I can place the fmb and fmx in predefined form path in Server.
Please help me out to solve this issue..

This is a little unclear. If your goal is to use the Forms Builder Debugger while running your form on a Unix machine, this can be done. However, the form must first be in running order. So before trying to attach the debugger you must first be able to start it without the debugger. For example:
http://yourServer:OHS_port_number/forms/frmservlet?form=yourFMX
Once this is properly running you can turn on debugging. If your form won't even start, then using the Debugger isn't going to help you because it is designed to troubleshoot coding problems and not configuration problems.
So, do this to use the Debugger:
http://yourServer:OHS_port_number/forms/frmservlet?form=yourFMX&debug=yes
This will display a dialog box with some information. Do not click on OK yet as you will need this information to enter into the Forms Builder. Now, open the Forms Builder and click on Debug > Attach Debug. You will be asked for the information displayed in the dialog where you attempted to start the form. Enter it here (in the Builder) then click on ok in both places. To display the Debugger (in the Builder), click on Debug > Debug Console. Then from its toolbar click on the buttons related to what you want to monitor. Including a break point in your application code is often a more helpful way to use the debugger.
Most of this information is explained in the Forms Builder Online Help
Forgot to mention...
To debug runtime issues, refer to the Forms Deployment Guide here (this assumes you are using 11.1.2):
http://docs.oracle.com/cd/E38115_01/doc.111210/e24477/appa.htm
Edited by: Michael Ferrante (Oracle) on Feb 21, 2013 1:45 PM

How to Debug the Failed Data loads?

Hi..All
Can Any one plz explain How to Debug the different types of Failed Data Loads?
Thanks & Regards
Jonn

Hi Jonn,
If any data failed ....1st analyze where it occurs according to that what we have to decide...
Analysis:
1.Check the Status Tab in RSMO--here we can get error information
2.Check the Details Tab in RSMO--here we can get whether extraction is completed,and where it is exactly failed i.e while updating from PSA or in Update rules etc
3.Check the corresponding request job log in SM37.
4.Check whether any shortdump in ST22.
5.Check the Request status in the Target...some times activation job failed in SM37 but in the Target we found as activated.
6.Check BD87 Transaction for any IDOC errors.
7.Check SM58 for TRFCs
Hope this helps u.....
Mohan

RE: How to debug enhanced classes

The line number information for classes is not affected by the
enhancement process. For example, the pre-enhanced code 'this.foo = 2'
looks like the following in pseudo-bytecode:
aload_0 // load 'this' onto stack
iconst_2 // load '2' onto stack
putfield <foo> // place '2' into field 'foo' of 'this'
The replacement code, 'jdoSetFoo (this, 2)' looks like this:
aload_0 // load 'this' onto stack
iconst_2 // load '2' onto stack
invokestatic <jdoSetFoo> // invoke static method jdoSetFoo with the
args
The two bytecode blocks are the exact same length, and this holds true
for setting fields as well.
Java line number tables mark the bytecode position and length of each
source code line. Because the enhancer doesn't change either of these
properties, the line number tables remain correct, and line numbers
match even after enhancement.
If you thought you saw line number discrepencies, I'd be very very
interested in seeing a specific example, because I just don't see how
they could possibly exist, with the exception of 2 places:
1. Cloning code. The enhancer adds special instructions after cloning.
2. Static initializer blocks. Again, the enhancer adds to the static
init block so that classes register themselves with the JDOImplHelper.
-----Original Message-----
From: David Ezzio
To: Tech Trader JDO List
Sent: 8/2/01 6:05 PM
Subject: Re: How to debug enhanced classes
In TT Beta 1, I noticed that the line numbers were not matched up
correctly for the enhanced classes. It's a bug. Don't know if Beta 2
is supposed to have fixed it. I used BugSeeker2.
David

Alex
I'm getting the same problem you had. I can't debug my enhanced classes
with JBuilder 6. Have you solved this question?
TIA
Arthur
Roytman, Alex wrote:
Eric,
I meant source debugging not just stack traces
I could not do it with JBuilder. I do not know how debugger works but
debug info in binaries do not match unenhanced source code
Alex
-----Original Message-----
From: Eric Lindauer [mailto:[email protected]]
Sent: Thursday, August 02, 2001 1:34 PM
To: Roytman, Alex; JDO-ListServ
Subject: Re: How to debug enhanced classes
Shouldn't you be able to debug them just like normal classes? The line
numbers in the stack traces shoud all be the same as those found in an
unenhanced class.
Of course, if you mean debug a problem with the JDO implementation,
well,
you don't have the source anyways so what good would it do? :)
-Eric
----- Original Message -----
From: "Roytman, Alex" <[email protected]>
To: "JDO-ListServ" <[email protected]>
Sent: Thursday, August 02, 2001 1:07 PM
Subject: How to debug enhanced classes
Has anybody came up with a method to debug enhanced classes?

How to debug "vic-2fxo"'s dialer information?

Similar Messages

Maybe you are looking for