Detecting MDB destination problems

I am pondering J2EE-compliant ways to detect problems with the destination to which an MDB is attached. I would like to be able to raise an alert if there's a network failure, for example.
The JBoss folks pointed me to a specific solution for their app server, but it would be useful to have a more general approach.
I thought of using a stateless session EJB to poll through the TimerService, but I'd certainly appreciate any other suggestions.
Thanks,
Keith

Scott, thanks for the reply.
That was my first thought. Unfortunately, there are a couple of problems with it. Firstly, it's explicitly forbidden by the J2EE spec, so that's a hinderance -- many app servers barf if you try to invoke setExceptionListener or other forbidden methods. Secondly, I don't think that the actual Connection is available in an MDB, which makes sense since both can be drawn from pools.

Similar Messages

Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must

Hi,
I am getting the below error whenever I try to run the extend script. Please let me know how to solve the issue.
"Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must quit.
A file named "C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt" has been generated which contains information that may help Frame development improve the product for future releases."
Review the file content here:
=== Header Begin ===
Internal Error: 10014, 7686536, 7686826, 10069773
FrameMaker 10.0.1 for Intel
Build: 10.0.1.402
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
Generated on: Thursday, July 28, 2011 3:41:01 PM
To file: C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt
=== Header End ===
=== Stack Trace Begin ===
$754988
$754aaa
$99a70d
=== Stack Trace End ===
=== Open Window List Begin ===
# not implemented
=== Open Window List End ===
=== Recent Commands Begin ===
=== Recent Commands End ===
=== Recent API Calls Begin ===
# not implemented
=== Recent API Calls End ===
=== Windows Relocation Information Begin ===
Application: 00400000
FrameMaker.exe: 00400000 0092f000
ntdll.dll: 7c900000 000b2000
kernel32.dll: 7c800000 000f6000
FMRuntime.dll: 10000000 00042000
USER32.dll: 7e410000 00091000
GDI32.dll: 77f10000 00049000
tbb.dll: 00350000 00020000
MSVCP90.dll: 78480000 0008e000
MSVCR90.dll: 78520000 000a3000
FMGridCtrl.dll: 00370000 0002c000
mfc90u.dll: 789e0000 003a1000
SHLWAPI.dll: 77f60000 00076000
ADVAPI32.dll: 77dd0000 0009b000
RPCRT4.dll: 77e70000 00093000
Secur32.dll: 77fe0000 00011000
msvcrt.dll: 77c10000 00058000
COMCTL32.dll: 773d0000 00103000
MSIMG32.dll: 76380000 00005000
OLEAUT32.dll: 77120000 0008b000
ole32.dll: 774e0000 0013e000
Asn.er.dll: 003b0000 0003c000
OLECLI32.dll: 71e10000 00015000
MPR.dll: 71b20000 00012000
AdobePSL.dll: 00d30000 00d0d000
FMBMP2Tiff.dll: 01a40000 00006000
libtiff.dll: 01a50000 00085000
zlib1.dll: 01ae0000 00013000
MSVCP60.dll: 76080000 00065000
FMTiff2PS.dll: 01b00000 0000b000
COMDLG32.dll: 763b0000 00049000
SHELL32.dll: 7c9c0000 00817000
gdiplus.dll: 4ec50000 001ab000
USP10.dll: 74d90000 0006b000
FMDBMS32.dll: 01b10000 0000e000
oledlg.dll: 7df70000 00022000
VERSION.dll: 77c00000 00008000
WININET.dll: 3d930000 000d1000
Normaliz.dll: 01b20000 00009000
iertutil.dll: 3dfd0000 00045000
WINSPOOL.DRV: 73000000 00026000
amtlib.dll: 01b30000 000ee000
AIDE.dll: 01c30000 00064000
MSVCR80.dll: 78130000 0009b000
MSVCP80.dll: 7c420000 00087000
BIB.dll: 01cb0000 00049000
CoolType.dll: 01d10000 002fb000
SVGRE.dll: 6f130000 00332000
icuuc32.dll: 4a800000 00095000
icudt32.dll: 4ad00000 0095a000
MSVCR71.dll: 7c340000 00056000
icuin32.dll: 4a900000 000aa000
NetLib.dll: 02030000 0001e000
CoreTypes.dll: 30100000 00026000
NetIO.dll: 30900000 00018000
LIBCURL.dll: 30000000 00023000
WS2_32.dll: 71ab0000 00017000
WS2HELP.dll: 71aa0000 00008000
WINMM.dll: 76b40000 0002d000
SSLEAY32.dll: 02090000 00027000
LIBEAY32.dll: 020c0000 000d1000
WSOCK32.dll: 71ad0000 00009000
icuio32.dll: 4ab00000 0000b000
MSVCP71.dll: 7c3a0000 0007b000
AdobePDFL.dll: 021a0000 0067b000
AdobeXMP.dll: 02830000 0004c000
JP2KLib.dll: 02890000 000aa000
BIBUtils.dll: 02950000 00040000
AGM.dll: 029a0000 0059d000
AXE8SharedExpat.dll: 02f50000 0002e000
XAPToolkitRelease.dll: 02f90000 0008b000
AdobeXMPFiles.dll: 03030000 0006c000
AdobeLinguistic.dll: 030b0000 001af000
PSAPI.DLL: 76bf0000 0000b000
AdobeOwl.dll: 03270000 00156000
AdobeOwlCanvas.dll: 033e0000 00048000
LogSession.dll: 03440000 00056000
SETUPAPI.dll: 77920000 000f3000
adbeape.dll: 034b0000 00009000
ahclient.dll: 034d0000 00021000
IMM32.DLL: 76390000 0001d000
LPK.DLL: 629c0000 00009000
tbbmalloc.dll: 03a30000 0000a000
UxTheme.dll: 5ad70000 00038000
MFC90ENU.DLL: 5d360000 0000d000
rdpsnd.dll: 5dac0000 00008000
WINSTA.dll: 76360000 00010000
NETAPI32.dll: 5b860000 00055000
MSCTF.dll: 74720000 0004c000
fmres.dll: 0ad90000 0025e000
fmdlg.dll: 04c40000 00064000
fmcustom.dll: 04cb0000 0005d000
msctfime.ime: 755c0000 0002e000
amtservices.dll: 0b0f0000 00112000
IPHLPAPI.DLL: 76d60000 00019000
WINHTTP.dll: 4d4f0000 00059000
adobe_caps.dll: 0b460000 0006a000
NTMARTA.DLL: 77690000 00021000
SAMLIB.dll: 71bf0000 00013000
WLDAP32.dll: 76f60000 0002c000
asneu.dll: 0b5f0000 00028000
xpsp2res.dll: 0b840000 002c5000
CLBCATQ.DLL: 76fd0000 0007f000
COMRes.dll: 77050000 000c5000
wbemprox.dll: 74ef0000 00008000
wbemcomn.dll: 75290000 00037000
wbemsvc.dll: 74ed0000 0000e000
fastprox.dll: 75690000 00076000
NTDSAPI.dll: 767a0000 00013000
DNSAPI.dll: 76f20000 00027000
updaternotifications.dll: 0be20000 00092000
mstask.dll: 75830000 00045000
USERENV.dll: 769c0000 000b4000
owlres.dll: 0b640000 000ae000
NetIODav.dll: 30a00000 0002c000
xerces-c_2_7.dll: 12000000 0019e000
rsaenh.dll: 68000000 00036000
unidrvui.dll: 7e5a0000 000ba000
mxdwdrv.dll: 3f500000 000c0000
FontSub.dll: 69310000 00017000
ATMLIB.dll: 73c20000 0000b000
adbeapecore.dll: 0c810000 0001b000
ACE.dll: 0c940000 000fe000
dvaadameve.dll: 0d580000 00354000
boost_threads.dll: 0d8f0000 0000e000
dvacore.dll: 0d910000 0018c000
dvaui.dll: 0dab0000 00381000
OPENGL32.dll: 5ed00000 000cc000
GLU32.dll: 68b20000 00020000
DDRAW.dll: 73760000 0004b000
DCIMAN32.dll: 73bc0000 00006000
WTSAPI32.dll: 76f50000 00008000
clickprt.dll: 0bff0000 0002f000
fmmediaannot.dll: 0c020000 0004a000
frame2pdf.dll: 0e470000 00044000
mailer.dll: 0c070000 00039000
MAPI32.DLL: 61e00000 0001f000
bookerrlog.dll: 0e4c0000 0003a000
ditamaperrlog.dll: 0e500000 0003a000
pdfsize.dll: 0e540000 0003d000
fmpdfreflow.dll: 0e580000 00041000
ecm.dll: 0e5d0000 000c3000
sgen.dll: 0e6a0000 000a8000
dispatch.dll: 0e760000 000cf000
trnslate.dll: 0e850000 0022b000
Xalan-C_1_10.dll: 0eb10000 001f8000
XalanMessages_1_10.DLL: 0ea90000 00007000
GoMarkup.dll: 0ed10000 0013b000
GoCore.dll: 0ee50000 00081000
SCL.dll: 0eaa0000 00044000
xmlcss.dll: 0f040000 001f8000
docbook.dll: 0f250000 001f3000
xhtml.dll: 0f460000 001f2000
qstart.dll: 0f670000 0002f000
cnvschma.dll: 0f6a0000 00093000
u3dfilter.dll: 0f750000 00038000
rt3d.dll: 0f790000 00327000
ditafm.dll: 0fad0000 00281000
ditafm_app.dll: 0fd70000 00210000
find_references.dll: 10050000 000a2000
PDFCommentsImport.dll: 10100000 00078000
InitCharMap.dll: 0ffa0000 00031000
PreserveEntity.dll: 10180000 001ed000
FrameMakerScriptingSupport.dll: 10370000 0025b000
ExtendScript.dll: 105d0000 000a6000
ScCore.dll: 10690000 00091000
RoboHelpPublish.dll: 10840000 00042000
AdobeCaptivatePlugin.dll: 10890000 0004a000
AdobeIllustratorPlugin.dll: 108e0000 00030000
mapper.dll: 10910000 00057000
masterpages.dll: 10970000 00036000
PhotoshopPlugin.dll: 109b0000 00031000
RHFrameMakerServer10.dll: 109f0000 00032000
RoboScreenCapturePlugin.dll: 10a50000 00031000
tablesort.dll: 10a90000 00037000
TextEditorPlugin.dll: 10ad0000 00031000
WebWorks.FrameMaker9.Client.dll: 10b10000 0003b000
AdobeSWFL.dll: 10b60000 00843000
OLEACC.dll: 74c80000 0002c000
CRYPT32.dll: 77a80000 00095000
MSASN1.dll: 77b20000 00012000
urlmon.dll: 113c0000 00128000
mscms.dll: 73b30000 00015000
DSOUND.dll: 73f10000 0005c000
dbghelp.dll: 59a60000 000a1000
mlang.dll: 75cf0000 00091000
icm32.dll: 66e90000 00041000
WINTRUST.dll: 76c30000 0002e000
IMAGEHLP.dll: 76c90000 00028000
wdmaud.drv: 72d20000 00009000
msacm32.drv: 72d10000 00008000
MSACM32.dll: 77be0000 00015000
midimap.dll: 77bd0000 00007000
schannel.dll: 767f0000 00028000
RASAPI32.dll: 76ee0000 0003c000
rasman.dll: 76e90000 00012000
TAPI32.dll: 76eb0000 0002f000
rtutils.dll: 76e80000 0000e000
msv1_0.dll: 77c70000 00025000
cryptdll.dll: 76790000 0000c000
sensapi.dll: 722b0000 00005000
mswsock.dll: 71a50000 0003f000
rasadhlp.dll: 76fc0000 00006000
hnetcfg.dll: 662b0000 00058000
wshtcpip.dll: 71a90000 00008000
appHelp.dll: 77b40000 00022000
cscui.dll: 77a20000 00054000
CSCDLL.dll: 76600000 0001d000
browseui.dll: 75f80000 000fd000
ntshrui.dll: 76990000 00025000
ATL.DLL: 76b20000 00011000
shdocvw.dll: 7e290000 00173000
CRYPTUI.dll: 754d0000 00080000
=== Windows Relocation Information End ===
=== Windows Exception Information Begin ===
[Exception Record]
0012be90: c0000005 00000000 00000000 103c150c
0012bea0: 00000002 00000000 00000000 0001003f
0012beb0: 00000000 00000000 00000000 00000000
0012bec0: 00000000 00000000 ffff027f ffff0100
0012bed0: ffffffff 106c2676 05d8001b 00000000
[Exception Context]
0012beac: 0001003f 00000000 00000000 00000000
0012bebc: 00000000 00000000 00000000 ffff027f
0012becc: ffff0100 ffffffff 106c2676 05d8001b
0012bedc: 00000000 ffff0023 00000000 00000000
0012beec: 00800000 00800080 ffff0080 00000000
0012befc: 80000000 0000c003 00000000 4004e000
0012bf0c: 00000000 e8000000 00004004 00000000
0012bf1c: 4004c000 00000000 e8000000 00004004
0012bf2c: 00000000 7fffc000 00000000 00000000
0012bf3c: 0000003b 00000023 00000023 00000000
0012bf4c: 1ff10000 00000000 1ff10000 0012c264
0012bf5c: 00000000 0d433820 103c150c 0000001b
0012bf6c: 00250212 0012c178 00000023 0100027f
0012bf7c: 05d80000 106c2676 0000001b 00000000
0012bf8c: 00000023 00001fa1 0000ffff 00000000
0012bf9c: 00000000 00000000 00000000 00800080
0012bfac: 00800080 0000ffff 00000000 00000000
0012bfbc: 80000000 0000c003 00000000 00000000
0012bfcc: e0000000 00004004 00000000 00000000
0012bfdc: e8000000 00004004 00000000 00000000
0012bfec: c0000000 00004004 00000000 00000000
0012bffc: e8000000 00004004 00000000 00000000
0012c00c: c0000000 00007fff 00000000 0000002b
0012c01c: 00000000 00000433 00000000 00000000
0012c02c: 40240000 00000000 00000000 00000000
0012c03c: 8a45f1c8 00000001 00000001 00000000
0012c04c: 8054c127 00000000 34306847 00000000
0012c05c: a201c954 bf802b2f 00000000 00000000
0012c06c: 408fe000 00000000 00000000 ba338540
0012c07c: 00000000 806e7410 8968bb20 a201ca74
0012c08c: 00000000 806e7427 00000008 0377de70
0012c09c: 0377df0a 0377de70 77f6797d 0377e0c4
0012c0ac: 00000000 7c9c6ec8 0377e0c4 77f64de0
0012c0bc: 00000000 0377e0a0 77f67abb 0377e0c4
0012c0cc: 0377de94 7c9c63f0 7cbcfef4 77f67ad4
0012c0dc: 77f64de0 0377e0c4 006f0053 00740066
0012c0ec: 00610077 00650072 004d005c 00630069
0012c0fc: 006f0072 006f0073 00740066 0057005c
0012c10c: 006e0069 006f0064 00730077 0043005c
0012c11c: 00720075 00650072 0074006e 00650056
0012c12c: 00730072 7c90cffa 77dd6c03 00000b2c
0012c13c: 00000002 0377e030 77f643e0 0000ffff
0012c14c: 0377e07c 00000004 00000002 0377eb70
0012c15c: 7c9c94f8 77f643ed 7c9c94f8 00000004
0012c16c: 00000000 0377e07c 00000b2c
=== Windows Exception Information End ===
=== Windows Stack Traceback Begin ===
=== Windows Stack Traceback End ===
Regards,
Valee

