Log file not creating
Hi, I tried to configure log for my application, but the log files are not getting created, I am getting the following error.
My log configuration -
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
<log-configuration>
<log-destinations>
<log-destination
count="10"
effective-severity="ALL"
limit="10000"
name="LogTestLog"
pattern="./log/applications/TestLog/LogTestLog.%g.log"
type="FileLog"/>
</log-destinations>
<log-controllers>
<log-controller
effective-severity="ALL"
name="System.out">
<associated-destinations>
<destination-ref
association-type="LOG"
name="LogTestLog"/>
</associated-destinations>
</log-controller>
<log-controller
effective-severity="ALL"
name="com.giri.test.LogServlet">
<associated-destinations>
<destination-ref
association-type="LOG"
name="LogTestLog"/>
<anonymous-destination
association-type="LOG"
type="FileLog"/>
</associated-destinations>
</log-controller>
</log-controllers>
</log-configuration>
#1.5#0030485D5AE617CD000000000000142000042AAA6682264C#1172811259302#/System/Logging##com.sap.tc.logging.FileLogInfoData.[getFileHeader(String fileName, int cntHeadLines)]######147f6460c87a11dba2920030485d5ae6#SAPEngine_System_Thread[impl:5]_99##0#0#Warning##Java#SAP_LOGGING_UNEXPECTED##Unexcepted error occured on !#1#FileHeader parsing#
#1.5#0030485D5AE617CD000000010000142000042AAA6682297F#1172811259302#/System/Logging##/System/Logging######147f6460c87a11dba2920030485d5ae6#SAPEngine_System_Thread[impl:5]_99##0#0#Path##Java###Caught #1#java.lang.Exception: .
log
applications
TestLog
LogTestLog.0.log (The system cannot find the path specified)
at com.sap.tc.logging.FileLogInfoData.getEOLLength(FileLogInfoData.java:432)
at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:348)
at com.sap.tc.logging.FileLogInfoData.getFileHeaderLines(FileLogInfoData.java:334)
at com.sap.tc.logging.FileLogInfoData.loadFileLogHeader(FileLogInfoData.java:320)
at com.sap.tc.logging.FileLogInfoData.init(FileLogInfoData.java:260)
at com.sap.tc.logging.FileLogInfoData.<init>(FileLogInfoData.java:119)
at com.sap.tc.logging.FileLog.init(FileLog.java:373)
at com.sap.tc.logging.FileLog.<init>(FileLog.java:282)
at com.sap.tc.logging.FileLog.<init>(FileLog.java:246)
at com.sap.engine.services.log_configurator.admin.LogConfigurator.adjustConfiguration(LogConfigurator.java:665)
at com.sap.engine.services.log_configurator.admin.LogConfigurator.applyConfiguration(LogConfigurator.java:1488)
at com.sap.engine.services.log_configurator.LogConfiguratorContainer.prepareStart(LogConfiguratorContainer.java:545)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:239)
at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:187)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:74)
at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:218)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
I have the same problem. I also see many similar exception from different apps, such as writing to file ".
log
applications
cms
default.0.trc", ".
log
applications
cms
default.0.trc"
Do I have to create log file before I use the logging service.
I change "ForceSingleTraceFile" to "NO" in "LogManager" by Visual Administrator. Could it be a problem?
I am running SAP Web AS 6.4 and deploying using SDM. I have a log-configuration.xml in the ear file. This is my log configuration
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log-configuration SYSTEM "log-configuration.dtd">
<log-configuration>
<log-formatters/>
<log-destinations>
<log-destination
count="10"
effective-severity="ALL"
limit="1000000"
name="TraceLog01"
pattern="./log/file.%g.trc"
type="FileLog"/>
</log-destinations>
<log-controllers>
<log-controller
effective-severity="ALL"
name="LogController01">
<associated-destinations>
<destination-ref
association-type="LOG"
name="TraceLog01"/>
</associated-destinations>
</log-controller>
</log-controllers>
</log-configuration>
Similar Messages
-
Why multiple log files are created while using transaction in berkeley db
we are using berkeleydb java edition db base api, we have already read/write CDRFile of 9 lack rows with transaction and
without transaction implementing secondary database concept the issues we are getting are as follows:-
with transaction----------size of database environment 1.63gb which is due to no. of log files created each of 10 mb.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb. so we want to know how REASON CONCRETE CONCLUSION ..
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001.....plz reply soonwe are using berkeleydb java edition db base api, If you are seeing __db.NNN files in your environment root directory, these are environment's shared region files. And since you see these you are using Berkeley DB Core (with the Java/JNI Base API), not Berkeley DB Java Edition.
with transaction ...
without transaction ...First of all, do you need transactions or not? Review the documentation section called "Why transactions?" in the Berkeley DB Programmer's Reference Guide.
without transaction-------size of database environment 588mb and here only one log file is created which is of 10mb.There should be no logs created when transactions are not used. That single log file has likely remained there from the previous transactional run.
how log files are created and what is meant of using transaction and not using transaction in db environment and what are this db files db.001,db.002,_db.003,_db.004,__db.005 and log files like log.0000000001Have you reviewed the basic documentations references for Berkeley DB Core?
- Berkeley DB Programmer's Reference Guide
in particular sections: The Berkeley DB products, Shared memory regions, Chapter 11. Berkeley DB Transactional Data Store Applications, Chapter 17. The Logging Subsystem.
- Getting Started with Berkeley DB (Java API Guide) and Getting Started with Berkeley DB Transaction Processing (Java API Guide).
If so, you would have had the answers to these questions; the __db.NNN files are the environment shared region files needed by the environment's subsystems (transaction, locking, logging, memory pool buffer, mutexes), and the log.MMMMMMMMMM are the log files needed for recoverability and created when running with transactions.
--Andrei -
Control file not created at time of installtion
control file not created at time of installtion of oracle database
now how we can create it
see alert file
Dump file e:\ORacle\admin\new\bdump\newALRT.LOG
Tue Sep 09 10:45:53 2003
ORACLE V8.1.6.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 , CPU type 586
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 59
shared_pool_size = 52428800
large_pool_size = 614400
java_pool_size = 20971520
control_files = e:\ORacle\oradata\new\control01.ctl, e:\ORacle\oradata\new\control02.ctl, e:\ORacle\oradata\new\control03.ctl
db_block_buffers = 19200
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
global_names = TRUE
distributed_transactions = 500
instance_name = new
service_names = new
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = new
open_cursors = 100
os_authent_prefix =
job_queue_processes = 0
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = e:\ORacle\admin\new\bdump
user_dump_dest = e:\ORacle\admin\new\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Tue Sep 09 10:45:55 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Sep 09 10:45:58 2003
create controlfile reuse set database new
datafile 'e:\ORacle\oradata\new\system01.dbf',
'e:\ORacle\oradata\new\temp01.dbf',
'e:\ORacle\oradata\new\rbs01.dbf',
'e:\ORacle\oradata\new\indx01.dbf',
'e:\ORacle\oradata\new\tools01.dbf',
'e:\ORacle\oradata\new\dr01.dbf',
'e:\ORacle\oradata\new\users01.dbf'
logfile 'e:\ORacle\oradata\new\redo01.log' size 1M,
'e:\ORacle\oradata\new\redo02.log' size 1M,
'e:\ORacle\oradata\new\redo03.log' size 1M resetlogs
Tue Sep 09 10:46:03 2003
ORA-1503 signalled during: create controlfile reuse set database new
datafile...
Tue Sep 09 10:46:03 2003
alter database new open resetlogs
ORA-1507 signalled during: alter database new open resetlogs...
Tue Sep 09 10:46:14 2003
alter database new character set WE8ISO8859P1
Tue Sep 09 10:46:14 2003
ORA-1507 signalled during: alter database new character set WE8ISO8859P1...
Tue Sep 09 10:46:14 2003
alter database new national character set WE8ISO8859P1
ORA-1507 signalled during: alter database new national character set WE8ISO88...
Shutting down instance (normal)
License high water mark = 1
Tue Sep 09 10:46:15 2003
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
archiving is disabled
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 59
shared_pool_size = 52428800
large_pool_size = 614400
java_pool_size = 20971520
control_files = e:\ORacle\oradata\new\control01.ctl, e:\ORacle\oradata\new\control02.ctl, e:\ORacle\oradata\new\control03.ctl
db_block_buffers = 19200
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
global_names = TRUE
distributed_transactions = 500
instance_name = new
service_names = new
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = new
open_cursors = 100
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = e:\ORacle\admin\new\bdump
user_dump_dest = e:\ORacle\admin\new\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Tue Sep 09 10:46:30 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Sep 09 10:46:31 2003
alter database mount
Tue Sep 09 10:46:34 2003
ORA-00202: controlfile: 'e:\ORacle\oradata\new\control01.ctl'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Tue Sep 09 10:46:34 2003
ORA-205 signalled during: alter database mount...
Dump file e:\ORacle\admin\new\bdump\newALRT.LOG
Tue Sep 09 11:18:54 2003
ORACLE V8.1.6.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 , CPU type 586
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 59
shared_pool_size = 52428800
large_pool_size = 614400
java_pool_size = 20971520
control_files = e:\ORacle\oradata\new\control01.ctl, e:\ORacle\oradata\new\control02.ctl, e:\ORacle\oradata\new\control03.ctl
db_block_buffers = 19200
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
global_names = TRUE
distributed_transactions = 500
instance_name = new
service_names = new
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = new
open_cursors = 100
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = e:\ORacle\admin\new\bdump
user_dump_dest = e:\ORacle\admin\new\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Tue Sep 09 11:18:57 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Sep 09 11:18:58 2003
alter database mount exclusive
Tue Sep 09 11:19:01 2003
ORA-00202: controlfile: 'e:\ORacle\oradata\new\control01.ctl'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Tue Sep 09 11:19:01 2003
ORA-205 signalled during: alter database mount exclusive...
Shutting down instance (abort)
License high water mark = 5
Instance terminated by USER, pid = 1156
Dump file e:\ORacle\admin\new\bdump\newALRT.LOG
Tue Sep 09 11:22:12 2003
ORACLE V8.1.6.0.0 - Production vsnsta=0
vsnsql=e vsnxtr=3
Windows 2000 Version 5.0 , CPU type 586
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 59
shared_pool_size = 52428800
large_pool_size = 614400
java_pool_size = 20971520
control_files = e:\ORacle\oradata\new\control01.ctl, e:\ORacle\oradata\new\control02.ctl, e:\ORacle\oradata\new\control03.ctl
db_block_buffers = 19200
db_block_size = 8192
compatible = 8.1.0
log_buffer = 32768
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
db_files = 1024
db_file_multiblock_read_count= 8
max_enabled_roles = 30
remote_login_passwordfile= EXCLUSIVE
global_names = TRUE
distributed_transactions = 500
instance_name = new
service_names = new
mts_dispatchers = (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
open_links = 4
sort_area_size = 65536
sort_area_retained_size = 65536
db_name = new
open_cursors = 100
os_authent_prefix =
job_queue_processes = 4
job_queue_interval = 10
parallel_max_servers = 5
background_dump_dest = e:\ORacle\admin\new\bdump
user_dump_dest = e:\ORacle\admin\new\udump
max_dump_file_size = 10240
oracle_trace_collection_name=
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
SNP0 started with pid=8
SNP1 started with pid=9
SNP2 started with pid=10
SNP3 started with pid=11
Tue Sep 09 11:22:15 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Sep 09 11:22:16 2003
alter database mount exclusive
Tue Sep 09 11:22:19 2003
ORA-00202: controlfile: 'e:\ORacle\oradata\new\control01.ctl'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.Hi Kuljeet,
since you have a Windows system, I suggest you to open Windows explorer and check if all the 3 control files are there or not in the given location. It seems that your control01.ctl file is missing. If so then you have 2 options;
1. Delete the entry from the parameter file for this control file so that Oracle does not use this file at all.
OR
2. Shut down your database normally and then copy the control02.ctl or control03.ctl manually with the copy command and rename it to control01.ctl. If you follow this option you need not delete the control01.ctl entry from the parameter file. But note to copy the control file the database has to be shutdown normally. -
Hai Gurus,
here i doing an archiving task,i havecreated the variant and assigned four weks to archive,after 40 min later i found the job is finished and when i started deleting ,the archived file file NOT created.So i cross checked in spool request and it shown as the "WAITING",the Statistics screen as NO data found.
I have my job log as the arching is been created with "1" archiving object, but actually it has to show me the file name:"archive_bw_000025236.....".So what can be the reason and where can be the file be gone or saved?what is the procedure to find the Archived file,i mean in which table i can see
please let me know
Points will allocated fully .........
Suri.Hi Suri,
When you archive any data( in your case- 4 weeks data), the system will confirm if this data is business complete. If YES, then it will archive your stipulated data and only then you may be able to see the Log of the archived data.
if there is no data ( business complete)to be archived, then NO archive file will be created.
You can see the Archive file name in the Job Log of that particular archiving run.
By the way, which data/object are u archiving ? may be i can help you. -
On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09
When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Unable to process the document in the module Save As. File not created"
http://youtu.be/l0a0lWexfNQ.Hi,
Please post your query in Adobe Acrobat Thread:Acrobat
Regards,
Florence -
BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED
Hello,
To generate the log report, /VIRSA/ZVFATBAK program is scheduled on hourly basis but some time report doesn't get generated and if we see the background job then it shows sucessfully finished.
If we see the maually the log report for FFID then below error message is displayed.
" BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED"
Can anyone guide me to solve the issue.
Thanks in advance.
Best Regards,
Prashant DubeyHi,
once chk the status of the job by selecting that and check job status(cltr+shift_f12)
since it was periodically scheduled job there will be a RELEASED job after every active job..
so try to copy that into another job using copy option and give some new name which u have to remember...
the moment u copy u can find the same copied job in SCHEDULED status...
from here, try to run it again on hourly basis....
After copying the job u can unschedule the old released job to scheduled otherwise 2 will run at a time...
rgds, -
SHADOW_IMPORT_UPG1 is very very slow, no log files are created
Hi all
We are now doing our production upgrade, during the SHADOW_IMPORT_UPG1 phase system is very slow
no log files are created in the /usr/sap/put/log directory.
only three files are growing in /usr/sap/tmp directory
orar3p> ls -lrt
total 219176
-rw-rw-rw- 1 r3padm sapsys 2693 Aug 15 18:42 UCMIG_DE.ECO
-rw-rw-rw- 1 r3padm sapsys 2374 Aug 15 18:42 R3trans.out
-rw-rw-rw- 1 r3padm sapsys 2685 Aug 15 18:46 ADDON_TR.ECO
-rw-rw-rw- 1 r3padm sapsys 726 Aug 15 20:04 crshdusr.log
-rw-rw-rw- 1 r3padm sapsys 3915 Aug 15 21:53 EU_IMTSK.ECO
-rw-rw-r-- 1 r3padm sapsys 257 Aug 15 22:09 SAPKKLFRN18.R3P
-rw-rw-r-- 1 r3padm sapsys 257 Aug 15 22:09 SAPKKLPTN18.R3P
-rw-rw-r-- 1 r3padm sapsys 257 Aug 15 22:09 SAPKKLESN18.R3P
-rw-rw-r-- 1 r3padm sapsys 36433272 Aug 15 23:44 SAPKLESN18.R3P
-rw-rw-r-- 1 r3padm sapsys 36807577 Aug 15 23:44 SAPKLFRN18.R3P
-rw-rw-r-- 1 r3padm sapsys 35372350 Aug 15 23:44 SAPKLPTN18.R3P
orar3p> date
Fri Aug 15 23:44:54 PDT 2008
Can anyone help what to do
Thanks
SenthilHello,
did you discover what the cause was for this phase running so slow? And how long did it take to complete in the end?
We are currently running an upgrade of our Development system and have struck the same issue.
I killed the upgrade after the phase had been running for 4 hours and restarted it, but it looks like it is still going to run for a long time.
Regards....John -
Log4j log file not being created
Using websphere for a web app. At first I was getting the error log4j:WARN No appenders could be found for logger....
So I created the property file and I assume correctly referenced it. The error went away and my logging messages are showing up in the websphere console, but the .log file specified in my log4j.properties file is not being written to... it is only writing to my systemOut.log.
If I remove the ROOT.File line it still does not create the file (I've done a search on the IBM directory
#Default log level to ERROR. Other levels are INFO and DEBUG.
log4j.rootLogger=INFO,ROOT
log4j.appender.ROOT=org.apache.log4j.RollingFileAppender
log4j.appender.ROOT.File=c:\myapplication.log
log4j.appender.ROOT.MaxFileSize=1000KB
#Keep 5 old files around.
log4j.appender.ROOT.MaxBackupIndex=5
log4j.appender.ROOT.layout=org.apache.log4j.PatternLayout
#Format almost same as WebSphere's common log format.
log4j.appender.ROOT.layout.ConversionPattern=[%d] %t %c %-5p - %m%n
#Optionally override log level of individual packages or classes
log4j.logger.com.webage.ejbs=INFO
private static final Logger logger = Logger.getLogger(LoginAction.class);
public ActionForward execute(ActionMapping mapping, ActionForm form,
HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException {
initializeLogger();
private void initializeLogger() {
org.apache.log4j.BasicConfigurator.configure();
//trying the above just to get it to work.. because by default this
//should look in WEB-INF/classes/log4j.properties... I thought
/*try {
String log4jUrl = servlet.getServletContext().getInitParameter(
"LOG4J_XML");
if (!(log4jUrl == null || log4jUrl.equals("")))
DOMConfigurator.configure(servlet.getServletContext()
.getResource(log4jUrl));
} catch (MalformedURLException e) {
e.printStackTrace();
} catch (FactoryConfigurationError e) {
e.printStackTrace();
} Edited by: gmachamer on Nov 30, 2007 6:37 AMok changed to xml file and found a few things out.
now when I debug though the logger that was created has an empty level... but if I look at the parent logger it is correctly pulling the root logger from my xml (if I change the priority attribute then it changes when debugging the code)
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="true">
<!-- this appender would be the same as having a System.out -->
<appender name="console" class="org.apache.log4j.ConsoleAppender">
<param name="Target" value="System.out"/>
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%-5p %c{1} - %m%n"/>
</layout>
</appender>
<appender name="rollingFileAppender" class="org.apache.log4j.RollingFileAppender">
<!-- name and location of the file to log to -->
<param name="File" value="c:/appLog.log"/>
<!-- the maximum size the file will be before it rolls the file -->
<param name="MaxFileSize" value="1000kb"/>
<!-- the number of backups you want to maintain -->
<param name="MaxBackupIndex" value="5"/>
<!--
This is the layout of your messages, you can do alot with this.
See the java docs for the class PatternLayout for an explanation of
the different values you can have.
-->
<layout class="org.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%t %-5p %c{2} - %m%n"/>
</layout>
</appender>
<root>
<priority value ="error" />
<appender-ref ref="rollingFileAppender" />
<appender-ref ref="console" />
</root>
</log4j:configuration> -
Cannot publish get error message - log file not being created
When trying to publish a FlashHelp project, I get an error
message window that says "Publishing has been cancelled. Failed to
create file: (project name).log "
When I click okay in the message window, the publishing
process stops. However, if I look in the SSL folder, I see the log
file. It is a text file.
I had this problem in January 09 but it seemed to be an issue
with the password and path in the FTP command window. I fixed it
and it worked fine. However, I haven't published since the end of
January. Now, when I try to publish, it is giving me the same error
message. I checked and reviewed the FTP window fields and they are
fine. But I'm still getting the error message and can't publish.
Why?
I need to get this problem fixed ASAP and ensure that it
doesn't occur again. What's strange is that I've got 3 other
projects and this is the only 1 that gets this error message.Yes, the generation worked. I checked the log file that
worked from the time it worked before and it seems to be the same
as the log file that is generated when I get the error message.
I created a new FlashHelp layout and got the same error
message. What's really weird is there is a log file in the SSL
folder but when you click OK in the error message, it stops the
publish function.
Last time I had to blow away the cpd file as if this was a
corrupt project. But that gets to be painful. As I use templates to
put change dates in the footers of topics and templates get lost
when you blow away the cpd.
Any other thoughts? -
Hello experts,
The SiteLog_<appl_name>.log file in the $ORACLE_HOME/j2ee/log directory stopped to be created 2 days ago.
No errors.
Which reason can be for that? How to enable creating this file?
Regards,
RamHi,
Are there any error when login OWA or ECP?
As Ed mentioned, please post specific information about your question for further troubleshooting.
Besides, please check to see if there is a SharedWebConfig.Config file in the following directories:
<install drive>\Program Files\Microsoft\Exchange Server\V15\ClientAccess
<install drive>\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
Also, here’s an thread about miss this file in relevant location. For your reference:
https://social.technet.microsoft.com/Forums/office/en-US/6699ad92-701d-4966-b202-90c9be6bf735/exchange-2013-cu6-event-id-1003?forum=exchangesvrgeneral
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support -
i follow the steps
1.In Application Set profile FND: Debug Log Level to "Statement"
2.restart apache
3.Run debug from help-->diagnostics-->debug
4.Secure debug log file which should be in
select value from v$parameter where name like 'utl_file%'
but the is no log file created i dont know why (these steps are provided by an SR)
thnxWhat about "FND: Debug Log Filename for Middle-Tier" and "FND: Diagnostics" profile options?
Note: 372209.1 - How to Collect an FND Diagnostics Trace (aka FND:Debug)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=372209.1
If the above does not help, set the debug log at the user level and check then.
Note: 390881.1 - How To Set The Debug Log At User Level?
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=390881.1 -
Log files when creating a pdf from PDFMaker Office COM addin
Hello,
I just bought Acrobat Standard to create pdfs on Word 2013.
I'm making a catalog using this two softwares, Word 2013 (latest version with all updates) and Acrobat XI (latest version, 11.0.06). Unfortunately things are not working as I wish, and on some documents almost at the end of the transformation process, it can't save the pdf file or it gives a major word error, exiting word.
When the transformation process is running/ending, are there any logs created to see what happens in case of errors?? If yes, where can I look up for them??Sorry, but when the pdf is created or not (like when happens on this particulary case), I don't see any logs on the same folder.
Let me try to explain my problem in depth. I have a docx, a big file with 200 pages. It's created with Word 2013 but using the 2010 docx format for compatibility reasons. I beggun using the Word x64 but now I'm using the x86 and the problem happens on both and in the same ways.
First. If I try to convert the whole document, most of the times (I'd say 70%) the pdf doesn't get created or the rest of the times (30%) It causes a crash to Word with a dll error. Normally it halts (whether it doesn't create the pdf of halts word) at a certain page, after repaginanting all pages and when it says that is creating page nº X.
I already pinpoint, more or less, where the error is. The error is located on the first pages, more exactly on the index pages. It's not a index created by the Word, it is a set of pages that I manually built with a grid of pictures with each one having a hyperlink to a designated bookmark to a desire page on the document. If I "pdfmaker" the rest of the whole document (without the index pages) I can get the pdf created.
So, the index is where the problem resides. On this thread, http://forums.adobe.com/message/5816803#5816803 , you will see that I had a another problem due to the method used on Word 2003 about hyperlink of images that no longer works (when exporting to pdf) on the latests words versions, at least on the Word 2013. The pdf file was created with no problem, but on the pdf the hyperlinks were not created due to something that M$ has resolved to change between Word 2003 and Word 2007. I found a way to fix that (listed on that thread link). But as I like to invent, on the Field box, on the field options, for this time, I decided to choose the option "Data not stored with the document". That is what is breaking the pdf conversion. Too bad. Now I have to clear the index all the way and start again from the beggining but without that option. I already remake 3 pages and after the conversion the pdf is created. I have to finish the index redone once again and then create the full pdf document to see if any of those errors/halts happen again.
I just wish to see a adobe log to see what type of error this bug produces so it would be possible to adobe crush the bug
P.S. - Sorry if I was too confusiong for anyone to understand what I'm trying to say here
Message was edited by: Onesolo -
Document Processor File not Created
XML Publisher 5.6.2 on 11.5.9 using a Java Concurrent Program to call the following XML control file via the DocumentProcessor class.
<?xml version="1.0" ?>
<xapi:requestset xmlns:xapi="http://xmlns.oracle.com/oxp/xapi">
<xapi:request select="/RXL_AR_CONS_PROJINV/LIST_G_TRX_NUMBER/G_TRX_NUMBER">
<xapi:delivery>
<xapi:filesystem output="/dat/${TRX_NUMBER}"></xapi:filesystem>
</xapi:delivery>
<xapi:document output-type="pdf">
<xapi:template type="rtf" location="/xml/Project-Invoice_v021.rtf"></xapi:template>
</xapi:document>
</xapi:request>
</xapi:requestset>
I fought through the errors generated by the XMLParser and Delivery engine and now everything completes normally and no exceptions appear to be caught by the Java concurrent program. The only problem is that the files are not generated on the directory structure. Is there somewhere else I can go to look at log files or has anyone experienced anything similar?
Thanks.I am still unable to physically create a file in any other directory than /usr/tmp.
The files created in /usr/tmp are owned by applmgr. I am able to create manual files in the other target directories from the command line as applmgr so I am suspecting that this is not an os permissions issue.
Is there some java directory administration required (similar to UTL directories) before java applications will recognize file directories?
Strangely enough, my XMLP temp directory is also pointed to /usr/tmp is it possible that this has something to do with this issue?
Any responses at all would be greatly appreciated. -
Error in creating log files in create script with ASM
In our create script we have:
LOGFILE GROUP 1 ('+REDO1/oradata/cssys/redo01a.log') SIZE 100M;
I'm getting the error ORA-00301: error adding log file '+REDO1/oradata/cssys/redo01a.log' - file cannot be created.
ORA-17502: ksfdcre:4 Failed to create file +REDO1/oradata/cssys/redo01a.log
ORA-15173: entry 'oradata' does not exist in directory '/'
The datafile didn't return an error and there we had DATAFILE '+DATA/oradata/cssys/system01.dbf.........
Not sure why the error occurs on the REDO, the DATA and REDO look fine in ASM. Thanks in advance.I have no personal experience with this, but pl see if MOS Doc 604982.1 (Unable To duplicate Database on ASM From one Server To Another Host) is applicable in your case
HTH
Srini -
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
Maybe you are looking for
-
Why can't I download certain songs/apps onto my iPhone?
I just got a new iPhone 4s, and I was super excited to put all my music on it so I could put more apps on my iPad. The trouble is, when I tried to download my songs onto my iPhone, a lot of them came up with an error saying "... could not be download
-
Can't create file with filename contains user-defined character
Dear all, I got a question about directory listing and file creation. My development OS is Win2K traditional chinese version and my JDK is 1.4.0 Internationation version. My program copy each of file into another directory. I call File.lists() to get
-
System.printing Namespace
Hai frndz. . . . i want to connect remote printer at server side using C# asp.net pls help me frnds. . . .
-
HT1893 i need driver install for HP 8550 COLOR LASER PRINTER. OS 10.5.8
i need driver install for HP 8550 COLOR LASER PRINTER. OS 10.5.8 for both MacBook pro, G% and I mac 20' OS 10.6 Help
-
Convert UPC-E to UPC-A upon insert with UDF
I have the function but I need this function to insert on the PosCode in my Products Table: CREATE TABLE [Pricebook].[Products] ( [PosCode] [dbo].[posCode] NOT NULL, [PosCodeFormat] AS ([dbo].[udf_PosCodeFormat]([PosCode])), [CheckDigit] AS ([dbo].[u