Exception occurs when accessing KM Content

Hi,
In our Portal system on NW 7.31.
While accessing any files under KM content, i get the following error
Runtime Error
An exception occured while processing the request.
Additional information: Exception during PageProcessorComponent.doContent()
Exception ID = a0fbde08-e68c-3110-0a99-a3bbe0cd7d4e
In the Default trace:
Caused by: com.sapportals.wdf.WdfError: com.sapportals.wdf.WdfException: org.xml.sax.SAXNotRecognizedException: Feature 'http://inqmy.org/sax/features/read-dtd' is not recognized.
I checked the note 1866966.
Our KM-BC component is at SP08 Patch 01, but the note recommends to be on Patch 02.
Now, we have the same KM-BC patch level in Sandbox and Development, but i dont get any error in Sandbox system. So this doesn't make a strong case to increase the patch level.
Please help me solve this issue and let me know if you need more information.
Thanks
Nanda

Hello Nanda,
It seems you've already found the solution to this issue yourself in note 1866966. Despite it not occuring in your sandbox system this is the only solution available for this issue. This issue is known to not always occur, I've seen in the past where some never encounter it, the note itself even hints at this: "If You try to navigate in the KM User Interface or in the KM Configuration You
might receive a Portal Runtime Error". It's impossible to define the exact set of circumstances why this might occur in one system and not in another, it would also be an extremely time consuming possibly fruitless task to try and compare both system to make sure there are no minor differences which could influence this behaviour.
I'm however confident that it would be resolved with KMC-BC SP8 Patch 2, you should apply this across all your systems to avoid it possibly coming up again in the future.
Kind regards,
Lorcan.

Similar Messages

Portal Runtime error - An exception occured : when accessing the SRM Portal

Dear Consultants,
We are logging onto the SRM Portal using url link. SAP Netweaver 7.0
But when we are trying to access any tabs in the Navigation frame of the portal it is throwing an error.
Error - Portal Runtime error
An exception has occured while processing your request.
Can you please let me know how can I find the correct reason for the error.
regards
Arindam

Hi Arindam,
Pls check Default Trace log in the NWA tool, path would be NWA --> Monitoring --> Logs and Traces --> Select Default Trace.
Find the log messages with the Exception ID found on your Portal Runtime error. These logs would specify the exact cause of error.
Thanks,
Swapna Priya.

Runtime Error when accessing KM Content

Hi Everyone,
I am getting Runtime Error when accessing KM Content through Content Administration/KM Content.
See the below error information.
Runtime Error
An exception occured while processing the request.
Additional information: String index out of range: -28
Exception ID = 00a67a58-06f5-2b10-b997-9edccc061ca6
What could be the problem.
Any help will be appreciated.
thank you
regards
sunil

hi Romano
Here is the log trace file text.
#1.5#001321C84B3300A304DC7AFD00001D50000465605028DB15#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651182th#
#1.5#001321C84B3300A304DC7AFF00001D50000465605028DBEB#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0100001D50000465605028DCB3#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B0200001D50000465605028DE21#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B0400001D50000465605028DF04#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651183th#
#1.5#001321C84B3300A304DC7B0600001D50000465605028DFDA#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0800001D50000465605028E0A1#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B0900001D50000465605028E1FE#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B0B00001D50000465605028E2DF#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651184th#
#1.5#001321C84B3300A304DC7B0D00001D50000465605028E3B5#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B0F00001D50000465605028E473#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B1000001D50000465605028E5D8#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B1200001D50000465605028E6B9#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651185th#
#1.5#001321C84B3300A304DC7B1400001D50000465605028E798#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
#1.5#001321C84B3300A304DC7B1600001D50000465605028E856#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java###CBS Instance pulse thread will try to recover#1#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#
#1.5#001321C84B3300A304DC7B1700001D50000465605028E9AD#1237364243036#com.sap.tc.cbs.server.rt.impl.CourteousTimer##com.sap.tc.cbs.server.rt.impl.CourteousTimer######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error##Java###A problem during RUN
[EXCEPTION]
#1#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.
     at com.sap.tc.cbs.server.rt.impl.Pulsar.beforeExecution(Pulsar.java:86)
     at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:116)
     at java.lang.Thread.run(Thread.java:534)