Thanks for your swift response. Here is my small script.
var doc = app.ActiveDoc();
var tbl = doc.FirstTblInDoc;
while (tbl.ObjectValid()){
$.writeln ("Loop through doc tables: " + tbl.ObjectValid());
tbl.NextTblInDoc
My another small script is:
alert("Hi Valee");
I am trying to run it from my FrameMaker 10 (Version: 10.0.1.402). Also I have updated the latest patch versions.
Regards,
Valee

FDK and FM 8: Internal Error: 8004, 6343724, 8484240, 0. FrameMaker has detected a serious problem a

I use FDK9 and FrameMaker 8. I used Visual C++ 2008 Express Edition and Microsoft SDKs to compiled sample FDK hello.c program, C:\Program Files\Adobe\FDK9\samples\hello. It compliled just fine without error or warning message. I registered the hello.dll to fminit directory and added the line: "hello=Standard, Greets user at startup,fminit\hello.dll, all" to maker.ini. When I brought up FrameMaker I got error message:
Internal Error: 8004, 6343724, 8484240, 0. FrameMaker has detected a serious problem and must quit.
A file named fminit\hello.dll has been generated which contains
information that may help Frame development improve the product for future releases.
Please describe your recent actions and send this, along with the generated file,
to [email protected] Due to the volume of feedback, we are unable to respond to technical questions.
For support, please refer to http://www.adobe.com/support.
Please help.
Thank you,
Thai Nguyen

Thai,
Here is what Wikipedia says:
"In April 2003, Microsoft introduced a minor upgrade to Visual Studio .NET called Visual Studio .NET 2003, codenamed Everett (for the city of the same name). It includes an upgrade to the .NET Framework, version 1.1, and is the first release to support for developing programs for mobile devices, using either ASP.NET or the .NET Compact Framework. The Visual C++ compiler's standards-compliance was improved, especially in the area of partial template specialization. Visual C++ Toolkit 2003 is a free version of the same C++ compiler shipped with Visual Studio .NET 2003 without the IDE, though it is no longer available and now superseded by the Express Editions. The internal version number of Visual Studio .NET 2003 is version 7.1 while the file format version is 8.0."
I think you should be OK with the later compiler. I don't know what is causing the crash, though. Perhaps you might consider setting up a new workspace according to the instructions in the Windows guide, then add hello.c to it, and see what happens. That would at least let you know if there is a compatibility problem with the sample, or if your current setup will simply not allow FDK9 development for FM8.
By the way, there is a Yahoo group dedicated to FDK development. If you don't get an answer here, consider posting there. Some of the users on that list are considerably smarter than me about these types of issues.
http://groups.yahoo.com/group/Frame_dev/
Russ

Problem Changing MDB Destination.

Greetings. I am gettign some rather odd errors in my deployment. It is
almost as if the destination topics for my MDBs are being coded into the
generated container files.
Snippet of my weblogic deployment descriptor.
<weblogic-enterprise-bean>
<ejb-name>beanDataImportDispatch</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>5</max-beans-in-free-pool>
</pool>
<destination-jndi-name>serial://jms/gcy/broadcast</destination-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/gcyRWDS</res-ref-name>
<jndi-name>jdbc/gcyRWDS</jndi-name>
</resource-description>
<ejb-reference-description>
<ejb-ref-name>ejb/beanMultiRowImporter</ejb-ref-name>
<jndi-name>gcy/MultiRowImporter</jndi-name>
</ejb-reference-description>
<ejb-reference-description>
<ejb-ref-name>ejb/beanMultiColImporter</ejb-ref-name>
<jndi-name>gcy/MultiColImporter</jndi-name>
</ejb-reference-description>
<ejb-reference-description>
<ejb-ref-name>ejb/beanPpiImporter</ejb-ref-name>
<jndi-name>gcy/PpiImporter</jndi-name>
</ejb-reference-description>
<ejb-reference-description>
<ejb-ref-name>ejb/beanVideoImporter</ejb-ref-name>
<jndi-name>gcy/VideoImporter</jndi-name>
</ejb-reference-description>
<ejb-reference-description>
<ejb-ref-name>ejb/beanHotplateImporter</ejb-ref-name>
<jndi-name>gcy/HotplateImporter</jndi-name>
</ejb-reference-description>
</reference-descriptor>
Error message on deployment
javax.management.MalformedObjectNameException: ObjectName: Invalid value ->
hq_Gencyclopedia-Server_GcyBeans.jar_beanDataImportDispatch_serial://jms/gcy
/broadcast@JMS HQ Main
at javax.management.ObjectName.validateAndAdd(ObjectName.java:444)
at javax.management.ObjectName.initObjectName(ObjectName.java:411)
at javax.management.ObjectName.<init>(ObjectName.java:254)
at
weblogic.management.WebLogicObjectName.<init>(WebLogicObjectName.java:197)
at
weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelega
te.java:90)
at
weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate
.java:83)
at
weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.jav
a:27)
at
weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDri
venEJBRuntimeMBeanImpl.java:27)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDriven
BeanPoolInfoImpl.java:173)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBea
nPoolInfoImpl.java:211)
at
weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.jav
a:1502)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1387)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:397)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:9
24)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
a:910)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllAppli
cations(SlaveDeployer.java:587)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:367
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Deplo
ymentManagerServerLifeCycleImpl.java:235)
at
weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:812)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:294)
at weblogic.Server.main(Server.java:31)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested
exception:
[javax.management.MalformedObjectNameException: ObjectName: Invalid value ->
hq_Gencyclopedia-Server_GcyBeans.jar_beanDataImportDispatch_serial://jms/gcy
/broadcast@JMS HQ Main]
at
weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelega
te.java:102)
at
weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate
.java:83)
at
weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.jav
a:27)
at
weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDri
venEJBRuntimeMBeanImpl.java:27)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDriven
BeanPoolInfoImpl.java:173)
at
weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(MessageDrivenBea
nPoolInfoImpl.java:211)
at
weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.jav
a:1502)
at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:1387)
at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:397)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:9
24)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.jav
a:910)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllAppli
cations(SlaveDeployer.java:587)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:367
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(Deplo
ymentManagerServerLifeCycleImpl.java:235)
at
weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:812)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:294)
at weblogic.Server.main(Server.java:31)
<24.05.2002 21:14:08 CEST> <Error> <EJB> <010072> <Error starting EJB Module
: GcyBeans.jar
Note that I USED to have serial://jms/gcy/broadcast@JMS HQ Main as my
destination but I edited it. What is up here ? TIA.
Robert Simmons Jr.
Senior Software Engineer
Ingenium Pharmaceuticals, Munich Germany.

