cancel
Showing results for 
Search instead for 
Did you mean: 

Lots of error in server's system log

Former Member
0 Kudos

I just installed SAPNetWeaver04_SP16Preview in a fresh Windows 2003 SP1. I am running it in VMware 1.0.3. I assigned VM 924MB RAM, 32GB hard drive and 2 Processors. Running JDK 1.4.2_09

After installation, I start the <b>J2E</b> from <b>SAP Management Console</b>. After the server is completely running. I look at the log (<i>\usr\sap\J2E\JC00\j2ee\cluster\server0\log\system\logging.0.log</i>). It is 1600KB now. I see a lot of similar errors. They are all from com.sap.tc.logging.FileLogInfoData

I post the very first one here

#1.5#000C299515C5000F0000000000000A4C000430B464E10B63#1179451251588#/System/Logging##com.sap.tc.logging.FileLogInfoData.[getFileHeader(String fileName, int cntHeadLines)]#######SAPEngine_System_Thread[impl:5]_93##0#0#Warning##Java#SAP_LOGGING_UNEXPECTED##Unexcepted error occured on {0}!#1#FileHeader parsing#
#1.5#000C299515C5000F0000000100000A4C000430B464E11826#1179451251588#/System/Logging##/System/Logging#######SAPEngine_System_Thread[impl:5]_93##0#0#Path##Java###Caught {0}#1#java.lang.Exception: .\log\services\log_configurator\default.0.trc (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:1484)
	at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.activateLogger(LogConfiguratorServiceFrameImpl.java:225)
	at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:134)
	at com.sap.engine.services.log_configurator.LogConfiguratorApplicationServiceFrame.start(LogConfiguratorApplicationServiceFrame.java:51)
	at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
	at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
	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:105)

The rest log are similar. They have different target file location. And they all throw at at com.sap.tc.logging.FileLogInfoData.getEOLLength(FileLogInfoData.java:432).

On the other side, I see an error from the log file ( <i>C:\usr\sap\J2E\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc</i>)

#
#1.5#000C299515C500390000003000000A4C000430B4667B0658#1179451278478#com.sapmarkets.bam.jmxadapter.util.LogDirectory##com.sapmarkets.bam.jmxadapter.util.LogDirectory#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###Error writing log directory entryC:\tmp\MARCH_J2E_00_6474950_lv_.xml (The system cannot find the path specified)#
#1.5#000C299515C500390000003200000A4C000430B4667B07B3#1179451278478#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: Error occured while trying to register	a new log#
#1.5#000C299515C500390000003400000A4C000430B4667B08D4#1179451278478#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###com.sapmarkets.bam.util.BAMRuntimeException: <--Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.#
#1.5#000C299515C500390000003600000A4C000430B4667B0D97#1179451278494#com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler##com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler#######SAPEngine_System_Thread[impl:5]_82##0#0#Error#1#/System/Server#Plain###Originated from: com.sapmarkets.bam.util.BAMRuntimeException: <--Localization failed: ResourceBundle='com.sapmarkets.bam.util.LogViewerMessages', ID='Error while writing to directory.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Error while writing to directory.
	at com.sapmarkets.bam.jmxadapter.util.LogDirectory.write(LogDirectory.java:779)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.addToDirectory(AbstractFileLogHandler.java:361)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogAsMBean(AbstractFileLogHandler.java:249)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:151)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:85)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.registerLogMBean(AbstractFileLogHandler.java:402)
	at com.sapmarkets.bam.jmxadapter.sapjlog.AbstractFileLogHandler.handleEvent(AbstractFileLogHandler.java:469)
	at com.sap.tc.logging.LoggingManager.addListener(LoggingManager.java:116)
	at com.sapmarkets.bam.jmxadapter.sapjlog.LogTypeConfiguratorImpl.configure(LogTypeConfiguratorImpl.java:98)
	at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypeConfigurators(MBeanRegistrar.java:106)
	at com.sapmarkets.bam.j2ee.services.logviewer.MBeanRegistrar.registerLogTypes(MBeanRegistrar.java:179)
	at com.sapmarkets.bam.jmx.connector.AbstractLVServer.init(AbstractLVServer.java:62)
	at com.sapmarkets.bam.j2ee.services.logviewer.LogViewer.start(LogViewer.java:158)
	at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
	at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
	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:105)

Not sure if they are related. However, I don't have folder with is "<b>C:\tmp\</b>". I only have "<b>C:\TEMP\</b>". I checked the system variables, "%TEMP%" and "%TMP" are point to "%SystemRoot%\TEMP".

So how can I fix all exception in the logs. What should I look at first? My goal is to use SAP logging. I tried on the other system and what I got is similar error from FileLogInfoData. So I thought I may mess up the setting. I install on the fresh OS, I have no clue now. Any suggestion would help.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

1.Try using latest JDK,j2sdk1.4.2_13.

2.Check if environment variables <b>JAVA_HOME</b> and <b>path</b> are set correctly

3.Check if there is sufficient space in installation drive.

4.try connecting to database and see if data logs are full.remove unnecessary logs in database.

5.manually start all services through telnet or visual admin.

reward points if helpful.........

Former Member
0 Kudos

Hi

Are you using any usage types in this jave stack?To start with check all the system component information. Check defaultTrace.trc also. Check all the service users like sapjsf and j2ee_admin. Like if these users are locked. Are you using a central SLD?

I faced the same problem in one of my installation i tried a lot....I ended up in java patch upgrade and after that it worked perfectly fine.