#1.5#001321C84B3300A304DC7B1900001D50000465605028EAA5#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces a problem time in sequence#2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#11651186th#
#1.5#001321C84B3300A304DC7B1B00001D50000465605028EB87#1237364243036#com.sap.tc.cbs.server.rt.impl.Pulsar##com.sap.tc.cbs.server.rt.impl.Pulsar######6575e170137111de9951001321c84b33#Thread[CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/Applications/CBS/Administration#Java### faces the following problem: #2#CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33#java.lang.IllegalStateException: CBS-Pulsar 12432550/ad9cf170-12e8-11de-99b2-001321c84b33 did not confirm instance activity for more than 180 sec.#
regards
sunil

Runtime error SQL error 3114 occurred when accessing program CX_ w

Hi Friends,
Iam in a big mess . I have one query based on one my Zinfocube.This query ia attached in the workbook .. Previuolsy all was fine , but now whever iam executing this query it is throwing me the exception
Query 0: Runtime error SQL error 3114 occurred when accessing program CX_ with parallel processing via RFC.
and
Beim Lesen der Daten sind Fehler aufgetreten. Navigation ist mÃ¶glich
I am not able to get the cause of error ..
Can anybody help me in this regrd as its a bit urgent.
Thanks in advance..

Hi , thanks for replying ,
I have tried running query through RSRT also , its not working still it is giving me the same error .
In st22 it is showing me the follwing dump.
DBIF_REPO_SQL_ERROR
Short text
    SQL error 3114 occurred when accessing program
What happened?
    The system is no longer linked to an ORACLE instance.
    No further operations can be performed on the database.
What can you do?
    You cannot eliminate this error yourself.
    Please inform your database administrator.
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    The system attempted to access an ORACLE instance to which
    it is no longer linked.
    This situation may arise because the ORACLE instance
    has been stopped due to an error or an external operation.
How to correct the error
    Database error text........: "ORA-03114: not connected to ORACLE"
    Triggering SQL statement...: "CX_SQL_EXCEPTION==============CP "
    The current status of the ORACLE instance cannot be determined.
    It may be still inactive or the database administrator may have
    restarted it.
    In any case, all systems that have accessed the ORACLE instance
    must be restarted after the ORACLE instance has been restarted.
    If you were working on a central system, inform
    your system administrator.
    If you were working on an external local system, inform
    the person responsible for this system.
    If you were working on your own local system, restart
    the system yourself.
    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:
    "DBIF_REPO_SQL_ERROR" " "
    "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
    "NEXT_PACKAGE"
    If you cannot solve the problem yourself and want to send an errornotification 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.
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:
"DBIF_REPO_SQL_ERROR" " "
"CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
"NEXT_PACKAGE"
Thanks in Advance..

An error occurred while accessing the content repository from JDeveloper

Hello,
I'm using Jdeveloper Studio Edition Version 11.1.1.5.0
I created Content Repository conection, following:
RIDC Socket Type: socket
Server hostname: localhost
Content Server Listener Port: 4444
Executing "Teste Connection" result "Success!"
But, trying connect, I receive:
oracle.webcenter.content.internal.model.rc.AbstractRepositoryLogic listFolder
An error occurred while accessing the content repository.
and when I login to my portal and go to administration page, then I am getting this error
"Messages for this page are listed below.
Could not retrieve members from policy store.
and when I go to services tab then i am getting this error "The Documents service is unavailable.
Error contacting the content repository."
Please help me to resolve this problem.
Thank You,
Muhammad Nasir

can anybody help me to resolve this issue please.

Transformer exception occurred when executing XSLT

Hi Friends,
Currently I am working on standard contents(XI) on IS-Retail.
I want to change standard XSLT mapping.
I done few changes but on testing of Interface mapping I got this error "Transformer exception occurred when executing XSLT"
1.
</xsl:template>
     
     
     <xsl:template name="POSLog">
          <ns0:Z_POSLog xmlns:ns0="http://sap.com/xi/StoreConnectivity">
               <xsl:call-template name="POSLogTransaction"/>
          </ns0:Z_POSLog>
          </xsl:template>
          
2.
               
                    <xsl:for-each select="GMTLogTransactionLine[TransactionType='B2']">
                         <xsl:call-template name="CaptureTenderID"/>
                    </xsl:for-each>
               
