Default Trace and system Log

Hi all,
I have got default trace and system log folders
Default trace - \usr\sap\J2E\JC00\j2ee\cluster\server0\log\.
Security log - \usr\sap\J2E\JC00\j2ee\cluster\server0\log\system
I need to know are these folders specific to setup package created . I mean can i get these folders for one i created on specified date.
Answers would be rewarded
Thanks and Regards
Neha Kapoor

The problem is solved

Similar Messages

Workflow Daemon is stuck in E sourcing CLM and documents are not flowing to approvers.which place should i check for this issue related information i have already checked default traces and Logs

Hi Guys,
We have a situation in our landscape where workflow daemon service is stuck and we have to restart the Esourcing system.
Could you please help here where should i check the cause of the issue.
i have already checked the Default traces and Esourcing traces.
Could you help in identifying the cause.
Regards
Tarun

Hi Tarun,
Open the Document for e.g. Contract Document, on the Document Tab there is an option for Phase Information open that page this will give you all the information related to the phase and where it is stuck, with which user it is pending etc.
Now since the workflow is stuck, either you can restart the Demon Registration via background Task Status. or else Cancel the Workflow so it can be restarted. by doing the below steps.
1) goto Setup
2) open Workflow Definition Under Workflow.
3) now choose the phase at which your Workflow is stuck.
4) open that phase.
5) under Reports Tab there is option for " Current Workflow Processes"
6) open the Current Workflow Processes
7) search the document which is stuck
8) click on the "X" mark = Cancel the workflow process option
9) it will take you to the workflow cancel wizard screen. give the comment why you need to cancel this and click on Finish
10 ) once the Workflow is canceled the phase will go to the Requester review phase and form here you will have to manully move to the next phase. so the workflow can be restarted. once done refresh it.
11) before doing this take Approval from the customer.
If the above does not work and still there is an issue then please check the Pre- Phase script.
Let me know if this works.
Thanks
kanchan

Console message and system.log

Hi,
in the console system.log always apear this message every 30 second:
+Feb 16 02:22:55 Macintosh SystemUIServer[346]: Error: ACInterfaceGetPower() called with invalid interface+
+Feb 16 02:23:25: --- last message repeated 5 times ---+
and every 5 second this other message:
16/02/08 02:40:55 SystemUIServer[346] Error: ACInterfaceGetPower() called with invalid interface
.. and the message look like an infinite loop message.
Is it a problem ?
And i can ear the Internal HD run always.
Thanks on advice for any help
Ale