If you create a Table of Contents through the TOC function, this automatically creates a hyperlink, and the destination is defined at the time of TOC generation. These hyperlinks do not show in the Hyperlinks panel, like manually created links. You will not be able to redirect the destination in Indesign. The TOC links are visible in Acrobat by selecting the Link tool and editing the destination there, but not recommended for many destination changes. In the event that content was moved to different pages in ID, and manual edits made to the TOC, the destinations of these hyperlinks are probaly not correct. You could remove all extraneous hyperlinks and regenerate a TOC with new link and destinations created, and see if this corrects issue.

MDB Deployment Problem in JBoss 4.0.3SP1

Hi All,
I am upgrading my App Server from JBoss 323 to JBoss 403.
I had some MDBs, that are running successfully in JBoss 323.
But when I tried to redeploy them(after recompiling with jdk1.5), I am facing few issues with them.
First of all, I have a MDB whose destination was in some other Jboss server instance. That means I am trying to connect my destination "Queue" as remotely. At that time it is thorowing exception like as follows at my server startup time.......
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter:                     java:/Server1JMSProvider
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter:                     org.jboss.jms.jndi.JNDIProviderAdapter@20dcb7
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory:                     org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection:                     Connection@10751758[token=ConnectionToken:null/b3e21fe26fd3b44f4a0c5bb69995e669                     rcvstate=STOPPED]
2006-04-17 07:17:15,472 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory]                     SpyDestinationObjectFactory->getObjectInstance()
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: QUEUE.DLQ
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@106989e
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: [u]xxxQueue[/u]
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for LifecycleMDB
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory:                                         org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/null
2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created XAQueueConnection:                                         Connection@13605872[token=ConnectionToken:null/ea8d256e12a297e358803b37d7bfee4d                               rcvstate=STOPPED]
2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not find the queue                                         destination-jndi-name=queue/[u]xxxQueue[/u]
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destination not found: queue/[u]xxxQueue[/u]                               reason: javax.naming.NameNotFoundException: [u]xxxQueue[/u] not bound
2006-04-17 07:17:15,488 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] creating a new temporary destination:                               queue/[u]xxxQueue[/u]
2006-04-17 07:17:15,488 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Attempting to create destination:                                    jboss.mq.destination:service=Queue,name=xxxQueue; type=org.jboss.mq.server.jmx.Queue
2006-04-17 07:17:15,488 INFO [org.jboss.mq.server.jmx.Queue.xxxQueue] Registration is not done -> stop
2006-04-17 07:17:15,488 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected:
org.jboss.deployment.DeploymentException: Error during queue setup; - nested throwable: (javax.management.MBeanException)
     at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)My jboss.xml was
