Code Page Repository Service
I installed Informatica on Linux Cent OS Successfully, but when I am trying to create repository service its giving error of code page incompatibility.
My database code page is AL32UTF8.
So what code page should i select for repository service,it should be subset I don't know which one.
Please help
thanks
I found the solution online,
it is ISO 8859-1 Western European
Similar Messages
-
Service process is running in code page [MS Windows Latin 1 (ANSI), superse
All,
I am trying to create Integration service, getting errors on Windows.
Can anyone tell me where exactly where the service process is pulling the Latin 1(Ansi) settings from.
I am stuck on this setup.
regards
girishyou first create the Informatica repository and then you have to select it for integration services, therefore the properties of integration services such as a code page are controlled by repository 's properties.
If you follow all the steps from this guide, informatica will configure fine. -
Can some one help me out here ?
Hello Experts, Am facing the below error in console page.Can someone help out here ? The following error occurred while performing a repository action. Error - [PCSF_10007] Cannot connect to repository [dev_repo] because \n[[REP_61082] AdminConsole's code page (UTF-8 encoding of Unicode) is not one-way compatible to repository dev_repo's code page (MS Windows Latin 1 (ANSI), superset of Latin1). Failed to connect to repository service [dev_repo].]. Below my environment variables in .bash_profile LANG=en_US.utf8; export LANGLC_ALL=en_US.utf8; export LC_ALLINFA_CODEPAGENAME=UTF-8; export INFA_CODEPAGENAME Thanks,Ahmed.
-
Here is a ticket regarding our current client web application ( Image data add, edit , delete in folder with form data in MSSQL Database) that using code c#, web form, ajax, VS2008, MSSQL Server2008 , it appears that there is an error where the HTTP
503 error occurs.
. Below is a conversation with Host Server support assistant.Can you take a look at it?
Ben (support) - Hi
Customer - We're having an issue with our windows host
Ben (support) - What's the issue?
Customer - 503 errors
Ben (support) - I am not getting any 503 errors on your site, is there a specific url to duplicate the error?
Customer - no, it comes and goes without any change Customer - could you have access to any logs ?
Ben (support) - Error logs are only available on Linux shared hosting, however with this error it may be related to you reaching your concurrent connections
Ben (support) - You can review more about this at the link \
Customer - probably yes - how can we troubleshoot ?
Ben (support) - http://support.godaddy.com/help/article/3206/how-many-visitors-can-view-my-site-at-once
Ben (support) - This is something you need to review your code and databases to make sure they are closing the connections in a timely manner
Customer - we're low traffic, this is an image DB to show our product details to our customers
Customer - ahhhh, so we could have straying sessions ?
Ben (support) - Correct Customer - any way you could check if it's the case ?
Customer - because it was working previously
Ben (support) - We already know that's the case as you stated the 503 errors don't happen all the time if it were issue on the server the the 503 would stay.
Customer - so our 2/3 max concurrent users can max out the 200 sessions
Customer - correct ?
Customer - is there a timeout ?
Ben (support) - no that's not a time out concurrent connections are a little different then sessions and or connections. Lets say for an example you have 5 images on your site and 5 7 users come to your site this is not 7 concurrent connections but 35. They
do close after awhile hence why the 503 error comes and goes. You can have these connections close sooner using code but this is something you have to research using your favorite search engine
Customer - thank you so much
Customer - I'm surprised that this just started a few weeks ago when we haven't changed anything for months
Customer - any changes from your side ? lowering of the value maybe ?
Customer - I'm trying to understand what I can report as a significant change
Ben (support) - We haven't touched that limit in years
Ben (support) - This could just be more users to your site than normal or even more images
Customer - I was thinking that could be it indeed
Customer - so I need to research how to quickly close connections when not needed
Ben (support) - Correctly
Ben (support) - correct
Customer - thanks !!
Ben (support) - Your welcome
Analysis :
The link provided tells us : All Plesk accounts are limited to 200 simultaneous visitors.
From what Ben (support) says and a little extra research, if those aren't visitors but connections then it's quite easy to max out, especially if the connections aren't closed when finished using. I'd suggest forwarding this to Kasem to see what he thinks.
Cheers,
CustomerHi Md,
Thank you for posting in the MSDN forum.
>>
I want to writte C# code for 503 Service Unavailable error to web application page immediate close connection any page loaded.
Since
Visual Studio General Forum which discuss VS IDE issue, I am afraid that you post the issue in an incorrect forum.
To help you find the correct forum, would you mind letting us know more information about this issue? Which kind of web app you develop using C# language? Is it an ASP.NET Web Application?
If yes, I suggest you could post the issue directly on
ASP.NET forum, it would better support your issue.
Thanks for your understanding.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey. -
String data code page - DB2 - Data Direct - Data Services
We are trying to connect to a DB2 source (Database product = DB2 OS/390 8.1.5) using Data Direct drivers and following error is showing up when we test the connectivity.
SQLConnect: Retrying Connect.
SQLConnect: Failed...
SQLSTATE = S1000
NATIVE ERROR = 0
MSG = [SAP BusinessObjects][ODBC DB2 Wire Protocol driver]String data code page conversion failed.
Wondering if anyone has had similar issue or if someone hasany ideas regarding how this can be resolved would be great.
Thanks for the helpCheck whether the DB2CODEPAGE env variable is set in your OS.
issue the following query against your database -
select codepage from syscat.tables where datatype='varchar'
This should return the corresponding codepage value.
In windows, create a user variable (environment variable) called DB2CODEPAGE and assign the value you got from the previous query.
If it is unix, use th setenv command
setenv DB2CODEPAGE 'cp1252'
, for instance
You may have to restart the machine once the variable is defined
Regards,
Shine -
Exceptions at log file while creating a repository service
Hello,
I have implemented a repository service and set it to respond to all events. The service is writing itself at the correct repositories but doesn't respond to any event. By going over the log files I found the following logs. Can someone please tell me if he sees something that can cause this?
Devtlev: If you are reading this post (and I'm sure you will at some point... ), it is a continuation to our long long repository service post, but I thought it would be better to open new one
// Log when deployingThe Repository Service
#1.5#000BCDFB696800620000004100001A200003FAA9C0F55D3A#1120031924082#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###An upload sequence will start now. Please do not stop the server or serious deployment issues may arise.#
#1.5#000BCDFB696800620000004400001A200003FAA9C0F749B6#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upgrades of the upload sequence will start now, there are 1 upgrade(s) to perform#
#1.5#000BCDFB696800620000004500001A200003FAA9C0F74A6B#1120031924207#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Processing upgrade: 1 out of 1. Config archive: RepositoryServices.prjconfig#
#1.5#000BCDFB696800620000004600001A200003FAA9C1050406#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: active#
#1.5#000BCDFB696800620000004700001A200003FAA9C105055B#1120031925114#com.sapportals.config.fwk.util.BasicConfigurable#sap.com/irj#com.sapportals.config.fwk.util.BasicConfigurable#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning##Plain###configurable [counter.CounterService] instance of [configclass_config://install/cm/repository_services/counter.CounterService] has a property without corresponding attribute: description#
#1.5#000BCDFB696800620000004B00001A200003FAA9C22E421E#1120031944597#com.sapportals.portal.prt.service.config.UpgraderBridge#sap.com/irj#com.sapportals.portal.prt.service.config.UpgraderBridge#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###Time to import the configuration of RepositoryServices.prjconfig: 19796#
#1.5#000BCDFB696800620000004D00001A200003FAA9C22E5257#1120031944597#com.sapportals.portal.prt.service.config.ConfigDeploymentService#sap.com/irj#com.sapportals.portal.prt.service.config.ConfigDeploymentService#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Info##Plain###The upload sequence is now complete, all the upgrades have been performed.#
#1.5#000BCDFB696800620000005300001A200003FAA9C230142B#1120031944706#com.sapportals.wcm.crt.CrtClassLoaderRegistry#sap.com/irj#com.sapportals.wcm.crt.CrtClassLoaderRegistry#RoyC#6977####9d399520e87311d98513000bcdfb6968#SAPEngine_Application_Thread[impl:3]_15##0#0#Warning#1#/Applications/KMC/CRT#Plain###register new classloader with id = null#
// Log when entering the KM under Content Administration -> KM Content
#1.5#000BCDFB6968003E0000008400001A200003FAA9CD1A7029#1120032127601#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16881e10e87411d9ce5b000bcdfb6968#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800600000004F00001A200003FAA9CD2343A8#1120032128179#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16e05030e87411d9ae07000bcdfb6968#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800510000002A00001A200003FAA9CD237B8D#1120032128195#com.sapportals.wcm.repository.runtime.CmSystem#sap.com/irj#com.sapportals.wcm.repository.runtime.CmSystem#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Info#1#/Applications/KMC/RF#Plain###CM system is starting ...
#1.5#000BCDFB6968006C0000003500001A200003FAA9CD257EF1#1120032128320#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB6968006C0000003800001A200003FAA9CD259C9B#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB6968006C0000003B00001A200003FAA9CD25AB06#1120032128335#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#RoyC#6677####16f5d400e87411d9b4b4000bcdfb6968#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##
#1.5#000BCDFB696800510000002B00001A200003FAA9CD405BCE#1120032130085#com.sapportals.wcm.protocol.webdav.UriMetaMap#sap.com/irj#com.sapportals.wcm.protocol.webdav.UriMetaMap#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Warning##Plain###replacing existing mapping WebUriMapper[/www/ep6sp9test <-> http://ep6sp9test.justice.gov.il/]#
#1.5#000BCDFB696800510000002C00001A200003FAA9CD6649D1#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB696800510000002D00001A200003FAA9CD665926#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:134)#
#1.5#000BCDFB696800510000002E00001A200003FAA9CD665A6A#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB696800510000002F00001A200003FAA9CD665BBC#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB696800510000003000001A200003FAA9CD665D8F#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB696800510000003100001A200003FAA9CD665F1D#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB696800510000003200001A200003FAA9CD666052#1120032132585#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB696800510000003300001A200003FAA9CD6661CE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB696800510000003400001A200003FAA9CD666301#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB696800510000003500001A200003FAA9CD666434#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB696800510000003600001A200003FAA9CD666569#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB696800510000003700001A200003FAA9CD666694#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB696800510000003800001A200003FAA9CD6667B1#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB696800510000003900001A200003FAA9CD666925#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB696800510000003A00001A200003FAA9CD666B06#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB696800510000003B00001A200003FAA9CD666C7B#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB696800510000003C00001A200003FAA9CD666DB2#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB696800510000003D00001A200003FAA9CD666ED3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB696800510000003E00001A200003FAA9CD666FFD#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB696800510000003F00001A200003FAA9CD667132#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB696800510000004000001A200003FAA9CD667271#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
#1.5#000BCDFB696800510000004100001A200003FAA9CD6673C7#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
#1.5#000BCDFB696800510000004200001A200003FAA9CD6674EA#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Control.create(Control.java:291)#
#1.5#000BCDFB696800510000004300001A200003FAA9CD6676AF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
#1.5#000BCDFB696800510000004400001A200003FAA9CD667867#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
#1.5#000BCDFB696800510000004500001A200003FAA9CD6679B6#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004600001A200003FAA9CD667AD3#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004700001A200003FAA9CD667BED#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004800001A200003FAA9CD667D13#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004900001A200003FAA9CD667E40#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004A00001A200003FAA9CD667F70#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000004B00001A200003FAA9CD66809D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000004C00001A200003FAA9CD66818D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
#1.5#000BCDFB696800510000004D00001A200003FAA9CD6682AB#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
#1.5#000BCDFB696800510000004E00001A200003FAA9CD66838A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
#1.5#000BCDFB696800510000004F00001A200003FAA9CD66847A#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005000001A200003FAA9CD668550#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005100001A200003FAA9CD668734#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB696800510000005200001A200003FAA9CD66889C#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
#1.5#000BCDFB696800510000005300001A200003FAA9CD6689CF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
#1.5#000BCDFB696800510000005400001A200003FAA9CD668AD8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
#1.5#000BCDFB696800510000005500001A200003FAA9CD668CAE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
#1.5#000BCDFB696800510000005600001A200003FAA9CD668E04#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
#1.5#000BCDFB696800510000005700001A200003FAA9CD668F2F#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
#1.5#000BCDFB696800510000005800001A200003FAA9CD669041#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000005900001A200003FAA9CD66921D#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
#1.5#000BCDFB696800510000005A00001A200003FAA9CD6693B8#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
#1.5#000BCDFB696800510000005B00001A200003FAA9CD669503#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
#1.5#000BCDFB696800510000005C00001A200003FAA9CD669638#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
#1.5#000BCDFB696800510000005D00001A200003FAA9CD669776#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
#1.5#000BCDFB696800510000005E00001A200003FAA9CD6698AE#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB696800510000005F00001A200003FAA9CD6699DF#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB696800510000006000001A200003FAA9CD669B11#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB696800510000006100001A200003FAA9CD669C39#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5#000BCDFB696800510000006200001A200003FAA9CD669D73#1120032132600#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
#1.5#000BCDFB696800510000006300001A200003FAA9CD669F50#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB696800510000006400001A200003FAA9CD66A0F4#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB696800510000006500001A200003FAA9CD66A240#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB696800510000006600001A200003FAA9CD66A362#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
#1.5#000BCDFB696800510000006700001A200003FAA9CD66A47E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
#1.5#000BCDFB696800510000006800001A200003FAA9CD66A5BC#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
#1.5#000BCDFB696800510000006900001A200003FAA9CD66A6E2#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB696800510000006A00001A200003FAA9CD66A82E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#000BCDFB696800510000006B00001A200003FAA9CD66A958#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000006C00001A200003FAA9CD66AA75#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
#1.5#000BCDFB696800510000006D00001A200003FAA9CD66AC60#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB696800510000006E00001A200003FAA9CD66ADF1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
#1.5#000BCDFB696800510000006F00001A200003FAA9CD66AF30#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
#1.5#000BCDFB696800510000007000001A200003FAA9CD66B04D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
#1.5#000BCDFB696800510000007100001A200003FAA9CD66B166#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
#1.5#000BCDFB696800510000007200001A200003FAA9CD66B29B#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
#1.5#000BCDFB696800510000007300001A200003FAA9CD66B3C6#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
#1.5#000BCDFB696800510000007400001A200003FAA9CD66B4FD#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#000BCDFB696800510000007500001A200003FAA9CD66B626#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#000BCDFB696800510000007600001A200003FAA9CD66B740#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
#1.5#000BCDFB696800510000007700001A200003FAA9CD66B930#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
#1.5#000BCDFB696800510000007800001A200003FAA9CD66BAE7#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#000BCDFB696800510000007900001A200003FAA9CD66BC1A#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB696800510000007A00001A200003FAA9CD66BD2E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
#1.5#000BCDFB696800510000007B00001A200003FAA9CD66BE38#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
#1.5#000BCDFB696800510000007C00001A200003FAA9CD66BF5C#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
caused by -
#1.5#000BCDFB696800510000007D00001A200003FAA9CD66C07D#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB696800510000007E00001A200003FAA9CD66D01F#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
#1.5#000BCDFB696800510000007F00001A200003FAA9CD66D1FB#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
#1.5#000BCDFB696800510000008000001A200003FAA9CD66D3C0#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
#1.5#000BCDFB696800510000008100001A200003FAA9CD66D517#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB696800510000008200001A200003FAA9CD66D633#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB696800510000008300001A200003FAA9CD66D742#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB696800510000008400001A200003FAA9CD66D86E#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB696800510000008500001A200003FAA9CD66D9A1#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB696800510000008600001A200003FAA9CD66DB03#1120032132616#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB696800510000008700001A200003FAA9CD66DC3B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB696800510000008800001A200003FAA9CD66DD5A#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB696800510000008900001A200003FAA9CD66DECD#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB696800510000008A00001A200003FAA9CD66E096#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB696800510000008B00001A200003FAA9CD66E20E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB696800510000008C00001A200003FAA9CD66E33B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB696800510000008D00001A200003FAA9CD66E464#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB696800510000008E00001A200003FAA9CD66E57D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB696800510000008F00001A200003FAA9CD66E6B8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB696800510000009000001A200003FAA9CD66E7F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB696800510000009100001A200003FAA9CD66E92F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB696800510000009200001A200003FAA9CD66EA5C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB696800510000009300001A200003FAA9CD66EDA0#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.prepareNestedControls(WdfProxy.java:1302)#
#1.5#000BCDFB696800510000009400001A200003FAA9CD66EF2B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createNestedControls(WdfProxy.java:1209)#
#1.5#000BCDFB696800510000009500001A200003FAA9CD66F066#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Control.create(Control.java:291)#
#1.5#000BCDFB696800510000009600001A200003FAA9CD66F186#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.create(WdfProxy.java:1280)#
#1.5#000BCDFB696800510000009700001A200003FAA9CD66F29B#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:464)#
#1.5#000BCDFB696800510000009800001A200003FAA9CD66F3D4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009900001A200003FAA9CD66F4FC#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009A00001A200003FAA9CD66F62F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009B00001A200003FAA9CD66F72E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009C00001A200003FAA9CD66F843#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009D00001A200003FAA9CD66F92E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.Pane.createControls(Pane.java:458)#
#1.5#000BCDFB696800510000009E00001A200003FAA9CD66F9F7#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.stack.PaneStack.createControls(PaneStack.java:479)#
#1.5#000BCDFB696800510000009F00001A200003FAA9CD66FABF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.doInitialization(WdfCompositeController.java:268)#
#1.5#000BCDFB69680051000000A000001A200003FAA9CD66FC22#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:659)#
#1.5#000BCDFB69680051000000A100001A200003FAA9CD66FDDF#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:32)#
#1.5#000BCDFB69680051000000A200001A200003FAA9CD66FF3C#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A300001A200003FAA9CD670042#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A400001A200003FAA9CD670207#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.Container.preRender(Container.java:118)#
#1.5#000BCDFB69680051000000A500001A200003FAA9CD670360#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.rendering.PageContext.render(PageContext.java:936)#
#1.5#000BCDFB69680051000000A600001A200003FAA9CD670467#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)#
#1.5#000BCDFB69680051000000A700001A200003FAA9CD670558#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)#
#1.5#000BCDFB69680051000000A800001A200003FAA9CD67063E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)#
#1.5#000BCDFB69680051000000A900001A200003FAA9CD67071D#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.htmlb.page.PageProcessorServlet.doGet(PageProcessorServlet.java:29)#
#1.5#000BCDFB69680051000000AA00001A200003FAA9CD6707FB#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
#1.5#000BCDFB69680051000000AB00001A200003FAA9CD6708D6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000AC00001A200003FAA9CD6709AA#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.app.servlet.WcmHtmlbBaseServlet.service(WcmHtmlbBaseServlet.java:100)#
#1.5#000BCDFB69680051000000AD00001A200003FAA9CD670AC3#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:321)#
#1.5#000BCDFB69680051000000AE00001A200003FAA9CD670BE6#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)#
#1.5#000BCDFB69680051000000AF00001A200003FAA9CD670D10#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#
#1.5#000BCDFB69680051000000B000001A200003FAA9CD670ED4#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#
#1.5#000BCDFB69680051000000B100001A200003FAA9CD67109E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB69680051000000B200001A200003FAA9CD671202#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB69680051000000B300001A200003FAA9CD67132E#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB69680051000000B400001A200003FAA9CD671447#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#
#1.5#000BCDFB69680051000000B500001A200003FAA9CD671574#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#
#1.5#000BCDFB69680051000000B600001A200003FAA9CD67169F#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#
#1.5#000BCDFB69680051000000B700001A200003FAA9CD6717D8#1120032132632#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#
#1.5#000BCDFB69680051000000B800001A200003FAA9CD67190F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#
#1.5#000BCDFB69680051000000B900001A200003FAA9CD671A2E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#
#1.5#000BCDFB69680051000000BA00001A200003FAA9CD671BF6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)#
#1.5#000BCDFB69680051000000BB00001A200003FAA9CD671DB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#
#1.5#000BCDFB69680051000000BC00001A200003FAA9CD671EFE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB69680051000000BD00001A200003FAA9CD672044#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#
#1.5#000BCDFB69680051000000BE00001A200003FAA9CD672159#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000BF00001A200003FAA9CD67227C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
#1.5#000BCDFB69680051000000C000001A200003FAA9CD6723A8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5#000BCDFB69680051000000C100001A200003FAA9CD6724D7#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
#1.5#000BCDFB69680051000000C200001A200003FAA9CD6725FB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
#1.5#000BCDFB69680051000000C300001A200003FAA9CD672716#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
#1.5#000BCDFB69680051000000C400001A200003FAA9CD6728EB#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
#1.5#000BCDFB69680051000000C500001A200003FAA9CD672A9C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
#1.5#000BCDFB69680051000000C600001A200003FAA9CD672BF0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
#1.5#000BCDFB69680051000000C700001A200003FAA9CD672D0F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
#1.5#000BCDFB69680051000000C800001A200003FAA9CD672E22#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
#1.5#000BCDFB69680051000000C900001A200003FAA9CD672F4E#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
#1.5#000BCDFB69680051000000CA00001A200003FAA9CD67309C#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
#1.5#000BCDFB69680051000000CB00001A200003FAA9CD6731D4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5#000BCDFB69680051000000CC00001A200003FAA9CD6732E5#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#
#1.5#000BCDFB69680051000000CD00001A200003FAA9CD6733F2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
#1.5#000BCDFB69680051000000CE00001A200003FAA9CD6735DA#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
#1.5#000BCDFB69680051000000CF00001A200003FAA9CD673771#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###----
caused by -
#1.5#000BCDFB69680051000000D000001A200003FAA9CD6738B2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain###com.sap.security.core.persistence.datasource.PersistenceException: The given ID "RoyC" is not valid!#
#1.5#000BCDFB69680051000000D100001A200003FAA9CD6739D8#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.splitPrincipalDatabagID(DataSourceBaseImplementation.java:492)#
#1.5#000BCDFB69680051000000D200001A200003FAA9CD673AFF#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.PrincipalFactory.getPrincipalType(PrincipalFactory.java:123)#
#1.5#000BCDFB69680051000000D300001A200003FAA9CD673C2F#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getReadonlyUser(UserFactory.java:127)#
#1.5#000BCDFB69680051000000D400001A200003FAA9CD673D53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:180)#
#1.5#000BCDFB69680051000000D500001A200003FAA9CD673E8A#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sap.security.core.imp.UserFactory.getUser(UserFactory.java:85)#
#1.5#000BCDFB69680051000000D600001A200003FAA9CD673FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at counter.CounterService.startUpImpl(CounterService.java:61)#
#1.5#000BCDFB69680051000000D700001A200003FAA9CD6740CE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.service.AbstractRepositoryService.start(AbstractRepositoryService.java:187)#
#1.5#000BCDFB69680051000000D800001A200003FAA9CD6742E2#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:231)#
#1.5#000BCDFB69680051000000D900001A200003FAA9CD67447D#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:106)#
#1.5#000BCDFB69680051000000DA00001A200003FAA9CD6745BE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:303)#
#1.5#000BCDFB69680051000000DB00001A200003FAA9CD6746D6#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:388)#
#1.5#000BCDFB69680051000000DC00001A200003FAA9CD6747F1#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)#
#1.5#000BCDFB69680051000000DD00001A200003FAA9CD674927#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)#
#1.5#000BCDFB69680051000000DE00001A200003FAA9CD674A53#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:260)#
#1.5#000BCDFB69680051000000DF00001A200003FAA9CD674B83#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)#
#1.5#000BCDFB69680051000000E000001A200003FAA9CD674CB0#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:224)#
#1.5#000BCDFB69680051000000E100001A200003FAA9CD674DCE#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)#
#1.5#000BCDFB69680051000000E200001A200003FAA9CD674FB4#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)#
#1.5#000BCDFB69680051000000E300001A200003FAA9CD67514B#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)#
#1.5#000BCDFB69680051000000E400001A200003FAA9CD675293#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.createResource(WdfProxy.java:1940)#
#1.5#000BCDFB69680051000000E500001A200003FAA9CD6753BD#1120032132647#System.err#sap.com/irj#System.err#RoyC#6677####16e2c130e87411d9b103000bcdfb6968#SAPEngine_Application_Thread[impl:3]_36##0#0#Error##Plain### at com.sapportals.wcm.rendering.control.cm.WdfProxy.getResource(WdfProxy.java:1514)#
#1.5#000BCDFB69680051000000E600001A200003FAA9CD6754FD#1120032132647#System.err#sap.com/irj#SysteHi Roy,
for the first log entry, see this posting: /thread/41655 [original link is broken]
Search for "property without corresponding attribute" in it and have a look at my answer.
The second error is, to be short:
com.sap.security.api.NoSuchUserException: The given ID "RoyC" is not valid!#
... at counter.CounterService.startUpImpl(CounterService.java:61)#
Have a look at your own code what's wrong with it (seems that you pass your user ID instead of uniqueID). Use getUserByLogonID(...) instead.
Hope it helps
Detlev -
Getting WCMException while configuring a repository service
Hi KM Experts,
I wrote a program to create a repository service, to start the approval process automatically, and select it for the required repository manager. I restarted the servlet engine, but still the status of newly added document is 'In Progress' and when I tried to submit it manually its throwing the following exception -
Could not execute command 'com.sapportals.wcm.rendering.uicommand.cm.UIStatemanagementCommand'
Below is the program written by me -
package com.infy.autoapprove;
import com.sapportals.wcm.repository.IResource;
import com.sapportals.wcm.repository.ResourceFactory;
import com.sapportals.wcm.repository.service.AbstractRepositoryService;
import com.sapportals.wcm.repository.service.IRepositoryServiceFactory;
import com.sapportals.wcm.repository.service.ServiceNotAvailableException;
import com.sapportals.wcm.repository.service.statemanagement.IResourceTransition;
import com.sapportals.wcm.repository.service.statemanagement.IStatemanagementManager;
import com.sapportals.wcm.repository.service.statemanagement.IStatemanagementResource;
import com.sapportals.wcm.repository.manager.IResourceEventReceiver;
import com.sapportals.wcm.repository.manager.IRepositoryManager;
import com.sapportals.wcm.repository.manager.ResourceEvent;
import com.sapportals.wcm.util.events.IEvent;
import com.sapportals.wcm.crt.component.*;
import com.sapportals.wcm.crt.configuration.*;
import com.sapportals.wcm.IWcmConst;
import com.sapportals.wcm.WcmException;
import java.util.Collection;
// implements IMyNewRepositoryService interface
Note: IReconfigurable and IResourceEventReceiver interfaces are optional
public class AutoApprove extends AbstractRepositoryService implements IReconfigurable, IResourceEventReceiver {
private static final String TYPE = "AutoApprove";
public AutoApprove() {
super();
// Do not add code here. Add it to startUpImpl() instead
public String getServiceType() {
return AutoApprove.TYPE;
protected void startUpImpl(Collection repositoryManagers) throws ConfigurationException, StartupException {
// implement this method as follows:
// - Verify configuration data
// - Get references to other needed (global) services
// - Check whether other repository services (this service depends on) are also assigned to the repository managers
// - Usually the service registers itself for certain events at all repository managers
try {
catch (Exception e) {
throw new StartupException(e.getMessage(), e);
protected void shutDownImpl() { }
protected void addRepositoryAssignment(IRepositoryManager mgr) throws ServiceNotAvailableException {
// Implement this method: Usually the service registers itself for certain events at the repository manager.
try
mgr.getEventBroker().register(this, new ResourceEvent(ResourceEvent.CREATE_CHILD, null));
catch(WcmException e)
protected void removeRepositoryAssignment(IRepositoryManager mgr) throws WcmException {
// Implement this method: Usually the service must unregister itself as an event handler.
public void reconfigure(IConfiguration config) throws ConfigurationException {
this.stateHandler.preReconfigure();
// check the new configuration data
try {
catch (ConfigurationException ex) {
this.stateHandler.postReconfigure(ex);
throw ex;
this.config = config;
this.stateHandler.postReconfigure();
public void received(IEvent event) {
IResource resource = (IResource)event.getParameter();
try
// get the statemanagement service from the resource
String rid = resource.getRID().toString();
if(rid.equals("/documents/TestScenario/XML Form Content/"+resource.getName()))
IRepositoryServiceFactory factory = ResourceFactory.getInstance().getServiceFactory();
IStatemanagementManager statemanagement = (IStatemanagementManager)factory.getRepositoryService(resource, IWcmConst.STATEMANAGEMENT_SERVICE);
IStatemanagementResource sResource = statemanagement.getStatemangementResource(resource);
IResourceTransition transition = sResource.getTransition("lbl.submit");
// if everything is correct than transition is not null
if (transition != null)
transition.execute();
}catch(Exception e){
e.printStackTrace();
Kindly help me out as I am not able to figure out the issue.
Thanks in Advance,
SaurabhHi Experts,
Any help on this ?
Regards,
Saurabh -
KM Repository Service for creating a folder structure
Hi All,
We have a requirement in KM. Whenever a folder is created inside a folder (say '/documents/testFolder') ... .. a couple of subFolders need to be created inside this new folder.
For example, if the new folder's name being created is <i>parentFolder1</i> then, the following structure shud be created inside this folder.
parentFolder1
|--> subFolder1
|--> subFolder11
|--> subFolder12
|--> subFolder2
|--> subFolder21
I tried to implement a KM repository service::
My Rep Service code::
package com.test;
import java.util.Collection;
import java.util.Iterator;
import com.sap.tc.logging.Location;
import com.sapportals.config.fwk.CannotAccessConfigException;
import com.sapportals.config.fwk.Configuration;
import com.sapportals.config.fwk.IConfigClientContext;
import com.sapportals.config.fwk.IConfigManager;
import com.sapportals.config.fwk.IConfigPlugin;
import com.sapportals.config.fwk.IMutableConfigurable;
import com.sapportals.config.fwk.InitialConfigException;
import com.sapportals.portal.security.usermanagement.UserManagementException;
import com.sapportals.wcm.WcmException;
import com.sapportals.wcm.crt.component.IReconfigurable;
import com.sapportals.wcm.crt.component.StartupException;
import com.sapportals.wcm.crt.configuration.ConfigurationException;
import com.sapportals.wcm.crt.configuration.IConfiguration;
import com.sapportals.wcm.repository.AccessDeniedException;
import com.sapportals.wcm.repository.ICollection;
import com.sapportals.wcm.repository.IResource;
import com.sapportals.wcm.repository.NotSupportedException;
import com.sapportals.wcm.repository.Property;
import com.sapportals.wcm.repository.ResourceException;
import com.sapportals.wcm.repository.manager.IRepositoryManager;
import com.sapportals.wcm.repository.manager.IResourceEvent;
import com.sapportals.wcm.repository.manager.IResourceEventReceiver;
import com.sapportals.wcm.repository.manager.ResourceEvent;
import com.sapportals.wcm.repository.service.AbstractRepositoryService;
import com.sapportals.wcm.repository.service.ServiceNotAvailableException;
import com.sapportals.wcm.util.config.ConfigCrutch;
import com.sapportals.wcm.util.events.IEvent;
// implements IMyNewRepositoryService interface
Note: IReconfigurable and IResourceEventReceiver interfaces are optional
public class MytestRepositoryService extends AbstractRepositoryService implements IReconfigurable, IResourceEventReceiver {
private static final String TYPE = "com.test.MytestRepositoryService";
private Collection repositoryManagers;
private static final Location log = Location.getLocation(MytestRepositoryService.class);
//variables
private static final String PLUGIN_FOLDERCREATION_SERVICE = "/cm/repository_services";
private static final String CONFIGCLASS_FOLDERCREATION_SERVICE = "com.test.MytestRepositoryService";
private static final String readPlugins[] = { PLUGIN_FOLDERCREATION_SERVICE };
public static final String PROP_MYFOLDER = "myFolder";
public MytestRepositoryService() {
super();
// Do not add code here. Add it to startUpImpl() instead
public String getServiceType() {
return MytestRepositoryService.TYPE;
protected void startUpImpl(Collection repositoryManagers) throws ConfigurationException, StartupException {
// implement this method as follows:
// - Verify configuration data
// - Get references to other needed (global) services
// - Check whether other repository services (this service depends on) are also assigned to the repository managers
// - Usually the service registers itself for certain events at all repository managers
try {
catch (Exception e) {
throw new StartupException(e.getMessage(), e);
this.repositoryManagers = repositoryManagers;
Iterator it = repositoryManagers.iterator();
while (it.hasNext()){
try {
addRepositoryAssignment((IRepositoryManager) it.next());
} catch (ServiceNotAvailableException e) {
e.printStackTrace();
protected void shutDownImpl() {
Iterator it = repositoryManagers.iterator();
while (it.hasNext()){
try {
removeRepositoryAssignment((IRepositoryManager) it.next());
} catch (WcmException e) {
e.printStackTrace();
protected void addRepositoryAssignment(IRepositoryManager mgr) throws ServiceNotAvailableException {
// Implement this method: Usually the service registers itself for certain events at the repository manager.
try {
// mgr.getEventBroker().register(this, ResourceEvent.ALL_TEMPLATE);
mgr.getEventBroker().register(this, new ResourceEvent(ResourceEvent.CREATE_COLLECTION, null));
} catch (WcmException e) {
e.printStackTrace();
protected void removeRepositoryAssignment(IRepositoryManager mgr) throws WcmException {
// Implement this method: Usually the service must unregister itself as an event handler.
// mgr.getEventBroker().unregister(this, ResourceEvent.ALL_TEMPLATE);
mgr.getEventBroker().unregister(this, new ResourceEvent(ResourceEvent.CREATE_COLLECTION, null));
public void reconfigure(IConfiguration config) throws ConfigurationException {
this.stateHandler.preReconfigure();
// check the new configuration data
try {
catch (ConfigurationException ex) {
this.stateHandler.postReconfigure(ex);
throw ex;
this.config = config;
this.stateHandler.postReconfigure();
public void received(IEvent event) {
IResourceEvent myEvent = (IResourceEvent) event;
IResource resource = (IResource) myEvent.getParameter();
String repositoryPath = "";
String parentPath = "";
//get the configuration...
try {
IConfigClientContext context = IConfigClientContext.createContext(ConfigCrutch.getConfigServiceUser());
IConfigManager cfg = Configuration.getInstance().getConfigManager(context);
IConfigPlugin configPlugin = cfg.getConfigPlugin(PLUGIN_FOLDERCREATION_SERVICE);
if (configPlugin != null) {
IMutableConfigurable[] configurables = configPlugin.getConfigurables(CONFIGCLASS_FOLDERCREATION_SERVICE, false);
for (int i = 0; i < configurables.length; i++) {
IMutableConfigurable configurable = configurables<i>;
if (configurable.getConfigClass().getName().equals(CONFIGCLASS_FOLDERCREATION_SERVICE)) {
// now get the attribute value...
repositoryPath = configurable.getPropertyValue(PROP_MYFOLDER); //// "documents/parentFolder1"
} catch (InitialConfigException e2) {
e2.printStackTrace();
} catch (CannotAccessConfigException e2) {
e2.printStackTrace();
} catch (UserManagementException e2) {
e2.printStackTrace();
try {
parentPath = resource.getParentCollection().getRID().toString();
} catch (AccessDeniedException e1) {
e1.printStackTrace();
} catch (ResourceException e1) {
e1.printStackTrace();
if(repositoryPath.equals(parentPath))
//write my code here
if (resource != null && (resource.isCollection()) )
ICollection parentFolder = (ICollection) resource;
try {
<b>parentFolder.createCollection("subFolder1",null);</b>
} catch (NotSupportedException e) {
e.printStackTrace();
} catch (AccessDeniedException e) {
e.printStackTrace();
} catch (ResourceException e) {
e.printStackTrace();
<b>...MytestRepositoryService.co.xml:</b>
- <Configurable configclass="com.test.MytestRepositoryService">
<property name="name" value="com.test.MytestRepositoryService" />
<property name="active" value="true" />
<i> <property name="myFolder" value="/documents/parentFolder1" /></i>
<property name="description" />
</Configurable>
<b>...MytestRepositoryService.cc.xml:</b>
- <ConfigClass name="com.test.MytestRepositoryService" extends="RepositoryService">
<attribute name="class" type="class" constant="com.test.MytestRepositoryService" />
</ConfigClass>
Have i done it right?? Where am i going wrong??? Plz advice.
I need to 'myFolder' as a configurable property in KM's <i>Content Management --> Repository Services</i> section.
Thanks!
Regards,
SK.Hi,
I haven't check your code but you know that you can archive the same without writing a portal componente by using the template feature. It is a simple customizing. See http://help.sap.com/saphelp_nw70/helpdata/en/55/83bd402b8d8031e10000000a1550b0/frameset.htm
Best Regards
Frank -
CRADSDatabase ERROR (5211): There is an error converting Unicode string to or from code page string
Device Blackberry Z10
Sw release 10.2.1.2977
OS Version 10.2.1.3247
The problem is known by Blackberry but they didn't make a little effort to solve this problem and they wonder why nobody buy Blackberry. I come from Android platform and I regret buying Blackberry: call problems(I sent it to service because the people that I was talking with couldn't hear me), jack problems (the headphones does not work; I will send it again to service). This synchronisation problem is "the drop that fills the glass". Please don't buy Blackberry any more.
http://btsc.webapps.blackberry.com/btsc/viewdocument.do?noCount=true&externalId=KB33098&sliceId=2&di...This is a Windows registry issue, if you search the Web using these keywords:
"how to fix craddatabase error 5211" you will find a registry editor that syas it can fix this issue. -
EJB called via JNDI in a Repository Service :: ClassCastException
Hi SDN,
I've got a problem in calling an EJB from a Repository Service...
Here the steps I've follow:
- An EJB has been created with some Business Methods in it; it has been packaged in an EAR and deployed;
- This EJB is looked up succesfully via JNDI in a WDJ application and also in an Abstract Portal Component; I use the following guides:
[Accessing EJB Apps using JNDI|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/0736159e-0301-0010- 9ea4-c63d83d0797b?QuickLink=index&overridelayout=true]
[Referencing an EJB in an Abstract Portal Component|http://wiki.sdn.sap.com/wiki/display/HOME/ConnectingEJBUsing ExternalJars]
- A Repository Service has been created and registered on "CREATE_CHILD_TEMPLATE" ResourceEvent; I can see from logs that this service works correctly;
- I've copied in the PAR lib and private/lib folders two jars (ejb20.jar and the JAR created building the EJB) and they are added to the build path;
- If I try to look up the EJB via JNDI in the received service method, I get a ClassCastException...
Here some code:
try {
//I use System.err to see log in the Default Trace
System.err.println("Initialize EJB");
//TestJNDIHome class seems to be visible at runtime, following instruction does not throw any exception
System.err.println("ToString TestJNDIHome: " + TestJNDIHome.class.toString());
//EJB and PAR are on the same J2EE engine, so no InitialContext parameters, I'm right?
InitialContext context = new InitialContext();
Object jndiobj = context.lookup("altevie.com/testear/TestJNDIBean");
System.err.println("Classe oggetto recuperato da lookup: " + jndiobj.getClass());
TestJNDIHome home = (TestJNDIHome) javax.rmi.PortableRemoteObject.narrow(jndiobj, TestJNDIHome.class);
testJNDI = home.create();
} catch (NamingException ex) {
System.err.println("NamingException :: " + ex.getLocalizedMessage());
} catch (RemoteException ex) {
System.err.println("RemoteException :: " + ex.getLocalizedMessage());
} catch (CreateException ex) {
System.err.println("CreateException :: " + ex.getLocalizedMessage());
Here the portalapp.xml (in the same PAR there are two objects, the Repository Service and an Abstract Portal Component, but I've got the same problem also removing the Abstract Portal Component...):
<application>
<application-config>
<property name="com.sap.engine.interfaces.cross.ObjectReferenceImpl" value="SAPJ2EE::altevie.com/testEAR"/>
<property name="SharingReference" value="usermanagement, knowledgemanagement, landscape, htmlb, exportalJCOclient, exportal"/>
<property name="PrivateSharingReference" value="SAPJ2EE::altevie.com/testEAR"/>
</application-config>
<components>
<component name="TestJSP">
<component-config>
<property name="ClassName" value="com.comer.eps.epcomp.TestJSP"/>
</component-config>
<component-profile/>
</component>
</components>
<services>
<service name="RFServiceWrapper">
<service-config>
<property name="className" value="com.sap.netweaver.rf.wrapper.RFServiceWrapper"/>
<property name="startup" value="true"/>
</service-config>
</service>
</services>
</application>
javax.rmi.PortableRemoteObject.narrow method call throws a ClassCastException...
From the previous println I can see the lookup method returns a com.sap.engine.interfaces.cross.ObjectReferenceImpl object, I do not know if it is correct...
I've tried to lookup the Local (localejbs/altevie.com/testear/TestJNDIBean) and Remote (altevie.com/testear/TestJNDIBean) JNDI Bean name, but I get the same error...
I'm sure the JNDI name is correct (it works with WDJ and Abstract Portal Component... I've also tested via LOOKUP command using telnet to connect to J2EE AS and I've checked JNDI Registry and EJB Container services in Visual Admin)...
Here the stack trace of the error:
java.lang.ClassCastException: com.comer.eps.ejb.AccessiEJBHome
at com.sap.engine.services.cross.PortableRemoteObjectContainer.narrow(PortableRemoteObjectContainer.java:179)
at com.sap.engine.system.PortableRemoteObjectProxy.narrow(PortableRemoteObjectProxy.java:24)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at com.comer.eps.repsrv.onsave.RipubblicaByDE.initializeEJB(RipubblicaByDE.java:145)
Can you help me? Why JNDI lookup works in an Abstract Portal Application and doesn't in a Repository Service (same code...)?
Thank you so much and best regards,
Manuel
Text Formatted: Manuel Xiccato on Sep 27, 2011 12:29 PMHi SDN,
I've got a problem in calling an EJB from a Repository Service...
Here the steps I've follow:
- An EJB has been created with some Business Methods in it; it has been packaged in an EAR and deployed;
- This EJB is looked up succesfully via JNDI in a WDJ application and also in an Abstract Portal Component; I use the following guides:
[Accessing EJB Apps using JNDI|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/0736159e-0301-0010- 9ea4-c63d83d0797b?QuickLink=index&overridelayout=true]
[Referencing an EJB in an Abstract Portal Component|http://wiki.sdn.sap.com/wiki/display/HOME/ConnectingEJBUsing ExternalJars]
- A Repository Service has been created and registered on "CREATE_CHILD_TEMPLATE" ResourceEvent; I can see from logs that this service works correctly;
- I've copied in the PAR lib and private/lib folders two jars (ejb20.jar and the JAR created building the EJB) and they are added to the build path;
- If I try to look up the EJB via JNDI in the received service method, I get a ClassCastException...
Here some code:
try {
//I use System.err to see log in the Default Trace
System.err.println("Initialize EJB");
//TestJNDIHome class seems to be visible at runtime, following instruction does not throw any exception
System.err.println("ToString TestJNDIHome: " + TestJNDIHome.class.toString());
//EJB and PAR are on the same J2EE engine, so no InitialContext parameters, I'm right?
InitialContext context = new InitialContext();
Object jndiobj = context.lookup("altevie.com/testear/TestJNDIBean");
System.err.println("Classe oggetto recuperato da lookup: " + jndiobj.getClass());
TestJNDIHome home = (TestJNDIHome) javax.rmi.PortableRemoteObject.narrow(jndiobj, TestJNDIHome.class);
testJNDI = home.create();
} catch (NamingException ex) {
System.err.println("NamingException :: " + ex.getLocalizedMessage());
} catch (RemoteException ex) {
System.err.println("RemoteException :: " + ex.getLocalizedMessage());
} catch (CreateException ex) {
System.err.println("CreateException :: " + ex.getLocalizedMessage());
Here the portalapp.xml (in the same PAR there are two objects, the Repository Service and an Abstract Portal Component, but I've got the same problem also removing the Abstract Portal Component...):
<application>
<application-config>
<property name="com.sap.engine.interfaces.cross.ObjectReferenceImpl" value="SAPJ2EE::altevie.com/testEAR"/>
<property name="SharingReference" value="usermanagement, knowledgemanagement, landscape, htmlb, exportalJCOclient, exportal"/>
<property name="PrivateSharingReference" value="SAPJ2EE::altevie.com/testEAR"/>
</application-config>
<components>
<component name="TestJSP">
<component-config>
<property name="ClassName" value="com.comer.eps.epcomp.TestJSP"/>
</component-config>
<component-profile/>
</component>
</components>
<services>
<service name="RFServiceWrapper">
<service-config>
<property name="className" value="com.sap.netweaver.rf.wrapper.RFServiceWrapper"/>
<property name="startup" value="true"/>
</service-config>
</service>
</services>
</application>
javax.rmi.PortableRemoteObject.narrow method call throws a ClassCastException...
From the previous println I can see the lookup method returns a com.sap.engine.interfaces.cross.ObjectReferenceImpl object, I do not know if it is correct...
I've tried to lookup the Local (localejbs/altevie.com/testear/TestJNDIBean) and Remote (altevie.com/testear/TestJNDIBean) JNDI Bean name, but I get the same error...
I'm sure the JNDI name is correct (it works with WDJ and Abstract Portal Component... I've also tested via LOOKUP command using telnet to connect to J2EE AS and I've checked JNDI Registry and EJB Container services in Visual Admin)...
Here the stack trace of the error:
java.lang.ClassCastException: com.comer.eps.ejb.AccessiEJBHome
at com.sap.engine.services.cross.PortableRemoteObjectContainer.narrow(PortableRemoteObjectContainer.java:179)
at com.sap.engine.system.PortableRemoteObjectProxy.narrow(PortableRemoteObjectProxy.java:24)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
at com.comer.eps.repsrv.onsave.RipubblicaByDE.initializeEJB(RipubblicaByDE.java:145)
Can you help me? Why JNDI lookup works in an Abstract Portal Application and doesn't in a Repository Service (same code...)?
Thank you so much and best regards,
Manuel
Text Formatted: Manuel Xiccato on Sep 27, 2011 12:29 PM -
How to get Resource Name in the Repository Service when Publish evt trigger
Hi ,
I have created a repository service in which I have registered the
StatemanagementEvent.PUBLISH
My requirement is I need to know which resource rather resource name triggered this event.
This is the code which
public class ApprovProcs extends AbstractRepositoryService implements IReconfigurable, IResourceEventReceiver
private static final String TYPE = "ApprovProcs";
private Collection repositoryManagers;
public ApprovProcs()
super();
// Do not add code here. Add it to startUpImpl() instead
public String getServiceType()
return ApprovProcs.TYPE;
protected void startUpImpl(Collection repositoryManagers) throws ConfigurationException, StartupException
// implement this method as follows:
// - Verify configuration data
// - Get references to other needed (global) services
// - Check whether other repository services (this service depends on) are also assigned to the repository managers
// - Usually the service registers itself for certain events at all repository managers
this.repositoryManagers = repositoryManagers;
Iterator it = repositoryManagers.iterator();
while (it.hasNext())
try
addRepositoryAssignment( (IRepositoryManager) it.next());
catch (ServiceNotAvailableException e)
e.printStackTrace();
protected void shutDownImpl()
Iterator it = repositoryManagers.iterator();
while (it.hasNext())
try
removeRepositoryAssignment( (IRepositoryManager) it.next());
catch (WcmException e)
e.printStackTrace();
protected void addRepositoryAssignment(IRepositoryManager mgr) throws ServiceNotAvailableException
// Implement this method: Usually the service registers itself for certain events at the repository manager.
try
// capture all the respurce which are published
mgr.getEventBroker().register( this, new StatemanagementEvent( StatemanagementEvent.PUBLISH, null ));
catch(WcmException e)
protected void removeRepositoryAssignment(IRepositoryManager mgr) throws WcmException
// Implement this method: Usually the service must unregister itself as an event handler.
//mgr.getEventBroker().unregister(this, new ResourceEvent(ResourceEvent.CREATE_COLLECTION, null));
mgr.getEventBroker().unregister( this, new StatemanagementEvent( StatemanagementEvent.PUBLISH, null ));
public void reconfigure(IConfiguration config) throws ConfigurationException
this.stateHandler.preReconfigure();
// check the new configuration data
try {
catch (ConfigurationException ex) {
this.stateHandler.postReconfigure(ex);
throw ex;
this.config = config;
this.stateHandler.postReconfigure();
public void received(IEvent event)
System.err.println( "----rid --42354543--- " );
IResource rsrPublished = (IResource)event.getParameter();
if( rsrPublished != null )
System.err.println( "----rid --42354543--- rsrPublished.getDescription() --- " + rsrPublished.getDescription() );
else
System.err.println( "Resource Does not exist -----" ) ;
In the log file I am getting Null Pointer Exception
Can any one please help me in this as where I am going wrong
thanks
pkHi Romano & Detlev ,
Thanks for the reply .
This is what I was looking
Detlev:
About the NPE ... in the above code I am not getting that.
Thats my mistake
Earlier I tried with
IResource rsrPublished = (IResource)event.getParameter();
String rid = rsrPublished.getRID().toString();
In the second line of code I was getting the NPE
after that I used to if condition to debug it
Sorry for the confusion...
One more thing
which is the event triggered for approval or how to capture the Approval Event when a content is approved by the Approver
thanks
pk -
Repository Service not working
Hi all,
I have designed a very simple repository service based on the several code samples here on the forums. Here is the received(IEvent) method i implemented:
public void received(IEvent event) {
IResourceEvent resEvent = (IResourceEvent) event;
IResource resource = resEvent.getResource();
try {
resource.rename("my_resource_" + resource.getName());
} catch (Exception e) {
e.printStackTrace();
When i deploy this PAR file, the service appears on the Repository Services part of the config iView. Then i created a new Repository Manager pointing to /room_extensions/cm_stores/questions/workspaces, which is the directory where this Service must act, and associated my Service with it. Even after restarting, the creation of documents on this folder does not trigger the Rep Service!!! Do you know what am i getting wrong?
Thanks in advance!
ThiagoHi Thiago,
Even I am facing a similar issue.Can you please let me know how did you resolve this.
I had one more doubt,
I have written a service for a CM repository manager , where the files are managed by the file system.
My query is -
If I create a new file directly in the file system (not through KM), will the repository service be triggered.
I hope it does. Please let me know.
Regards,
Vivek -
Hello,
We are doing an upgrade from 4.6b to ECC6.0 and also a Unicode conversion. Could someone clarify the following doubts related to vocabulary maintenance?
Will text elements used by programs be automatically translated into the right Unicode page (e.g. based on the language key provide for each text elements) or does the code page selection need to be done via the vocabulary maintenance?
Any other development objects that could be affected if the code page selection is not done via the vocabulary maintenance?
What would be the impact on the development objects if the code page selection is not done via vocabulary maintenance?
Thanks in advance,
ReenaHi Reena,
> * Will text elements used by programs be automatically translated into the right Unicode page (e.g. based on the language key provide for each text elements) or does the code page selection need to be done via the vocabulary maintenance?
I assume you have an MDMP system. For such a system, all entries in language dependent tables will be converted based on the language key of the according entry. Text elements are stored in language dependent tables and therefore will be converted properly (if the code page fits to the language) independently of the maintenance of the vocabulary maintenance in transaction SPUMG.
> * Any other development objects that could be affected if the code page selection is not done via the vocabulary maintenance?
Actually I do not know of any. However I have to admit that I am not a developer ...
> * What would be the impact on the development objects if the code page selection is not done via vocabulary maintenance?
If you have already executed the SPUMG scan "Tables without language info", you can check the tables which inserted words into the vocabulary (choose on the selection screen : STATUS = W). Now you have to know whether the content of the listed tables is relevant for your development ...
Best regards,
Nils Buerckel
Solution Management
Globalization Services
SAP AG -
Hello All,
I am using Oracle 11.2.0.3.0 version, my database code page is as shown below.
SELECT USERENV ('language') FROM DUAL;
AMERICAN_AMERICA.WE8MSWIN1252May i please know if the DB is compatible to load the Unicode characters?
Is" AMERICAN_AMERICA.WE8MSWIN1252" code page superset of "UTF-8 encoding Unicode" character set?
Thank you.I am trying to install Informatica services on a 'Oracle 11.2.0.3.0' database in 'Red hat Linux 64 bit OS' and I am confused about choosing or determining the code page during installation though i read the manuals, as there are multiple components in installation.
when i do "locale -a | grep en_us" on Linux OS it gives below.
en_US.UTF-8
en_us.iso-8859-1
en_us.iso-8859-15when i do "echo $LANG" it gives below though not set in app user OS profile, probably the default code page set by system administrator
en_US.UTF-8$LC_ALL & $NLS_LANG at OS level were not set yet in the application user profile,i need to set this as well.
And below are my NLS_DATABASE_PARAMETERS are as below
PARAMETER VALUE
NLS_CHARACTERSET WE8MSWIN1252
NLS_NCHAR_CHARACTERSET AL16UTF16We have to load the XML files (UTF-8) into Oracle database via Informatica, Manual says for UNIX OS choose the code page as "en_us.iso-8859-1" but nothing specifically for Linux OS and it also says the target database code page should be superset of all my sources (flatfiles,xml etc) and rest of the Informatica component code pages.
Can you please provide me an idea or approach? what should be my OS parameters $LANG & $NLS_LANG (oracle client) values before starting the installation for codepage compatibility?
Thank you.
Edited by: Ariean on Apr 16, 2013 10:05 PM -
Repository Service for Auto Submit for Approval
Hi all,
Can anyone help me with the creation of a Repository Service to auto 'submit for approval' any document created.
My main problem is in two methods:
1) removeRepositoryAssignment(IRepositoryManager mgr)
In some samples, I saw always this code line:
mgr.getEventBroker().unregister(this, ResourceEvent.CREATE_CHILD);
But in my project the unregister method doesn't have that parameters
2) received(IEvent event)
I need some help to know what code should I put
The remaining steps, I think I can handle by myself.
Many Thanks,
LuisHi,
1) make sure you use com.sapportals.wcm.repository.manager.IRepositoryManager, use the JAR (bc.rf.framework_api.jar from the \usr\sap\XXX\JCXX\j2ee\cluster\serverX\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.netweaver.bc.rf\lib folder) from the portal you are willing to develop to make sure you have the actual libraries.
2) in this method you have to catch the events that creates the resource (ResourceEvent.CREATE_CHILD) - later you will see, that you have to handle also the CHANGE events and so on. When you have the event, get the resource - for CREATE_CHILD it is
event.getResource()
Now you can handle the submit for approval by yourself.
Romano
Maybe you are looking for
-
How can i get the max rpm from cpu fan??
how can i get the max rpm from my cpu cooler regarding that i don't have a speed controller attached to the cpu fan ,,, ?? please make things clear for me thanks
-
Does the iBooks Author support Right-to-Left languages?
Hi, I wish to know if the iBooks Author support languages which are written from Right to Left, such as Arab, and Hebrew. Moreover, can it show those foreign letters? Does it look okay, or unorganized? And another small thing - can you upload a textb
-
Dear experts PO created with release strategy ,then in conditions custom clearing charges were included and this vendor was included .Now this PO was re-released . Another PO with release strategy , ,then in conditions custom clearing ch
-
Hi, I am doing iDOC to File scenario. I have done all the steps of Integeration Repository(Design) but when i move into Integeration Directory(Configuration) and try to click on Configuration Wizard it gives me an Error "Cannot connect to Integeratio
-
Hi, adcmctl.sh command takes a lot of time to bring down the concurrent services in R12 env compared to 11i version. I can understand this if we have brought down the services when any concurrent requests are still running , but this happens even whe