WLS 10.3.3 (OSB) Exception faced : General runtime error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.

WLS 10.3.3 not supporting SHA2 cert at provider end . (wild card certificate cannot be imported to trusted certs)
During integration from OSB 11g we face below exception :
General runtime error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received
Regards,
Anitha

Enable -Dssl.debug=true java option and capture the logs.
You might find this userful
http://weblogic-wonders.com/weblogic/2010/01/28/troubleshooting-ssl-issues/

Similar Messages

Getting error in OSB :: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received..

Hi There,
am getting error when invoking a webservice from OSB .
"The invocation resulted in an error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received..".
certs were loaded to the trust store and could see certificates in Trust store.
surprisingly, same webservice works from SOA BPEL and even from soapUI.
I even made Host Name verification to NONE... none of those helped.
your suggestions are very much appreciated.
Thanks,
Karthik.

Enable -Dssl.debug=true java option and capture the logs.
You might find this userful
http://weblogic-wonders.com/weblogic/2010/01/28/troubleshooting-ssl-issues/

BEA-380000: General runtime error: Read channel closed - intermittent

I am encountering this error code intermittently. My production has been live from past 20 months and I see this error very recently and its like once a week.
I doubt if this has something to do with the network and as this is very generic error(BEA-380000) I am not able to find any pointers on this error.
My environment
Solaris 10,Weblogic 10.3(Not clustered)
fault="<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382500</con:errorCode>
<con:reason>OSB Service Callout action received SOAP Fault response</con:reason>
<con:details>
<con1:ReceivedFaultDetail xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
<con1:faultcode xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">soapenv:Server</con1:faultcode>
<con1:faultstring>BEA-380000: General runtime error: Read channel closed</con1:faultstring>
<con1:detail>
<con:fault>
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>General runtime error: Read channel closed</con:reason>
<con:location>
<con:node>RouteNode1</con:node>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</con1:detail>
</con1:ReceivedFaultDetail>
</con:details>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>"
Cheers
Sridhar

Matt,
How are you invoking local proxy from HTTP proxy (using route node or service callout)? Is local proxy calling another proxy/business service? Do you have fault handling implemented?
Can you also check server log to figure out any additional error information (like stacktrace)?
Regards,
Anuj

Facing a Runtime Error u201C GETWA_NOT_ASSIGNED u201C in report at background

Hi All,
I am facing a Runtime Error u201C GETWA_NOT_ASSIGNED u201C when a custom report is executed in the background,
whereas the same report in getting executed properly in foreground.
The reason, which, the Dump Analysis specifies is u201C Field symbol has not yet been assigned in the ABAP program "SAPLKKBL "
Any one pls. let me know the solution
I have already checked my field catalog & all the field names are in Capital.
Please suggest the solution.
Thanks in advance.
Thanks & Regards,
Sudhir Dure
9972097464

please check the fields in the output display with currency /quantity fields/packed decimal fields...
try by moving the data into a char field..it will work..

Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised

Hi All,
I am facing a runtime error, while using transaction DSWP --> Set-up System Monitoring --> Copy Customizing -->
At that time we are getting "Runtime error RAISE_EXCEPTION Exception condition "METADATA_MISSING" raised
===========================================
Runtime Errors RAISE_EXCEPTION
Date and Time 25.07.2008 08:31:11
Short text
Exception condition "METADATA_MISSING" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
A RAISE statement in the program "SAPLDSVAS_SERV" raised the exception
condition "METADATA_MISSING".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"RAISE_EXCEPTION" " "
"SAPLDSVAS_SERV" or "LDSVAS_SERVC7I"
"MAP_DSVAS_TT_DATA_TO_TT_25"
or
"SAPLDSVAS_SERV" "METADATA_MISSING"
or
"RDSMOP_MAIN " "METADATA_MISSING"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "terra"
Network address...... "172.16.1.198"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 2
Shortdump setting.... "full"
Database server... "TERRA"
Database type..... "ORACLE"
Database name..... "DSM"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 01:07:18"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 133
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 37628064
Heap.... 0
Page.... 65536
MM Used. 31785376
| MM Free. 1656912
=============================================
Configuration:
OS :Windows 2003 server.
Solution Manager 7.0 SP15
Oracle 10.2
RAM - 2 GB
Its bit urgent, Please help out us.
Thanks in advance.
Best Regards,
Pratyusha

Hi
Check the SP level for ABAP and Basis. Download the latest SP level from SWDC and apply it on the system
This error is related to ABAP program.
Currently the latest available patch level is 16. Please download both ABAP and BASIS SP 16 and apply them on the system.

Nokia n8-00 General system error appears? Email al...

Hey guys, last night my nokia n8 keeps getting a randomly appearing message "general system error" and only comes up with i think it was either back, continue or close. The strange thing is nothing happens, then after maybe half an hour it appears again, then a few minutes again after that and happened during random intervals.
Im now afraid of turning off my phone just because it might prevent it from turning on properly and i dont want to lose all my data, (my opera bookmarks, my apps, music, etc) What also happens is that my email wont sync properly anymore. Ive had to re add my account just to get it to resync emails again, works for a day then just stops.
After the general system error it doesnt even show emails anymore, not even ones previously received