<jboss>
   <enterprise-beans>
      <message-driven>
         <ejb-name>LifecycleMDB</ejb-name>
         <destination-jndi-name>queue/xxxQueue</destination-jndi-name>
         <invoker-bindings>
           <invoker>
             <invoker-proxy-binding-name>server1-message-driven-bean</invoker-proxy-binding-name>
           </invoker>
         </invoker-bindings>
         <resource-ref>
            <res-ref-name>jms/QueueFactory</res-ref-name>
            <jndi-name>UIL2XAConnectionFactory</jndi-name>
         </resource-ref>
      </message-driven>
   </enterprise-beans>
   <invoker-proxy-bindings>
       <invoker-proxy-binding>
         <name>server1-message-driven-bean</name>
         <invoker-mbean>default</invoker-mbean>
         <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
         <proxy-factory-config>
         <JMSProviderAdapterJNDI>Server1JMSProvider</JMSProviderAdapterJNDI>
         <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
         <CreateJBossMQDestination>true</CreateJBossMQDestination>
            <MaximumSize>15</MaximumSize>
            <MaxMessages>1</MaxMessages>
            <MDBConfig>
               <ReconnectIntervalSec>10</ReconnectIntervalSec>
               <DLQConfig>
                  <DestinationQueue>queue/DLQ</DestinationQueue>
                  <MaxTimesRedelivered>10</MaxTimesRedelivered>
                  <TimeToLive>0</TimeToLive>
               </DLQConfig>
            </MDBConfig>
         </proxy-factory-config>
      </invoker-proxy-binding>
