Error while scanning for Serial-ATA devices.

There was an error while scanning for Serial-ATA devices. I'm not sure how to trouble shoot this. I believe a secondary drive in bay 2 died.

I also have just began to hit this issue.
I have 4 2T enterprise class WD drives in a raid 1+0 (or was it 0+1) config.
Device Model: WDC WD2002FYPS-01U1B1
One disk (disk0 in bay 2) keeps disappearing. Completely. /dev/disk0 and /dev/rdisk0 vanish.
If I look at "about this mac" / "More Info" / "Serial-ATA" I get the "error while scanning ...".
If I reboot, the offending disc comes back and the raid volumes start rebuilding.
The SMART status is (reported to be) fine.
I use the 'smartmon' tools and look at the extended SMART status and the values of the counters all looks the same as the other drives. I can run an extended offline test, which takes forever to execute. disk 1 and 3 eventually finish with success (it writes this status into a SMART log area on the disc).
Disk 2 and 0 take longer. I image this is because 2 is being read to resilver 0. Currently, I am running with disk0 absent again, and disk 2s test did not complete. It claims it was aborted by the host, so I imagine the one on disk0 will claim the same after I reboot.
My system is under extended AppleCare until 16 Jan 2011, so if I can determine that this is a disc controller error, I can get it fixed. The drives have a 5 year warrantee, and are less than 1yr old, so they are covered. I just need to figure out what the issue is.
I will now reboot and recover disk0 and see if perhaps there is anything recorded in the SMART log.
There is nothing in kernel.log specific to disk0. I include the log extract here for posterity. The "speed" volume is not raid 0+1, just striped, which is why it gets aborted.
Dec 21 23:30:26 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 21 23:30:26 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 22 04:17:22 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 04:17:22 8way kernel[0]: AppleRAIDMirrorSet::rebuild complete for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 05:23:16 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:23:30 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:23:44: --- last message repeated 1 time ---
Dec 22 05:23:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:24:14: --- last message repeated 4 times ---
Dec 22 05:24:19 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:24:56: --- last message repeated 2 times ---
Dec 22 05:24:56 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:25:17: --- last message repeated 1 time ---
Dec 22 05:25:17 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:25:31: --- last message repeated 1 time ---
Dec 22 05:25:31 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
Dec 22 05:25:45: --- last message repeated 1 time ---
Dec 22 05:25:45 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:26:15: --- last message repeated 2 times ---
Dec 22 05:26:21 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:26:51: --- last message repeated 4 times ---
Dec 22 05:27:12 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:27:33: --- last message repeated 1 time ---
Dec 22 05:27:26 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:27:40: --- last message repeated 1 time ---
Dec 22 05:27:40 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:28:24: --- last message repeated 1 time ---
Dec 22 05:28:24 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:28:39: --- last message repeated 1 time ---
Dec 22 05:28:39 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25
Dec 22 05:29:14 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76), member 3C6E9EA4-831A-4
57A-8CA5-6E7E9CBEED25, set byte offset = 222462894080.
Dec 22 05:29:14 8way kernel[0]: AppleRAID::recover() member 3C6E9EA4-831A-457A-8CA5-6E7E9CBEED25 from set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76) has been marked
offline.
Dec 22 05:29:14 8way kernel[0]: AppleRAID::restartSet - restarting set "usr_2" (4EA5DD68-D6D0-4CF3-A741-BFBC5ECE8A76).
Dec 22 05:32:38 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:33:22: --- last message repeated 1 time ---
Dec 22 05:33:22 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:34:06: --- last message repeated 1 time ---
Dec 22 05:34:06 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002ca on 9722C38E-DFF9-468F-8DE5-809432493168
Dec 22 05:34:53: --- last message repeated 1 time ---
Dec 22 05:34:53 8way kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002ca detected for set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D), member 9722C38E-DFF9-4
68F-8DE5-809432493168, set byte offset = 35194773504.
Dec 22 05:34:53 8way kernel[0]: AppleRAID::recover() member 9722C38E-DFF9-468F-8DE5-809432493168 from set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D) has been marked
offline.
Dec 22 05:34:53 8way kernel[0]: AppleRAID::restartSet - restarting set "sys_2" (C398B450-28A3-4C1D-A6A8-5B617661789D).
Dec 22 05:37:24 8way kernel[0]: AppleAHCIDiskQueueManager::setPowerState(0x13d64500, 2 -> 1) timed out after 100113 ms
Dec 22 05:37:44 8way kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
Dec 22 05:37:44 8way kernel[0]: AppleRAIDMember::synchronizeCacheCallout: failed with e00002be on EB932B0E-8476-480C-BBD4-53A9A77D9FEF
Dec 22 05:37:44 8way kernel[0]: AppleRAID::recover() member EB932B0E-8476-480C-BBD4-53A9A77D9FEF from set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0) has been marked
offline.
Dec 22 05:37:44 8way kernel[0]: AppleRAID::restartSet - restarting set "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BBE0).
Dec 22 05:37:44 8way kernel[0]: disk4: media is not present.
Dec 22 05:37:59 8way kernel[0]: speed::terminate(kIOServiceSynchronous) timeout
Dec 22 05:37:59 8way kernel[0]: AppleRAID::completeRAIDRequest - underrun detected, expected = 0xa000, actual = 0x9e00, set = "speed" (190EC75B-C702-4481-ABCF-8C5A0D54BB
E0)
Dec 22 05:37:59 8way kernel[0]: disk4: data underrun.
Dec 22 05:37:59 8way kernel[0]: jnl: disk4: dojnlio: strategy err 0x5
Dec 22 05:37:59 8way kernel[0]: jnl: disk4: end_transaction: only wrote 0 of 40960 bytes to the journal!
Dec 22 05:37:59 8way kernel[0]: disk4: media is not present.
Dec 22 05:38:00 8way kernel[0]: jnl: disk4: close: journal 0x13f34e04, is invalid. aborting outstanding transactions