MajorFoley,
Welcome to Nokia Discussions!
Can you please provide the following information, so I can provide the proper steps to take next:
Look for the firmware version by going to Standby Screen> Call button> enter this code: *#0000# and the software information should appear. The earlier version should start with 11, newer versions are codenamed Symbian Anna, Symbian Belle, and Symbian Refresh.
Have you tried to backup the contents inside the phone? If not, you can do that by getting the latest Nokia Suite at http://nds1.nokia.com/files/support/global/phones/software/Nokia_Suite_webinstaller_ALL.exe using a Windows loaded computer.
Good luck

Null pointer exception in native code. error 52 in Weblogic8.1

Hi all,
I'm using WLS 8.1SP5 with 1.4.2_08 and having this dump once a day, when people is working. I tryed google, but no luck. Can someone can help please?
===== BEGIN DUMP =============================================================
JRockit dump produced after 5 days, 00:39:42 on Mon Oct 01 16:59:00 2007
Additional information is available in:
D:\web\bea\user_projects\domains\APIA_Prod\jrockit.2188.dump
D:\web\bea\user_projects\domains\APIA_Prod\jrockit.2188.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error code: 52
Error Message: Null pointer exception in native code
Version : BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 ari-49095-20050826-1856-win-ia32
Threads / GC : Native Threads, GC strategy: parallel
: mmHeap->data = 0x00B60000, mmHeap->top = 0x40B60000
: mmStartCompaction = 0x1EB60000, mmEndCompaction = 0x23B60000
CPU : Intel Pentium 4 (HT)
Number CPUs : 8
Tot Phys Mem : 4025999360
OS version : Microsoft Windows Server 2003 Service Pack 1 (Build 3790)
State : JVM is shutting down
Command Line : -Djava.class.path=.;C:\Program Files\Java\j2re1.4.2_05;C:\Program Files\Java\j2re1.4.2_05\lib;C:\Program Files\Java\j2re1.4.2_05\lib\tools.jar -Djrockit.launcher.type=jrockit.shipment -Xms1024m -Xmx1024m -Xgc:parallel -Xcleartype:local -Dweblogic.management.server=http://10.128.12.23:7001 -Dbea.home=D:\web\bea -Dweblogic.RootDirectory=D:\web\bea\user_projects\domains\APIA_Prod -Djava.class.path=.;D:\web\bea\jdk142_08\lib\tools.jar;D:\web\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\web\bea\WEBLOG~1\server\lib\weblogic.jar -Djava.security.policy==D:\web\bea\WEBLOG~1\server\lib\weblogic.policy -Dweblogic.Name=Apia_Svr1 -Dweblogic.system.BootIdentityFile=D:\web\bea\WEBLOG~1\common\nodemanager\NodeManagerLogs\NodeManagerInternal\bootFile_APIA_Prod_Apia_Svr1 -Dweblogic.system.NodeManagerBoot=true -Dweblogic.system.NodeManagerAddress=null::5555 -Dweblogic.nodemanager.ServerStartTime=1190834358456 -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Dsun.java.command=weblogic.Server
Environment : JAVA_HOME=C:\Program Files\Java\j2re1.4.2_05, java.home=d:\web\bea\jrockit81sp5_142_08\jre, java.class.path=.;D:\web\bea\jdk142_08\lib\tools.jar;D:\web\bea\WEBLOG~1\server\lib\weblogic_sp.jar;D:\web\bea\WEBLOG~1\server\lib\weblogic.jar, java.library.path=d:\web\bea\jrockit81sp5_142_08\bin;.;C:\WINDOWS\system32;C:\WINDOWS;D:\web\bea\WEBLOG~1\server\bin;D:\web\bea\jdk142_08\bin;D:\web\bea\jdk142_08\jre\bin;C:\Program Files\VERITAS\NetBackup\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Java\j2re1.4.2_05\bin
C Heap : Good; no memory allocations have failed
Registers (from context struct at 0x41D6F488/0x41D6F5A4):
Converted EIP: 41eafe45
EAX = 00001e90 EBX = 009db42c
ECX = 003c1e90 EDX = 00000000
ESI = 71c14280 EDI = 00000000
EIP = 41eafe45 ESP = 41d6f870
EBP = 41d6f880 EFL = 00010a03
CS = 001b DS = 0023 ES = 0023
SS = 0023 FS = 003b GS = 0000
Stack:
41d6f870 :00000000 00000000 003c95a8 003c1e90 00000000 004e91e1
41d6f888 :0000008f 00000000 41d6f8c4 009db42c 00000001 00000000
41d6f8a0 :41b802e0 4cfa3940 012b5068 4d87a5cc 012b5068 00000000
41d6f8b8 :012b5068 41b81710 4ccfcdda 009b9ba8 004e9244 012b5310
41d6f8d0 :0054deca 012b5315 4ccfc945 0000008f 50a0f1e8 009db42c
41d6f8e8 :00000000 012b5258 4ccfcb33 012b5315 0000008f 012b5258
41d6f900 :4ccfca44 012b525d 00000000 009b9ba8 41d6f918 41b823f8
41d6f918 :4ccfc980 00553ff5 ffffffff 00000010 00000000 41d6f9e4
41d6f930 :4d1126e8 009b9c34 41d6fa48 41d6f978 009b9c34 437faab0
41d6f948 :fffffffe 00000002 fffffffe 00000000 41d6f978 00570b50
41d6f960 :00000000 009b9ba8 00090000 009b9c34 00000001 7c8302e7
41d6f978 :00000000 00570b50 fffffff8 00000001 0000008f 0000008c
41d6f990 :437faaf0 00000000 00000000 00000000 00000000 41d6f918
41d6f9a8 :41b823c0 ffffffff 437f9fc0 437faab0 009b9c34 4ccfc980
41d6f9c0 :0000008f 41d6f918 00000001 00000001 00000010 00000000
41d6f9d8 :00000000 41d6f918 009b9c34 009b9ba8 00533bb1 009b9c34
41d6f9f0 :50a0f1b8 4d1126e8 00000000 41d6fa44 005539c0 41d6fa48
41d6fa08 :009b9ba8 437f9fc0 41d6fa50 009b9c34 0059065c 50a0f1b8
41d6fa20 :00535583 009b9c34 437faab0 00000000 41d6fa44 005539c0
41d6fa38 :00000001 41d6fa48 00533729 41d6fa68 00000000 00000000
41d6fa50 :0000008f 00569db2 009b9c34 437f9fd4 437faab0 0000008f
41d6fa68 :009b9ba8 009b9c34 0000000f 00000002 00569ef7 0000008f
41d6fa80 :009b9ba8 0056a38d 009b9ba8 009b9ba8 41d6ff80 009b9ba8
41d6fa98 :7ffde000 009b9c34 41d6ff98 00525ca0 00572cf0 00000000
41d6fab0 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fac8 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fae0 :00030178 00000269 00000000 00000000 00000000 00000000
41d6faf8 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fb10 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fb28 :00000000 00000000 00037c28 00000000 00000000 00000000
41d6fb40 :00000000 00000013 00000000 00037c20 00030168 00000042
41d6fb58 :00037c20 00000013 00030178 00000000 00000098 00000000
41d6fb70 :00030000 009d6850 00000210 4100fbbc 00000098 4100f980
41d6fb88 :00380000 41d6f988 00000000 41d6fbd4 7c82f680 7c82fb28
41d6fba0 :ffffffff 7c82fb23 7c3423aa 771f123c 00000000 00000002
41d6fbb8 :771f0000 41d6fc10 00095e70 00000001 00000000 41d6fca8
41d6fbd0 :771f46c9 771f1240 ffffffff 771f123c 771f11e8 771f0000
41d6fbe8 :00000002 00000000 00000000 41d6fc10 00000001 41d6fc1c
41d6fc00 :7c82257a 771f0000 00000001 00000000 00000001 00000000
41d6fc18 :00097f98 00000001 00000000 41d6fcb8 7c81a81b 7c889d94
41d6fc30 :7c81b26f 00000000 7ffdc000 00000000 00000000 00000000
41d6fc48 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fc60 :00000000 00000024 00000001 00000000 00000000 00000070
41d6fc78 :ffffffff ffffffff 7c81a7dc 7c81a7a4 00000000 00000000
41d6fc90 :00097f98 771f11a0 00000418 000000f5 009dc120 41d6fecc
41d6fca8 :7c82fda6 7c82fb23 0000040c 0000040c 009b9ba8 7c822054
41d6fcc0 :7c81b23f 41d6fd28 00000000 009dbad8 00000000 00000000
41d6fcd8 :00000000 00000000 00000000 00000000 00000000 00000000
41d6fcf0 :00000000 00000000 00000000 41d6fcc4 00000000 41d6fff4
41d6fd08 :7c82f680 009dc530 ffffffff 7c81b23f 7c8211b4 0000000c
41d6fd20 :41d6fd28 00000001 00010017 00000000 00000000 00380178
41d6fd38 :00000000 00000000 00000000 00000005 f7547000 0000010d
41d6fd50 :000007ff 00000001 624e4d43 00000060 ae19faa4 009dc120
41d6fd68 :e4d11360 e24e4d43 00000005 0000000e e310e008 ffffffff
41d6fd80 :3b9aca07 e33dd7e8 3b9aca07 3b9aca07 00380178 1a30eb0a
41d6fd98 :009dc538 8093d69b 009d99e8 00000000 00380178 c0000034
41d6fdb0 :808ad480 00000000 00000038 009d99f0 00000023 00000000
41d6fdc8 :00000000 009dbad8 00000000 00000000 0056f660 00000000
41d6fde0 :77e6b5f3 0000001b 00000200 41d6fffc 00000023 00000698
41d6fdf8 :0000076a e47bbbf0 00000090 00000006 00000005 f7547000
41d6fe10 :ae19fbd4 e131ec08 ae19fbd8 d3f0fe22 d3f0fe22 000000f5
41d6fe28 :8093cb16 e131ec08 e105bf1c 00000025 ae19fbd0 009d99f0
41d6fe40 :e105bfb0 ae19fbd4 8093cb6e 3b9aca07 e131ec08 8083a8f5
41d6fe58 :00000000 00000000 80a78be3 badb0d00 80010031 00000005
41d6fe70 :009dc120 00000005 c0502000 009dccd8 77ce8221 00000083
41d6fe88 :00000000 009dc118 ae19fba8 00000418 009dc118 009dc120
41d6fea0 :00380178 00000001 00000418 0000ad58 00380000 41d6fcb0
41d6feb8 :f772fa00 41d6fefc 7c82f680 7c82fb28 ffffffff 7c82fb23
41d6fed0 :7c3416b3 00380000 00000000 7c3416b8 0000040c 00000000
41d6fee8 :009b9ba8 ffffffff 41d6ff3c 41d6fee0 41d6ff40 41d6ff98
41d6ff00 :7c34240d 7c37a2a8 ffffffff 7c3416b8 7c3416db 0000040c
41d6ff18 :7c3416f8 0000040c 00000000 00504b4d 0000040c 0107e577
41d6ff30 :41d6ff6c 0057de91 009b9ba8 009b9ba8 00003000 00000140
41d6ff48 :41d6ff64 41d6ffa0 0056f1f9 41c70000 00003000 009b9ba8
41d6ff60 :009db8b0 009b9ba8 0056e9c2 7c821dd4 009b9ba8 009b9ba8
41d6ff78 :009b9ba8 00572ce9 41d6ffa0 00572ded 77e6eccd 009dbad8
41d6ff90 :009dbad8 7ffde000 41d6ffdc 00525ca0 41d6ffec 0056f6c7
41d6ffa8 :009b9ba8 00000000 00000000 00000740 009dbaf4 77e6608b
41d6ffc0 :00000740 00000000 00000000 009dbad8 c9792963 41d6ffc4
41d6ffd8 :000d4193 ffffffff 77e6b7d0 77e66098 00000000 00000000
Code:
41eafd45 :00000000 00000000 00000000 00000000 00000000 00000000
41eafd5d :00000000 00000000 ff4e4be0 00ffffff 007ffdc0 00000000
41eafd75 :34001590 0041eafd 98000000 d041eaff 0077e6b7 0077e6bb
41eafd8d :a4000000 4241eafd 2877e6ba ff000007 00ffffff 68000000
41eafda5 :0c41d6f8 280056e6 ff000007 0fffffff 48001d1a 8000aece
41eafdbd :00006093 987ffda0 c0005710 98004fe0 38009da3 0041eafe
41eafdd5 :40000000 9841eafe f8009da3 0001c83c e0000000 0001c83c
41eafded :17000000 80004f66 38006093 3841eafe 2041eafe 00f7c4ca
41eafe05 :da7ffda0 20004f20 c0f7c4ca 00004fe0 00000000 b5000000
41eafe1d :98004f2e 98009da3 00009da3 9841eaff 58009da3 00303fe0
41eafe35 :00000000 50000000 0000570b 98000000 00009da3 00000000
41eafe4d :80000000 f5006093 388083a8 5041eafe 0000570b 98000000
41eafe65 :31009da3 00800100 60000000 00005c0e 58000000 5041eafe
41eafe7d :0000570b 98000000 00009da3 00000000 d0000000 00005c0e
41eafe95 :31000000 00800100 00000000 00000000 ff000000 00ffffff
41eafead :00000000 cc000000 0080a78b e0f7757a 78adbbab 5041eafe
41eafec5 :0000570b 98000000 b7009da3 608083e6 2888736a 90005c0e
41eafedd :7888736a 5041eafe 0000570b 98000000 3c009da3 0041eaff
41eafef5 :20000000 00005c0f 80000010 f041eaff 0000572c 84000000
41eaff0d :917c8218 ff77e41a 3cffffff 4041eaff 4041eaff 64000001
41eaff25 :f041eaff 6c009de2 2d41eaff 0600540a 98000000 f0009da3
41eaff3d :00009de2 40000030 64000001 a041eaff f941eaff 000056f1
Loaded modules:
(* denotes the module causing the exception)
0x7c800000-0x7c8bffff C:\WINDOWS\system32\ntdll.dll
0x77e40000-0x77f41fff C:\WINDOWS\system32\kernel32.dll
0x77f50000-0x77febfff C:\WINDOWS\system32\ADVAPI32.dll
0x77c50000-0x77ceefff C:\WINDOWS\system32\RPCRT4.dll
0x77ba0000-0x77bf9fff C:\WINDOWS\system32\MSVCRT.dll
0x00410000-0x0061afff d:\web\bea\jrockit81sp5_142_08\jre\bin\jrockit\jvm.dll
0x76aa0000-0x76accfff C:\WINDOWS\system32\WINMM.dll
0x77c00000-0x77c47fff C:\WINDOWS\system32\GDI32.dll
0x77380000-0x77411fff C:\WINDOWS\system32\USER32.dll
0x7c8d0000-0x7d0d3fff C:\WINDOWS\system32\SHELL32.dll
0x77da0000-0x77df1fff C:\WINDOWS\system32\SHLWAPI.dll
0x71c00000-0x71c16fff C:\WINDOWS\system32\WS2_32.dll
0x71bf0000-0x71bf7fff C:\WINDOWS\system32\WS2HELP.dll
0x7c340000-0x7c395fff C:\WINDOWS\system32\MSVCR71.dll
0x71bc0000-0x71bc7fff C:\WINDOWS\system32\rdpsnd.dll
0x771f0000-0x77200fff C:\WINDOWS\system32\WINSTA.dll
0x71c40000-0x71c97fff C:\WINDOWS\system32\NETAPI32.dll
0x76b70000-0x76b7afff C:\WINDOWS\system32\PSAPI.DLL
0x77420000-0x77522fff C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.3790.2778_x-ww_A8F04F11\comctl32.dll
0x76f50000-0x76f62fff C:\WINDOWS\system32\Secur32.dll
0x00b30000-0x00b48fff d:\web\bea\jrockit81sp5_142_08\jre\bin\java.dll
0x00b50000-0x00b5dfff d:\web\bea\jrockit81sp5_142_08\jre\bin\verify.dll
0x71b20000-0x71b60fff C:\WINDOWS\System32\mswsock.dll
0x76ed0000-0x76efefff C:\WINDOWS\system32\DNSAPI.dll
0x76f80000-0x76f87fff C:\WINDOWS\system32\rasadhlp.dll
0x42c30000-0x42c34fff D:\web\bea\weblogic81\server\bin\wlntio.dll
0x68000000-0x6802efff C:\WINDOWS\system32\rsaenh.dll
0x00a90000-0x00a95fff D:\web\bea\jrockit81sp5_142_08\jre\bin\ioser12.dll
0x02800000-0x028c0fff d:\web\bea\jrockit81sp5_142_08\jre\bin\dbghelp.dll
0x77b90000-0x77b97fff C:\WINDOWS\system32\VERSION.dll
Java Thread ID = 0x00000100, lastJavaFrame = 0x41D6F8E0, Name = (Signal Handler)
Thread Stack Trace:
at _vmShutdown+225()@0x004E91E1
at java/lang/Shutdown.halt(Native Method)@0x4CCFC910
at java/lang/Shutdown.exit(Unknown Source)@0x4CCFCA44

