Failed to start e-TEST agent: error starting agent: \ne-TEST process ...
Hi,
wihout changing the version or so we suddenly we experience the following error at status page (although the monitored web-page is fine):
Current alert: Failed to start e-TEST agent: error starting agent: \ne-TEST process has not established socket in 30 seconds.
Any ideas?
Thanks in advance
Hi emposadi,
It looks like the e-Load server is having trouble communicating with the agent. Are you running the load test using an agent on the same machine or remote machine? You might want to see if a process has grabbed a port that the server communicates with the agent on. I would reboot the machines in question, shut down the Empirix Application Server and verify that ports 1099 and 9001 are not in use. Those are the ports that e-Load uses to communicate with the agent.
-GateCity_QA
Similar Messages
-
After upgrading to 27, firefox will not start. Saw an error message during the upgrade process.
After upgrading to 27, firefox will not start. Saw an error message during the upgrade process but cannot remember.
Tried to run firefox.exe -P but receive error message:
XML Parsing error: undefined entity
Location: chrome://mozapps/content/profile/profileSelection.xul
Line number 18, Column 1:
<dialog
^
Running on Windows XP SP3. No problem whatsoever before upgrading to 27. Sending this from Chrome as I cannot open Firefox at all.Thanks jschaer2000: after starting it once in safe mode, I closed Mozilla and tried several restarts in normal mode. So far, all worked:-)
Thank you very much again.
Still the automatic update process bothers me: it took me several days to discover the reason to the malfunction, since when I removed the problematic version from Add and Remove Programs, I didn't pay attention at first that it was another version, not v26 which I installed from my folder.
In addition, I like to save the installation files before I run new programs and if I didn't have v26 exe file, I couldn't have operated Mozilla at all. Not that it was fun to remove and install again each time v27 didn't react, but it was better than nothing, I still prefer Mozilla over its competition. -
Orphaned Agent Error - Unexpected Agent Exit. Code = 128
Hello,
I am currently running tests using the Load Testing Tool bundled with Oracle Application Testing Suit, to run performance tests for a web services application. Everything was running smoothly until I tried to run a total of 2000 users (200 users across 10 agent machines), which started to cause the tool to return "Orphaned Agent" errors ("Unexpected Agent exit. Code = 128" or "Unexpected Agent exit. Code = 1"). The Orphaned Agent errors aren't occuring right away, after user ramp up, it can be another 5 minutes or so before they are actually occuring. CPU and memory usage on the agent machines is not being maxed out (approx 30% usage).
I am using build 8.50.0260 of OATS.
I have checked the EmpStart.log file, and I am getting the following exception:
ERROR [EmpStartMain] oracle.oats.empstart.PortListener
java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at oracle.oats.utilities.DHAgreementHelper.performKeyAgreement(DHAgreementHelper.java:159)
at oracle.oats.utilities.SecureServerSocket.accept(SecureServerSocket.java:41)
at oracle.oats.empstart.PortListener.readFromSocket(PortListener.java:121)
at oracle.oats.empstart.PortListener.run(PortListener.java:84)
at java.lang.Thread.run(Unknown Source)
ERROR [EmpStartMain] oracle.oats.empstart.PortListener
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at java.io.DataOutputStream.write(Unknown Source)
at java.io.FilterOutputStream.write(Unknown Source)
at oracle.oats.utilities.DHAgreementHelper.performKeyAgreement(DHAgreementHelper.java:156)
at oracle.oats.utilities.SecureServerSocket.accept(SecureServerSocket.java:41)
at oracle.oats.empstart.PortListener.readFromSocket(PortListener.java:121)
at oracle.oats.empstart.PortListener.run(PortListener.java:84)
at java.lang.Thread.run(Unknown Source)
Hopefully someone can point me in the right direction :)
MichaelHi Alex,
Thank-you for your prompt response. I reduced the number of agents I was using to 5, with 400 users on each (2000 users total). I then changed the Tools > Options > Scenario Defaults to use Java Mode and updated the maximum heap size to both 512 and 1024, however the error still occurs.
Here is the log from one of the agent machines
INFO | jvm 1 | 2009/11/24 15:47:38 | INFO [AgentProcess] Launched process 3753803 for agent agId12902_rnd1409932225
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [AgentProcess] Exited process 3753803 for agent agId12902_rnd1409932225
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [ProcessRunner] Agent x33620:1099:queue/AgentPoolNotificationQueue:agId12902_rnd1409932225 exited, code = 128
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Messenger Loaded....
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Try server=x33620:1099 queue=queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Got ConnectionFactory
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Got queue queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Created queue connection.
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Created queue session.
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Connected to server=x33620:1099 queue=queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Try server=x33620:1099 queue=queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Got ConnectionFactory
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Got queue queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Created queue connection.
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Created queue session.
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Messenger] Connected to server=x33620:1099 queue=queue/AgentPoolNotificationQueue
INFO | jvm 1 | 2009/11/24 15:52:03 | INFO [Request] [Host:x33620;Port:1099;Requestor ID:null;Requestor Key:JBOSS-x33620-1099;Requestor Queue:queue/AgentPoolNotificationQueue;Request ID:131;Request:stopagent;] - authentication successfull
INFO | jvm 1 | 2009/11/24 15:52:03 | ERROR [EmpStartMain] Unknown agent ID: agId12902_rnd1409932225
So it looks as though the memory is OK, however, for some reason half-way through the test the agent ID becomes unknown. This error is the same across all the agents.
Thanks in advance,
Michael -
Failed to Open FR report With Error code 500 - 'unable to process request'
I am running a load test against PBCS service. The service is load-balanced with 2 managed servers : EPMServer0 and EPMServer1
When I put the loads with 60 VUs -- all visiting FR reports, the service runs without error. But when the VU# increased to 90, it began to respond with Error code 500 - 'unable to process request'.
I tried to correlate the FRLogging logs to the errors, and found during the time those error happens, there are logs like this:
>>>>>>>>>>>>>>>>>>>>>>>>>>
[2013-09-27T05:21:29.325+00:00] [EPMServer0] [WARNING] [00365] [oracle.EPMFR.core] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: sysname50134114.PerfUser0439] [ecid: 004tpQ^VFHT7m3RLIYDCif0007a30002bD,0:2:1:1] [APP: FINANCIALREPORTING#11.1.2.0] [SRC_CLASS: com.hyperion.reporting.connection.UserConnection] [SRC_METHOD: openConnection] User authentication information is invalid. Unable to connect to datasource.[[
com.hyperion.reporting.util.HyperionReportException: Error connecting to database connection Vision:Plan1: Failed to sync with user provisioning.com.hyperion.planning.HspRuntimeException
at com.hyperion.reporting.connection.UserConnection.openConnection(Unknown Source)
at com.hyperion.reporting.connection.UserConnection.openConnection(Unknown Source)
at com.hyperion.reporting.connection.UserConnection.<init>(Unknown Source)
at com.hyperion.reporting.connection.ConnectionManager.getConnection(Unknown Source)
at com.hyperion.reporting.connection.ConnectionManager.getCube(Unknown Source)
at com.hyperion.reporting.connection.ConnectionManager.getCube(Unknown Source)
at com.hyperion.reporting.webviewer.WebDynamicReport.validateDatasources(Unknown Source)
at jsp_servlet._modules._com._hyperion._reporting._web._reportviewer.__hrhtmlreport._jspService(__hrhtmlreport.java:1999)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.hyperion.reporting.webviewer.HRSecurePagesFilter.needAuthentication(Unknown Source)
at com.hyperion.reporting.webviewer.HRSecurePagesFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.hyperion.reporting.webviewer.FRClusterHelper.doFilter(Unknown Source)
>>>>>>>>>>>>>>>>>>>>>>>>>
It looks like the servlet failed to open the datasource connection while handling the FR requests. But there are several data sources. My questions are:
1) Which datasource is corresponding to the issue? Is it EPMSystemRegistry?
2) What is the recommended configuration for the connection pool max capacity setting? -- current setting for EPMSystemRegistry is 30
3) Whether it could be a connection leak problem as only 90 concurrent end user is visiting and it failed to connect?
Thanks,
Ellick Lu
Type
JNDI Name
Targets
aif_datasource
Generic
jdbc/aif_datasource
EPMServer
calc_datasource
Generic
jdbc/calc_datasource
EPMServer
EPMSystemRegistry
Generic
jdbc/EPMSystemRegistry
EPMServer
odiMasterRepository
Generic
jdbc/odiMasterRepository
EPMServer
planning_datasource
Generic
jdbc/planning_datasource
EPMServer
raframework_datasource
Generic
jdbc/raframework_datasource
EPMServerIt is checking for Database connection in Workspace. Check Editing Database Connections
Can those users login to Planning? Do they have correct security setup (I guess not)
Regards
Celvin
http://www.orahyplabs.com -
System launchd agent error starting/stopping system processes
I installed PHP 5.4 via brew package manager. I kept the system Apache & configured it to work with this version of PHP rather than the system copy. I used launchctl (sudo launchctl load -w /System/Library/LaunchDaemons/org.apache.httpd.plist) to load apache automatically on boot. I created a Sites folder for Mountain Lion and opened http://localhost/index.php and got the standard PHP 5.4 system config page showing that everything is working fine. I checked my system logs just to be sure nothing was out of the ordinary and I am seeing these errors in my log even though everything seems to be fine and I am not seeing system crashes, slow runtimes, etc:
9/5/12 2:38:51.292 PM com.apple.launchd[1]: (org.freeradius.radiusd[3055]) Exited with code: 1
9/5/12 2:38:51.292 PM com.apple.launchd[1]: (org.freeradius.radiusd[3055]) Exited with code: 1
9/5/12 2:38:51.292 PM com.apple.launchd[1]: (org.freeradius.radiusd) Throttling respawn: Will start in 10 seconds
9/5/12 2:38:56.686 PM com.apple.launchd[1]: (org.isc.named[3056]) Exited with code: 1
9/5/12 2:38:56.686 PM com.apple.launchd[1]: (org.isc.named) Throttling respawn: Will start in 10 seconds
9/5/12 2:39:01.328 PM com.apple.launchd[1]: (org.freeradius.radiusd[3057]) Exited with code: 1
9/5/12 2:39:01.328 PM com.apple.launchd[1]: (org.freeradius.radiusd) Throttling respawn: Will start in 10 seconds
9/5/12 2:39:06.700 PM com.apple.launchd[1]: (org.isc.named[3058]) Exited with code: 1
9/5/12 2:39:06.700 PM com.apple.launchd[1]: (org.isc.named) Throttling respawn: Will start in 10 seconds
9/5/12 2:39:11.359 PM com.apple.launchd[1]: (org.freeradius.radiusd[3060]) Exited with code: 1
9/5/12 2:39:11.359 PM com.apple.launchd[1]: (org.freeradius.radiusd) Throttling respawn: Will start in 10 seconds
9/5/12 2:39:16.715 PM com.apple.launchd[1]: (org.isc.named[3061]) Exited with code: 1
9/5/12 2:39:16.715 PM com.apple.launchd[1]: (org.isc.named) Throttling respawn: Will start in 10 seconds
9/5/12 2:43:17.060 PM named[3171]: starting BIND 9.8.1-P1 -f
9/5/12 2:43:17.060 PM named[3171]: built with '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--disable-dependency-tracking' '--prefix=/usr' '--sysconfdir=/private/etc' '--localstatedir=/private/var' '--enable-atomic=no' '--with-openssl=yes' '--with-gssapi=yes' '--enable-symtable=none' 'CC=/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.8.xctoolchain/u sr/bin/cc' 'CFLAGS=-arch i386 -arch x86_64 -g -Os -pipe -gdwarf-2 ' 'LDFLAGS=-arch i386 -arch x86_64 -framework IOKit -framework CoreFoundation' 'CXX=/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.8.xctoolchain/ usr/bin/c++' 'CXXFLAGS=-arch i386 -arch x86_64 -g -Os -pipe '
9/5/12 2:43:17.064 PM named[3171]: /private/etc/named.conf:4: open: /etc/rndc.key: file not found
9/5/12 2:43:17.064 PM named[3171]: loading configuration: file not found
9/5/12 2:43:17.064 PM named[3171]: exiting (due to fatal error)
9/5/12 2:43:17.065 PM com.apple.launchd[1]: (org.isc.named[3171]) Exited with code: 1
9/5/12 2:43:17.065 PM com.apple.launchd[1]: (org.isc.named) Throttling respawn: Will start in 10 seconds
9/5/12 2:43:22.164 PM com.apple.launchd[1]: (org.freeradius.radiusd[3173]) Exited with code: 1
9/5/12 2:43:22.164 PM com.apple.launchd[1]: (org.freeradius.radiusd) Throttling respawn: Will start in 10 seconds
9/5/12 2:43:27.075 PM named[3174]: starting BIND 9.8.1-P1 -f
Process: SleepServicesD [48]
Path: /System/Library/CoreServices/SleepServicesD
Identifier: SleepServicesD
Version: 1.43
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 0
Date/Time: 2012-09-05 07:47:33.363 -0400
OS Version: Mac OS X 10.8.1 (12B19)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Assertion failed: (ret == kIOReturnSuccess), function -[PowerStateTracker init], file /SourceCache/SleepServicesD_executables/SleepServicesD-1.43/SleepServicesD/Powe rStateTracker.m, line 148.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8cbbe212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff897deb34 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff89822dfa abort + 143
3 libsystem_c.dylib 0x00007fff89823dd5 __assert_rtn + 146
4 SleepServicesD 0x000000010ce44e09 0x10ce43000 + 7689
5 SleepServicesD 0x000000010ce43e75 0x10ce43000 + 3701
6 libdyld.dylib 0x00007fff87b2b7e1 start + 1
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff8cbbed16 kevent + 10
1 libdispatch.dylib 0x00007fff8bba8e26 _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff8bba8a2a _dispatch_mgr_thread + 54
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff52dbcd28 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff52dbcd50 rsp: 0x00007fff52dbcd28
r8: 0x00007fff77590278 r9: 0x0000000000000094 r10: 0x0000000020000000 r11: 0x0000000000000206
r12: 0x000000010ce4e16e r13: 0x000000010ce4e050 r14: 0x00007fff77591180 r15: 0x000000010ce4e06a
rip: 0x00007fff8cbbe212 rfl: 0x0000000000000206 cr2: 0x00007fff77589fe8
Logical CPU: 0
Binary Images:
0x10ce43000 - 0x10ce50fff SleepServicesD (1.43) <0FDAEB5E-4E24-3836-AFBD-81E309DEB0DC> /System/Library/CoreServices/SleepServicesD
0x7fff6ca43000 - 0x7fff6ca7793f dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
0x7fff87083000 - 0x7fff870d4fff com.apple.SystemConfiguration (1.12 - 1.12) <7A8300B5-F5B3-39F0-A4B2-4C0C293FA29F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff871b7000 - 0x7fff871dbff7 libc++abi.dylib (24.2) <340E7C7B-DC93-3AA2-B015-B1C9541EC255> /usr/lib/libc++abi.dylib
0x7fff87314000 - 0x7fff87315ff7 libSystem.B.dylib (169.3) <365477AB-D641-389D-B8F4-A1FAE9657EEE> /usr/lib/libSystem.B.dylib
0x7fff87382000 - 0x7fff873a3ff7 libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
0x7fff8754e000 - 0x7fff875fffff com.apple.LaunchServices (539 - 539) <04FA5C61-6349-3841-9609-B650B6222800> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x7fff87772000 - 0x7fff877a8fff libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
0x7fff877d8000 - 0x7fff87827ff7 libcorecrypto.dylib (106) <57BC99C6-3C3F-344C-BDD6-25E845D956F2> /usr/lib/system/libcorecrypto.dylib
0x7fff87935000 - 0x7fff87936ff7 libdnsinfo.dylib (453.16) <38A3E0F4-E34C-3D45-A2C9-4CDE2DF007BD> /usr/lib/system/libdnsinfo.dylib
0x7fff87aca000 - 0x7fff87b27ff7 com.apple.AE (645 - 645) <9C3E54BA-EE6B-3F02-8775-9C4AF40F40CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff87b29000 - 0x7fff87b2cff7 libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
0x7fff893df000 - 0x7fff8944cfff com.apple.datadetectorscore (4.0 - 269.1) <C94C372B-3821-3A46-A8C2-091AB1CFF7F4> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff897c9000 - 0x7fff89895fef libsystem_c.dylib (825.24) <16B6B86C-53EE-36E8-AC2B-4AADC1008098> /usr/lib/system/libsystem_c.dylib
0x7fff89e95000 - 0x7fff89e96fff liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
0x7fff89ec4000 - 0x7fff89ec7fff com.apple.TCC (1.0 - 1) <DE7ECAC3-BD08-323A-9C12-EE4A49B72871> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x7fff8a2ae000 - 0x7fff8a421ff7 com.apple.CFNetwork (596.1 - 596.1) <62830510-738D-3719-AD51-68E816B13BB7> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff8a438000 - 0x7fff8a440ff7 libsystem_dnssd.dylib (379.27.1) <B9F7B01D-8FAF-3CA5-909E-4D52B8D2DD8A> /usr/lib/system/libsystem_dnssd.dylib
0x7fff8a914000 - 0x7fff8a97dfff libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
0x7fff8a989000 - 0x7fff8a989fff com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x7fff8a9a5000 - 0x7fff8a9a7fff libquarantine.dylib (52) <4BE2E642-A14F-340A-B482-5BD2AEFD9C24> /usr/lib/system/libquarantine.dylib
0x7fff8b648000 - 0x7fff8b656ff7 libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
0x7fff8bab4000 - 0x7fff8bae5fff com.apple.DictionaryServices (1.2 - 184) <B37F9A90-8954-3DEC-A216-8ABB15C615A1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x7fff8bba4000 - 0x7fff8bbb9ff7 libdispatch.dylib (228.18) <0B6B6E7F-4D8A-3F3B-A4BF-6CF34638DBBB> /usr/lib/system/libdispatch.dylib
0x7fff8bbbc000 - 0x7fff8bbbcfff libOpenScriptingUtil.dylib (148) <4DB14EC4-422C-3AE8-83BF-354FEC197FD3> /usr/lib/libOpenScriptingUtil.dylib
0x7fff8bbbd000 - 0x7fff8bc3efff com.apple.Metadata (10.7.0 - 707.1) <ED39A710-1D87-3207-BB7D-4465B2673C1D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x7fff8bd19000 - 0x7fff8bd26fff libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
0x7fff8bd82000 - 0x7fff8bd8afff liblaunch.dylib (442.21) <224CB010-6CF8-3FC2-885C-6F80330321EB> /usr/lib/system/liblaunch.dylib
0x7fff8bd8b000 - 0x7fff8bd8cfff libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
0x7fff8bdc2000 - 0x7fff8bdc7fff libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
0x7fff8c7ee000 - 0x7fff8cb05ff7 com.apple.CoreServices.CarbonCore (1037 - 1037) <5127E2AB-AE98-3393-AEF6-CA8C1090F921> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x7fff8cbaa000 - 0x7fff8cbabff7 libremovefile.dylib (23.1) <DBBFAF35-AC78-3856-92F6-6E4FD9DF14A2> /usr/lib/system/libremovefile.dylib
0x7fff8cbac000 - 0x7fff8cbc7ff7 libsystem_kernel.dylib (2050.9.2) <F646589B-13F8-3685-8C17-92C77993AE86> /usr/lib/system/libsystem_kernel.dylib
0x7fff8d38e000 - 0x7fff8d3a5fff com.apple.GenerationalStorage (1.1 - 132.1) <EAB41613-0145-3CE5-AA60-A8A791A3EE22> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x7fff8d600000 - 0x7fff8d601fff libDiagnosticMessagesClient.dylib (7) <56A70657-E8C2-3804-AB87-77DC100512A4> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff8e379000 - 0x7fff8e3a4fff libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
0x7fff8e3a5000 - 0x7fff8e3aafff libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
0x7fff8e580000 - 0x7fff8e58fff7 libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
0x7fff8fb43000 - 0x7fff8fb49fff libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
0x7fff8fb96000 - 0x7fff8fb9dfff libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
0x7fff8fb9e000 - 0x7fff8fefaff7 com.apple.Foundation (6.8 - 945) <0C972F73-0C07-3384-98F2-B176E0289494> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff8ffbd000 - 0x7fff8ffbfff7 libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
0x7fff900df000 - 0x7fff900edff7 libkxld.dylib (2050.9.2) <4BEE9BC3-3708-330E-89D6-03E715D712CC> /usr/lib/system/libkxld.dylib
0x7fff90313000 - 0x7fff90410fff libsqlite3.dylib (138) <8D6A6805-1494-30D1-9F2A-F58FA3C0D7EE> /usr/lib/libsqlite3.dylib
0x7fff9044b000 - 0x7fff904d8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x7fff905f7000 - 0x7fff9070fa27 libobjc.A.dylib (532) <9FA80CDA-97F4-3801-8879-0C1B976BC5CA> /usr/lib/libobjc.A.dylib
0x7fff90767000 - 0x7fff90772fff libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
0x7fff9084e000 - 0x7fff90855fff com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x7fff90856000 - 0x7fff90868ff7 libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
0x7fff90904000 - 0x7fff90904fff libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
0x7fff90988000 - 0x7fff9099ffff com.apple.CFOpenDirectory (10.8 - 151.10) <FFBBA538-00B5-334E-BA5B-C8AD6CDCDA14> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff91197000 - 0x7fff9119dfff com.apple.DiskArbitration (2.5 - 2.5) <348AC0CC-6BCE-3416-9141-A5C1164EDDFF> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x7fff912a3000 - 0x7fff9148cfff com.apple.CoreFoundation (6.8 - 744) <47AEA7C7-EF9B-3FC6-AEBF-CE02FC650301> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff9194b000 - 0x7fff91959fff libcommonCrypto.dylib (60026) <2D6537F5-1B5E-305C-A1CF-D1FA80CA3939> /usr/lib/system/libcommonCrypto.dylib
0x7fff91cb1000 - 0x7fff91cbeff7 com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff91cbf000 - 0x7fff91cc5ff7 libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
0x7fff91cc6000 - 0x7fff91d33ff7 com.apple.framework.IOKit (2.0 - 755.9.7) <9B7C5E7A-3F7A-3E70-8179-4384992B84E0> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x7fff91f9d000 - 0x7fff9226aff7 com.apple.security (7.0 - 55178.0.1) <8102877E-C866-33D4-A947-02FC7F4BAA95> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x7fff924c7000 - 0x7fff9256dfff com.apple.CoreServices.OSServices (557 - 557) <F5955FD8-E6E1-359F-9D9D-381E55E3EF37> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff925a2000 - 0x7fff9260aff7 libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
0x7fff92615000 - 0x7fff92643ff7 libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
0x7fff928ad000 - 0x7fff928aeff7 libsystem_sandbox.dylib (220) <3C3B03CF-C525-3CB3-8557-62E91B93AC95> /usr/lib/system/libsystem_sandbox.dylib
0x7fff934b2000 - 0x7fff934c5ff7 libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
0x7fff934c6000 - 0x7fff934cafff libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
0x7fff934d7000 - 0x7fff93523ff7 libauto.dylib (185.1) <73CDC482-16E3-3FC7-9BB4-FBA2DA44DBC2> /usr/lib/libauto.dylib
0x7fff93524000 - 0x7fff93546ff7 libxpc.dylib (140.37) <C552985C-2171-3136-A1B9-3AB21CBF7C4A> /usr/lib/system/libxpc.dylib
0x7fff93547000 - 0x7fff93644ff7 libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
0x7fff9380f000 - 0x7fff93a0ffff libicucore.A.dylib (491.11.1) <17E8B610-6B16-3F91-B49C-7CAE0D08E9CF> /usr/lib/libicucore.A.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 21
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=79.5M resident=36.3M(46%) swapped_out_or_unallocated=43.2M(54%)
Writable regions: Total=40.1M written=332K(1%) resident=408K(1%) swapped_out=0K(0%) unallocated=39.7M(99%)
REGION TYPE VIRTUAL
=========== =======
MALLOC 31.3M
MALLOC guard page 32K
STACK GUARD 56.0M
Stack 8712K
VM_ALLOCATE 8K
__DATA 3240K
__LINKEDIT 52.8M
__TEXT 26.7M
__UNICODE 544K
shared memory 12K
=========== =======
TOTAL 179.1M1. Mae sure that the ports you have specified in the Communiation tab are not specified anywhere else, either in PCo or in another application on the PCo worstation. For testing, set either MII or Legacy and use the same port number for each, just don't chec both boxes at the same time.
The Legacy and MII port settings must be different, or you should receive an error in PCo. As Steve mentioned, a port address can only be used once by any application on a given server. Multiple PCo agents using the same port will cause a conflict as will trying to use the same port for both Legacy and MII connector for a single agent. MII 11.5 only supports the Legacy (UDC) Connector, so I suggest that you do not select the MII connector check box and leave the port setting blank. Select Legacy connector and set a port address for that connector.
To determine if a port is available to use, you can open a command prompt and use the command netstat -a -o to list all the ports which are in use. Please note, this is only active ports.
2. I think you will need to get the compatibility issue between xMII 11.5 and PCo 2.1 answered by the PCo team; I have no way of testing this.
MII 11.5 should work with PCo 2.1. Configure the PCo agent to use the Legacy connector. Create a UDC data server in MII and Pco should work like the UDS.
Regards
Chris Carney -
I'm trying to create a development machine where we can test new code without using our physical hardware. I've followed this guide in setting up a simulated device. I can get to step 3.2b, but the device does not show up in the DAQ assistant. In MAX, the device self tests and self calibrates successfully, and when I open the test panels, I see some sort of signal. I assume this is a default simulated input since I haven't told the device to look for anything? Note that the two devices I'm trying to create show up in the Devices and Interfaces section, but that even after running Self-Calibrate, the Self-Calibration date is still unspecified.
When I try to test the device and create a voltage input according to the guide, I am unable to see either device in the DAQ task creator.
Steps 1 and 2 of this guide are obviously satisfied. Step 3 is not, but this is unsurprising since a simulated device wouldn't be found in the Device Manager anyways. Also, I am not running RT, so step 4 is satisfied.
Does anyone have any ideas?
Solved!
Go to Solution.That would be because the PXI 5124 is a digitizer not a analog input device. You need to use the NI SCOPE driver not NI DAQmx
Jeff -
DBW0 - error starting instance
oracle-xe on debian
when I execute /etc/init.d/oraxle-xe start - I get no error message, but no oracle processes are started
see my alert log
paco:/usr/lib/oracle/xe/app/oracle/admin/XE/bdump# more alert_XE.log
Wed Jan 17 14:28:58 2007
Starting ORACLE instance (normal)
Wed Jan 17 14:28:58 2007
WARNING: EINVAL creating segment of size 0x0000000011801000
fix shm parameters in /etc/system or equivalent
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
sessions = 49
sga_target = 293601280
control_files = /usr/lib/oracle/xe/oradata/XE/control.dbf
compatible = 10.2.0.1.0
db_recovery_file_dest = /usr/lib/oracle/xe/app/oracle/flash_recovery_area
db_recovery_file_dest_size= 10737418240
undo_management = AUTO
undo_tablespace = UNDO
remote_login_passwordfile= EXCLUSIVE
dispatchers = (PROTOCOL=TCP) (SERVICE=XEXDB)
shared_servers = 4
local_listener = (ADDRESS = (PROTOCOL=TCP) (HOST=paco) (PORT=1528))
job_queue_processes = 4
background_dump_dest = /usr/lib/oracle/xe/app/oracle/admin/XE/bdump
user_dump_dest = /usr/lib/oracle/xe/app/oracle/admin/XE/udump
core_dump_dest = /usr/lib/oracle/xe/app/oracle/admin/XE/cdump
audit_file_dest = /usr/lib/oracle/xe/app/oracle/admin/XE/adump
db_name = XE
open_cursors = 300
os_authent_prefix =
pga_aggregate_target = 96731136
PMON started with pid=2, OS id=4040
PSP0 started with pid=3, OS id=4042
MMAN started with pid=4, OS id=4044
Wed Jan 17 14:28:58 2007
Process startup failed, error stack:
Wed Jan 17 14:28:58 2007
Errors in file /usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_4037.trc:
ORA-27300: OS system dependent operation:fork failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpspawn5
Process DBW0 died, see its trace file
USER: terminating instance due to error 443
Instance terminated by USER, pid = 4037
and the trace file
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
System name: Linux
Node name: paco
Release: 2.6.19.2-vs2.2.0-rc7
Version: #1 SMP Sun Jan 14 17:01:12 CET 2007
Machine: i686
Instance name: XE
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
Unix process pid: 4037, image: oracle@paco
KCCDEBUG_LEVEL = 0
Running with 1 strand for Non-Enterprise Edition
Running without dynamic strand for Non-Enterprise Edition
Dynamic strand is set to FALSE
Running with 1 shared and 10 private strand(s). Zero-copy redo is FALSE
*** 2007-01-17 14:28:58.448
Process startup failed, error stack:
ORA-27300: OS system dependent operation:fork failed with status: 0
ORA-27301: OS failure message: Error 0
ORA-27302: failure occurred at: skgpspawn5
*** 2007-01-17 14:28:58.448
KSTDUMP: In-memory trace dump
TIME:SEQ# ORAPID SID EVENT OP DATA
========================================================================
DCCC590F:00000003 39 0 10254 34 KSBS1P: process USER trying to start background PMON
DCCCE78B:0000000E 39 0 10254 40 KSBS1P: spawn succeeded ospid = 4040
DCCCF126:0000000F 39 0 10254 50 KSBS1P: out of loop: process is up and running
DCCCF12D:00000010 39 0 10254 34 KSBS1P: process USER trying to start background TEST
DCCCF12E:00000011 39 0 10254 36 KSBS1P: process TEST already running or not enabled
DCCCF12F:00000012 39 0 10254 34 KSBS1P: process USER trying to start background DIAG
DCCCF130:00000013 39 0 10254 36 KSBS1P: process DIAG already running or not enabled
DCCCF131:00000014 39 0 10254 34 KSBS1P: process USER trying to start background FMON
DCCCF132:00000015 39 0 10254 36 KSBS1P: process FMON already running or not enabled
DCCCF133:00000016 39 0 10254 34 KSBS1P: process USER trying to start background PSP0
DCCD4C91:00000022 39 0 10254 40 KSBS1P: spawn succeeded ospid = 4042
DCCD4CA1:00000023 39 0 10254 50 KSBS1P: out of loop: process is up and running
DCCD4CA4:00000024 39 0 10254 34 KSBS1P: process USER trying to start background LMON
DCCD4CA5:00000025 39 0 10254 36 KSBS1P: process LMON already running or not enabled
DCCD4CA7:00000026 39 0 10254 34 KSBS1P: process USER trying to start background LMD0
DCCD4CA7:00000027 39 0 10254 36 KSBS1P: process LMD0 already running or not enabled
DCCD4CA9:00000028 39 0 10254 34 KSBS1P: process USER trying to start background LMS0
DCCD4CAA:00000029 39 0 10254 36 KSBS1P: process LMS0 already running or not enabled
DCCD4CAB:0000002A 39 0 10254 34 KSBS1P: process USER trying to start background LMS1
DCCD4CAC:0000002B 39 0 10254 36 KSBS1P: process LMS1 already running or not enabled
DCCD4CAD:0000002C 39 0 10254 34 KSBS1P: process USER trying to start background LMS2
DCCD4CAE:0000002D 39 0 10254 36 KSBS1P: process LMS2 already running or not enabled
DCCD4CAF:0000002E 39 0 10254 34 KSBS1P: process USER trying to start background LMS3
DCCD4CB0:0000002F 39 0 10254 36 KSBS1P: process LMS3 already running or not enabled
DCCD4CB1:00000030 39 0 10254 34 KSBS1P: process USER trying to start background LMS4
DCCD4CB2:00000031 39 0 10254 36 KSBS1P: process LMS4 already running or not enabled
DCCD4CB3:00000032 39 0 10254 34 KSBS1P: process USER trying to start background LMS5
DCCD4CB4:00000033 39 0 10254 36 KSBS1P: process LMS5 already running or not enabled
DCCD4CB4:00000034 39 0 10254 34 KSBS1P: process USER trying to start background LMS6
DCCD4CB5:00000035 39 0 10254 36 KSBS1P: process LMS6 already running or not enabled
DCCD4CB6:00000036 39 0 10254 34 KSBS1P: process USER trying to start background LMS7
DCCD4CB7:00000037 39 0 10254 36 KSBS1P: process LMS7 already running or not enabled
DCCD4CB8:00000038 39 0 10254 34 KSBS1P: process USER trying to start background LMS8
DCCD4CB9:00000039 39 0 10254 36 KSBS1P: process LMS8 already running or not enabled
DCCD4CBA:0000003A 39 0 10254 34 KSBS1P: process USER trying to start background LMS9
DCCD4CBB:0000003B 39 0 10254 36 KSBS1P: process LMS9 already running or not enabled
DCCD4CBC:0000003C 39 0 10254 34 KSBS1P: process USER trying to start background LMSa
DCCD4CBD:0000003D 39 0 10254 36 KSBS1P: process LMSa already running or not enabled
DCCD4CBE:0000003E 39 0 10254 34 KSBS1P: process USER trying to start background LMSb
DCCD4CBF:0000003F 39 0 10254 36 KSBS1P: process LMSb already running or not enabled
DCCD4CC0:00000040 39 0 10254 34 KSBS1P: process USER trying to start background LMSc
DCCD4CC1:00000041 39 0 10254 36 KSBS1P: process LMSc already running or not enabled
DCCD4CC2:00000042 39 0 10254 34 KSBS1P: process USER trying to start background LMSd
DCCD4CC3:00000043 39 0 10254 36 KSBS1P: process LMSd already running or not enabled
DCCD4CC4:00000044 39 0 10254 34 KSBS1P: process USER trying to start background LMSe
DCCD4CC5:00000045 39 0 10254 36 KSBS1P: process LMSe already running or not enabled
DCCD4CC7:00000046 39 0 10254 34 KSBS1P: process USER trying to start background LMSf
DCCD4CC7:00000047 39 0 10254 36 KSBS1P: process LMSf already running or not enabled
DCCD4CC9:00000048 39 0 10254 34 KSBS1P: process USER trying to start background LMSg
DCCD4CCA:00000049 39 0 10254 36 KSBS1P: process LMSg already running or not enabled
DCCD4CCB:0000004A 39 0 10254 34 KSBS1P: process USER trying to start background LMSh
DCCD4CCF:0000004B 39 0 10254 36 KSBS1P: process LMSh already running or not enabled
DCCD4CD0:0000004C 39 0 10254 34 KSBS1P: process USER trying to start background LMSi
DCCD4CD1:0000004D 39 0 10254 36 KSBS1P: process LMSi already running or not enabled
DCCD4CD2:0000004E 39 0 10254 34 KSBS1P: process USER trying to start background LMSj
DCCD4CD3:0000004F 39 0 10254 36 KSBS1P: process LMSj already running or not enabled
DCCD4CD5:00000050 39 0 10254 34 KSBS1P: process USER trying to start background LMSk
DCCD4CD5:00000051 39 0 10254 36 KSBS1P: process LMSk already running or not enabled
DCCD4CD7:00000052 39 0 10254 34 KSBS1P: process USER trying to start background LMSl
DCCD4CD8:00000053 39 0 10254 36 KSBS1P: process LMSl already running or not enabled
DCCD4CD9:00000054 39 0 10254 34 KSBS1P: process USER trying to start background LMSm
DCCD4CDA:00000055 39 0 10254 36 KSBS1P: process LMSm already running or not enabled
DCCD4CDB:00000056 39 0 10254 34 KSBS1P: process USER trying to start background LMSn
DCCD4CDC:00000057 39 0 10254 36 KSBS1P: process LMSn already running or not enabled
DCCD4CDD:00000058 39 0 10254 34 KSBS1P: process USER trying to start background LMSo
DCCD4CDD:00000059 39 0 10254 36 KSBS1P: process LMSo already running or not enabled
DCCD4CDF:0000005A 39 0 10254 34 KSBS1P: process USER trying to start background LMSp
DCCD4CDF:0000005B 39 0 10254 36 KSBS1P: process LMSp already running or not enabled
DCCD4CE1:0000005C 39 0 10254 34 KSBS1P: process USER trying to start background LMSq
DCCD4CE2:0000005D 39 0 10254 36 KSBS1P: process LMSq already running or not enabled
DCCD4CE3:0000005E 39 0 10254 34 KSBS1P: process USER trying to start background LMSr
DCCD4CE4:0000005F 39 0 10254 36 KSBS1P: process LMSr already running or not enabled
DCCD4CE5:00000060 39 0 10254 34 KSBS1P: process USER trying to start background LMSs
DCCD4CE6:00000061 39 0 10254 36 KSBS1P: process LMSs already running or not enabled
DCCD4CE8:00000062 39 0 10254 34 KSBS1P: process USER trying to start background LMSt
DCCD4CE9:00000063 39 0 10254 36 KSBS1P: process LMSt already running or not enabled
DCCD4CEA:00000064 39 0 10254 34 KSBS1P: process USER trying to start background LMSu
DCCD4CEB:00000065 39 0 10254 36 KSBS1P: process LMSu already running or not enabled
DCCD4CEC:00000066 39 0 10254 34 KSBS1P: process USER trying to start background LMSv
DCCD4CED:00000067 39 0 10254 36 KSBS1P: process LMSv already running or not enabled
DCCD4CEF:00000068 39 0 10254 34 KSBS1P: process USER trying to start background LMSw
DCCD4CF0:00000069 39 0 10254 36 KSBS1P: process LMSw already running or not enabled
DCCD4CF1:0000006A 39 0 10254 34 KSBS1P: process USER trying to start background LMSx
DCCD4CF2:0000006B 39 0 10254 36 KSBS1P: process LMSx already running or not enabled
DCCD4CF3:0000006C 39 0 10254 34 KSBS1P: process USER trying to start background LMSy
DCCD4CF4:0000006D 39 0 10254 36 KSBS1P: process LMSy already running or not enabled
DCCD4CF6:0000006E 39 0 10254 34 KSBS1P: process USER trying to start background LMSz
DCCD4CF7:0000006F 39 0 10254 36 KSBS1P: process LMSz already running or not enabled
DCCD4CF9:00000070 39 0 10254 34 KSBS1P: process USER trying to start background MMAN
DCCDB8DB:0000007C 39 0 10254 40 KSBS1P: spawn succeeded ospid = 4044
DCCDB8E8:0000007D 39 0 10254 50 KSBS1P: out of loop: process is up and running
DCCDB8ED:0000007E 39 0 10254 34 KSBS1P: process USER trying to start background DBW0
DCCDBD9E:00000080 39 0 10254 51 KSBS1P: out of loop: process did not start
KSTDUMP: End of in-memory trace dump
*** 2007-01-17 14:28:58.449yes, but I'm inside a vserver and the kernel parameters are hidden away from me ... :(
I found this
Database creation failure
If database creation fails, either during install or using dbca, the potential
error/warning is due to some default kernel parameters. The following error
generally indicates a wrong setting for SHMMAX and semaphore parameters.
“WARNING: EINVAL creating segment of size 0x000000000c400000”
Correct values needs to be set for shared memory parameters.
I hope the host server can make the changes ... -
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
Hi there
Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
After searching about this, I found this page from Niall Brady, which explained the problem:
http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
Now...
...I have a question.
The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
However there seems to be some confusion over whether this would actually make a difference.
I read through this link:
http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
There's seems to be no consensus on this.
Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
or
Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
I'd be grateful for some clarity on this.
Regards,
John, Glasgow.Hi Jason
Thank you for replying, I appreciate it.
1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
deleting all but the latest software update group?
2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
"The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
Can you shed some light on why there isn't a policy for an image?
Thanks again for replying,
John. -
Hello All,
Posting this problem here and hoping for a solution from the experts in this forum.
When i have restarted the Analysis Services , i see that it has been stopped but never started back. It fails with an error
"The SQL Server Analysis Services (MSSQLSERVER) service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
When Checked the Event Viewer i see the following error -
The service cannot be started: The following system error occurred: The filename, directory name, or volume label syntax is incorrect. File system error: Error occurred during the creation of directory: '\\?\E:\OLAP\MSSOLAPFactory\OlapData;M:\Test
Backup'.
I remember changing the BackupDir value of Analysis Services few days back, and i think it could have impacted. Can you please help me how can i change back the BackupDir value and have the server back?
Let me know if you need any more details
SGIs this still an issue? If so, I would find msmdsrv.ini and make sure you don't have two folders listed in the BackupDir (or DataDir or TempDir). You'll have to runas Administrator to edit the msmdsrv.ini file and save changes. Once you fix that, it should
succeed.
http://artisconsulting.com/Blogs/GregGalloway -
Weblogic Managed Server Error- JavaEE agent test failed in ODI
Hi All,
Please help wit the issue below !!
Versions: ODI 11.1.1 and Weblogic 11g Release1 10.3.3.
Server : Windows 2003 server ,32-bit OS.
->Able to connect the Standalone agent succesfully .
Issue : In Weblogic ,the admin server is connecting without error . But when i start the Managed server"odi_server1" we found the major error occuring while connecting to the Master Repository . Pasted below the Error log .
Please help!!
####<Mar 23, 2011 3:58:16 PM IST> <Error> <Deployer> <admin-3fqjbc1oo> <odi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1300876096336> <BEA-149231> <Unable to set the activation state to true for the application 'oraclediagent'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".
ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: ODI-1404: Agent OracleDIAgent start failure: an authentication error occurred while connecting to the master repository,
at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:233)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thanks
KennyHi Kenny,
This error seems to indicate the credentials you've specified for the master repo are not working. Either ensure the login works at the repo, or rerun the installer and specify a set of known good credentials there.
Regards,
Robb Salzmann -
Postscript report fail - REP-3000: Internal error starting Oracle toolkit
Hi,
I am receiving the error REP-3000: Internal error starting Oracle Toolkit when I am running a conc. program with postscript as output. I changed Active Users program and tested it. It failed.
Metalink says DISPLAY issue. I ran the concurrent program - "Prints environment variable values" giving DISPLAY as variable. I received a value. like <hostname>:0.0
What could be the issue?
Release - 11.5.10.2
OS -Linux
Apache, Forms on 1 Node, Concurrent Manager on the second one.
Database - 10g R2 on Unix.
Thanks
Cherrish Vaidiyan
Edited by: Cherrish on Aug 19, 2010 5:01 PMHi Hussein,
Please find the complete concurrent program log:
Application Object Library: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
FNDSCURS module: Active Users
Current system time is 19-AUG-2010 15:34:33
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.WE8ISO8859P1
REP-3000: Internal error starting Oracle Toolkit.
REP-3000: Internal error starting Oracle Toolkit.
Report Builder: Release 6.0.8.28.0 - Production on Thu Aug 19 15:34:33 2010
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Enter Username:
Start of log messages from FND_FILE
End of log messages from FND_FILE
Program exited with status 1
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 73686471.
Review your concurrent request log and/or report output file for more detailed information.
Executing request completion options...
Finished executing request completion options.
Concurrent request completed
Current system time is 19-AUG-2010 15:34:46
I will check the old forums too.
Thanks -
I SCREWD UP AND SHUT DOWN MY MAC WHEN IT WAS IN THE PRIVLEDGES STAGE BECAUSE MY PLUG-INS FOR AFTER EFFECTS WASNT WORKING, WHEN I SHUT IT DOWN AND TRIED TO START IT BACK UP, MY MAC KEPT RESTARTING, TEST-RAN-ERROR..4MOT/1/40000003:HDD-14444? WAT IS THIS? WAT DO I DO TO GET MY MAC BACK RUNNING
I believe you've posted this multiple times. Once is all that's needed. Also, please don't use all caps. Aside from the fact it means you're shouting it's also harder to read than mixed case.
The error means a bad fan motor or the HDD has failed. In your case it's the latter. You can try the following:
Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
When formatting has completed quit DU and return to the installer. Complete the OS X installation. -
I keep getting this strange error logged as Error event id 2. Note session string is blank "". Any ideas?
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 24/12/2009 09:08:20
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: George-XXL
Description:
Session "" failed to start with the following error: 0xC000000D
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2009-12-24T09:08:20.835299100Z" />
<EventRecordID>36</EventRecordID>
<Correlation />
<Execution ProcessID="1944" ThreadID="1948" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>George-XXL</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">
</Data>
<Data Name="FileName">
</Data>
<Data Name="ErrorCode">3221225485</Data>
<Data Name="LoggingMode">5</Data>
</EventData>
</Event>Can you let us know if you get any Blue Screen crush error while using your comptuer?
Generally we can safely ignore the errors in the Event log. Aas we don't if you have get other issues in your computer, you can test your computer in the Clean Boot mode. This method will help us determine if this issue is caused by a loading program or service.
You can try the the following steps:
1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.
Please test this issue in this Clean Boot environment, if the issue disappears in the Clean Boot environment, you can use the dichtomy to quickly narrow down which entry is causing the issue. You can refer to the
KB929135.
Good luck!
John
This is a very poor answer. This guy doesn't know what he's talking about because if you tell someone its ok to "safely ignore the errors in the event log" as a blanket instruction ESPECIALLY because as he stated so himself
he didn't know if there were other issues with the OP's pc then he's giving really bad advice. If you ignore errors in the event log then over time your system will degrade and you will have other issues.. Every error on your pc should NOT be ignored.
It should be decided on a case by case situation.
Furthermore this is an error involving the Windows Session which it states has failed. Definitely should NOT be ignored.
I've got the same error which has suddenly just showed up. No BSOD, Do not have WHS installed and all my media center connectors have NEVER been connected. I don't believe this is a service issue. I think it has something
to do with kernel event tracing.
Of course, it's just my opinion....I could be wrong! -
Failed to initialize the Fetchlet Manager while starting agent
Hi all,
I am getting following error message while starting an agent. This agent installation gets failed at the point of starting agent. Normally this happens when the dns /hostfile entry have any problems and I made sure those things are OK.
This agent is on a Solaris server and all other similar servers are working fine. Have anyone came across this situation?
$ emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent ........ failed.
Failed to initialize the Fetchlet Manager.
Consult the log files in: /u01/oracle/product/agent10g/sysman/logcat emagent.trc
2009-12-04 12:25:54 Thread-1 ERROR util.files: ERROR: nmeufis_new: failed in lfi opn on file: /u01/oracle/product/agent10g/sysman/emd/agntstmp.txt. error = 2 (No such file or directory)
2009-12-04 12:25:54 Thread-1 ERROR pingManager: nmepm_pingReposURL: Did not rece ive a response header from repository
2009-12-04 12:25:54 Thread-1 WARN command: Job Subsystem Timeout set at 600 sec onds
2009-12-04 12:25:54 Thread-1 ERROR fetchlets: Error when initializing C Logging Package for ECID generation.
2009-12-04 12:25:54 Thread-1 ERROR main: nmefmgr_initialize failed to initialize Fetchlet Manager -
Error Message "ElementsAutoAnalyzer.exe unable to locate. This application failed to start because ExtendedScript.dll was not found".
This error message is seen every time when first starting Windows Vista, PRIOR to starting Photoshop Elements 12.1
It does not seem to interfere with the normal operation of Photoshop Elements, but it is a constant annoyance.try removing all itunes and all other apple program
follow this link for more info. http://support.apple.com/kb/HT1923
reboot ur window after uninstalling
after that download the latest itunes setup and install.
Maybe you are looking for
-
How can I set up airport extreme using my existing 11.g router
My existing router (ZyXEL - supplied by Telefonica with my land line) is an 11.g type and does not allow me to use iPad/iPod in certain areas of my home. Yesterday I bought an Airport Extreme and was told that I could either connect my existing rout
-
HP Pavillion dv6 w/ windows 7 cannot play blu ray
I have the above mentioned device with a blu ray / dvd player installed with it. Problem is that it won't play blu rays with windows media player and it says empty disc when I try to play with VLC this is the message I get: Blu-ray error: This Blu-r
-
How can locate my iPad 2,someone signed in to my Facebook account today and confirmed a friend request,is there anyway to find out where the ip address was signed in from,help
-
My home PC obviously downloaded the file for later installation. It looked like a Firefox file, but I came to install the file, the source was a name xxxxxxxxxxx.cz Does Mozilla originate in Czechoslovakia?
-
Sudden issue: Charging is not supported with this accessory
Hello - I've had a 32GB 3rd generation iPod Touch since right around the new year. It's worked nearly perfect since January until today, when I plugged it into my PC to charge. I got the error "Charging is not supported with this accessory". This see