I just went through a bunch of research on this on my own iMac G5. (BTW - do you have an iMac G5 or an iMac Intel Core Duo? It can't be both)
It comes down to the items that the SystemUIServer is trying to call. if you look at <homefolder>/Library/Preferences/com.apple.systemuiserver.plist and open it with TextEdit, you'll see that, among other things, it references 8 menuExtras -
Battery.menu
Displays.menu
TimeMachine.menu
Bluetooth.menu
AirPort.menu
Volume.menu
Clock.menu
User.menu
While logged in as an administrative user, I launched System Preferences, Activity Monitor, and the Console looking at *+All Messages+*. I got the same ACInterfaceGetPower() error every 5 seconds, too. So I went through the Preferences and deactivated each menu item above, but the messages continued to appear.
I had two items that might have been causing a problem. The first was the fact that I had the AirPort signal showing up in the menu bar, even though the Network location I have set up does not have AirPort as an available service. I added the Airport service back in, disabled the menu icon, removed the AirPort service again, and Applied the changes. I'm pretty sure the error message was still appearing at this point.
The big change came when I opened up Accounts. First, I went to the Login Items section for my current user. I noticed that the EyeTV Helper and an Adobe process were both there along with the iTunes Helper process. I removed the first two using the "-" at the bottom. That actually appeared to fix it, but I proceeded to the Login Options section and disabled *Fast User Switching*. That removes the users from the menu bar. By this time the only thing left in the menu bar was the Spotlight icon.
Switching over to Activity Monitor, I killed the SystemUIServer process. It restarted and the ACInterfaceGetPower() messages did not reappear. I then re-activated each item, one at a time, killing the SystemUiServer after each activation. Again, the messages did not appear. I did not re-activate Bluetooth or AirPort, since I do not need them.
I am no longer getting those messages and the system appears to be running fine right now.
I have an external monitor attached to the iMac G5 as well as 4 FireWire hard drives. I am connected to the outside world via FiOS and I have a 100 Mb CAT-5 connection to that router.

Console and system log help please

During boot-up I get these errors in the system log:
During shutdown (power then restart option) 2-4 times in a block
Aug 15 11:31:16 EPsMBP kernel[0]: (63: coreservicesd)tfp: failed on 0:
During restart 5 times in a block
Aug 15 11:31:20 EPsMBP kernel[0]: (1183: ps)tfp: failed on 0:
Later 5 times in a block
Aug 15 11:31:24 EPsMBP kernel[0]: (1219: ps)tfp: failed on 0:
Later
Aug 15 11:31:59 localhost kernel[0]: USBF: 9.640 Errata bits for controller 0x8086/0x27cc(rev 0x2) are 0x5800
Aug 15 11:31:59 localhost kernel[0]: USB caused wake event (EHCI)
Aug 15 11:31:59 localhost kernel[0]: USBF: 9.659 Errata bits for controller 0x8086/0x27c8(rev 0x2) are 0xe800
Aug 15 11:31:59 localhost kernel[0]: USBF: 9.659 Errata bits for controller 0x8086/0x27c9(rev 0x2) are 0xe800
Aug 15 11:31:59 localhost kernel[0]: USBF: 9.659 Errata bits for controller 0x8086/0x27ca(rev 0x2) are 0xe800
Aug 15 11:31:59 localhost kernel[0]: USBF: 9.659 Errata bits for controller 0x8086/0x27cb(rev 0x2) are 0xe800
Then general under 5 times in a block:
Aug 15 11:32:03 EPsMBP kernel[0]: (49: SystemStarter)tfp: failed on 0:
Also in the console log during boot-up:
NOTE: ignoring this component:
Discovered 0 component = 0x64e6f6 type = imdc subt = 1Bt2 manu = Domi flags = 0
NOTE: ignoring this component:
Discovered 0 component = 0x64e104 type = imdc subt = 1Bt3 manu = Domi flags = 0
NOTE: ignoring this component:
Discovered 0 component = 0x64e154 type = imco subt = 1Bt3 manu = Domi flags = 0
What does this mean? I'm running on a brand new install or 10.4.7 with all firmware updates for my macbok pro. No hardware attached, permissions repaired, disk repaired, memtest checks out OK.
should I be worried?
Thanks
Edd

Exact same issue here!
I think it has to do with some third party app. I've used Kuvvo to automatically get wallpapers from the net en change them.
After I decided to go back to my own wallpapers and removed the Kuvvo app, my wallpaper prefs is crashing.
I tried to reinstall Kuvvo with the hope of fixing broken links / references but to no avail!

.default files and Apache logs in 10g AS(10.1.2.3)

Hi Friends,
I am using Oracle 10g AS (10.1.2.3) and i have some .default files in my Middle Tier and Infra home like
httpd.conf.default , access.conf.default.....
Is it safe to remove these files?
Will these files cause any Vulnerability issue on my server?
Also will Apache Log files cause Vulnerability issue on my server?
Please clarify
Regards,
DB

Default files are there as a backup for those files. If you happen to modify your files without saving a copy then this would take you back to how a typical httpd.conf (for instance, or plsql.conf or sso.properties, etc) would look like.
I do not think they are any greater source of vulnerability than any other backup files you have on your server. I do not delete them either and wouldn't from any of the servers that I administer.
thanks,
AMN

NWA logs and trace does not show the content of Default trace

Hi All,
The content which i see in /usr/sap/SID/DV*/j2ee/cluster/server0/log/default trace
i am unable to see the same in default trace in NWA logs and traces,
It is a 7.0 system..
Coudl you please suggest.
Rgds
S

Hello,
Is it newly built system? Please compare log and trace levels with other java systems in your landscape.
You can give a try as following..
       1.      Goto NWA and click on Log Configurator service.
       2.      Switch to advanced mode.
       3.      Select the Location tab page.
       4.      Choose the location of default.trc file.
       5.      Save the configuration
       6.      Restart JAVA and see.
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Jan 12, 2012 3:36 PM

Error Logs in the Default Trace

Hi All,
Iam getting following eror for every second in the Default Trace log but no users are effected with this log. Can anybody tell me what this error is about .
Date : 12/20/2006
Time : 11:18:43:702
Message : Exception in method: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
[EXCEPTION]
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Severity : Error
Category :
Location : com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()
Application : sap.com/irj
Thread : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Datasource : 34368150:/usr/sap/PP1/JC03/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA4DBF04001100003473000012530004250B918DE14E
Source Name : com.sap.ip.collaboration.rtc
Argument Objs : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Arguments : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
     at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
     at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
     at java.lang.Thread.run(Thread.java:534)
Dsr Component :
Dsr Transaction :
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.ip.collaboration.rtc
ThreadObject : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Transaction :
User : j2ee_guest
Thanks,
Master

I am having this same issue as well. I upgraded our BI and BI Portal to SP12. Everything worked fine. Then I started the BI integration as outlined in OSS note 917950 -> Setting up BEx Web - Problem analysis.doc and restarted the J2EE engine and now I have this same error in the default trace and I can't log into the visual admin as the j2ee_admin user. I get "error while connecting".   But I can connect to the visual admin as myself. If I login to the BI portal as my self and click on user administration I get this error "A required service for the identity management user interface is not available. Contact your system administrator"
Here's the error as seen in the default trace file that keeps repeating.
#1.#0003BA21A6F5005C000000590000595B000439DE957600B4#1189528059902#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration
.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#J2EE_GUEST#0####d71a1250608111dcbcf70
003ba21a6f5#Thread[Thread-57,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: com.sap.engine.se
rvices.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfa
ctory/default/QueueConnectionFactory.
[EXCEPTION]
#1#com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the wh
ole lookup name is jmsfactory/default/QueueConnectionFactory.
        at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
        at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
        at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
        at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
        at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at javax.naming.InitialContext.lookup(InitialContext.java:347)
        at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1238)
        at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1182)
        at java.lang.Thread.run(Thread.java:534)
