Run-time specification of DTD
Is there anyway to apply a DTD to an XML file that does not contain a DTD or DTD reference?
Users will generate XML files without a DTD.
When we receive the XML we will attempt to parse it but would like to apply a DTD against it to check its validity.
(Using SAX with C++ Parser)
null
Hi Rajesh,
Here are the attributes.
1.FIXED_COLS
2.LINES
3.TOP_LINE
4.CURRENT_LINE
5.LEFT_COL
6.LINE_SEL_MODE
7.COL_SEL_MODE
8.LINE_SELECTOR
9.V_SCROLL
10.H_GRID
11.V_GRID
12.COLS
13.INVISIBLE
Edited by: Vigneswaran S on May 16, 2008 12:26 AM
Similar Messages
-
Error run time DYNPRO_FIELD_CONVERSION
I have a dump:
Errore run-time DYNPRO_FIELD_CONVERSION
Verific. il 28.11.2007 h 02:12:16
A conversion error occurred.
Causa dell'errore
The current screen processing was terminated, since a situation
occurred from which it could not continue processing.
This is probably due to an error in the current screen of the ABAP
program.
Possibili soluzioni
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Analisi errori
The program flow was interrupted and could not be resumed.
Program "SAPMM06B" tried to display fields on screen 0106. However, an
error occurred while this data was being converted.
Indic. per la correzione
A conversion error occurred while the program was trying to
display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. When attempting to
display the date on the screen, an error will occur that triggers the
error message.
Screen name.............. "SAPMM06B"
Screen number............ 0106
Screen field............. "EBAN-MENGE"
Error text............... "FX015: Sign lost."
Further data:
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
It is probably not possible to eliminate the system error
with ABAP alone.
If you have access to SAPnet, you can search for a relevant note
using the following keywords:
"DYNPRO_FIELD_CONVERSION" " "
"SAPMM06B" bzw. "MM06BO0R_RM06B-EPSTP"
"RM06B-EPSTP"
Ambiente sistema
SAP Release.............. "620"
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system......... "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 26
Short dump setting....... "full"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database owner........... "SAPR3"
Character set............ "it_IT.ISO8859-1"
SAP kernel............... "640"
Created on............... "Jul 16 2006 20:40:53"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "139"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Utente, transazione.....
Client.............. 300
User................ "CONSULENTI"
Language key........ "I"
Transaction......... "ME52 "
Program............. "SAPMM06B"
Screen.............. "SAPMM06B 0106"
Screen line......... 26
Informazioni punto di interr.
The termination occurred in the ABAP program "SAPMM06B" in "RM06B-EPSTP".
The main program was "SAPMM06B ".
The termination occurred in line 14 of the source code of the (Include)
program "MM06BO0R_RM06B-EPSTP"
of the source code of program "MM06BO0R_RM06B-EPSTP" (when calling the editor
140).
The program "SAPMM06B" was started as a background job.
Errore verificatosi durante un'elaborazione Batch-Input
Dettaglio cd. sorgente
000010 *eject
000020 *----
000030 * Positionstyp aufbereiten *
000040 *----
000050 MODULE RM06B-EPSTP OUTPUT.
000060
000070 CALL FUNCTION 'ME_ITEM_CATEGORY_OUTPUT'
000080 EXPORTING
000090 PSTYP = EBAN-PSTYP
000100 IMPORTING
000110 EPSTP = RM06B-EPSTP
000120 PTEXT = T163Y-PTEXT.
000130
ENDMODULE.
Contenuto campi sistema
Cmpo SY Contenuto.................... Cmpo SY Contenuto....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 1 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY VU
SY-UCOMM
SY-TITLE Richiesta d'acquisto mod.: Riepilogo pos.
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Richiami/eventi attivi
N..... Tipo........ Nome..........................
Programma
Include Riga
Classe
1 MODULE (PBO) RM06B-EPSTP
SAPMM06B
MM06BO0R_RM06B-EPSTP 14
Variabili selezionate
1 MODULE (PBO) RM06B-EPSTP
SAPMM06B
MM06BO0R_RM06B-EPSTP 14
DIEN DIEN
4444
495E
EBAN-PSTYP 0
3
0
LIM LIM
4442
C9D0
RM06B-EPSTP
2
0
POTE TXP
5552
4800
T163Y-PTEXT Standard
57666676222222222222
341E4124000000000000
Chiamate applicazione
Il dump non riporta informazioni relative
Informazioni applicazione
Il dump non riporta informazioni relative
Note interne
The termination occurred in the function "dynpconv.c" of the SAP
Basis System, specifically in line 701 of the module
"//bas/640_REL/src/krn/dynp/dybas.c#4".
The internal operation just processed is "ENDM".
The internal session was started at 20071128021215.
Application server....... "assapoa"
Network address.......... "10.58.19.23"
Operating system ........ "AIX"
Release.................. "5.2"
Hardware type............ "00CB585E4C00"
Database server.......... "ars005sapdb"
Database type............ "ORACLE"
Database name............ "PRD"
Database user ID......... "SAPR3"
Rich. attivi nel nucleo SAP
=> 64 bit R/3 Kernel
=> 64 bit AIX Kernel
=> Heap limit = unlimited
=> Stack limit = unlimited
=> Core limit = 1073741312
=> File size limit = unlimited
=> Heap address = 0x11dd952a0
=> Stack address = 0xfffffffffffa920
=> Stack low = 0xfffffffffffa920
=> Stack high = 0xffffffffffff910
=> Stack Trace:
AixStack() at 0x1000206bc
CTrcStack2() at 0x1000207b4
rabax_CStackSave__Fv() at 0x1001520d4
ab_rabax() at 0x10014ef04
dyHandleError() at 0x1005a6850
dypcnvoXt() at 0x100cbd6cc
dynplend() at 0x1010cf268
dynpmcal() at 0x1010c6f60
dynppbo0() at 0x1010c5134
dynprctl() at 0x1010ce40c
dynpen00() at 0x100bd0c30
Thdynpen00() at 0x1000a1f7c
TskhLoop() at 0x1000a5298
tskhstart() at 0x1000bb0d8
DpMain() at 0x101579ca0
nlsui_main() at 0x10154d428
__start() at 0x1000002fc
!!! Invalid stack address encountered: 0x0
!!! Stack corrupted.
Lista dei programmi ABAP in oggetto
Tipo
Programma
DataGen Ora
Dim.car.
Prg
SAPMM06B
25.09.2007 16:07:55
514048
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Typ
T160
12.05.1997 15:22:15
2048
Prg
SAPFMMEX
18.11.2007 09:34:59
177152
Typ
TSTCT
14.02.1998 14:31:34
2048
Typ
TMED
27.08.1994 21:59:16
2048
Typ
TPRG
14.02.1998 14:06:12
2048
Typ
T160D
11.02.2000 14:20:36
5120
Typ
T160V
14.05.1998 22:44:11
6144
Typ
T168T
28.08.1997 09:05:04
2048
Prg
SAPLMEXF
18.11.2007 09:35:00
166912
Typ
T162
02.10.2001 13:56:13
2048
Prg
SAPLSTUP
17.06.2004 12:05:43
65536
Prg
SAPLCNDP
17.06.2004 15:06:47
163840
Prg
SAPFGUICNTL
09.01.2003 17:18:52
20480
Prg
SAPLOLEA
17.06.2004 15:12:42
78848
Prg
SAPLSGUI
09.01.2003 17:15:12
31744
Prg
SAPLSTTM
17.06.2004 15:08:30
75776
Prg
SAPLSBDC
07.01.2003 18:31:25
38912
Prg
SAPLSFES
17.06.2004 15:15:58
174080
Prg
SAPLURFC
17.06.2004 14:25:28
16384
Prg
SAPLSPLUGIN
14.02.2002 14:22:48
6144
Typ
SWCBCONT
15.11.2000 17:55:11
3072
Typ
OLE_VERBS
04.04.1995 16:02:20
2048
Typ
OLE_PA
04.04.1995 16:02:19
2048
Prg
SAPLSCNT
14.02.2002 14:22:47
24576
Prg
SAPSHDTV
17.06.2004 11:46:16
28672
Typ
EBANW
17.06.2004 15:55:16
21504
Prg
CL_CONTEXTFIELD_MM============CP
25.09.2007 16:07:49
9216
Prg
/1BCDWBEN/SAPLMEN0000
18.11.2007 09:35:16
237568
Prg
SAPLSENA
17.06.2004 14:19:40
28672
Typ
EBAN
13.11.2006 11:19:59
20480
Prg
CL_PROCESS_STATE_MM===========CP
25.09.2007 16:07:50
16384
Prg
SAPLSWUG
17.06.2004 14:22:25
53248
Typ
SWCONT
04.04.1995 16:18:01
2048
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Typ
SWOTOBJID
04.05.1995 15:20:52
2048
Typ
SWHACTOR
04.04.1995 16:18:07
2048
Prg
CL_GOS_MANAGER================CP
11.04.2001 13:02:00
17408
Prg
CL_GOS_VIEW_MANAGER===========CP
24.01.2002 20:31:22
22528
Typ
SIBFLPOR
15.11.2000 17:53:54
2048
Typ
SGOS_MVOBJ
24.07.2001 09:18:06
3072
Typ
BORIDENT
28.08.1997 08:38:50
2048
Prg
SAPLSUU1
17.06.2004 15:13:06
165888
Typ
USR02
17.06.2004 15:05:37
7168
Typ
USREFUS
07.01.2003 18:24:17
2048
Typ
SIBFLPORB
15.11.2000 17:53:55
2048
Prg
CL_GOS_TOOLBOX_MODEL==========CP
17.06.2004 15:04:37
38912
Typ
SGOS_MODL
24.07.2001 09:18:05
4096
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSWOR
17.06.2004 15:08:55
270336
Typ
SWOTRI
03.01.1996 15:29:13
2048
Typ
SWOTRETURN
20.08.1998 10:59:29
3072
Prg
SAPLSWOH
14.02.2002 14:22:48
7168
Typ
SWOTENV
11.02.2000 14:20:34
4096
Typ
TOJTD
15.11.1995 03:08:46
2048
Prg
SAPLRHS0
14.02.2002 14:22:47
11264
Prg
SAPLSDIFRUNTIME
17.06.2004 14:20:44
82944
Typ
DFIES
09.11.2000 14:07:05
8192
Typ
X031L
15.11.2000 18:03:28
5120
Prg
SAPLSDNT
17.06.2004 12:06:43
199680
Prg
SAPLSUGS
21.11.2002 10:20:02
29696
Typ
TOJTD
15.11.1995 03:08:46
2048
Typ
TOJTB
14.02.1998 14:02:55
8192
Typ
SWOTLI
04.04.1995 17:30:59
2048
Typ
T100
28.08.1997 09:04:45
2048
Prg
CL_EXITHANDLER================CP
17.06.2004 15:04:37
26624
Prg
CL_ABAP_TYPEDESCR=============CP
17.06.2004 14:19:33
21504
Prg
CL_ABAP_ELEMDESCR=============CP
17.06.2004 14:19:13
18432
Prg
CL_ABAP_DATADESCR=============CP
17.06.2004 14:19:13
14336
Prg
CL_ABAP_REFDESCR==============CP
17.06.2004 14:19:33
16384
Prg
CL_ABAP_STRUCTDESCR===========CP
17.06.2004 14:19:33
19456
Prg
CL_ABAP_COMPLEXDESCR==========CP
17.06.2004 14:19:13
13312
Prg
CL_ABAP_TABLEDESCR============CP
17.06.2004 14:19:33
17408
Prg
CL_ABAP_CLASSDESCR============CP
17.06.2004 14:19:33
23552
Prg
CL_ABAP_OBJECTDESCR===========CP
17.06.2004 14:19:33
25600
Prg
CL_ABAP_INTFDESCR=============CP
17.06.2004 14:19:13
19456
Prg
CL_ABAP_SOFT_REFERENCE========CP
29.03.2001 16:42:12
7168
Prg
CL_ABAP_REFERENCE=============CP
14.02.2002 14:22:46
6144
Prg
IF_EX_GOS_SRV_SELECT==========IP
04.12.2000 16:22:18
4096
Prg
%_CABAP
07.01.2003 18:31:23
23552
Typ
SXS_INTER
30.11.1998 15:55:16
2048
Prg
SAPLSEXV
17.06.2004 15:04:40
106496
Prg
CL_BADI_FLT_DATA_TRANS_AND_DB=CP
17.06.2004 15:04:37
33792
Typ
SXS_ATTR
20.08.2001 12:23:27
4096
Typ
V_EXT_ACT
09.11.2000 14:27:05
2048
Typ
SXC_EXIT
09.11.2000 14:23:43
2048
Prg
CL_EX_GOS_SRV_SELECT==========CP
17.06.2004 15:04:37
13312
Prg
%_CSXRT
17.06.2004 15:04:37
11264
Prg
CL_EXIT_MASTER================CP
17.06.2004 15:04:37
13312
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Typ
V_EXT_IMP
09.11.2000 14:27:05
2048
Prg
SAPLBDLS
17.06.2004 11:45:48
176128
Typ
T000
11.09.1997 10:17:18
4096
Typ
SWOTRTIME
14.02.1998 10:19:46
3072
Prg
%_CSWOB
14.02.2002 14:22:46
13312
Typ
SWOTINVOKE
14.02.1998 10:18:40
6144
Typ
SWOTLV
04.12.2000 14:59:45
10240
Prg
SAPLSWCD
17.06.2004 15:06:55
78848
Prg
RBUS2105
13.11.2006 11:20:02
57344
Prg
CL_GOS_PUBLICATION============CP
13.11.2000 16:31:37
15360
Prg
SAPLSGOSHIST
17.06.2004 14:23:50
46080
Typ
EBKN
16.06.2004 13:09:57
9216
Typ
T161
16.06.2004 13:14:35
5120
Typ
T161T
14.02.1998 10:55:58
2048
Typ
CMMDA
18.09.2001 10:02:31
4096
Prg
SAPLMMDA
04.09.2006 11:00:54
65536
Typ
TWLAD
13.08.1997 14:04:45
2048
Typ
TTXID
27.08.1999 17:40:33
3072
Prg
SAPLSTXD
17.06.2004 15:06:22
347136
Typ
STEXTNAME
18.09.2001 10:03:52
1024
Typ
STXDRID
26.02.1999 14:48:42
2048
Typ
STXDRLANG
26.02.1999 14:48:42
2048
Typ
STXDRNAME
26.02.1999 14:48:42
2048
Typ
STXDROBJ
26.02.1999 14:48:42
2048
Typ
THEAD
09.11.2000 14:15:08
6144
Prg
CL_ABAP_CHAR_UTILITIES========CP
07.01.2003 18:31:23
11264
Typ
STXH
17.06.2004 14:15:46
6144
Typ
TCATALOG
25.05.1998 12:19:20
3072
Typ
T168F
27.05.1992 20:16:27
3072
Typ
T168
27.05.1992 17:53:38
3072
Prg
SAPLMECCP
25.09.2007 16:07:53
39936
Prg
CL_BADI_MM====================CP
08.01.2003 16:43:11
9216
Prg
%_CCXTAB
14.02.2002 14:22:46
6144
Prg
SAPLEINH
25.09.2007 16:07:53
56320
Typ
T001W
16.06.2004 13:14:17
9216
Prg
SAPLVDAT
19.02.2002 12:59:51
25600
Typ
T163Y
28.08.1997 09:05:01
2048
Prg
SAPCNVE
14.02.2002 14:22:47
6144
Prg
SAPLOMCV
17.06.2004 10:54:26
16384
Prg
CL_EX_BADI_MATN1==============CP
17.06.2004 10:27:52
22528
Prg
IF_EX_BADI_MATN1==============IP
17.06.2004 10:53:59
4096
Typ
TMCNV
24.02.1999 03:33:25
3072
Typ
RM06B
17.06.1998 03:23:02
10240
Lista tabelle interne
Il dump non riporta informazioni relative
Indice delle tabelle applicative
Programma
Nome................ Contenuto..1.......2........3........4........5....+....
SAPMM06B
SYST |00000000000x010000000000000000
EBAN |300001100895000010NB B NB 1 Elena Varett20071
*EBAN | 00000 00000
EBKN | 0000000 00000000 000000x0C
AEBAN |3000011008950NB BBEUR |
EBANW |300001100895000010NB B NB 1 Elena Varett20071
RM06B | 00000000000000000010 00
*RM06B | 00000000000000000000 00
RM06E | 000000000000000 00000000 00000
TPRG |300IW2Formato settimana Sett. |
T001W |3006 PIATTAFORMA DI LEINI' 6 CEDI6 0000000
T023 |
T024 |
T160 |300ME52 VB B |
T160V |300C1XX A XX X X |
T161 |300BNB 000100102NBB NB 00000
T161T |300INB BRichiesta d'acquisto|
T168 |300B AB *** 1 106 0x0C0x0C0x0C0x0C|
T168F |300B AB XXX |
T168T |300IB0106002 |
TTXID |EBAN B04 X
T163K | |
T163Y | Standard |
T001L |
T160D | XXXXXXXXXXXXXXXXXXXXXX
T161E | |
SAPFMMEX
TMED |300BB |
SAPLMEXF
T161 |300BNB 000100102NBB NB 00000
T162 |300PT0B ...................................
SAPLSUU1
USR02 |300CONSULENTI ÷x9Fw'x97[æÆ0000000000000000A
USREFUS |300CONSULENTI
SAPLSWOR
TOJTB |BUS2105 XI RBUS2105
SWOTLV |BUS2105 EXISTENCECHECK M
TOJTD | |
SAPLBDLS
T000 |300Mandante produzione Arenzano EUR
SAPMM06B
*RM06E | 000000000000000 00000000 00000
MARA | 00000000 00000000
T006 | 00 00000000000000x0C 0
SAPLVDAT
TPRG |300IW2Formato settimana Sett. |
SAPLOMCV
TMCNV |300MATCONV 0x120000000x12
Directory delle tabelle applicative (inf. di gestione)
Programma
Nome.......................... tempo..........lungh....
SAPLOMCV
SYST 20010612125650 00002404
EBAN 20061113111959 00000892
*EBAN 20061113111959 00000892
EBKN 00000421
AEBAN 20000323224119 00000027
EBANW 00000896
RM06B 20000323224119 00000529
*RM06B 20000323224119 00000529
RM06E 20020124202505 00001154
TPRG 20000323231030 00000032
T001W 20040617141548 00000338
T023 20040616131428 00000102
T024 20040616131429 00000352
T160 00000035
T160V 00000050
T161 20040616131435 00000095
T161T 00000029
T168 00000035
T168F 00000044
T168T 00000013
TTXID 00000058
T163K 20000323230840 00000023
T163Y 00000026
T001L 20000323230832 00000069
T160D 00000069
T161E 20000323230840 00000025
SAPFMMEX
TMED 00000010
SAPLMEXF
T161 00000095
T162 00000234
SAPLSUU1
USR02 00000226
USREFUS 00000067
SAPLSWOR
TOJTB 00000453
SWOTLV 00000701
TOJTD 00000033
SAPLBDLS
T000 00000107
SAPMM06B
*RM06E 20020124202505 00001154
MARA 20071118093457 00001118
T006 20001109142345 00000080
SAPLVDAT
TPRG 00000032
SAPLOMCV
TMCNV 00000062
Blocchi di contr. CONT ABAP
Include Riga Codice sorg.
Ind. Nome FI Co Par01 Par2. Par3. Par4. Tab.
MM06BO0R_RM06B-EEIND 25 EXIT.
2502 BRAX 00
MM06BO0R_RM06B-EEIND 27 ENDSELECT.
2503 BRAX 00
2504 SQLS 08
MM06BO0R_RM06B-EEIND 31 ENDMODULE.
2505 ENDM 00
2506 -
MM06BO0R_RM06B-EPSTP 7 CALL FUNCTION 'ME_ITEM_CATEGOR
2507 FUNC 00
2508 FUNC 00
2509 PAR2 02 0336
2511 FUNC 10
2512 PAR2 01 03B9
2514 PAR2 01 03BA
2516 FUNC FF
MM06BO0R_RM06B-EPSTP 14 ENDMODULE.
>>>>> ENDM 00
2518 -
MM06BO0V_VRTKZ 6 CASE EBAN-VRTKZ.
2519 BREL 04
MM06BO0V_VRTKZ 7 WHEN '1'.
2520 when 00 02 0090
2522 BRAN 02
2523 BRAX 00
MM06BO0V_VRTKZ 8 RM06B-MKNTW = '3 '. "3 Nachkom
2524 MOVL 00 02 0136
MM06BO0V_VRTKZ 9 WHEN '2'.
2526 BRAX 00
Fine dell'analisi err. run-time
Help me.
Thank youHello Maurizio,
Thre screen field EBAN-MENGE is unable to handle a sign along with the value.
Regards,
Ammey Kesarkar -
My basic question is:
If the execution state of vi is "bad" under the development environment, shouldn't it also be "bad" under the run-time environment?
So here is the background:
So I use SVN and I ran into this problem where I would be working on one piece of code without having my top-level vi open and would inadvertantly break the top-level vi. And being in hurry or whatever I would not open the top-level vi to check the run arrow and I would check in my code, which of course breaks the top-level vi for everyone else and causes lots of problems.
So to solve this I wanted to create a Tortoise SVN client side hook to check the check the top-level vi(s) to see if the run arrow was broken before I commit my changes. I'm trying to use the Execution State to check this. I am using an Equals primitive to compare it to a "Bad" constant. (as a side question is checking the execution state the best way to do this? or is this even a valid way to do this? It's the only way I've found so far to check the run arrow.).
So the way I'm going about this is:
1. I create a executable (written in LabVIEW) which is run by TSVN
2. When TSVN calls it (I set it up as a start-commit hook) I pass it a parameter which is text file which lists all the top level vi(s)
I do these first 2 steps in order to make it as generic as possible. I can use it on any project with any number of top-level vis (or dynamically called vis) all I do is point it to a different text file.
3. Inside the executable I just read the list of vis, open a reference to each one and check the execution state. I do this inside a for loop, but keep the references open and close them after the for loop in case they share some subvis or libraries, so they stay in memory (could this be the cause of some of my problems??)
4. Then after the for loop executes and the references are closed I simply fire off a popup if any of them are broken.
5. Then I simply exit LabVIEW to return control to TSVN.
So my problem is this:
In the development environment everything works as expected. But when I try the exact same thing in the executable it tells me the run arrow is broken.
Why the difference? I'm checking the same list of vis and the runs arrows have not changed, they are still all good.
So it appears that checking the execution state to see if it is bad behaves differently in the run-time versus the development environment.
Can anyone confirm or deny that?
It seems to me that it should behave the same.
The help for the Vi.Exec.State property says that it works in the run-time (Read-only), so why am I getting different results?
On a side question if anyone knows of an easier way to accomplish what I want to do, please let me know. I went this route because I had some experience with writing TSVN hooks and I thought it would be pretty simple and it is if I can get this comparison to behave.
edited to fix a typo and to remove the duplicate attachment
Attachments:
Check Run Arrow_BD.png 6 KBI believe that plugins rely on the libraries being located in a specific location. The installer can place these libraries in the specific location or some other installer can do that. You can create code that scans the library directly to "learn" what packages/libraries are available. Then you would build the path to that VI and open the reference to it.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot -
"no data found" run-time error masking SQL/report mismatch
Hi all,
At last, figured out a vexing problem and wondering if anyone else either:
a) has also hit the problem, and hopefully
b) has figured out a clever way around it.
Namely, in our AppEx apps, we rely on SQL query generation from PL/SQL packaged functions. This "best practice" promotes reuse, automated testing, etc. Great idea - works great.
However, we've repeatedly come across a situation where we go to run a page with a report on it only to get a "report error: ORA-01403: no data found" message where the report should be. Not much to go on. After trial and error, it turns out that simply going to the Region Definition page (where the PL/SQL function call is defined) and clicking the "Apply Changes" button cleared the problem up.
Mystifying because the actual SQL query generated by the PL/SQL is valid (we've got a nightly testing job that pulls the PL/SQL function calls out of the AppEx metadata tables, executes them to get back the SQL and then validates the SQL).
Turns out this problem looks to be a result of columns changing in the actual SQL itself, and hence not matching up to the Region Attributes (column names, one assumes) that AppEx knows about. Simply clicking Apply Changes causes AppEx to validate the returned query and then it adjusts the column attributes (one assumes) so that things match up.
So - the $64,000 question(s):
1) Are there any cool AppEx APIs to be able to try and detect this situation? Given an app of middling complexity (50-100 pages, each with various queries/reports), this is not an attractive issue to deal with manually.
2) Any cool AppEx APIs to fix, or auto-sync these situations? (Essentially programmatically calling the "Apply Changes" button if you will).
At a minimum, it would be great if AppEx could be updated to put out some kind of more informative error message when this occurs - maybe something along the lines of "Region Attributes Do Not Match Data Returned from Query", or something like that at least.
Thanks for any input/ideas,
Jim C.Thanks to all for your prompt responses.
Vikas actually did me the favor of pretty much clarifying my info for me (tks Vikas). Yes, to all the above. It's PL/SQL code generating a SQL query, so 1 is (a); we want to use query-specific columns so it is (2a). And yes, the whole problem is that the something does change to cause the SELECT statement column list to change...nature of the beast, so "don't do that" doesn't really help here.
Scott - sorry, should have been more explicit. Basically, we have a PL/SQL function behind a report that returns a SQL statement for the report. If that PL/SQL code changes to add a new column to the report (without going to the corresponding Report Attributes page and clicking the "Apply Changes" button to get AppEx to revalidate the query), then you wind up with this "no data found" error msg, which doesn't exactly point you to the root of the problem.
It seems as though the "parse at compile-time" is really what's going on here. There must be some kind of "run-time" check going on as well, that is resulting in the "no data found" message. Seems as though it ought to be fairly straightforward to add some kind of check at run-time to handle that exception a little cleaner. Is there an official process to register a "Request for Process Enhancement" for AppEx to do this?
In the meantime, thank you Vikas for the pointer to the APEX_APPLICATION_PAGE_RPT_COLS view - that looks like it will do the trick nicely. Given that, we can now add logic to our nightly "app tester" job that can compare what columns AppEx expects to find in a given report (for a given page) with the actual SQL (coming back from the PL/SQL function call) to essentially "validate" the AppEx meta data and at least let us know when these things get out of sync.
BTW - if anyone would be interested in the actual contents of that "app tester" logic, I'd be happy to post it (someplace...here? Studio site?). It's basically just a PL/SQL block of code that currently runs in cron that just validates any SQL embedded in our app. (I suppose it is a little "hard-coded" since it does use our naming conventions for packages/functions to parse the PL/SQL calls from the Meta Data but it might still serve as a usefull starting point...) Since our AppEx app(s) sit on top of a database schema that is in fairly constant flux, we need the ability to know when somebody has changed something in the schema that needs to be accounted for in AppEx. The job primarily just parses the AppEx meta data to find PL/SQL function calls that return SQL, executes that PL/SQL to get the generated SQL, then just validates that SQL and reports back any invalid SQL calls. Perhaps we're in some unusual development environment (15-20 people working on a database schema with 700-800 tables/views) but it seems as though it would be fairly easy, for anybody using PL/SQL to generate SQL (which is a GREAT and powerful thing, by the way - thanks to whoever thought that up in AppEx land) to run into this issue.
Jim C. -
Executable not working - Looking for LabVIEW Run-Time Engine
This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro -
NI LabVIEW Run-Time Engine + TCP/IP
Hello, Anybody knows how to activate TCP/IP service on PC with standard NI LabView Run-Time Engine installed. If I trying communicate with server from my PC (LVRTE) its works correctly. However, when I am trying interchange client and server applications it appears with error 1. Probably I need to add some settings to *.ini files on PC with LVRTE? --- Alex
<Alex> wrote:
Client/Server applications are communicate via standard TCP/IP VIs. I have tried to add 3 line as you wrote to server.ini, but it's didn't help
As I indicated, the lines are only applicable to using the VI Server. You had not indicated whether you were using the VI Server or just the TCP/IP VIs. At this point we need a better explanation of what you're doing. Specifically:
What does this: "If I trying communicate with server from my PC (LVRTE) its works correctly." mean? What is the "server"? What's it running? What do you mean by your "PC (LVRTE)"?
What does this: "However, when I am trying interchange client and server applications it appears with error 1" mean? What is the "interchange client" and the "server applications". Reading this implies you have more than one application running on the "server", whatever that is.
Seeing some code wouldn't hurt either. -
I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
RomanHi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
Right-click "Build Specifications" and choose "New->Application(EXE)".
In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
Save the properties.
Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ -
Error 1334 (in LabVIEW Run-Time Engine 7.1.1 setup) when launching VB6's IDE
What's going on here? I have LabVIEW 7.0 and Visual Basic 6 installed on this Win-XP computer. When I open VB6, I always get what looks like a Windows Installer error:
First, it asked me for the location of "lvruntimeeng.msi", which I located for it. The next progress-window says:
NI LabVIEW Run-Time Engine 7.11
Please wait while Windows configures NI LabVIEW Run-Time Engine 7.11
Finally it fails with this error-message window:
NI LabVIEW Run-Time Engine 7.11
Error 1334. The file 'NIMDFManifestFileId.53736431_DBEC_4582_B072_2F1F0A2C4EA6' cannot be installed because the file cannot be found in cabinet file 'lbruntimeeng_mft'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
[OK]
The two windows repeat twice each time I launch VB6's IDE, and that causes a long delay. What can I do to prevent this error?
Message Edited by citizenDAK on 04-23-2008 01:34 PMYes it occurrs every time I launch VB6.
For a long time now, at least many months. It's not every day that I need to open good old VB6. I was hoping it'd just 'go away' but it hasn't.
I don't know what changes lead up to it. LOTS of things have been updated, security-patched, etc... (It is XP.) I've even un-installed the runtime, then re-installed it when I kept getting the same prompt. Don't have any idea why, I was hoping you could tell me from the specific file named in the error. (Google didn't find it for me, and neither did searching ni.com)
p.s., Sorry I left out a decimal and copy/pasted it several times... should've said "NI LabVIEW Run-Time Engine 7.1.1" -
There are many threads regarding usage of MS office with LV, but I was not able to find the answer to the following question. I hope somebody can help or point me to a useful thread.
I have an excel template file and would like to create new reports each time from it. There are a couple of solutions for this problem which are fine. But, at the end, I am going to build an application and install it on an industrial PC which does not have MS office installed. The question is if the application works on the target machine as well.
I am specifically pointing to the solution in here which uses ActiveX reference to Excel._Application. Any chance that this solution or any similar one works on my target PC?
If you wonder why I want excel reports on a machine that does not have MS Office, I should say that the reports are just stored somewhere on the disk to be transferred later to headquarters let say!
Developing machine: Win7, LV8.6 Pro + Report generation toolkit
Target machine: WinXP SP3, LV run-time engine
Thanks in advance!
Soroush
Solved!
Go to Solution.You need to have Office installed on the computer that is running the LabVIEW application. It is the Office applications that provide ActiveX functionality to the Report Generation Toolkit. Without them, LabVIEW has nothing to interface to.
http://digital.ni.com/public.nsf/allkb/02E339E26484F30186256E920061FBD9
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness -
URGENT: I want to pass a variable to a stored procedure at run time
Post Author: aruplabs
CA Forum: Data Connectivity and SQL
I work for a health care provider and I have reports that pull PHI (Protected Health Information) about patients that needs to be logged according to federal HIPAA regulations. One of the pieces of information that needs to be logged is the username of the person who ran the report. Since these reports will be run from our Crystal Enterprise server I can get this from the CurrentCEUserName variable but I am looking for a way to pass this value to a stored procedure that will not only return the records for the report, but also log the disclosure in our PHI disclosure tracking table. I know you can pass a parameter to a stored procedure but I dont know how, or if it is even possible, to pass a run time variable. This is an urgent problem that I need to find a solution for. Any help would be appreciated.
Thank you.Here it is. Right now, when i press te "Go" it runs for the specific time i've set and when its done the variable "Run" is set true. When i call this VI from another VI it waits for the loop to be finished before it will read the variable.
Regards
Viktor
Attachments:
Untitled 2.vi 26 KB -
Is it possible to modify a view at run time?
Hi,
I am relatively new to using SQL Server, so sorry if this is impossible or very easy and I missed the solution.
I am working on an enterprise SQL Server 2008 R2. Because of the size of the company, we do not want to create new Views as they need to be maintained. With that said, I need to use Views and not tables because of DB traffic issues.
HERE IS MY QUESTION:
Is it possible to Alter a view at run time; in this specific instance I want to change a constraint in the WHERE clause to include one more value in an IN() constraint. Specifically I want the modified SQL to go from WHERE column IN('A', 'B', 'C')
to
WHERE column IN('A', 'B', 'C', 'L'). I do not want to permanently modify the View, I just want the View to change when it is run for this report. I need to do this in order to fix a dynamic report. I am sure that there is another way to
accomplish this; however, a solution of this manner would also have many other uses, so I am curious if this is possible.
Feel free to tell me that it can be done.
Thanks for your ideas!!Right, I understand those fundamentals. We outsource a lot of out view creation and do not have permission to create views for Business reasons; these are beyond my control. However, I can see the source code to many Views. We have also
been told that we should not use tables in our queries. Therefore, I need to use existing Views. Specifically, I would like to add an additional value to an IN() constraint. This would change the constraint as showed below:
IN('A', 'B', 'C') ---> IN('A',
'B', 'C', 'L')
I am wondering if this change can be made when the view runs and only for this one report, with the change being made from the report. This would be very easy if the constraint was removing a value. Obviously I could change the constraint from
IN('A', 'B', 'C') to IN('A','B') very easily with out modifying the View. This would be done by writing a query against the view and in the WHERE clause adding the new IN('A', 'B') statement. However, I want to do the opposite and add a value... -
Add Jcombo in Jtable at run time
hello,
i want to add jcombo box in jtable every cell & i also add column in run time.proble is when i add new column that time last column combo is add but prievious column its remove automatic.
so give me some code & where i can get see good example for add combo in jtable.
thankshi j-rg,
It was really appreaciating to c ur reply, regarding the specific problem.Actually wht i was facing the peoblem, Am adding a colomn in the run time and in that column am adding a combo in each cells of that column.AS i was expecting am able to add a new colum in th erum time with the combo in each cells of that column,now when am adding another column in the run time am getting all the required things,but the problem is " in the previous cloumn am not getting that combo"(only the combo is been added in the last column).
What am expecting is the combo should be there in each cell of the column(all columns)
Am also sending the code wht am using, plz have a look below,
df1.addColumn(result);
TableColumn aa= tb1.getColumnModel().getColumn(tb1.getColumnCount()-1);
aa.setCellEditor(new DefaultCellEditor(comboBox));
wating for ur reply
thanks and regards
sandeep -
How do you set the size / bounds of a waveform chart at run time?
I have a plot area that I would like to fill with as many waveform charts as the user specifies (at run time). The "bounds" property is read only and I haven't noticed an additional "size" property for a waveform chart as there is for a button. Is there a way to set the size of a waveform chart at run time, and if not, why not? (Labview 6.1)
Look at it a little more carefully, I suspect that your assumption is only half wrong. The property does only resize the plot area--LV resizes the frame to fit the resized plot on it's own.
You'll need to bear this in mind when you're figuring-out what size to set the property to.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps -
Run time error while saving sales order
Hi all,
i am working on IDES ECC 6.0, when i am saving an sales order(OR) i am getting run time error in the table CRMPAROLTP, program SAPMV45A.
i am using 4 GB RAM, still having a space of 30 GB for only IDES to save the data.
so, how to solve it.Hello,
I doubt the runtime error (I am assuming you mean that you got a short dump) you mentioned in your original post has anything to do with the warning messages you see when doing a check (Ctrl+F2) on table CRMPAROLTP and program SAPMV45A. These warnings should not cause a short dump or runtime error.
The warning message for the table has the following long text:
Table CRMPAROLTP: Key length > 120 (Restricted functionality)
Message no. DT214
Diagnosis
The key length, i.e. the sum of the field lengths of all the key fields of the table, is more than 120 bytes.
System response
This is a warning.
Procedure
Note the following restricted fuctionality for this table:
- Table contents cannot be transported by specifying key values, at
best by specifying generic key values with a maximum length of 120
bytes.
- The table may not be used as the base table of a lock object.
The warnings in SE38 for program SAPMV45A are mostly related to Unicode and have no reference to the table CRMPAROLTP.
If you haven't already done so, please check the SAP Note referenced in my first reply since this does provide a solution for short dumps related to table CRMPAROLTP.
Of course, since I don't know specifically what the short dump message is that you received, I could be basing my assessment on false assumptions. If you have those details it is better for the SDN community as a whole if you include the information in this thread instead of sending it to me offline.
Best Regards,
Jamie -
Building an Application in Windows to be used in Linux (with the Run-Time Engine)
Hi All,
I have an LabVIEW project I have developed in a Windows environment. I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment. The OS is openSUSE v10.3 (with GNOME). I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box? According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for LinuxThe cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant
Maybe you are looking for
-
I have the 64bit version of itunes on windows 7. When I connect my iphone5 it says that I don't have the correct software and that I need to install itunes 64bit! And I can go no further! I've uninstalled and reinstalled but it makes no difference. I
-
I like to keep my iPhone's language and regional settings in Japanese. This in turn redirects all Google related activity to google.co.jp (and Wikipedia also goes to .co,jp), but I want to keep it to google.com so that my search results are in Englis
-
Webi export to excel having issues.
Hi, I have a webi report which generates 62 mb excel file when exported to excel. It can be saved to excel without any error but when we open the excel report it shows the error that there are some damage done to report and excel is trying to recover
-
Record in Bex shows variations in decimals
Hi All, I am facing a problem in the decimal places which impacts huge difference in the report. Actually i had wirtten the currency conversion coding in the update rules of the cube.The data is converted and gives exact value with respect to decimal
-
Image OK in RGB -- Missing in CMYK
I have a PDF file that when I open in Photoshop in RGB the image appears correctly. When I open it as a CMYK part of a logo is missing. Any explanation?