You would need to get BEA support, after verifying you are on a supported configuration (http://edocs.bea.com/jrockit/jrdocs/suppPlat/supp_142.html).
Otherwise you may need to try update 10, or use Sun JVM.

Portal Runtime Error : An exception occurred while processing a request

Hello friends,
After upgradation of my portal to the following patch level, SAP J2EE 6.20:
Portal Version : EP 6 SP 2 patch 29 hotfix 0
Content Mgmt and Collaboration version : 6 SP2 patch 5
i faced many performance related issues. Portal seems to be very slow. After logging in, most of the time I get 2 errors:
Either
1> Iview remains blank.
Or
2> Portal Runtime Error : An exception occurred while processing a request. Portal Runtime exception occured. Please check the System Log.
But when I refresh that particular iview, it works fine.
I went through the portal.log file (/usr/sap/PEP6/j2ee/j2ee_00/cluster/server/managers/log/portal/logs). And found the root cause of most of the exceptions as "com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found."Aug 18, 2005 6:07:42 PM # PRT-Async 2 Fatal Exception ID:06:07_18/08/05_0669
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/ACCContent/ACCContent.Roles/Company/R.Employee/W.MyWork/P.MyWork.DesktopTools/I.Contacts
Component class : com.sapportals.portal.prt.pom.RootComponentNode
User : tempuser
 at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:853)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:311)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: PortalComponentException
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:153)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Caused by: com.inqmy.services.servlets_jsp.server.ServletNotFoundException: The requested servlet ( portal ) not found.
 at com.inqmy.services.servlets_jsp.server.ServletContextFacade.loadServletLocal(ServletContextFacade.java:3660)
 at com.inqmy.services.servlets_jsp.server.InvokerServlet.service(InvokerServlet.java:81)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:275)
 at com.inqmy.services.servlets_jsp.server.RequestDispatcherImpl.include(RequestDispatcherImpl.java:384)
 at com.sapportals.portal.prt.pom.RootComponentNode.service(RootComponentNode.java:144)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:301)
 at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:138)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:376)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
 at java.lang.Thread.run(Thread.java:479)