3.
     
     <xsl:template name="CaptureTenderID">
          <xsl:if test="following-sibling::GMTLogTransactionLine[1][TransactionType='B2']">
               <Tender>
                    <TenderID>
                         <xsl:value-of select="following-sibling::GMTLogTransactionLine[TransactionType='B2'][1]/TenderID"/>
                    </TenderID>
               </Tender>
          </xsl:if>
     </xsl:template>
     

Hello flok,
just have a look into this thread may be you can find the solution
XSLT Mapping, Transformer configuration exception occurred when loading
http://xml.apache.org/xalan-j/apidocs/javax/xml/transform/TransformerException.html
Regards,
Ravi.

Cfobject - An exception occurred when instantiating a COM object

I'm getting the following error:
An exception occurred when instantiating a COM object.
The cause of this exception was that: java.lang.RuntimeException: Can not use native code: Initialisation failed.
1 :
2 : <cfscript>
3 :     oLoader = CreateObject("com", "easyPDF.Loader.6");
4 : </cfscript>
This is on a dedicated server with 64bit Windows Server 8 and 64bit ColdFusion 9. easyPDF is a program that will convert files into PDF on the server, it is also the 64 bit version.
I'm not even trying to do anything but load the object and am getting the error. I took a peek inside the registry and searched for "easyPDF.Loader" and it was found.
Any ideas what could be going wrong? Is there something I need to do with the CF setup or IIS to get this working? It gives the same error with the following line of code as well.
<cftry>
    <cfobject type="com" action="connect" class="Word.application" name="this.wordCom" context="local">
    <cfcatch>
        <cfobject type="com" action="create" class="Word.application" name="this.wordCom" context="local">
    </cfcatch>
</cftry>
Any help or guidance would be great. Is there a basic <cfobject type="com"> that should work on ANY computer without installing something that I could use to test?
Thanks!

Just to give everyone some closure in this matter:
I've opened a case with Adobe Support. Their reply was:
COM interoperability with CF9 is not supported on 64 bit Windows OS. This is due to the limitations imposed by JIntergra. You can find a reference for this in the following tech-note:http://helpx.adobe.com/coldfusion/kb/coldfusion-limitations-running-coldfusion-64.html
It seems that J-Integra (http://j-integra.intrinsyc.com/support/kb/article.aspx?id=30963) won't update their code libraries for 64-bit support due to lack of customer demand for this functionality. Mind you this is the newest technot I could find on the matter but it was last update in 2010. I've also emailed j-Integra sales (http://j-integra.intrinsyc.com/contact.asp) to inquire about any progress in porting over their libraries to 64-bit. Who knows, if they get enough requests...
I will now try to access my COM libraries from a .NET dll and call it using cfexecute.

Error message: An error occurred when loading the content. Please try again later

Why do some radios do not work on the Apple TV as iTunes, there is no problem ...?
Error message: An error occurred when loading the content. Please try again later
Thanks

Having this problem today. You Tube and other internet parts of the apple tv works. I just can't access my iTunes tv shows.

An exception occurred when instantiating a COM object

I have installed ColdFusion 9.1 on a 64-bit server running Windows 2008 R2. I am using IIS 7.5.
When I try to access the following URL http://localhost/myhousing/security/login_admin.cfm I get the following error. Is there a patch available for CF 9 to resolve this error?
The web site you are accessing has experienced an unexpected error.
Please contact the website administrator.
The following information is meant for the website developer for debugging purposes.
Error Occurred While Processing Request
An exception occurred when instantiating a COM object.
The cause of this exception was that: java.lang.RuntimeException: Can not use native code: Initialisation failed.
The error occurred in C:/inetpub/wwwroot/MyHousing/Application.cfm: line 22
20 : <CFINCLUDE template="lib/housing_functions.cfm">
21 : <CFSET Application.obj_name = "UserInfo325DLL.UserClass">
22 : <CFOBJECT name="obj" action="create" type="com" class="#Application.obj_name#">
23 : 
24 : 
Resources:
Check the ColdFusion documentation to verify that you are using the correct syntax.
Search the Knowledge Base to find a solution to your problem.
Browser   Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Remote Address   ::1
Referrer
Date/Time   08-May-13 01:49 PM
Stack Trace (click to expand)
at cfApplication2ecfm293894775.runPage(C:/inetpub/wwwroot/MyHousing/Application.cfm:22) at cfApplication2ecfm293894775.runPage(C:/inetpub/wwwroot/MyHousing/Application.cfm:22)
java.lang.RuntimeException: Can not use native code: Initialisation failed
at com.linar.jintegra.NativeObjRef.<init>(Unknown Source)
at com.linar.jintegra.Dispatch.createDispatch(Unknown Source)
at com.linar.jintegra.Dispatch.<init>(Unknown Source)
at com.intrinsyc.typeInfo.IMacroViewerProxy.<init>(IMacroViewerProxy.java:32)
at com.intrinsyc.typeInfo.MacroViewer.<init>(MacroViewer.java:90)
at com.intrinsyc.typeInfo.MacroViewer.<init>(MacroViewer.java:69)
at com.intrinsyc.typeInfo.InterfaceInfoFactory.getInfoGivenPROGID(InterfaceInfoFactory.java: 50)
at coldfusion.runtime.com.ComProxy.<init>(ComProxy.java:114)
at coldfusion.runtime.com.ComProxyFactory.getProxy(ComProxyFactory.java:41)
at coldfusion.runtime.ProxyFactory.getProxy(ProxyFactory.java:65)
at coldfusion.runtime.CFPage.createObjectProxy(CFPage.java:4947)
at coldfusion.tagext.lang.ObjectTag.doStartTag(ObjectTag.java:427)
at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2722)
at cfApplication2ecfm293894775.runPage(C:\inetpub\wwwroot\MyHousing\Application.cfm:22)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:231)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:416)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.CfincludeFilter.include(CfincludeFilter.java:33)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:279)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:48)
at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:94)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:70)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:46)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62)
at coldfusion.CfmServlet.service(CfmServlet.java:200)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:86)
at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 )
at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46)
at jrun.servlet.FilterChain.doFilter(FilterChain.java:94)
at jrun.servlet.FilterChain.service(FilterChain.java:101)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:106)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:286)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:543)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:203)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:320)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:266)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)