Also, at the very beginning of the default trace file I see this error:
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null

Unable to view latest default trace in log viewer

Hello all,
We have NW 7.0 J2EE production server. We have a CI and two application servers.
Our SP level is SP18.
The DB is oracle and the operating system in RHEL 4.
I have a problem in viewing the default trace files in log viewer using the visual administrator.
I am able to view the old default trace but unable to view the latest trace data generated.
I am facing this problem when i try to view the logs of a particular application server.
Able to view the latest default trace properly for CI and the other application server. Problem lies only with a single application server.
I have also check the permissions in OS level for the trace files. Everything looks fine.
Could some one give me a clue on how to solve this issue.
Regards,
Chandru

Hello Joey,
The trace file isnt too big....
We have set the file size as 10 MB.
We have some 15 to 16 default trace files for each of the server process and we have 3 server process in that application server.
The ForceSingleTraceFile parameter is set as YES in visual admin.
So the logs will be displayed in visual admin as a single default trace file.
Hope I had provided the inputs you have asked...
Regards,
Chandru

Huge System.log and asl files. Can these be deleted? What may be the casue?

Following on from an earlier posting regarding disappearing disk space, a couple of responses suggested running a disk utility such as OmniDiskSweeper.
I ran this and it highlighted that the private folder, specifically 'private/var/log' is taking up almost 49 GB! There are 2 system log files:
system.log.0 is almost 20 GB and system.log is close to 19 GB and a file, asl is 10 GB
What are these, can they be deleted, and what may have caused them to be so large in the first place?

This was being written repeatedly to the system.log file. I removed the application, restarted the Mac and the problem appears to be resolved
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * _NSAutoreleaseNoPool(): Object 0x25ad980 of class NSCFString autoreleased with no pool in place - just leaking\nStack: (0x939f6dac 0x93923e14 0x9394ff04 0xb0007438 0xb0004b8c 0xc054 0xc618 0x7000e7c8 0x7000dda8 0x7000cf64 0x90358c10 0x903587d4 0x90358718 0x903abb88 0x903582f4 0x90358464 0x903582f4 0x9036dd48 0x7000cad0 0x70005d04 0x7001140c 0x924d6624 0x924d62b0 0x924d6164 0x924d4b34 0x924d47f4 0x924c2de8 0x9232b0c8)
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * -[NSConditionLock unlockWithCondition:]: lock (<NSConditionLock: 0x12c2c0> '(null)') unlocked when not locked
Feb 4 21:45:23 adsl-69-111-166-204 radioSHARKServer[133]: * Break on _NSLockError() to debug.