</invoker-proxy-bindings>
</jboss>and my deployment file consist of the following code
<server>

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
      name="jboss.mq:service=JMSProviderLoader,name=Server1MQProvider">
    <attribute name="ProviderName">Server1JMSProvider</attribute>
    <attribute name="ProviderAdapterClass">
      org.jboss.jms.jndi.JNDIProviderAdapter
    </attribute>
    
    <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
    
    <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
    
    <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
    
    <attribute name="Properties">
       java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
       java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
       java.naming.provider.url=jnp://SERVER:1499
    </attribute>
</mbean>
</server>

Did you find a solution to this problem?

JRE Detection using javascript problem

I am using following code to detect the JRE is installed on machine or not.
it is working fine if the JRE is not installed.
But if it is installed , it gives the debugger error in internet explorer.
Here _ie == true means Internet Explorer condition.
if (_ie == true){ document.write('<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93"
codebase="http://java.sun.com/update/1.4.2/jinstall-1_4-windows-i586.cab#Version=1,4,0,0" height=0 width=0');
document.write("<PARAM NAME=back VALUE=false>");
document.write("</OBJECT>");
I think it is trying to start webstart but resulting in error in Internet Explorer exe.
Please help it out.

Thanks Andrew, but my problem not solved yet.
I copied the deployJava.js in the destination folder where i have my html file.
but I am not able to call the methods in the deployJava.js .
Not able to see any affects while using those methods as below.
<script type="text/javascript" src="deployJava.js"></script>
<script type="text/javascript" >
//alert(deployJava.getJREs(););
document.write("Test");
deployJava.installLatestJRE();
</script>

OC4J & MDB Deployment Problems

I really am at a loss here. This is the error I get when I try to deploy a MDB to OC4J.
[May 23, 2007 7:59:43 PM] Application Deployer for eaDUR STARTS.
[May 23, 2007 7:59:43 PM] Copy the archive to D:\product\10.1.3\OracleAS\j2ee\InternalApps\applications\eaDUR.ear
[May 23, 2007 7:59:43 PM] Initialize D:\product\10.1.3\OracleAS\j2ee\InternalApps\applications\eaDUR.ear begins...
[May 23, 2007 7:59:43 PM] Removing everything under: D:\product\10.1.3\OracleAS\j2ee\InternalApps\applications\eaDUR
[May 23, 2007 7:59:43 PM] Unpacking eaDUR.ear
[May 23, 2007 7:59:44 PM] Done unpacking eaDUR.ear
[May 23, 2007 7:59:44 PM] Initialize D:\product\10.1.3\OracleAS\j2ee\InternalApps\applications\eaDUR.ear ends...
[May 23, 2007 7:59:44 PM] Starting application : eaDUR
[May 23, 2007 7:59:44 PM] Initializing ClassLoader(s)
[May 23, 2007 7:59:44 PM] Initializing EJB container
[May 23, 2007 7:59:44 PM] Loading connector(s)
[May 23, 2007 7:59:44 PM] Starting up resource adapters
[May 23, 2007 7:59:44 PM] Processing EJB module: DURAppEJB.jar
[May 23, 2007 7:59:44 PM] Compiling EJB generated code
[May 23, 2007 7:59:44 PM] application : eaDUR is in failed state
[May 23, 2007 7:59:44 PM] Operation failed with error: No javax.jms.Destination found at the specified destination-location (java:comp/resource/JMSUSERRP/Queues/DUR_QUEUE) for MessageDrivenBean RequestProcessorMDB
My deployment descriptors are as follows.
Here is my application.xml
<application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd" version="1.4" xmlns="http://java.sun.com/xml/ns/j2ee">
<display-name>DURApp</display-name>
<module>
<ejb>DURAppEJB.jar</ejb>
</module>
</application>
Here is my orion-application.xml:
<orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd">
<resource-provider class="oracle.jms.OjmsContext" name="JMSUSERRP">
<description>OJMS Context Using a datasource</description>
<property name="datasource" value="jdbc/durDS"></property>
</resource-provider>
</orion-application>
Here is my ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee">
<enterprise-beans>
<message-driven>
<description>Message Driven Bean</description>
<display-name>RequestProcessorMDB</display-name>
<ejb-name>RequestProcessorMDB</ejb-name>
<ejb-class>com.accredohealth.dur.mdb.RequestProcessorMDBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-destination-type>javax.jms.Queue</message-destination-type>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>RequestProcessorBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Here is my orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'windows-1252'?>
<orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-ejb-jar-10_0.xsd" schema-major-version="10" schema-minor-version="0">
<enterprise-beans>
<session-deployment name="RequestProcessorBean"/>
<message-driven-deployment name="RequestProcessorMDB"
connection-factory-location="java:comp/resource/JMSUSERRP/QueueConnectionFactories/DUR_REQUEST_QT"
max-instances="5"
min-instances="5"
listener-threads="5"
destination-location="java:comp/resource/JMSUSERRP/Queues/DUR_QUEUE"
dequeue-retry-count="3"
transaction-timeout="20"/>
</enterprise-beans>
<assembly-descriptor/>
</orion-ejb-jar>

Ok, I was looking in the actual log file for the message when they were actually come out onto the console that starts up whne you start the server... problem solved.

Creation of RFC Destination problem

Hi Experts,
I need to establish an RFC communication between TREX7.0 server running on windows 2003 server and the SAPR/3 4.7 EE server running on windows2000.
server. Initially i used TREXAdminTool to create RFC Destination, i was unable to create successfully
Then i used SAPR/3 server from TCODE: SM59, here also am facing the same problem, what are the values i have to give for
1. RFC Destination, 2. Program id 3. Gateway Host and Gateway Service.
PLZ guide me step by step procedure with some example values to create RFC Destination to TREX Server successfully using TREXAdminTool or from SAPR/3 server---SM59
ADV Thanks
Regds
phanikumar

Hi,
Till now i didn't install explicitly any SAP Gateway on TREX server.
I installed TREX server along with SAP Netweaver WEB AS java.
Shall i need to install any SAP Gateway to configure RFC Destination?
If so can you give me the procedure how to install explicitly SAP gateway?
Regds
Phanikumar

ITunes cannot run because it has detected audio configuration problem?

I've got Windows XP, recently did a system restore and was forced to re-install iTunes afterwards. After installation, I click the iTunes icon and get a pop up "iTunes cannot run because it has detected a problem with your audio configuration." I went to the iTunes support page and found a similar trouble shooting scheme. I applied both options and both failed. I tried re-installing again to repair, but after the repair, the problem still remains. I found a major difference in the trouble shooting scheme however and I wander if that could be it. The web page shows quick time's audio channels as "Stereo (L R)", however my quick time control panel doesn't feature that channel. Instead, there are 7 "LayoutTags" to choose from, each containing 7 digits. I'm no computer whiz, so I'm going to need help on this one.

replying to lowriderpharaoh.
hmmmmm. it's sounding like you've still got a damaged version of QuickTime in the PC. (or at least, there's something going wrong with the quicktime.)
let's try swapping out the QuickTime again. we'll take a few additional explicit precautions this time.
Download and install the Windows Installer CleanUp utility. then use it to clear any existing QuickTime installation configuration information from your PC:
Description of the Windows Installer CleanUp Utility
Next, we’ll manually remove leftover program files and folders.
1. On the Start menu, click My Computer (or double-click My Computer on the Desktop).
2. In My Computer, open Local Disk.
3. Open Program Files.
4. Right-click on the QuickTime folder and click Delete from the shortcut menu.
5. Navigate to C:\Windows\system32\.
6. Remove the files QuickTime.qts and QuicktimeVR.qtx.
7. Restart your computer.
next, we'll try to get a fresh copy of QuickTime into your PC by doing a repair install of itunes.
switch off antivirus and antispyware applications prior to the repair install.
go into Add/Remove and select itunes. click "Change" and then click "Repair".
if the repair install goes through okay, restart the PC and try launching itunes again. does it launch properly now?
if it doesn't launch properly, are you still getting the unusual display effects in the QT preferences?

Rfc Destination problem in RFC Sender Adapter

Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
   i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku

Destination problems

I made an 80 minute movie in FCP and exported it as a QT file. I then imported this QT file into Compressor and chose the DVD 90 minute preset setting. Shortly after submitting this I get a warning saying "This target will overwrite an existing file with the same name...To preserve the existing file, change the destination or change the name of the output file.".
So I do exactly that , but I still keep getting the same message no matter where I change the destination to or even the file name. This has been driving mad for nearly 2 days now , even changing the drive location doesn't work.
The manual seems tortuously unhelpful with this sort of problem , it tells you what Compressor can do but not actually HOW to do it. What on earth am I doing wrong here?.....I desperately need help before I turn into an axe murderer!!.

I have also noticed the same thing. Here is my theory on what is going on and bow to address:
I was exporting from Final Cut using Compressor so I could create a DVD. I used the export to compressor command in final cut (exporting an 80 min. Program). Compressor Opened and the program movie was in the job area. I dragged the HI Quality Dvd-90 min folder (2 settings) onto the file, then created a custom destination and set for both targets. After chugging away, I got the naming error described. My solution was to change the file names of the targets. I shortenend them both, leaving the Dolby and Mpeg parts of the name, but added an "a" and a "v" to the filenames of their respective files. I put the "a" and "v" prior to the Dolby or Mpeg portion of the name, before the hyphen. This seemed to fix the problem and created the appropriate files.
Why I think this works? I believe that the 2 streams needed for a DVD just need a slight change in filename so that compressor doesn't try to overwrite what has just been created. It could also be a confounding factor that filenames get too long and are truncated, making for duplicate names.
Anyway, I hope this helps. It seems to have worked for me. My only other issue is that once the job completes, it seems to start again. It could be that I had submitted the job multiple times in my attempt to figure it out, but not sure. When the job starts again, I get the same filename error.

MQSeries and MDB communication problem

I was trying to write one MDB which will talk to MQSeries. After configuring everything(including the bindings and changes in weblogic-ejb-jar.xml) i deployed the MDB in weblogic6.1 sp2 server. It did not give me any error while deploying and container called the ejbCreate and setMessageContext methods without any problem. But it is not reading the messages from the MQ. It never picked up the messages from MQ. Can anyone please tell me what may be the reason?

I would suggest that you look at the JMS FAQ or read the archives in the JMS newsgroup. There's lots of posts about getting this to work.
-- Rob
Sujoy Das wrote:
I was trying to write one MDB which will talk to MQSeries. After configuring everything(including the bindings and changes in weblogic-ejb-jar.xml) i deployed the MDB in weblogic6.1 sp2 server. It did not give me any error while deploying and container called the ejbCreate and setMessageContext methods without any problem. But it is not reading the messages from the MQ. It never picked up the messages from MQ. Can anyone please tell me what may be the reason?--
AVAILABLE NOW!: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnWebLogic.com
[att1.html]

Web Service Destination Problem

Hi,
I want to try out this simple example of using a Web service in Visual Composer (http://help.sap.com/saphelp_nwce711/helpdata/en/0d/a467e29b3f4b0db27cec840066e5b1/frameset.htm).
After I have created a destination in the NetWeaver Administrator, I tried to search for Web services in the "Search" panel and I got this error message "Could not complete search. Check log for more information".
It was a surprise to me, because it requires just a simple configuration (copy and paste the WSDL URL (http://www.webservicex.net/CurrencyConvertor.asmx?WSDL), but it did not work out.
I wonder where is the problem and could anyone tell me how can I find out the log information? I suppose it is in the NetWeaver Administrator, right?
Thanks.
Regards,
Joon Meng

Hi,
finally I have located the log for the error in the log viewer.
There are two entries:
1.
SystemHandler: search in system: CurrencyConverter ,function expression : * ,object expression: null failed. Reason: Could not retrieve metadata
2.
(VC-DevServer)(error in search WebServicesProvider/CurrencyConverter)<Localization failed: ResourceBundle='com.sap.ds.core.exceptions.DevserverMessages', ID='SystemHandler#search: Could not find the functions metadata', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key SystemHandler#search: Could not find the functions metadata
There is firewall in my corporate network. Could this be the source of the problem?
Anyone has idea about this?
Thanks in advance.
Regards,
Joon Meng
Edited by: Joon Meng Goh on Sep 2, 2009 10:03 AM
Edited by: Joon Meng Goh on Sep 2, 2009 11:18 AM

DEFAULT_WS_DEST web service destination - problem with production server

Hi All,
I'm getting close to go live for a project which uses a vast number of custom web services to access an Oracle DB backend to supply data to a Portal front end. Many of the applications we have developed are based on Web Dynpro and so we have used adaptive web service models to call the web services. My basis guy and I sat down and configured the DEFAULT_WS_DEST logical web service destination to work correctly in both our DEV and QA systems.
We completed the production build but when testing the Web Dynpro applications I get a dump saying '"DEFAULT_WS_DEST/default" cannot be found'.
Does anyone know why our production system is looking for a connection called "DEFAULT_WS_DEST/default" instead of just "DEFAULT_WS_DEST" as per our DEV and QA system?
Thanks in advance.

Ok, I was really hoping for some response at least! Guess no-one has had this problem before?
Here's the exception message:-
Caused by: java.rmi.RemoteException: Error while processing document security. The error was class com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path
"webservices/proxies/sap.com/DynamicWSProxies/DEFAULT_WS_DEST/default" does not exist.. See trace entry [no trace for com.sap.security.core.client.ws.DeployableSecurityProtocol (severity above PATH)].;
nested exception is: com.sap.engine.services.webservices.jaxrpc.wsdl2java.ClientProtocolException: Error while processing document security. The error was class
com.sap.engine.frame.core.configuration.NameNotFoundException A configuration with the path "webservices/proxies/sap.com/DynamicWSProxies/DEFAULT_WS_DEST/default" does not exist.
If anyone has any suggestions at all I'd be very grateful. As mentioned, the DEFAULT_WS_DEST configuration does exist and it works perfectly in both DEV and QA but not PROD.
Thanks,
Gareth.

Regarding Logical destination problem.. urgent please

Hi gurus,
I am facing one problem in printing credit memo from vf02,
when i give one logical destination( means printer ) for example A its working fine., if i will give apart from A printer, outout could not be issued giving this information, if i will give LOCAL printer LP01 then also not working....
i have seen all confugaration also there they local printer only..
print privew is coming to all printers( logical destinations)
but print is not coming..
Regards
Nagu

Hi,
You have to write in form calc under form ready event.
As of now, i dont have any system to check.You can check any standard forms like vendor statement / customer statement which have page totals.
for example, drag the S1 subform into one more sumforn with flow content say SS1.Write the below (similar) code.
// get total number of records
Var record_count = $.Table1.data.all.length
Var flag
Var value_check = '222'
For I = 0 upto ( record_count - 1 ) step 1 do
if $.Table1.data<i>.field1 = = value_check
flag = 'X'
endif
Endfor
if flag = = 'X'.
$.S1.presence = "hidden"
endif
Please check the syntax.
pavan meda

Detecting MDB destination problems

Similar Messages

Maybe you are looking for