Let's narrow down the problem by substituting the variable with the value directly on the cfobject tag.
<CFOBJECT name="obj" action="create" type="com" class="UserInfo325DLL.UserClass">
... and see if that works.
Another thing you might want to check if this is correct, UserInfo325DLL.UserClass.

Error message in TRFC 'An SQL error occurred when accessing a table'

Hi all,
Can any one tell what this below error message is about in while go into TRFC
'An SQL error occurred when accessing a table'.
and please tell me how to solve this problem.

Hi
Try to see what all tables are accessed by data source. and see if there is any lock on that..
If some other job is accessing that table - then there might be lock on that which is causing failure..
1) Try looking at ST22 dump also..
2) Try to do RSA3 in R/3 and if see if its is fetching any records or not..
Hoep it helps
--SA

Orchestration exception:Exception occurred when persisting state to the database because of special character ' ' in HL7 message.

In some scenarios HL7 message is coming with special character ‘’ and HL7 dis-assembler escaping this character with “”. But while sending out (pass thru pipeline but orchestration trying to persist here at last sendshape.) from orchestration
this message failing with the error “Exception occurred when persisting state to the database.”
As per the analysis , Orchestration is unable to convert to xml document from a
XLANGMessage because of this special character. We have tried to call custom .net class with following code and its failing here as well (I think orchestration also trying to do same way and failing with the message and failing with same error.).
public void ProcessRequest(XLANGMessage reqMessage)
XmlDocument xmlDocument = (XmlDocument)reqMessage[0].RetrieveAs(typeof(XmlDocument)); It is failing here with the error
“ ', hexadecimal value 0x10, is an invalid character. Line 1, position 1865. “
Note : Please find the special character in the attachment circled in red color.

Hi ,
Please find the xml and the screenshot.
<OBX_ObservationResult>
<OBX_1_SetIdObx>3</OBX_1_SetIdObx>
<OBX_2_ValueType>TX</OBX_2_ValueType>
<OBX_3_ObservationIdentifier>
<CE_0_Identifier>P.112</CE_0_Identifier>
<CE_1_Text>Where pt. will be transported to \T\ where famly can wait:</CE_1_Text>
</OBX_3_ObservationIdentifier>
<OBX_4_ObservationSubId />
<OBX_5_ObservationValue>Y</OBX_5_ObservationValue>
<OBX_6_Units>
<CE_0_Identifier />
</OBX_6_Units>
<OBX_7_ReferencesRange />
<OBX_8_AbnormalFlags />
<OBX_9_Probability />
<OBX_10_NatureOfAbnormalTest />
<OBX_11_ObservationResultStatus>N</OBX_11_ObservationResultStatus>
</OBX_ObservationResult>