Similar Messages

  • SEVERE: An error occured while scanning for the next trigger to fire

    Hi All,
    I followed below steps to configure Oracle BI publisher scheduler on oracle 10g database.
    1.Log in to BI Publisher as a user with Administrator privileges and select the Admin tab.
    2.Under System Maintenance, select Scheduler Configuration.
    3.Enter the database connection information for the target Oracle database and user.
    Database Type: 10g
    Connection String: jdbc:oracle:thin://<hostname>:<port#>:<oracle SID>
    Username/Password for the database user
    Database Driver Class: oracle.jdbc.driver.OracleDriver
    4.Click the Test Connection button to make sure the connection information is valid.
    5.Click the Install Schema button to install the scheduler tables.
    6.Restart the BI Publisher application.
    The Schema installed successfully.
    But when I am starting the weblogic server I am getting below error and BI publisher application is not getting up.
    INFO: Handling 6 triggers that missed their scheduled fire-time.
    23-Dec-2011 05:29:38 org.quartz.core.ErrorLogger schedulerError
    SEVERE: An error occured while scanning for the next trigger to fire.
    org.quartz.JobPersistenceException: Couldn't acquire next trigger: Couldn't retrieve trigger: Invalid column name [See nested exception: org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]]
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1773)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    * Nested Exception (Underlying Cause) ---------------
    org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1126)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    * Nested Exception (Underlying Cause) ---------------
    java.sql.SQLException: Invalid column name
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
    at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3372)
    at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:2009)
    at oracle.jdbc.driver.OracleResultSet.getBinaryStream(OracleResultSet.java:668)
    at org.apache.commons.dbcp.DelegatingResultSet.getBinaryStream(DelegatingResultSet.java:233)
    at org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.getObjectFromBlob(OracleDelegate.java:154)
    at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:2382)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1115)
    at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
    at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
    at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
    23-Dec-2011 05:30:55 org.quartz.core.ErrorLogger schedulerError
    The system details are as below :
    BI Publisher version : 10.1.3.4
    Oracle DB : 10 G
    Weblogic server :10.3.2
    Please suggest to resolve this issue.
    Thanks,
    Sachin

    Hi,
    This errors occurs if you have configured some schema for the scheduler and configured it on BIP, but the configured schema is no longer available.
    That is why I am suggesting you to replace the current quartz.properties file with the original file that exits during installation.
    Then try to start the server, and see if the server starts without error.
    After that you can try to configure the scheduler from BIP console.
    thanks,
    sandeep

  • Failed while scanning for CD/DVD drives, error 2355

    Failed while scanning for CD / DVD drives, error 2355.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    D: Unsupported CD or DVD drive.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    As far as I know I do NOT have a virtual drive on this pc.
    Any help???

    Failed while scanning for CD / DVD drives, error 2355.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    D: Unsupported CD or DVD drive.
    Virtual drives can sometimes interfere with reading and writing CDs in iTunes. If this is a virtual drive and you are having problems with other drives, try uninstalling the virtual CD application.
    As far as I know I do NOT have a virtual drive on this pc.
    Any help???

  • An error occurred while scanning for security updates. (0x80004003)

    Has anyone seen this error:   An error occurred while scanning for security updates. (0x80004003)?
    This error occurs when I run the MBSA tool either locally or remote against a workstation.  I also thought that the firewall may be the issue, it is not.  I ran the MBSA tool on the WSUS replica and WSUS upstream server and received the same results. I
    have been running the MBSA tool and have not run into this probem before.   I am running SolarWinds PatchManager on the upstream WSUS server and have recently configured the upstream and downstream servers to communicate, I imported
    the certifcate from the WSUS upstream to the replica and noticed that after this we started having issues with the MBSA scans.  Not sure if this is related but it is the only change between MBSA working and not working.  P.S.  The scan does
    work when we use the offline scenario instead of pointing to the WSUS server.
    Any help would be appreciated.
    Thanks
    bc

    Yes, the log file was too large I have pasted the 2nd half after running MBSA on the server (the setting is to scan using Windows Server Update Services (WSUS) only.)  This second half of the windowslog file shows errors after running MBSA
    MBSA scan time was 9:44 PM
    2014-07-31   
    19:38:35:487  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:44:14:497  216   2344  
    Report Uploading 4 events using cached cookie, reporting URL =
    http://eus1:8530/ReportingWebService/ReportingWebService.asmx
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING: ReportEventBatch failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING: SOAP Fault: 0x00012c
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    faultstring:Fault occurred
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    ErrorCode:ConfigChanged(2)
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    Message:(null)
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch"
    2014-07-31   
    19:44:14:555  216   2344  
    PT     WARNING:    
    ID:2b9836c5-3159-494b-ae27-72559d089586
    2014-07-31   
    19:44:14:555  216   2344  
    Report WARNING: Reporter failed to upload events with hr = 8024400d.
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc   =========== 
    Logging initialized (build: 7.6.7600.256, tz: -0400) 
    ===========
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc     = Process: C:\Program Files\Microsoft Baseline Security Analyzer 2\mbsa.exe
    2014-07-31   
    19:45:57:201  9128   12a8  
    Misc     = Module: C:\Windows\system32\wuapi.dll
    2014-07-31   
    19:45:57:200  9128   12a8  
    COMAPI -------------
    2014-07-31   
    19:45:57:201  9128   12a8  
    COMAPI -- START --  COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:45:57:202  9128   12a8  
    COMAPI ---------
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  *************
    2014-07-31   
    19:45:57:218  9128   12a8  
    COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  ** START **  Agent: Finding updates [CallerId = MBSA]
    2014-07-31   
    19:45:57:218  216   2344  
    Agent  *********
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Include potentially superseded updates
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Online = Yes; Ignore download priority = No
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Criteria = "IsInstalled=0 or
    IsInstalled=1"
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-07-31   
    19:45:57:218  216   2344  
    Agent    * Search Scope = {Machine}
    2014-07-31   
    19:45:58:410  216   2344  
    PT     +++++++++++  PT: Synchronizing server updates 
    +++++++++++
    2014-07-31   
    19:45:58:410  216   2344  
    PT       + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://eus1:8530/ClientWebService/client.asmx
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING: SOAP Fault: 0x00012c
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    faultstring:Fault occurred
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    ErrorCode:ConfigChanged(2)
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    Message:(null)
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2014-07-31   
    19:46:00:453  216   2344  
    PT     WARNING:    
    ID:e9b0d06e-d0c8-443f-abc9-512bc0f2cfa1
    2014-07-31   
    19:46:00:481  216   2344  
    PT     Initializing simple targeting cookie,
    clientId = e651f142-bc0f-467d-b416-d344215f5c0a, target group = EMCC Servers, DNS name = elf1.monarch.com
    2014-07-31   
    19:46:00:481  216   2344  
    PT       Server URL =
    http://eus1:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-07-31   
    19:46:18:451  216   2344  
    PT     +++++++++++ 
    PT: Synchronizing extended update info  +++++++++++
    2014-07-31   
    19:46:18:451  216   2344  
    PT       + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://eus1:8530/ClientWebService/client.asmx
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {92AEAB02-F8FC-4527-B285-50FDC8EF3F85}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {2212D902-7C3B-408E-96A3-ECE4D00BFAE6}.101 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {490BE004-BC5C-4EEF-AC82-769542FC3A2D}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {568C1005-5178-4C13-8486-18E2C5AF4834}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {D9F49D05-AC6D-4A2A-8150-D2B4B730DEED}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {74844E07-2F55-40D4-9E16-E17A2815FEBE}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {3C72A908-F3CD-413D-B2BF-ECB68D24B6FE}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {50990D0B-4795-4830-9C3A-753485B2D433}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {9DB82D0B-5611-4BC1-A4B8-432FE1A3CC43}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {7BB7B30C-351D-4F8C-ABE4-5F7965635A03}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {AEF6280F-8C4D-4804-9913-407582227E75}.202 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {16BB6A11-B540-4486-AB13-F3B9789E90B5}.105 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {1B127611-D28E-4167-A1DC-243A51BC528F}.203 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {2F6F2013-2990-4FA6-8AB9-CA59DCA4E62D}.202 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {21732D13-3D34-4DD7-B663-32F2A1631EA9}.105 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {E879EE15-340D-442C-B8A4-CF91D18C1B6B}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent  Update {99FEC317-44CD-40B4-B67E-94C840510983}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {8096C018-252D-4C32-BC9E-F33AC67ECFF1}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {ECCC4D19-3032-4C82-91AB-A31560B13F80}.205 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {BB49CC19-8847-4986-AA93-5E905421E55A}.103 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {023BB023-490F-4DF3-BCAA-9521EE8B5847}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {9676C624-58CB-4A30-B7B3-1D013CF3DBBC}.201 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {1BB3DE24-0D76-4D59-9B9E-556722BFE852}.101 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {F4695A25-0D22-4E3B-9BA9-9BBC62198C28}.103 to search result
    2014-07-31   
    19:46:18:893  216   2344  
    Agent    * Added update {11152F27-ACCA-4438-B21D-A0B61480D33B}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {308DE327-7354-4481-9981-DEA0FC61925E}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {16E9C62D-05B2-4E14-BFB0-CF55EDBD4F61}.106 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {C750962E-9D5E-45CE-9967-AE2D67115966}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {9F7D6930-6816-423A-AF3C-C83ADFA7F612}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {497BCC31-ACF7-46E2-B664-C79FD2D39F8B}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Update {E00B2634-BEF9-4C32-B2BF-DEAF7D7221E4}.102 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {7738E837-B152-487B-8527-CD3A9C0E43E3}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {39757C3A-7ABE-4418-8B2A-C7EA7D88B36A}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {A8968B3A-7FB5-4089-888F-4CDB14055DE9}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {E6ED643C-8611-4453-A723-9847B7BF60EB}.103 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {C499223D-2F22-4626-BBE5-F5A35E7A5854}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {48BEEF41-9D2D-4E72-9A61-59F98B12C07A}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {332AA342-7AC4-4FB4-9C27-C2C9F4EAE6C0}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {2661BD46-2980-4FCF-A062-B3A0C7820663}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {DC548E48-407C-48E1-ACA4-6B4C0DF14E69}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {ED981249-8D8F-42A1-87DB-0AB5C07430B2}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {18FEE64A-1E7F-4932-8158-E8AB241F3A1A}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {3732354D-3DAE-4E71-B82C-61A12C300F72}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {3061954E-EDAA-4625-837C-CE768D68927D}.204 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {78F92451-801A-40F5-9582-CB8D1CA993BE}.202 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {ADA7CF51-66B0-4A00-B37B-68D569D6FF8B}.102 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {345B0353-DFC6-48CC-A6B6-A490CA26B503}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {1330DB53-75FF-4D87-9270-6A5449A67AD7}.101 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent    * Added update {E35E5957-A5A9-4576-9D54-314A34C47C53}.201 to search result
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:894  216   2344  
    Agent  Update {DC17765A-6814-47AD-9F54-5BFBCBF95FB0}.101 is not a valid bundle. Not
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CEFF8CA0-08DB-41D0-B825-FCC2CEBAF8B4}.108 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {2FECFFA0-44C8-4719-8F72-EC7BD8EDB793}.1 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {2BDE2BA3-EF93-49C6-A3C6-A806835A680F}.200 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {FA04F2A3-4DB5-4903-A08C-ADDFCF93EE28}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {0B8586A5-EEB6-4DC0-BCDA-2635C7E12B55}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:895  216   2344  
    Agent  Update {A6BD61A7-CC63-4068-8510-AA5268FB03E8}.101 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {4C0BA6A7-A8F0-417E-B9DA-906207429CE6}.204 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CE9876A9-83BF-4EDC-8793-4CBD6F3A6C5A}.202 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {63A011AC-FF81-44B9-811C-BECE5DC6C34B}.101 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {4A0A69AD-4237-43E7-8FB9-5A814361EC76}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {7E8ACCAD-2892-4F2D-9549-1FF8BE44AAD1}.203 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {E17C01AE-BACC-4147-97AD-51A0708126D2}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {CB1F1FAE-F738-49E7-AE3E-7A0C2308838B}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {9696B7B0-FF6F-4AA6-B29C-E0200CB6EB79}.200 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {B58F24B1-58A0-4661-9882-0FF509712946}.102 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {E47BE4B1-5EF0-442F-995F-C000D5AFF062}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {D68E0CB2-9501-405E-AF9C-156F352D6735}.107 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {09593FB3-C94B-4A07-84C4-2E60703AD644}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {99C920B7-65AB-4ACD-A4AD-C4F522E4D7A9}.201 to search result
    2014-07-31   
    19:46:18:895  216   2344  
    Agent    * Added update {EDE986B7-03CE-4B0C-8891-AF09113CB0DB}.200 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {B8315ACF-BF26-4C3A-979B-80A46D06697F}.200 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {013AF7D6-EC9F-4DEF-AE41-007D211F9FBC}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {6E3C01DB-6977-46D2-A537-00F53DA0B3B3}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {9842D9DB-8AE8-4F0B-B974-66787AEC8FBC}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent  Bundle contains no deployed children and thus is invalid.
    2014-07-31   
    19:46:18:896  216   2344  
    Agent  Update {0C1447DC-904E-4DCE-B208-50741D1CC65C}.102 is not a valid bundle. Not returning it.
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {DD7619DD-D6A6-4765-8406-612FD79583BA}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {ABB0AFDD-4B0A-4C3E-8341-07EA3941C465}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {B66BA1DF-4BC1-4145-859F-239C9F9BB5A0}.201 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {E2C928E1-BE92-4715-817D-FD6090F2FB07}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {C16FDFFD-A0D3-49EB-A8EB-B8F5E21D52C3}.202 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent    * Added update {57260DFE-227C-45E3-9FFC-2FC77A67F95A}.104 to search result
    2014-07-31   
    19:46:18:896  216   2344  
    Agent   * Added update {5BCDA2FE-A3F5-42C9-91F0-823230942BD8}.204 to search result
    2014-07-31   
    19:46:18:897  216   2344  
    Agent    * Found 151 updates and 95 categories in search; evaluated appl. rules of 1327 out of 2207 deployed entities
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  *********
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  **  END 
    **  Agent: Finding updates [CallerId = MBSA]
    2014-07-31   
    19:46:18:918  216   2344  
    Agent  *************
    2014-07-31   
    19:46:18:932  216   2344  
    Report REPORT EVENT: {A427D5D8-F546-4FBB-9F5F-931DF1F46063}      
    2014-07-31 19:46:18:898-0400      1     
    147    101    {00000000-0000-0000-0000-000000000000}  
    0       0     
    MBSA   Success      
    Software Synchronization   Windows Update Client successfully detected 151 updates.
    2014-07-31   
    19:46:18:932  216   2344  
    Report REPORT EVENT: {C8151494-E563-4AEB-B37F-14FD7864BF5D}      
    2014-07-31 19:46:18:898-0400      1     
    156    101    {00000000-0000-0000-0000-000000000000}  
    0       0     
    MBSA   Success      
    Pre-Deployment Check Reporting client status.
    2014-07-31   
    19:46:18:933  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:934  9128   2550  
    COMAPI >>--  RESUMED 
    -- COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:46:18:934  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:934  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:935  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:18:936  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    2014-07-31   
    19:46:19:032  9128   2550  
    COMAPI   - Updates found = 151
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI ---------
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI --  END 
    --  COMAPI: Search [ClientId = MBSA]
    2014-07-31   
    19:46:19:033  9128   2550  
    COMAPI -------------
    2014-07-31   
    19:46:23:918  216   2344  
    Report CWERReporter finishing event handling. (00000000)
    bc

  • Unable to burn cds. Have run diognostics. i tunes not running in safe mode. invalid lower filters registry value. Failed while scanning for CD/DVD drives, error 2500. Please help.

    Unable to burn CDs using i tunes. Have run diognostics.    Summary:-   i tunes not running in safe mode.
                                                                                                                                        Invalid lower filters registry value.
                                                                                                                                        Failed while scanning for CD/DVD drives, error 2500
    Please help.

    That's why you want to make a backup of the registry. If you didn't make a backup, use MS system restore to go back. The only values you should remove are UpperFilter or LowerFilter - one or both may be in there and can be removed. If neither value exists, then that is probably why you can't burn and Windows is not recognizing your drive as a writable drive.
    ... an HP employee expressing his own opinion.
    Please post rather than send me a Message. It's good for the community and I might not be able to get back quickly. - Thank you.

  • Change detector failed while scanning for changes to type User

    I'm receiving lots of system log warnings in IdM.
    These warnings are not bound to any particular action in IdM, they just do appear while IdM is on.
    Almost one warning per one second.
    Change detector failed while scanning for changes to type Server
    Change detector failed while scanning for changes to type UserForm
    Change detector failed while scanning for changes to type User
    Change detector failed while scanning for changes to type Resource
    SysLog detail:
    Timestamp 123
    Event
    Server server11
    Severity Warning
    Component Repository
    Error Code OCDT00
    Message Change detector failed while scanning for changes to type User
    Reported cause java.lang.NullPointerException
    java.lang.NullPointerException
    at com.waveset.repository.ObjectChange.equals(ObjectChange.java:112)
    at java.util.HashMap.eq(HashMap.java:299)
    at java.util.HashMap.containsKey(HashMap.java:381)
    at java.util.HashSet.contains(HashSet.java:182)
    at com.waveset.repository.ObjectChangeManager$RemoteChangeDetector.dispatchChanges(ObjectChangeManager.java:398)
    at com.waveset.repository.ObjectChangeManager$RemoteChangeDetector.run(ObjectChangeManager.java:314)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)

    same here, just deployed 8.1 with oracle as db. It results in syslog table growing into 10+G and still growing.
    wonder if there are others who are seeing this.
    my "syslog -d 1" output looks like this...
    2009-12-02 04:52:55.972 null W xxx RP OCDT00 Change
    detector failed while scanning for changes to type Account
    2009-12-02 04:53:06.400 null W xxx RP OCDT00 Change
    detector failed while scanning for changes to type Server
    2009-12-02 04:53:06.578 null W xxx RP OCDT00 Change
    detector failed while scanning for changes to type User
    2009-12-02 04:53:06.914 null W xxx RP OCDT00 Change
    detector failed while scanning for changes to type Account
    2009-12-02 04:53:17.479 null W xxx RP OCDT00 Change
    detector failed while scanning for changes to type Server
    C:\Program Files\Apache Software Foundation\Apache Tomcat 6.0.18\webapps\ims\bin
    lh syslog -d 1

  • Error while scanning is the message that it shows

     There is a message that shows error while scanning .
     dont know what has to be done .
     please suggest how to overcome this problem.

    Hello kunalbahrus,
    Welcome to the HP Forums.
    I see that you are having and issue when attempting to scan to the computer.
    Please write me back with the exact error message the you are seeing when attempting to scan.
    I am also going to give you the link to the HP Print and Scan Doctor.  Please let me know if you see any error codes or messages.
    I look forward to hearing back from you.
    Cheers,  
    Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    W a t e r b o y 71
    I work on behalf of HP

  • T61: Windows needs to install driver software for your ATA Device-help!!

    Every once in a while after I turn on my laptop I get this message: "Windows needs to install driver software for your ATA Device." WTF? REALLY W-T-F? I am not computer illiterate When I reinstall the driver (from the site) it works. Then I turn on the computer and get the same message. PLEASE HELP... W-T-F?????????
    The DVD player has been out of commission all of May so far.  I can't stand this.  What is happening?
    I can't even download the driver from Lenovo.
    PLEASE HELP.
    Thanks in advance.
    You are a God if you can't help me fix this.
    Moderator note: Type added to subject line for clarity. The title of a thread should accurately reflect the subject of the discussion and be as technically specific as possible as stated in the forum rules.
    Message Edited by Agotthelf on 30-05-2009 08:21 AM

    Welcome to the forum!
    Since I'm not quite certain that God frequents this forum, would you please tell us the model number and operating system of your ThinkPad and we'll take it from there...
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • Error while registering for index relevant events: Invalid RID: No reposito

    Hi,
        I created an index and assigned a datasource to search the Windows network drive. I activated the index and now when I am  monitoring the application log, I see the error <b>Error while registering for index relevant events: Invalid RID: No repository manager found for prefix: and XIndexing documents failed. AbstractTrexIndex: indexing some of the resources failed Continue crawling and Indexing document failed. Access denied </b> for the <b>IndexmanagementService</b>.
    When I see the queue status, the queue status is always idle, even after I activate the queue.
    In the indexing monitor, I see the error <b>Trex: Preparation failed: index operation</b>
    could anyone tell me what could be wrong?
    Thanks,

    Hi Christian,
    thanks for your reply.
    we are using 7.2 SP02. Do you think it could be the version that has some issues with custom mapping functions?
    regards
    Yao

  • RMAN-10011: synchronization error while polling for rpc 8, action=startdefa

    Could anybody explain what is this error message caused by?
    TIA
    The entire spool below:
    051107064744: NetBackup RMAN Backup Started
    ORACLE_SID=db02
    backup_type=cold
    number_of_channels=2
    Started by: Oracle
    051107064745: Checking database status
    051107064745: Database status: OPEN
    051107064745: Getting database password
    051107064746: Checking database password
    051107064746: Database password: Valid
    051107064746: Checking Database mode
    051107064746: Database mode: NOARCHIVELOG
    051107064746: Shutdown no archive
    051107064838: RMAN BACKUP STARTED
    Recovery Manager: Release 10.1.0.4.0 - 64bit Production
    Copyright (c) 1995, 2004, Oracle. All rights reserved.
    connected to target database: db02 (DBID=3504436532)
    RMAN> connect catalog *
    2> run
    3> {
    4> sql 'alter session set sort_area_size=12582912';
    5> sql 'alter session set sort_area_retained_size=1048576';
    6> allocate channel t1 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
    7> format 'df_%d_%p_%u_%t';
    8> set limit channel t1 maxopenfiles=1;
    9> allocate channel t2 type 'SBT_TAPE' parms="ENV=(NB_ORA_POLICY=ORA_solcdi02, NB_ORA_SERV=sun4)"
    10> format 'df_%d_%p_%u_%t';
    11> set limit channel t2 maxopenfiles=1;
    12> backup database filesperset=64
    13> include current controlfile;
    14> sql 'alter database open';
    15> release channel t1;
    16> release channel t2;
    17> }
    18>
    connected to recovery catalog database
    starting full resync of recovery catalog
    full resync complete
    sql statement: alter session set sort_area_size=12582912
    sql statement: alter session set sort_area_retained_size=1048576
    allocated channel: t1
    channel t1: sid=160 devtype=SBT_TAPE
    channel t1: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
    allocated channel: t2
    channel t2: sid=159 devtype=SBT_TAPE
    channel t2: VERITAS NetBackup for Oracle - Release 5.1 (2004122521)
    Starting backup at 11-MAY-07
    channel t1: starting full datafile backupset
    channel t1: specifying datafile(s) in backupset
    input datafile fno=00005 name=/oradata/10gid/u01/grid102/grid102/mgmt.dbf
    input datafile fno=00006 name=/oradata/10gid/u01/grid102/grid102/mgmt_ecm_depot1.dbf
    input datafile fno=00007 name=/oradata/10gid/u01/grid102/grid102/system02.dbf
    input datafile fno=00004 name=/oradata/10grid/u01/grid102/grid102/users01.dbf
    channel t1: starting piece 1 at 11-MAY-07
    channel t2: starting full datafile backupset
    channel t2: specifying datafile(s) in backupset
    input datafile fno=00008 name=/oradata/10ggrid/u01/grid102/grid102/mngmecm02.dbf
    input datafile fno=00001 name=/oradata/10ggrid/u01/grid102/grid102/system01.dbf
    input datafile fno=00002 name=/oradata/10ggrid/u01/grid102/grid102/undotbs01.dbf
    input datafile fno=00003 name=/oradata/10ggrid/u01/grid102/grid102/sysaux01.dbf
    channel t2: starting piece 1 at 11-MAY-07
    channel t2: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_19ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t2: backup set complete, elapsed time: 00:06:05
    channel t2: starting full datafile backupset
    channel t2: specifying datafile(s) in backupset
    including current controlfile in backupset
    channel t2: starting piece 1 at 11-MAY-07
    channel t2: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_1aihed24_622277700 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t2: backup set complete, elapsed time: 00:00:35
    channel t1: finished piece 1 at 11-MAY-07
    piece handle=df_GRID102_1_18ihecmm_622277334 comment=API Version 2.0,MMS Version 5.0.0.0
    channel t1: backup set complete, elapsed time: 00:06:48
    Finished backup at 11-MAY-07
    Starting Control File and SPFILE Autobackup at 11-MAY-07
    piece handle=c-3404436532-20070511-00 comment=API Version 2.0,MMS Version 5.0.0.0
    Finished Control File and SPFILE Autobackup at 11-MAY-07
    sql statement: alter database open
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-10010: error while checking for RPC completion
    RMAN-10011: synchronization error while polling for rpc 8, action=startdefault
    Recovery Manager complete.
    051107065708: RMAN BACKUP FAILED, RMAN exit status=1
    051107065708: Cleaning log file (removing passwords)
    051107065709: Error Log Check
    051107065837: Rman Stat Generator
    051107065956: Backup Html Generator
    051107065956: NetBackup RMAN Backup Finished
    ######################################################

    Check on metalink:
    RMAN-10011: synchronization error while polling for rpc 3, action=startdefault
    Note:429572.1
    Werner

  • Is it recommend to have a vulnerability scan for Cisco ASA device.

    Dear everyone. 
    I have a doubt on vulnerability scan for Cisco ASA device. Currently we have a vulnerability for network devices include firewall. But after run the vulnerability scan for cisco ASA, found nothing show in the scan report. 
    Is it recommend to have a vulnerability scan for Cisco ASA and will it be defeat the purpose of firewall?

    Do I understand are you asking can you configure the ASA to allow an external user run a scan against the internal network?
    If so, the answer is generally no. The ASA will, by default, not allow any inbound connections (or attempted connections) that are not explicitly allowed in an inbound access-list (applied to the outside interface). In most cases there would also need to be network address translation (NAT) rules configured.
    If you had a remote access VPN, you could allow the external scanner to log in via that, Then they would then have the necessary access to scan the internal systems (assuming the VPN granted access to all the internal networks)

  • Error msg : Message no. IO304 while delivery for serial no.

    Hi,
    In serial no. profile we have maitain
        MMSL     Maintain goods receipt and issue doc.     03     01
        PPAU     Serial numbers in PP order                           03     01
        PPRL     PP order release                           03     01
       PPSF     Serial nos in repetitive manufacturing     03     01
       QMSL     Maintain inspection lot                           03     01
       SDAU     Serial numbers in SD order     01     01
       SDCC     Completness check for delivery     02     01
       SDCR     Completion check IR delivery     02     01
       SDLS     Maintain delivery                          02     01
       SDRE     Maintain returns delivery                          02     01
    as per abovw while creating delivery serial no. are optional even als but While doing PGI  i am getting error message
    Only 0 serial numbers entered instead of 1
    Message no. IO304
    Diagnosis
    There is a serial number obligation, so the number of serial numbers must equal the number of serial numbers in the material document.
    You can post the operation only if you entered the correct number of serial numbers previously.
    can you help on this issue.
    regards,
    zafar

    Done it with some "diff. way"
    What way ???  Please develop the habit of updating the forum if you resolved any issue on your own.
    thanks
    G. Lakshmipathi

  • "Application Error"  While running application in real device

    HI all,
    When i run application on real device( Nokia 7360), It gives me Application Error
    My application is running well in wireless toolkit Emulator..
    I dont know why this is happining on real device?...
    regards
    Pravin

    Here is the code
    It just create a new contact in the AddressBook
    and i use Nokia 7360 for running my application
    import javax.microedition.midlet.*;
    import javax.microedition.lcdui.*;
    import javax.microedition.pim.*;
    import java.util.Enumeration;
    public class AddContact extends MIDlet implements CommandListener,Runnable
         Form form;
         Display display;
         Command exit;
         Command add;
         Alert alert;
         public Thread th;
    private boolean quit = false;     
         public AddContact()
         display = Display.getDisplay(this);
         form = new Form("Add Contact");
         exit = new Command("Exit",Command.EXIT,1);
         add = new Command("Add Contact",Command.OK,1);
         alert = new Alert("Add Contact","Contact Added Succesfully",null,null);
         alert.setTimeout(Alert.FOREVER);
         form.addCommand(add);     
         form.addCommand(exit);
         form.setCommandListener(this);
         public void startApp()
              display.setCurrent(form);
              th = new Thread(this);  
         public void pauseApp()
         public void destroyApp(boolean unconditional)
          public void commandAction(Command c, Displayable d) {
               if(c==exit)
                   destroyApp(false);
                         notifyDestroyed();
              else if (c == add)
                        if(!quit)
                        th.start();
                        display.setCurrent(alert);
         public void quit()
         quit = true;
         public void run()
         while (!quit)
              try
              PIM pim = PIM.getInstance();
              ContactList cl = null;
              Contact new_contact = null;
              Enumeration read_contact = null;
              String final_no="";
              try
                   cl = (ContactList)pim.openPIMList(PIM.CONTACT_LIST,PIM.READ_WRITE);
              catch(PIMException pime)
                   Alert alert_1 = new Alert("Error","Error Accessing Database"+pime,null,null);
                   alert_1.setTimeout(Alert.FOREVER);
                   alert_1.setType(AlertType.ERROR);
                   display.setCurrent(alert_1);
              catch(SecurityException se)
                   Alert alert_2 = new Alert("Error","Security Error"+se,null,null);
                   alert_2.setTimeout(Alert.FOREVER);
                   alert_2.setType(AlertType.ERROR);
                   display.setCurrent(alert_2);
              new_contact = cl.createContact();
              new_contact.addString(Contact.TEL,Contact.ATTR_HOME,"123456");
              new_contact.addString(Contact.FORMATTED_NAME,Contact.ATTR_NONE,"AasdD");
              new_contact.addString(Contact.TEL,Contact.ATTR_MOBILE,"2634465");
              new_contact.addString(Contact.TEL,Contact.ATTR_FAX,"+91 7834465");
              new_contact.addString(Contact.TEL,Contact.ATTR_PAGER,"7034465");
              new_contact.addString(Contact.TEL,Contact.ATTR_MOBILE,"9234465");
              try
                   new_contact.commit();
              catch(PIMException piem)
                        Alert alert_4 = new Alert("Error","Error while saving  Data"+piem,null,null);
                        alert_4.setTimeout(Alert.FOREVER);
                        alert_4.setType(AlertType.ERROR);
                        display.setCurrent(alert_4);
              try
                   cl.close();
              catch(PIMException piem)
                   Alert alert_5 = new Alert("Error","Error Closing Application"+piem,null,null);
                        alert_5.setTimeout(Alert.FOREVER);
                        alert_5.setType(AlertType.ERROR);
                        display.setCurrent(alert_5);
              catch (Exception e)
                   Alert alert_4 = new Alert("Error","Error on first try"+e,null,null);
                   alert_4.setTimeout(Alert.FOREVER);
                   alert_4.setType(AlertType.ERROR);
                   display.setCurrent(alert_4);
              quit();
         

  • Occasional hang at boot while scanning for PnP cards

    Sometimes my media center won't boot. It hangs at:
    isapnp: Scanning for PnP cards...
    This only happens once in a while (once every 10 or 20 boots). The system is an ION based system, it does not happen on my desktop system? Anyone seen this behaviour? Something ACPI related maybe? Thanks!

    i know, but i really dont know what else to include. I dont know what log files i should be reading. Im new to Arch
    EDIT: I just checked my /var/log/slim.log file and i notice every time the system fails it has the message::
    slim: unexpected signal 15
    EDIT: i also get the following message in slim.log:
    slim: pam_end: system error
    Last edited by yuggoth (2013-03-18 21:37:03)

  • Officejet 6700 error while searching for updates: 'Printer could not connect to server'

    I recently purchase the Officejet 6700 Premium. While setting the printer up, I received the error 'The printer could not connect to the server.' I first received this while the printer was searching for updates. I later received the same error while trying to set up ePrint from my computer.
    The printer is connected through my wireless router. All other print services function normally. It is connected to the network, and I have printed several times over the wireless network.
    Though I don't think it matters, since the on-board print set-up gave me the error, I run Windows 7 64-bit on my computer.
    Thanks for any help!

    What is the IP address of the printer?  What is the make and model of the router that you use in the wireless set up? Is the router firmware up to date? 
    I would first try power cycling the router and the printer. Turn off/unplug the router and then power down the printer. Then plug the router back in and wait for it to be fully up and functioning before turning the printer back on.  After you have both pieces of equipment back on and functioning attempt to connect to web services again.
    If still having problems I would attempt to set a static DNS on the printer through the embedded web server (EWS) by entering the printer's IP address into the address bar of  a browser on a computer. 
    Once that computer displays that page click on the Network tab.
    Then look in the column to the left and find the Wireless section
    Click on IPv4
    Then on that page look at the 2nd section that is labeled DNS Address configuration
    Change the radio button to the manual option
    Then for the manual preferred fill it out and make sure it reads 8.8.8.8
    Secondary should be set to 8.8.4.4
    Then hit Apply
    Read the next screen carefully. That message with the "OK" button below it  is one that states to click that button to undo the changes you  just made.  Just navigate away from that page by clicking on another tab.
    Then reattempt to connect to web services.  
    I am a former employee of HP...
    How do I give Kudos?| How do I mark a post as Solved?

Maybe you are looking for