Help needed.(as i am helpless now.)
Regards,
Nilz

Anthony,
I had check it. It was correct. But the thing when I saw in the component Inspector of portal, my iview did not appear.
I created like this
 project-> rightclick-> export-> par ->selecting project-> givint protal password-> and finish.
The NW didn't give any error, but the par file didn't appear in the portal componet Inspect.
but the par file is created in the NW studio Navigation bar.
Let me know any help regarding this
thanks
venkat

Org.xml.sax.SAXException: Error:General Schema Error

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
 <soapns:Header/>
 <soapns:Body>
<test:GWSMapRequestMessage>
 </test:GWSMapRequestMessage>
 </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
 <soapns:Header/>
 <soapns:Body>
<test:GWSMapRequestMessage>
 </test:GWSMapRequestMessage>
 </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

Org.xml.sax.SAXException: Error:General Schema Error: Grammar

I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema" namespace
or
the instance document's namespace may not match the targetNamespace of the schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation", Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema" xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
 <soapns:Header/>
 <soapns:Body>
<test:GWSMapRequestMessage>
 </test:GWSMapRequestMessage>
 </soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>

I guess the problem is due to the schema namespace
you are using.
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
pls try with :
"http://www.w3.org/2001/XMLSchema"
regards,
-manoj
"Eva Flora" <[email protected]> wrote in message
news:[email protected]...
I am getting the error below. Any clues/workarounds? I am
using WL 6.1.
Thanks in advance,
Eva
The following files are below:
Validate.java
BMDefaultHandler.java
validate.xml
validate.xsd
org.xml.sax.SAXException: Error:General Schema Error: Grammar with
uri:http://schemas.xmlsoap.org/soap/envelope/
, can not be
found; schema namespace maybe wrong:
Xerces supports schemas from the "http://www.w3.org/2001/XMLSchema"
namespace
or
the instance document's namespace may not match the targetNamespace of the
schema.
at
com.bluemartini.xml.BMDefaultHandler.error(BMDefaultHandler.java:32)
at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1249)
at
org.apache.xerces.validators.common.XMLValidator.reportRecoverableXMLEr
ror(XMLValidator.java:1821)
at
org.apache.xerces.validators.common.XMLValidator.validateElementAndAttr
ibutes(XMLValidator.java:3232)
at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLVa
lidator.java:1229)
at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentS
canner.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispat
ch(XMLDocumentScanner.java:949)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentSca
nner.java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
at
org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.ja
va:195)
at
javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:191)
at com.bluemartini.test.Validate.main(Validate.java:32)
===Validate.java
package com.bluemartini.test;
import java.io.*;
import org.w3c.dom.*;
import com.bluemartini.xml.*;
// JAXP imports
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.ParserConfigurationException;
* Sample test case.
* Eva Flora
public class Validate {
public static void main(String[] argv) {
try {
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
factory.setValidating(true);
factory.setAttribute("http://xml.org/sax/features/validation",
Boolean.TRUE);
factory.setAttribute("http://apache.org/xml/features/validation/schema",
Boolean.TRUE);
DocumentBuilder builder = factory.newDocumentBuilder();
BMDefaultHandler bmErrorHandler = new BMDefaultHandler();
builder.setErrorHandler(bmErrorHandler);
File temp = new File("validate.xml");
Document doc = builder.parse(temp);
} catch (Exception e) {
e.printStackTrace();
===BMDefaultHandler.java
package com.bluemartini.xml;
import com.bluemartini.dna.*;
import org.xml.sax.helpers.DefaultHandler;
import org.xml.sax.*;
public class BMDefaultHandler extends
DefaultHandler
public BMDefaultHandler()
public void warning(SAXParseException spe)
throws SAXException
System.out.println("Warning: " + spe.getMessage());
public void error(SAXParseException spe)
throws SAXException
throw new SAXException("Error:" + spe.getMessage());
public void fatalError(SAXParseException spe)
throws SAXException
throw new SAXException("Fatal Error: " + spe.getMessage());
===validate.xml
<?xml version="1.0" encoding="UTF-8"?>
<soapns:Envelope xmlns:soapns="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
xmlns:test="http://www.test.com"
xsi:noNamespaceSchemaLocation="validate.xsd">
<soapns:Header/>
<soapns:Body>
<test:GWSMapRequestMessage>
</test:GWSMapRequestMessage>
</soapns:Body>
</soapns:Envelope>
===validate.xsd
<schema xmlns="http://www.w3.org/2000/10/XMLSchema">
<element name="GWSMapRequestMessage" type="TestType"/>
<complexType name="TestType">
</complexType>
</schema>
[att1.html]

Runtime Errors Raise Exception in Solution Manager

Hi Guru's,
While I try to excute the transaction solman_issue_mgnt in solution manager for issue tracking, runtime errors occurs.
Error analysis
    A RAISE statement in the program "CL_GUI_HTML_VIEWER============CP" raised the
     exception
    condition "CNHT_ERROR_PARAMETER".
    Since the exception was not intercepted by a superior
    program, processing was terminated.
Could anyone suggest me on this issue.
regards,
Guna

Hi Juan,
As per the note, everything was fine there. We have SAP_Basis 700 with SP16.
Earlier it was worked fine. Now only we are facing this issue while excuting the t-code solman_issue_mgmt.
regards,
Guna

MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred on the current command. The results, if any, should be discarded".

MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred
on the current command. The results, if any, should be discarded". We are facing this issue for past two month.But funny thing is server will be up automatically with out any service restart manually. Also if we try to restart the SQL
server service manually then SQL server will be in a dead lock situation and it will not come up even if we wait for long time. Then we should do a windows server machine restart to
make the SQL sever up. As a suggestion from Microsoft to fix this kind of similar issue,
we have installed service pack 3 for SQL Server. But even after we are facing same issue.
Server Details:
Server OS: Windows Server 2008 R2
Two type of database servers are installed on server:
1. MS SQL Server 2008 R2
2. My SQL
Also Reporting server is configured for the purpose of generating SSRS report from a dot net website.
NOTE:Immediately after the data retrieval/save, we are closing the connection explicitly by the
application.
we have checked the windows event log and below are the details:
Log Name: Application
Source: ASP.NET 4.0.30319.0
Application information:
 Application domain: /LM/W3SVC/5/ROOT-1-130718142067856406
 Trust level: Full
 Application Virtual Path: /
 Application Path: E:\WebSpaceFolder\ACSQuiK\Production\
 Machine name: DBSERVER
Process information:
 Process ID: 148
 Process name: w3wp.exe
 Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
 Exception type: SqlException
 Exception message: A severe error occurred on the current command. The results, if any, should be discarded.
 at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
 at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
 at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
Log Name: Application
Source: Report Server Windows Service (MSSQLSERVER)
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Report Server Windows Service (MSSQLSERVER)" />
 <EventID Qualifiers="0">107</EventID>
Could anybody can suggest any kind of fix for this issue? Thanks in advance.

Hi YesYemPee,
I have tried but still not clear about your issue, I would like you provide more details information about your issue based on below points to better analysis about the issue:
What action did you do and caused the error "A severe error occurred on the current command. The results, if any, should be discarded", did you run report on the web application or something else then the error happen?
If you rendering the report and got the error, please try to provide us more error information in the log files which path like:
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
If it is not the case in step1, Please try to provide SQL Server Error log(SQL Server Logs) and more details information.
If you still have any problem, please feel free to ask.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
ERROR
Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
STEPS
The issue can be reproduced at will with the following steps:
1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
2) Created dnd.param file in SIebel server SDQCOnnector folder.
3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
6) Configured the Siebel components for EDQ integration.
7) Realtime EDQ jobs are running.
8) Create a new Account
Env details are
On : 8.2.2.14 [IP2014] version, Client Functionality
EDQ 11.1.1.7.4
IBM JDK 1.7 32 bit
Using Open UI
Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
Regards
Monoj Dey
9007554589