XSLT Mapping, Transformer configuration exception occurred when loading

Hi,
My source message is an IDOC HRMD, I need my target message to include exactly
<EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
I have therefore suggested to use XSLT mapping.
Here is the test_mapping.xsl that I Imported as Zip in Imported Archives.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://polyright.com/xi/HR">
     <xsl:template match="/">
          <EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
                      <xsl:for-each select="HRMD_A07/IDOC/E1PLOGI">
            <CONTEXTPERSON personid="" id="">
                  <PERSON action="add">
                           <TITLE></TITLE>
                           <FIRSTNAME><xsl:value-of select="E1PITYP/E1P0002/VORNA"/></FIRSTNAME>
                           <SECONDNAME></SECONDNAME>
                           <NAME><xsl:value-of select="E1PITYP/E1P0002/NACHN"/></NAME>
                           <ADDRESS1></ADDRESS1>
                           <ADDRESS2></ADDRESS2>
                           <POSTALCODE></POSTALCODE>
                           <CITY></CITY>
                           <COUNTRY></COUNTRY>
                           <COUNTRYID></COUNTRYID>
                           <PROFESSION></PROFESSION>
                           <LANGUAGE></LANGUAGE>
                           <LANGUAGEID></LANGUAGEID>
                           <PERSONTYPEID></PERSONTYPEID>
                           <CREATIONDATE></CREATIONDATE>
                           <BIRTHDATE></BIRTHDATE>
                           <CATEGORY></CATEGORY>
                         </PERSON>
                  </xsl:for-each>
          </EPERSON>
     </xsl:template>
</xsl:stylesheet>
When I test the Interface mapping, I get the following error:
Transformer configuration exception occurred when loading XSLT test_mapping.xsl (http://polyright.com/xi/HR, 783938d1-4463-11dd-b136-e03ac0a80c15, -1)
Searching through the forum, it is probably an namespace issue, but I have no idea of what needs to be changed. Any suggestions ?

Try running end-to-end scenario and check if you could get detailed error message.
Also check if the problem arises from the "ns0" usage.
Regards,
Prateek

SQL Error 3114 occured when accessing program CX_

Hi there,
I have build an infoset on a infocube and ODS. On this infoset I've build a query using a calculated key figure: Availibility%
Inside this key figure I have 2 restricted key figures: Allocation and Availibility
When I execute this query I get the error: "SQL Error 3114 occured when accessing program CX_"
If I remove the calculated key figure from the columns it works fine. If I place one of the 2 restricted key figures in the query it also work fine. But If i place both the restricted key figures in the columns, I also get the error. Or If I place the calculated key figure in the columns, I also get the error. Does somebody know what the problem is?

No they don't show me the problem. I've executed with RSRT transaction and I;ve got this error with the ABAP-debugger:
error in >> l_repid       <<
            >> l_include     <<
            >> l_source_line <<

An Exception Occured when refershing the query

Hello All,
Below exception occured for the following two scenarios.
It occured when i tried to refresh the query.
Other Case, exception occured when i enter the user prompts , it was about to refresh and got the same error messageNeed to know, when this type of error message occurs generally " An exception occured in one of the data source " and " Nested Exception".Need your inputs.
Thanks in advance.
John

We are using AO 1.4 SP5..
I have don't have the hotfix whether hotfix has been installed or not.
Regards,
John

IC WC: Exception occured when combine with Custom Controller

Hi All,
I was trying to combine a context node in my application to the context node "CurrentContext" of custom contrroler CuCoBDC.do however the following exception occured when I tried to display the page: "BSP exception: The object CuCoBDC.do in the URL /sap(bD1lbiZjPTAwMQ==)/bc/bsp/sap/crm_ic_preview/root.do is not valid."
Can anyone please give me some hints?
Thank you
Heather

Hi heather,
can you please check the BOL entity used for both custom controller and view contex nodes are the same!.
also do check the binding code in the method create_context_node( ) in _CTXT class of the view!.
Regards,
sudeep.

Exception occurs when accessing KM Content

Similar Messages

Maybe you are looking for