System.log file are large, and cause a kernel panic when deleting

Hello everyone,
I am trying to solve a dillema. I discovered that over 60GB of my 120GB SSD drive are taken up by system.log files. All 3 are around 20GB. I left my laptop running so none of them are the current one. They are system.log.0, system.log.3 and system.log.4. I have tried several ways to delete them:
Using Disksweeper
At a terminal prompt using sudo rm
At a terminal prompt using sudo su - (to get root access) and then rm -f ....
Rebooting the system in single user mode, mounting the drive and then attempting to delete them
Each time I do, the system reboots with a kernel panic. I have not looked at the panic log yet, but can post that if you need to.
I did look at the end of the current log file to discover there were some issues with programs, and I have fixed it so that these size log files "shouldn't" be generated anymore.
Looking for advice as to how to delete these files! This is driving me nuts. It shouldn't be this hard.
Thanks for any help or insight you can give.

OK, I actually was able to solve this myself. My problem was that ther kernel panic was caused by the journaling. So here is what I had to do:
I temporarily disabled journaling, see here: http://forums.macrumors.com/showthread.php?t=373067
Then I was able to delete the files by starting a terminal session and using sudo rm to delete the files.
Re-enabled journaling (I don't know if it is needed, but it was on before).
Hope this can help someone else in the future.

Time stamp information in default trace file

How to check the time stamp in defaulttrace.trc or application.trc files for logs in XI server.
I have seen following timestamp in above mentioned trace files. But seem to me, during the shutdown time of server, system put the timestamp in trace file.
ERROR       gateway shutdown
TIME        Fri Jun 20 11:01:08 2008
Except for shutdown time, how the system put the timestamp for other activity of system in the default trace and application trace file??
Sometime, i need to check the timestamp to get some specific information in default trace file for some system activities.
is timestamp mentioned in coded form as per following log:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException#
#1.#36CC34C00F02009B000001B500001FF40004510B33EAB76C#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS                          #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException
Thanks
Amar

Hi Amarjit
The timestamp is noted in unix epoch time (java does use this as well). It is this field:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3# 1215008464352 #com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS
The first 10 digits are seconds since epoch. The last 3 digits are milisecondes. Converted in human readable format: 07/02/2008 16:21:04.352
[Unix Time|http://en.wikipedia.org/wiki/Unix_time]
Damn, i remeber having answered this already here in the forums, but i cannot find the thread anymore myself :-(((
Best regards
Michael

Solution for "Error while trying to synchronize Audio and MIDI" and "System Overload" messages

Article for those who hate Logic error windows
Seen in Logic Pro 9.1.7 on Mac OS X Lion 10.7.4
and Logic Pro 9.0.0 on Mac OS X Snow Leopard 10.6.5
Logic Pro:
System Overload.
The audio engine was not able to process all required data in time.
(-10011)
Error while trying to synchronize Audio and MIDI.
Sample Rate xxxxx recognized.
Check conflict between Logic Pro and external device.
The search in the help given as follows: overload occurs when you use a lot of tracks and a lot of effects on them, and the synchronization is lost when the selected MIDI track for recording or playback. Yes, this is all that is written in the resources. And here are useful tips that have been found:
The Bounce function allows the entire instrument track to be recorded as an audio file. This bounced audio file can then be used (as an audio region) on a standard audio track, allowing you to reassign the available processing power for further software instrument tracks. For more details, see "Bouncing Your Project."
You can also make use of the Freeze function to capture the output of a software instrument track, again saving processing power. For details, see "Freezing Tracks in the Arrange Area."
These tips - about the timing. About overload - there are no tips, except as "reducing the number of plug-ins" and "increasing latency". Zero useful tips - I got two errors in the test project with a blank audio track with no effects, MIDI drums and standard synthesizer, it was no aux buses, and the entire project was only a single plugin in the master track.
Here is the configuration of my computer:
iMac12, 2
CPU: Intel Core i5 3,1 GHz
Memory: 4 GB
And here's a project that almost immediately stops Logic, all instruments and plug-ins with the init-patch, ie not the most demanding settings:
It's sad.
When this happened the first time, I could start the project only if the empty audio track has been selected, a track specially designed so that you can at least start the project. Then, this problem has evaporated along with the changing conditions of work and I forgot about it until the last case.
I was looking for the cause of the problem in the console and the system monitor for two days, and finally I found that Logic ping to the network frequently. I remembered the exact time of occurrence of the problem, and system logs revealed that the problems began immediately, as soon as I deactivate the service of the Internet.
Solution: enable the Internet, or add a new network service on a computer with no Internet. I just created the Ethernet connection to the ip address 1.0.0.0
Logic immediately began to sing.

Hi gabaghoul
Yes, it worked for me on four different OS and Logic versions (10.6 - 10.8 and 9.0 - 9.1.6)
It does not work in some cases, hard enough to tell in which one, but you can try, it very easy: go to the net settings and create new Ethernet connection to the ip address 1.0.0.0 and connect LAN cable to the port.
Also you can try to figure out what happens in your system while Logic error occured - fot that you just start Console and search "logicpro"
Pay attention to repetitive events in a console and events with suitable timing, not so far from error
The problem may be related to the GUI or system memory, sometimes turning off Safari (or Chrome, others browsers) might help.
Message was edited by: spred

RPC client access log and IIS log, difference??

RPC logging is in "C:\Program Files\Microsoft\Exchange Server\V14\Logging\RPC Client Access" by default.
And IIS logs is in "C:\inetpub\logs\LogFiles\W3SVC1" by default.
Just want to know which client will generate which Log?
For example, exchange server 2010 supports:
Outlook Web App
Outlook anywhere
Exchange ActiveSync
POP3 and IMAP4
Autodiscover
So far as I know, "exchange activesync" is always appear in IIS log. But outlook users(all in domain), most of them are always appear in RPC log, but sometime a few users appear in IIS log.
For example:(IIS log)
2014-03-31 00:01:51 172.23.0.100 POST /EWS/Exchange.asmx - 443 TEST\alice 172.26.0.41 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7116;+Pro) - 200 0 0 312
RPC log:
2014-03-31T00:42:09.964Z,1024,1,/o=first organization/ou=exchange administrative group(fydibohf23spdlt) /cn=recipients/cn=alice,,OUTLOOK.EXE,14.0.7108.5000,Cached,,,ncacn_http,,OwnerLogon,0,00:00:00.0156287,,
I want to understand the logging rules, please help?

Hi, Steve:
Thanks very much for your reply. I have a question to your reply here.
RPC-->Outlook clients, and then EWS(includes Outlook 2011??) What's the difference between Outlook clients and Outlook 2011(I think it should be 2010?), but is that Outlook 2010 not belong to 'Outlook clients'?
Best Regards,
Ryo

Safari system.log messages - what do they mean?

hey could use any help regarding some messages i received in BOTH console.log and system.log regarding Safari:
Oct 31 20:01:23 nicks-Computer /Applications/Safari.app/Contents/MacOS/Safari: * Warning: ATSUSetFontFallbacks has been deprecated. Use ATSUFontFallbacks objects instead. *
Oct 31 21:55:06 nicks-Computer /Applications/Safari.app/Contents/MacOS/Safari: * Warning: Line option kATSLineIsDisplayOnly has been deprecated. *
any help? thanks,
imac g4 Mac OS X (10.3.9) have 5th generation ipod

Doesn't affect the User. More for developer information. I guess one of those things that ought to be hidden from the non-developers view.

When upgrading from 10.7 to 10.8.2, are the system.log files backed up anywhere?

One of my clients needs to confirm whether a USB device was plugged into their computer between two dates in September 2012 because they're worried some sensitive data may have been stolen. However, their computers were upgraded from 10.7 to 10.8.2 on the 29th of November 2012, and since the kernel.log and system.log files have now been combined in this update, it has obviously created a new file in the new format. Sadly, this has only come to light now, and there appear to be no backups of the whole drive from before this date.
Does anyone know if the 10.7 logfiles would have been preserved anywhere during the upgrade, or are they lost for good?

No, the merging operation deletes the old files during upgrading the OS X. Have you tried searching even hidden files starting at the root level so see if anything has been hidden away somewhere? I haven't seen the upgrade do that but if this is really important it may be worth the effort.

Default Trace and system Log

Similar Messages

Maybe you are looking for