Hi Monoj,
A few questions:
- What OS is Siebel running on?
- What version of the Siebel connector are you using?
- Which libdnd.so file are you using?
- What's the contents of your dnd.parms file?
thanks,
Nick

Internal Delievery channel AIP-51505: General Validation Error

hi ,
I am trying HL7 sample provided with B2b installation. It works fine . Have modified internal delievery channel as file protocol & provided the folder uri , so as to b2b engine picks it up as xml message is dropped in folder. It is resulting in B2B - (ERROR) Error -: AIP-51505: General Validation Error .
Just wondering why the B2B process is not validating xml file by just modifing internal delievery channel. Do i have to take additional care to configure Internal Delievery channel. ??
2008.12.04 at 12:05:49:734: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
 at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:195)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1364)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
2008.12.04 at 12:05:49:734: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
 at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:195)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1364)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-51505: General Validation Error
2008.12.04 at 12:05:49:734: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=a01.xml, filesize=1901, file_ext=xml, *fullpath=C:\files\a01.xml, timestamp=2008-12-04T11:43:31.640-05:00}*
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-51505: General Validation Error
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2008.12.04 at 12:05:49:750: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2008.12.04 at 12:05:49:781: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2008.12.04 at 12:05:49:812: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exception null
2008.12.04 at 12:05:49:812: Thread-14: B2B - (ERROR) java.lang.NullPointerException
 at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:839)
 at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:5150)
 at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3831)
 at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:3702)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1383)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
Thanks

Hi Ramesh,
Thank you for your reply. Basically i need to convert HL7 xml to HL7 binary with delivery channel as file. Changed the
oracle.tip.adapter.b2b.allTPInOneDirectory= True from false.
Created Internal Delievery channel with folder as c:\USLabs (USLabs is a host trading partner) on localhost.
i am placing xml file with name as USLabs_123.xml in this particular folder.
This xml file is same as a01.xml provided with HL7 sample. but i get this exception.
Protocol = File
Version = 1.0
Transport Header
filename:USLabs_123.xml
filesize:1888
file_ext:xml
fullpath:C:\USLabs\USLabs_123.xml
timestamp:2008-12-04T12:27:58.546-05:00
<?xml version="1.0" ?><ADT_A01 xmlns="http://www.edifecs.com/xdata/200 " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.3.1" CreatedDate="2005-08-16T16:52:26" CreatedBy="ECXEngine_826" GUID="{1A2726C6-B00E-DA11-8F7A-080020C8D296}"><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>#Property(MessageSendingApp)#</HD.1></MSH.3><MSH.4><HD.1>#Property(MessageSendingFacility)#</HD.1></MSH.4><MSH.5><HD.1>#Property(MessageReceivingApp)#</HD.1></MSH.5><MSH.6><HD.1>#Property(MessageReceivingFacility)#</HD.1></MSH.6><MSH.7><TS.1>20050804162010</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>ADT</MSG.1><MSG.2>A01</MSG.2></MSH.9><MSH.10>#ControlNumber#</MSH.10><MSH.11><PT.1>#Property(ProcessingID)#</PT.1></MSH.11><MSH.12><VID.1>2.3.1</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13><MSH.14 xsi:nil="true"></MSH.14><MSH.15>AL</MSH.15><MSH.16>ER</MSH.16><MSH.17>#Property(CountryCode)#</MSH.17><MSH.18>ASCII</MSH.18><MSH.19><CE.1>ENG</CE.1></MSH.19></MSH><PID><PID.1>1</PID.1><PID.2 xsi:nil="true"></PID.2><PID.3><CX.1>A0000010</CX.1></PID.3><PID.4 xsi:nil="true"></PID.4><PID.5><XPN.1><FN.1>Miranda Charles 01_10</FN.1></XPN.1></PID.5><PID.6 xsi:nil="true"></PID.6><PID.7><TS.1>20001001</TS.1></PID.7><PID.8>F</PID.8></PID><PV1><PV1.1>1</PV1.1><PV1.2 xsi:nil="true"></PV1.2><PV1.3 xsi:nil="true"></PV1.3><PV1.4 xsi:nil="true"></PV1.4><PV1.5 xsi:nil="true"></PV1.5><PV1.6 xsi:nil="true"></PV1.6><PV1.7 xsi:nil="true"></PV1.7><PV1.8 xsi:nil="true"></PV1.8><PV1.9 xsi:nil="true"></PV1.9><PV1.10 xsi:nil="true"></PV1.10><PV1.11 xsi:nil="true"></PV1.11><PV1.12 xsi:nil="true"></PV1.12><PV1.13 xsi:nil="true"></PV1.13><PV1.14 xsi:nil="true"></PV1.14><PV1.15 xsi:nil="true"></PV1.15><PV1.16 xsi:nil="true"></PV1.16><PV1.17 xsi:nil="true"></PV1.17><PV1.18 xsi:nil="true"></PV1.18><PV1.19><CX.1>10010</CX.1></PV1.19></PV1></ADT_A01>
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS enter
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS checking header names
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filename
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filesize
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =file_ext
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =fullpath
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =timestamp
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS exit
2008.12.05 at 06:03:28:046: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2008.12.05 at 06:03:28:109: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2008.12.05 at 06:03:28:109: Thread-17: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
2008.12.05 at 06:03:28:125: Thread-17: B2B - (DEBUG) DBContext commit: Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.05 at 06:03:28:125: Thread-16: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2008.12.05 at 06:03:28:125: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2008.12.05 at 06:03:28:125: Thread-16: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpack:Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@7f8922
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) MimePackaging:unpack:Exit
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {File}
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = USLabs_123.xml
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage File TP Host name = USLabs
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: USLabs Type: null Value: null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = USLabs
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: USLabs Type: null Value: null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2008.12.05 at 06:03:28:171: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2008.12.05 at 06:03:28:187: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:identifyIncomingDocument Enter
2008.12.05 at 06:03:28:187: Thread-16: B2B - (WARNING) checkForEB:Does not end with EB. Appending EB to payload
2008.12.05 at 06:03:28:234: Thread-17: B2B - (DEBUG) DBContext commit: Transaction.commit()
2008.12.05 at 06:03:28:234: Thread-17: B2B - (DEBUG) DBContext commit: Leave
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl Enter
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl document params = null
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:isValidateEnvelope oracle.tip.adapter.b2b.hl7.ignoreValidation set to ALL
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl validateEnvelope = false
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:HL7SelectorImpl Leave
2008.12.05 at 06:03:28:406: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:cloneSelector Enter
2008.12.05 at 06:03:28:421: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.hl7.HL7SelectorImpl@1e1ec86
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
2008.12.05 at 06:03:31:046: Thread-16: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
 at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
 at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
 at oracle.tip.adapter.b2b.document.hl7.HL7DocumentPlugin.identifyIncomingDocument(HL7DocumentPlugin.java:328)
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3024)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
*2008.12.05 at 06:03:31:046: Thread-16: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error*
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3043)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=USLabs_123.xml, filesize=1888, file_ext=xml, fullpath=C:\USLabs\USLabs_123.xml, timestamp=2008-12-04T12:27:58.546-05:00}
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2008.12.05 at 06:03:31:046: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2008.12.05 at 06:03:31:062: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2008.12.05 at 06:03:31:078: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2008.12.05 at 06:03:31:093: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = USLabs_123.xml@C0A8006411E06D104AB0000013426420
2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) Engine:notifyApp Enter
2008.12.05 at 06:03:31:109: Thread-16: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>C0A8006411E06D1048C0000013426410</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (xpone)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
 at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3043)
 at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
 at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
 at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
 at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
 at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
 at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
 at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Please help.
Thanks

Runtime Error-Description of Exception in Moni with Checked Flag

Hi Floks,
I am working on one interface ABAP proxy to File.While Executing the interface i am getting checked Flag in the Moni but when i double clicked on it.Its Displaying an error message.The error message is displaying like *Runtime Error-Description of Exception*
*Under that the Short text is The Current application Triggered a termination with a Short Dump*.But I am getting the proper Out put.
Please do needfull help on this.
Regards,
sai

Hi,
In error analysis iam getting this can u
Error analysis
    Short text of error message:
    Control Framework : Error processing control
    Long text of error message:
     Diagnosis
         An error occurred when the system tried to process the comma
         from the Automation Queue on the presentation server.
         There are several possible reasons for this:
         - The installation of the SAP GUI on the presentation server
         faulty or obsolete.
         - There is an error in the application program
         - There is an error in the SAPGUI or an integrated control
     Procedure
         1. Make sure that you have imported the appropriate Support
         Package, the current kernel, and GUI patch for the release o
         system
         2. Check whether the error occurs locally on one or a few PC
         generally on all PCs. Note whether the error only occurs for
         users, for example because of a specific Customizing setting
         If it only occurs locally, this suggests an installation pro
         with the PC. Check the installation; if necessary, reinstall
         software. In the dump, search for the SY-MSGLI field, since
         point to the cause of the error.
         3. Activate the Automation Trace (in accordance with SAP Not
         158985).
         4.Start the transaction and continue until the screen immedi
         before the dump.
         5. From the System -> Utilities menu, choose Autom. Queue,
                  Synchronous Processing.
         The status bar of the GUI displays the text:
            "Automation synchron flush mode on"
         6. If you now proceed with the application, the short dump will
         display the ABAP call that caused the error; the Automation Trace
         will contain the error on the presentation server.
         7. If necessary, load the short dump and trace files on to
         sapservX, so that SAP can analyze them.
    Technical information about the message:
    Message class....... "CNDP"
    Number.............. 006
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
this message i am getting so can u plazzzzz

WLS 10.3.3 (OSB) Exception faced : General runtime error: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.

Similar Messages

Maybe you are looking for