VSS error on host-level backups

We have recently virtualized a Windows Server 2003 SP2 server into a Hyper-V 2008 R2 cluster, and as we're running DPM 2012 R2 we have to protect it on host-level as there's no agent support for W2003 in DPM 2012 R2. However, I keep getting the error below
when running a consistency check on the server:
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried, the error may not reoccur (0x800423F3).
There are a lot of VSS writers with "waiting for completion" status after a snapshot - System writer, NTDS, IIS, and FRS. The Hyper-V writer gets a retryable error on the host, but other VM's on the same host works just fine. We have
also tried to move this VM to another Hyper-V host but with the same result. KB940349 is already installed on the server but it doesn't seem to help.
Any ideas or suggestions are much appreciated!
/Amir

1. http://support.microsoft.com/kb/2460912 - volsnap.sys
2. http://support.microsoft.com/kb/2263829 - hvboot.sys
3. http://support.microsoft.com/kb/2541014 - diskdump.sys
Can you upgrade (reinstall) cluster to Windows Server 2012 or R2?
Protecting Windows 2003 Workload Hyper-V DPM 2012 R2
also Looking in the VM there was 0 bytes free , leaving the VSS writer unable to do any work , so after expanding the drive the backup is successful
http://flemmingriis.com/replica-is-inconsistent-hyper-v-2012-dpm-vm-backup/                                                                                                                                                  
http://jeffgraves.me/2010/04/08/error-0x800423f3-backing-up-hyper-v-vm-with-dpm-2007/

Similar Messages

  • Problem: VSS error with 'SQL Server Backup to Windows Azure Tool' installed

    When 'SQL Server Backup to Windows Azure Tool' is installed, shadow copies cannot be enable and backups fail.  When attempting to enable shadow copies, we get a "volsnap" error:  "The shadow copies of volume X were aborted because
    of a failed free space computation".  After uninstalling the "Tool", VSS works.  Reinstalling "Tool" causes the problem to return.
    While the error suggests a space issue, there is plenty of space on the server's two volumes.  Additionally, another 100GB volume was added and VSS storage was allocated to it; still received the error.
    Issue seems to point to 'SQL Server Backup to Windows Azure Tool'.
    Environment:  Hyper-V guest:  "Windows Server 2012 R2 Standard" with "SQL Server 2008 R2 Standard".  Using "Azure Storage" for SQL backups.
    Suggestions?

    Hello,
    Yes, we have a confirmed interference between the tool and the VSS Framework. This was identified very recently and is under investigation by the product group. Since the issue is within the filter driver shipped by the tool, that unfortunately means that
    you currently need to choose between the tool and a working VSS Framework. If the latter is more important, then uninstall the tool (that will require a restart).
    We apolologize for the inconvenience. I'm going to try to get the home page of the tool updated to avoid other situations like yours. Hopefully we should see a new version of the tool soon.
    As a side note, recent versions of SQL Server can directly use Azure Storage as backup target, see
    http://msdn.microsoft.com/en-us/library/jj919148(v=sql.110).aspx.
    Regards,
    Guillaume Fourrat - Microsoft France

  • Disable guest aplication interaction during Host level backup

    Hi,
    I have a 3 nodes Hyper-V Cluster, the hosts are Windows 2012 R2 Datacenter.
    Some of my guests are Windows Server 2008 R2 with Exchange 2010.
    When i backup the Exchange VMs the guest is aware of the backup and it flush the transaction logs.
    I want to disable this feature. Every solution I found refers to this KB:
    http://support.microsoft.com/kb/975354
    but this KB refers to Windows Server 2008 R2 Hyper-V host, I'm not sure that it applies also to Windows 2012 R2 Hyper-V hosts.
    Is there somebody that tried on Windows Server 2012 Hyper-V host? Does it still apply?
    Roberto
    Roberto Ferazzi
    Microsoft® MVP Exchange Server
    Moderator in the Microsoft TechNet Forums
    My MVP Profile
    MSExchange.Community

    Hi Sir,
    That registry should work , please refer to the answer of this similar thread :
    https://social.technet.microsoft.com/Forums/en-US/0f782ec5-489a-473c-893b-e260455d75cd/dpm-2012-r2-windows-server-2012-r2-hyperv-exchange?forum=dpmhypervbackup
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • VSS error 8193 and 22 by backup task (Windows server 2012)

    Hello,
    On the WinServer 2012 Std , I am facing VSS error when it starts "system state backup".
    The user account of this task is a member of "local Backup operators".
    how can I correct this error ?
    In the forum, I found a topic that had mentioned regsvr32.
    But Microsoft said it does not recommended/ supported for 2008 or later.
    http://social.technet.microsoft.com/Forums/office/en-US/2b1f44e0-725a-4fc5-bc1d-69437871fe90/wierd-volume-shadow-copy-service-errors?forum=winserverfiles
    -Quote [start]-
    Reregistering files was a common way to fix VSS issues back in Windows 2003.  However, due to the changes in Windows 2008 and 2008R2 servicing, reregistering files will either not work or actually damage Windows.
    Please discontinue using
    regsvr32.
    Robert Mitchell Senior Support Escalation Engineer Microsoft Corp.
    -Quote [End]-
    the detail of event logs are ;
    Log Name:      Application
    Source:        VSS
    Event ID:      22
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance
    on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered ].
    Log Name:      Application
    Source:        VSS
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
    hr = 0x80040154, Class not registered .
    Thank you for your support.

    Dear Sophia,
    Thank you for your instruction, the below is result of vssadmin.
    I am using CA Arcserve 16.5 for backing up system state.
    Writers
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Writer name: 'Task Scheduler Writer'
        Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
        Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
        State: [1] Stable
        Last error: No error
    Writer name: 'VSS Metadata Store Writer'
        Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
        Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
        State: [1] Stable
        Last error: No error
    Writer name: 'Performance Counters Writer'
        Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
        Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
        State: [1] Stable
        Last error: No error
    Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {540ecfcf-7f41-43cc-9521-d73d1881b85f}
        State: [1] Stable
        Last error: No error
    Writer name: 'SqlServerWriter'
        Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
        Writer Instance Id: {1fe1e4af-26ab-4113-8079-2c853e1a32fc}
        State: [1] Stable
        Last error: No error
    Writer name: 'ASR Writer'
        Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
        Writer Instance Id: {8094a9a6-29e1-4276-a8b0-7f9bd34e7ad5}
        State: [1] Stable
        Last error: No error
    Writer name: 'WMI Writer'
        Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
        Writer Instance Id: {3812a483-5e46-4c06-a64d-4caa1184705e}
        State: [1] Stable
        Last error: No error
    Writer name: 'IIS Config Writer'
        Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
        Writer Instance Id: {094ddb56-3e9a-452f-951a-22da278d7666}
        State: [1] Stable
        Last error: No error
    Writer name: 'Registry Writer'
        Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
        Writer Instance Id: {4f57f2af-4a0e-443d-ac27-c9b858c50744}
        State: [1] Stable
        Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
        Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
        Writer Instance Id: {54fb8f5c-2dff-479d-8ed1-b7de3c7495c3}
        State: [1] Stable
        Last error: No error
    Writer name: 'COM+ REGDB Writer'
        Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
        Writer Instance Id: {901cd0a6-895a-4942-ac60-c8a6a7796583}
        State: [1] Stable
        Last error: No error
    Providers
    C:\Windows\system32>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Provider name: 'SmVssProvider'
        Provider type: Hardware
        Provider Id: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
        Version: 10.84.02
    Provider name: 'Microsoft File Share Shadow Copy provider'
        Provider type: Fileshare
        Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
        Version: 1.0.0.1
    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
        Provider type: System
        Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
        Version: 1.0.0.7
    Shadows
    C:\Windows\system32>vssadmin list shadows vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    ^C
    Since command prompt has no output for 5mins, I pressed CTRL+C
    Shadowstorage
    C:\Windows\system32>vssadmin list shadowstorage vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    No items found that satisfy the query.
    Volumes
    C:\Windows\system32>vssadmin list volumes vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Volume path:
    \\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
         Volume name:
    \\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
    Volume path: D:\
         Volume name:
    \\?\Volume{88a134c9-020e-4020-8697-dc44c8a3c89a}\
    Volume path: C:\
         Volume name:
    \\?\Volume{d2760d79-5868-11e3-93e7-806e6f6e6963}\
    C:\Windows\system32>

  • Windows server backup crash vss errors

    We're having an issue where every other day the system state fails. We use a 3rd party piece of software that uses WSB for the system state. We get the following in the eevnt logs:
    Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
    Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
    Exception code: 0xc0000005
    Fault offset: 0x0000000000055384
    Faulting process id: 0x3560
    Faulting application start time: 0x01d01197a2bdc7a1
    Faulting application path: C:\Windows\system32\wbengine.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: d6f0610d-7d8f-11e4-a8f7-5cf3fc557333
    and the following when running vssadmin list writers:
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {7655da00-923b-441b-bc40-d64e3d44aaa9}
       State: [1] Stable
       Last error: No error
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {0e9c9681-5e67-4748-900c-b32ff7ebd072}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {3e4d034d-b955-428e-952b-0581f8e05203}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {3ee8ab83-468c-4cfe-8613-6946976820fb}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {2975a331-2068-4a6e-a16f-4635f5ce2856}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {43188986-6573-45a8-b871-4be3d189a45f}
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {a9632f02-31e3-424c-8c87-69395dbf04e2}
       State: [1] Stable
       Last error: No error
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {180f4d03-93aa-4947-b874-c2d0d7546ca0}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {231ceb2e-3b8c-40f1-8d02-22a4f263802d}
       State: [1] Stable
       Last error: No error
    Writer name: 'TS Gateway Writer'
       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
       Writer Instance Id: {60237974-e116-454e-b29c-6ffeffd1bd9d}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {440c5208-9d3a-4c84-884c-f9a3d8ad2c1e}
       State: [1] Stable
       Last error: No error
    Writer name: 'NPS VSS Writer'
       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
       Writer Instance Id: {d6ae39a4-2c8b-4e48-9f79-12247b9fac5b}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {c616d312-5e21-47df-9e59-100cf6ac6f0e}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {8f945f3b-d50b-47b8-9085-1416d0b094e1}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {50c005a1-35e8-4bc1-a0c1-1bcdc9351322}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {2bcebf65-9243-4ccd-bae2-6ae12efd9a51}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {4101713c-f207-431f-be52-1171f1227c0b}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {aa053355-2571-4e37-ba1d-501127ab2846}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {7645b18a-8aa4-49d3-abd1-5d7debd4b3f3}
       State: [1] Stable
       Last error: No error
    as i said - this happens every other day, the 3rd party software provider say this is a microsoft issue but this doesnt happen when running a system state directly from WSB

    Hi,
    What third party software do you use? There is a similar thread, please try to restart Block Level Backup Engine Service and VSS service to check if could resolve the issue. 
    For more detailed information, please refer to the thread below:
    Backup SystemState 2008 R2 failed - The RPC server is unavailable.
    https://social.technet.microsoft.com/Forums/en-US/f92c0a5b-2cfb-47f9-9ace-6028f5316a03/backup-systemstate-2008-r2-failed-the-rpc-server-is-unavailable
    Best Regards,
    Mandy 
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried, the error may not reoccur. (0x800423F3))

    I got this error, how to fix it?
    DPM 2010 with latest roll-up (KB2615782) | DELL Server R710 (Windows 2008 R2 SP1) RAM: 24GB PF: 36-60GB | DELL TL4000 (4 Drives) | DELL TL2000 (2 Drives) | And still struggling and monitoring... Battle continues... life never happy ever after.. :(

      In Hyper-v, I have this errors: 
    List Writers
    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {52a247b1-bd8e-499c-915d-314f9080e993}
       State: [11] Failed
       Last error: Retryable error
    Eventvwr:
    SOURCE: VSS ID: 8229
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    Operation:
       PostSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {52a247b1-bd8e-499c-915d-314f9080e993}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 2460
    SOURCE: HYPER-V-VMMS ID: 10143
    Failed to delete the shadow copy (VSS snapshot) set with id '3ED86740-3BFC-4FD5-B6B6-5ADD63E87DB0' in the running virtual machine 'MACHINENAME': This operation returned because the timeout period expired. (0x800705B4). (Virtual machine ID E130C3C7-D2BC-4234-BD2A-766054A163F9)

  • Windows 2012 Server Backup Problems - VSS Error

          Our company uses Windows Server Backup to back up our Windows 2012 Server.  We back up the host component and the two virtual machines on the server.  Every time I install windows updates
    on our server my backup jobs stop working and I get a VSS error.  In order to get backup working again, I have to recreate my backup job.  In order to do this I have to attach all the backup drives to the computer at the same time. 
    This has been an issue all the way back to when the server was first installed.  At that time the person who installed Windows Server talked to Microsoft.  Microsoft said the problem would be fixed in the first service pack which they ended
    up never releasing.  I have looked online, but haven’t found any information on these issues.  Are there any fixes for these two problems?

    Hi,
    Sorry for the delay.
    Can you first do a backup then install windows updates? Please provide more detailed message about the VSS error.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Catalog backup getting Error resolving host - unknown host name in dataset

    I have new install of OSB version 10.3.0.1.0 [Admin, Mediaserver, Client] installed on the same OEL server. My Catalog Backup jobs end up with error " unknown host name in dataset" and the job detail shows only "Error resolving host - unknown host name in dataset" while I can ping the admin host with obtool pingh command. The standard auto created Catalog backup dataset looks like this:
    Dataset: OSB-CATALOG-DS
    # Dataset for backing up the OSB Catalog on this administrative host
    include catalog
    I am able to create a separate dataset with the hostname defined and able to backup filesystems on the same host, np . Only the catalog backup from system generated dataset and schedule doesn't run. I appreciate any help or tip to make this catalog backup work. Thanks.

    This problem is fixed by just restarting observiced on admin server.

  • Error vss writers exchange 2010 windows backup

    I have this error, when running windows backup on server with exchange 2010:
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {400de426-a419-459f-a953-91026051bf91}
       State: [8] Failed
       Last error: Retryable error
    I've rebooted the server several times, but without success.
    Does anyone have any idea?
    Thank you
    Cristiano Ianiri

    Hi,
    Do you have any running AV software? If there is, please set the AV Exclusion on database file or disable AV temporarily.
    From the description, you have restarted server several times. It didn't work. To narrow down the issue, could you please restart the Microsoft Exchange Information Store service again on the server where you did backup at your convenience?
    After that, please run the VSSadmin list writers command to determine whether the writer state returns to a stable state.
    Besides, please check the database that you want to backup to see if it is in healthy state. You can use the get-mailboxdatabasecopystatus cmdlet to check this.
    If you have checked steps above, please increase the diagnostic logging level for the Exchange Writer and check if there is any clues.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Large number VSS errors "The specified network resource or device is no longer available."

    I have a 2 node Hyper V Cluster backed up via Veeam Off-Host Proxy. I've already logged, without answer, a thread about the Off-Host Proxy server randomly (I guess) creating new duplicate iSCSI connections.
    Today I have a single VM that won't backup. On inspection through the hosting servers Application Log I see a high amount of VSS errors being logged which I believe is possibly related to the iSCSI issue being logged by the SAN.
    I'm not sure how to "show" the issue without a giant wall of the events but there is like half a dozen different events being logged when whatever this is is happening. For instance as well last night 60/61 VMs backed up find, but these errors
    were logged constantly while the backup ran...
    The question as well is is this a Windows/VSS issue, a Veeam issue or a Equallogic issue?
    Also how do I find what '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'. actually is?
    In order of how they come I guess:
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:28:19 AM
    Event ID:      8229
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    Operation:
       PrepareForSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {881f5207-f769-4b40-986a-c6bd56d8aa1e}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 3268
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:31 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'.  hr = 0x80070037, The specified network resource or device is no longer available.
    Operation:
       Check If Volume Is Supported by Provider
    Context:
       Execution Context: Coordinator
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\
    Log Name:      Application
    Source:        EqualLogic
    Date:          6/01/2015 7:29:43 AM
    Event ID:      4001
    Task Category: VSS
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    iSCSI logout error 0xEFFF0040 from target NULL.
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:43 AM
    Event ID:      12293
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details OnLunStateChange(\\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})
    failed with error 0xefff0040 [hr = 0xefff0040]. 
    Operation:
       Notifying hardware provider to free a drive
       Break with LUN mask
       Delete Shadow Copies
       Processing PostFinalCommitSnapshots
       Executing Asynchronous Operation
    Context:
       Volume Name: \\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
       Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
       Execution Context: Provider
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Snapshot Context: 4194336
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Current State: DoSnapshotSet
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:43 AM
    Event ID:      12293
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details could not free LUN [hr = 0x8004230f, The shadow copy provider had an unexpected error while trying to process the
    specified operation.
    Operation:
       Break with LUN mask
       Delete Shadow Copies
       Processing PostFinalCommitSnapshots
       Executing Asynchronous Operation
    Context:
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
       Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
       Execution Context: Provider
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Snapshot Context: 4194336
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Current State: DoSnapshotSet
    (Below logged 3 times)
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:49 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'.  hr = 0x80070037, The specified network resource or device is no longer available.
    Operation:
       Check If Volume Is Supported by Provider
    Context:
       Execution Context: Coordinator
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\

    This is the issue having with redundant iSCSI connections being created:
    Not sure this is a Veeam issue, just that it's occurring with Veeam backup process.
    We have a server configured as an Off-Host Proxy with Veeam; it connects to the SAN storage via iSCSI same as the other hosts but accesses the storage as read only.
    Randomly we will get alerts from the SAN as below:
    iSCSI login to target '172.16.0.50:3260, iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1' from initiator '172.16.0.44:64108, iqn.1991-05.com.microsoft:arcbackproxy.domain.local' failed for the following reason:
    Requested target not found.
    On inspection of the Off-Host Proxy's iSCSI configuration additional iSCSI connections are present as inactive, with an existing connections name amended with the date at the end. For instance (and in the example error above) there will be:
    iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1
    and
    iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1
    Not really causing an issue, the backups are running OK, or any issues we have aren't related. But getting annoying getting the alerts from the SAN of the Off-Host Proxy trying to connect to an incorrect iSCSI target.
    Any ideas why this is occurring?
    Obvious is we delete the extra connection, which stops the alert, but the issue will reoccur within a day or two usually.
    Today I found twice the alert as above and sure enough the iSCSI on the Off-Host Proxy is as below:
    Maybe these redunandant connections being created is related? Maybe that's the where the "The specified network resource or device is no longer available." is coming from or something?

  • VSS Error in writer Hyper-V

    I have a cluster with CSV 5 and DPM can't perform backup on only a few machines in the cluster, it apesenta VSS the following error:
    The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\Máquina on MAQUINA.CLOUD04.dominio.local is inconsistent with the protected data source.
    All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. 
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency
    check on the farm. (ID 3106)
    DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
     (0x800423F3))
    Well investigating deeper into the Hyper-V server virtualization encounter the following errors:
    Eventvwr:
    SOURCE: VSS ID: 8229
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    Operation:
       PostSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {52a247b1-bd8e-499c-915d-314f9080e993}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 2460
    SOURCE: HYPER-V-VMMS ID: 10143
    Failed to delete the shadow copy (VSS snapshot) set with id '3ED86740-3BFC-4FD5-B6B6-5ADD63E87DB0' in the running virtual machine 'MAQUINA': This operation returned because the timeout period expired. (0x800705B4). (Virtual machine ID E130C3C7-D2BC-4234-BD2A-766054A163F9)
    List Writers
    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {52a247b1-bd8e-499c-915d-314f9080e993}
       State: [11] Failed
       Last error: Retryable error
    Well, how did not get any results in searches, then checked the versions of the IC on client machines as clusters migrated from 2008 to 2012 some were outdated, updated them, even just to leave everything compliance. 
    So I decided to clear the "Backup (volume snapshot)" and now he backs up but does the same linux machines, saving the machine and causing downtime of it, and even if you are a linux machine with this option it can not perform the backup this because
    it tries utilizr VSS method (I think).
    Please, anyone help-me?
    thanks!

    Hi ,
    Please refer to following similar thread :
    http://social.technet.microsoft.com/Forums/en-US/be7fd80f-d2bc-4e1b-9bc2-a60af6e89e2a/dpm-faild-to-backup-hyperv-gest-vm-code-0x800423f3-id-30112?forum=dpmhypervbackup
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows Server 2012 Windows Backup failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).

    The Volume Shadow Copy service initially was running under the context of System, so we thought that ‘System’ doesn’t have permissions to access network shares. 
    When the Volume Shadow Copy service was running under the context of System, this was the error logged:
    “failed with following error code '0x8078014B' (There was a failure in creating a directory on the backup storage location.).”
    Which is likely due to not having permissions to write to the network location. 
     This is a scheduled backup trying to write to a network location, so we changes the service to run under the context of an account that does have permissions to write to the network share.
      Then the error changed to this:
    “failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).”
    HRESULT 0x8078006b
    DetailedHRESULT 0x8004230f
    ErrorMessage %%2155348075
    BackupState 12
    VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0"
    BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0"
    TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228"
    DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0"
    FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0"
    /></VolumeInfo>
    We aren’t really seeing anything that gives any hint on what the issue is. 
    Any ideas?  Thanks in advance!

    We are trying to back up folders/files from 2 local drives (C: & D:), both of which have only 10% space used, and 100 GB free. 
    We are attempting to back the files up to a Remote Shared File (and there is 100+ GB free space out there). 
      If we try another network location, we receive the exact same error. 
     This is Windows Server 2012, not running Hyper-V and is a physical server not a VM.
    Thank you for the link. 
    Looking in: 
    Event Viewer / Application and Service Logs / Microsoft / Windows / Backup / Operational
    But it doesn’t seem to give any more details: 
    Log Name:     
    Microsoft-Windows-Backup
    Source:       
    Microsoft-Windows-Backup
    Date:         
    7/8/2013 8:00:12 PM
    Event ID:     
    5
    Task Category: None
    Level:        
    Error
    Keywords:     
    User:         
    SYSTEM
    Computer:     
    servername.edu
    Description:
    The backup operation that started at '‎2013‎-‎07‎-‎09T02:00:06.273000000Z' has failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).
    Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
    <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" />
    <EventID>5</EventID>
    <Version>3</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2013-07-09T02:00:12.872602100Z" />
    <EventRecordID>30</EventRecordID>
    <Correlation />
    <Execution ProcessID="3028" ThreadID="3996" />
    <Channel>Microsoft-Windows-Backup</Channel>
    <Computer>servername.edu</Computer>
    <Security UserID="S-1-5-18" />
      </System>
      <EventData>
    <Data Name="BackupTemplateID">{A421E864-A115-4288-8D12-F4878CF8A248}</Data>
    <Data Name="HRESULT">0x8078006b</Data>
    <Data Name="DetailedHRESULT">0x8004230f</Data>
    <Data Name="ErrorMessage">%%2155348075</Data>
    <Data Name="BackupState">12</Data>
    <Data Name="BackupTime">2013-07-09T02:00:06.273000000Z</Data>
    <Data Name="BackupTarget">\\servername\BACKUP</Data>
    <Data Name="NumOfVolumes">2</Data>
    <Data Name="VolumesInfo">&lt;VolumeInfo&gt;&lt;VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0"
    IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;VolumeInfoItem
    Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0"
    NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;/VolumeInfo&gt;</Data>
    <Data Name="SourceSnapStartTime">2013-07-09T02:00:06.289250300Z</Data>
    <Data Name="SourceSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="PrepareBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PrepareBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="DVDFormatStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="DVDFormatEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="MediaVerifyStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="MediaVerifyEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupPreviousState">2</Data>
    <Data Name="ComponentStatus">&lt;ComponentStatus&gt;&lt;/ComponentStatus&gt;</Data>
    <Data Name="ComponentInfo">&lt;ComponentInfo&gt;&lt;/ComponentInfo&gt;</Data>
    <Data Name="SSBEnumerateStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBEnumerateEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBVhdCreationStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBVhdCreationEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBBackupStartTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SSBBackupEndTime">1601-01-01T00:00:00.000000000Z</Data>
    <Data Name="SystemStateBackup">&lt;SystemState IsPresent="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="BMR">&lt;BMR IsPresent="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="VssFullBackup">false</Data>
    <Data Name="UserInputBMR">false</Data>
    <Data Name="UserInputSSB">false</Data>
    <Data Name="BackupSuccessLogPath">
    </Data>
    <Data Name="BackupFailureLogPath">
    </Data>
    <Data Name="EnumerateBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="EnumerateBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PruneBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PruneBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupFlags">0x9</Data>
    <Data Name="ComponentInfoSummary">&lt;ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /&gt;</Data>
      </EventData>
    </Event>

  • Getting error when try to backup oracle rac to another location

    Hi there,
    I am attempting to backup database to another location from a Oracle RAC database version 11gr2. Here is my script:
    #!/bin/ksh
    export ORACLE_SID=vvsms1
    ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE
    ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1; export ORACLE_HOME
    BASE_PATH=/usr/sbin:$PATH; export BASE_PATH
    PATH=$ORACLE_HOME/bin:$BASE_PATH; export PATH
    /u01/app/oracle/product/11.2.0/dbhome_1/bin/rman target sys/viviet@vvsms log /home/oracle/log_rman/vvsms.log append <<EOF
    RUN {
    CROSSCHECK BACKUP;
    CROSSCHECK ARCHIVELOG ALL;
    ALLOCATE CHANNEL CHANNEL1 TYPE DISK FORMAT '/home/oracle/backup/vvsms/backup_%U';
    BACKUP INCREMENTAL LEVEL 0 TAG 'incr_vvsms' DATABASE;
    BACKUP ARCHIVELOG ALL;
    DELETE OBSOLETE;
    RELEASE CHANNEL CHANNEL1;
    EXIT;
    EOF
    I write it into a .sh file and set crontab to run it. But when it run i get the error like these:
    Starting backup at 22-OCT-12
    channel CHANNEL1: starting incremental level 0 datafile backup set
    channel CHANNEL1: specifying datafile(s) in backup set
    input datafile file number=00002 name=+DISK2/vvsms/datafile/sysaux.289.794242439
    input datafile file number=00006 name=+DISK2/vvsms/datafile/ts_service.dbf
    input datafile file number=00007 name=+DISK2/vvsms/datafile/ts_viviet.dbf
    input datafile file number=00008 name=+DISK2/vvsms/datafile/viviet.dbf
    input datafile file number=00009 name=+DISK2/vvsms/datafile/ts_vivietct_primary.dbf
    input datafile file number=00003 name=+DISK2/vvsms/datafile/undotbs1.290.794242445
    input datafile file number=00001 name=+DISK2/vvsms/datafile/system.288.794242429
    input datafile file number=00004 name=+DISK2/vvsms/datafile/undotbs2.292.794242453
    input datafile file number=00005 name=+DISK2/vvsms/datafile/users.293.794242455
    channel CHANNEL1: starting piece 1 at 22-OCT-12
    released channel: CHANNEL1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on CHANNEL1 channel at 10/22/2012 01:50:16
    ORA-19504: failed to create file "/home/oracle/backup/vvsms/backup_2anobqu5_1_1"
    ORA-27040: file create error, unable to create file
    Linux-x86_64 Error: 2: No such file or directory
    I don't know what i'm wrong? The location is correct ("/home/oracle/backup/vvsms/).
    Please suggest me some things about it. What do i need to do?
    Thanks in advance!
    P/s: Sorry for my bad English.

    /u01/app/oracle/product/11.2.0/dbhome_1/bin/rman target sys/viviet@vvsms  log /home/oracle/log_rman/vvsms.log appendThis line can be your problem.
    As this database is a RAC and your are using a service with load balance "vvsms" and "/home/oracle/backup/vvsms" is not a shared location. RMAN is starting a session on Other node where "/home/oracle/backup/vvsms" does not exists.
    Try change it :
    /u01/app/oracle/product/11.2.0/dbhome_1/bin/rman target sys/viviet@vvsms  log /home/oracle/log_rman/vvsms.log appendTo this (using Easy Connect Method):
    /u01/app/oracle/product/11.2.0/dbhome_1/bin/rman target sys/viviet@localhost:1521/VVSMS  log /home/oracle/log_rman/vvsms.log appendWhere:
    localhost: your local node
    VVSMS : is the service of database
    Also check if "/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora" have configured the line "NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)"
    P.S : When RMAN start a session it show where is logged, check on logs what instance RMAN was logged.
    HTH,
    Levi Pereira

  • Solaris 10 SCSI transport failed reason 'tran err' on host level

    Hello,
    we are frequently getting below errors on host, can any one please help to solve this issue?
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
    Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
    Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
    Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
    Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
    Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
    Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
    Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
    Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
    Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
    Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
    Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
    Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
    Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
    Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
    Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
    Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
    Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
    Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
    Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
    Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
    Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
    Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
    Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
    Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
    Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
    Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
    Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
    Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
    Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
    Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
    Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.core

    Hello,
    we are frequently getting below errors on host, can any one please help to solve this issue?
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 1 04:41:49 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 04:41:49 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 1 16:51:30 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 1 16:51:30 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 1 20:41:09 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 1 20:41:09 host SCSI transport failed: reason 'tran_err': retrying command
    Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::GPN_ID for D_ID=2e1400 failed
    Mar 2 00:30:14 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 disappeared from fabric
    Mar 2 00:30:16 host fctl: [ID 517869 kern.warning] WARNING: fp(3)::N_x Port with D_ID=2e1400, PWWN=50060e80164ed673 reappeared in fabric
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 2 00:30:16 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 2 00:30:16 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 2 00:30:18 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 2 00:30:18 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Requested Block: 367501 Error Block: 367501
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B0
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:30:18 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:30:36 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,5 (ssd112):
    Mar 2 00:30:36 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Requested Block: 201152 Error Block: 201152
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B5
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:30:36 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:31:40 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
    Mar 2 00:31:40 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Requested Block: 10063136 Error Block: 10063136
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B2
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:31:40 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 00:32:31 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,4 (ssd113):
    Mar 2 00:32:31 host Error for Command: write(10) Error Level: Retryable
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Requested Block: 71274 Error Block: 71274
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B4
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 00:32:31 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 03:41:29 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,3 (ssd114):
    Mar 2 03:41:29 host Error for Command: read(10) Error Level: Retryable
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Requested Block: 88112 Error Block: 88112
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B3
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 03:41:29 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 06:00:00 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,1 (ssd116):
    Mar 2 06:00:00 host Error for Command: read(10) Error Level: Retryable
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Requested Block: 202608 Error Block: 202608
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Vendor: HP Serial Number: 50 14ED622B1
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] Sense Key: Unit_Attention
    Mar 2 06:00:00 host scsi: [ID 107833 kern.notice] ASC: 0x29 (power on, reset, or bus reset occurred), ASCQ: 0x0, FRU: 0x0
    Mar 2 17:02:01 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 2 17:02:01 host SCSI transport failed: reason 'timeout': retrying command
    Mar 4 02:07:11 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-1
    Mar 4 02:07:21 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130304020711-2
    Mar 5 02:06:47 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-1
    Mar 5 02:06:57 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130305020647-2
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 5 08:02:48 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 08:02:48 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 5 10:02:55 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,2 (ssd115):
    Mar 5 10:02:55 host SCSI transport failed: reason 'timeout': retrying command
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 5 14:09:40 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 5 14:09:40 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 02:06:38 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-1
    Mar 6 02:06:48 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130306020638-2
    Mar 6 05:00:00 host explorer: [ID 702911 daemon.notice] Explorer started
    Mar 6 05:02:49 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18043] core dumped: /ecmp/ecm/log/cores/luxadm.host.18043.core
    Mar 6 05:02:50 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18046] core dumped: /ecmp/ecm/log/cores/luxadm.host.18046.core
    Mar 6 05:02:54 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[18331] core dumped: /ecmp/ecm/log/cores/luxadm.host.18331.core
    Mar 6 05:03:46 host explorer: [ID 702911 daemon.notice] Explorer finished
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 6 06:01:22 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 06:01:22 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 12:27:02 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28834] core dumped: /ecmp/ecm/log/cores/luxadm.host.28834.core
    Mar 6 12:27:33 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[28839] core dumped: /ecmp/ecm/log/cores/luxadm.host.28839.core
    Mar 6 15:24:11 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5006] core dumped: /ecmp/ecm/log/cores/luxadm.host.5006.core
    Mar 6 15:30:52 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5699] core dumped: /ecmp/ecm/log/cores/luxadm.host.5699.core
    Mar 6 15:31:57 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5975] core dumped: /ecmp/ecm/log/cores/luxadm.host.5975.core
    Mar 6 15:32:39 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[5987] core dumped: /ecmp/ecm/log/cores/luxadm.host.5987.core
    Mar 6 15:36:16 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6274] core dumped: /ecmp/ecm/log/cores/luxadm.host.6274.core
    Mar 6 15:36:38 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[6286] core dumped: /ecmp/ecm/log/cores/luxadm.host.6286.core
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=5 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=4 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=3 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=2 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=1 ffffffff
    Mar 6 16:18:20 host scsi: [ID 243001 kern.info] /pci@8,600000/SUNW,qlc@1/fp@0,0 (fcp3):
    Mar 6 16:18:20 host ndi_devi_online: failed for scsa,00.bfcp: target=2e1400 lun=0 ffffffff
    Mar 6 18:23:44 host scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e80164ed673,0 (ssd117):
    Mar 6 18:23:44 host SCSI transport failed: reason 'tran_err': retrying command
    Mar 7 01:43:47 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.139069 s
    Mar 7 02:07:10 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-1
    Mar 7 02:07:20 host buxus: [ID 702911 daemon.notice] SYSLOG check 20130307020710-2
    Mar 7 02:07:58 host xntpd[735]: [ID 774427 daemon.notice] time reset (step) 0.152342 s
    Mar 7 07:23:29 host genunix: [ID 603404 kern.notice] NOTICE: core_log: luxadm[24350] core dumped: /ecmp/ecm/log/cores/luxadm.host.24350.core

  • Windows 2008 r2 windows installer issue error 1719 when install Backup exec 12.5

    Hi all
    After a epic weekend of rebuilding our exchange server I have tried to reinstall Backup exec 12.5 64bit, this was installed with no issues during the last build, however at the end of this build I went to reinstall Backup Exec 12.5 and it is failing with
    error 1719 Windows installer issue.
    I have looked on many sites and tried many things non of them have worked, has anyone managed to resolve this issue.
    Dave
    DJH

    Hi Lenora
    See below
    Symantec Backup Exec (TM) 12.5 for Windows Servers Installation Log
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\setup.exe
    03-19-2013,17:33:38 : CSetupApp::GetInstalledGUID
    03-19-2013,17:33:38 : CSetupApp::LoadSetupXML
    03-19-2013,17:33:38 : CSetupApp::ScanXML
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Bin\Setup.xml
    03-19-2013,17:33:38 : MSI File Name = WindowsInstaller-KB893803-v2-x86.exe
    03-19-2013,17:33:38 : MSI Version = 3.1
    03-19-2013,17:33:38 : MSI Package Name = Symantec Backup Exec for Windows Servers.msi
    03-19-2013,17:33:38 : System Central Processor = 64
    03-19-2013,17:33:38 : Product Type = SETUP_BEX64
    03-19-2013,17:33:38 : Product Name = Symantec Backup Exec for Windows Servers
    03-19-2013,17:33:38 : Current Installing GUID ={BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : Product Version = 12.5
    03-19-2013,17:33:38 : CSetupSupport::IsValidMSIPackage
    03-19-2013,17:33:38 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Symantec Backup Exec for Windows Servers.msi
    03-19-2013,17:33:38 : {BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : {BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:33:38 : Equal PID
    03-19-2013,17:33:38 : Product version: 12.5.2213
    03-19-2013,17:33:38 : StartBESequence
    03-19-2013,17:33:38 : Executing BE_PreCheckInstall
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:33:38 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:33:38 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:33:38 : Executing StartBESequence
    03-19-2013,17:33:38 : Pulling user data from the MSI
    03-19-2013,17:33:38 : Upgrade state set to 0
    03-19-2013,17:33:38 : Executing SSO::PullDataMSI()
    03-19-2013,17:33:38 : Executing CDlgCAS::PullDataMSI()
    03-19-2013,17:33:38 : MSI processing complete
    03-19-2013,17:33:38 : Pulling user data from the command line
    03-19-2013,17:33:38 : COMMAND LINE: Checking UIMODE value
    03-19-2013,17:33:38 : COMMAND LINE: Checking for program group placement value
    03-19-2013,17:33:38 : COMMAND LINE: Checking for main feature selection
    03-19-2013,17:33:38 : COMMAND LINE: Checking for serialization values
    03-19-2013,17:33:38 : CDlgChooseCustom::PullDataSilent
    03-19-2013,17:33:38 : After check for parameter file exists.
    03-19-2013,17:33:38 : CDlgLocalChooseCustom::Pass
    03-19-2013,17:33:38 : After Check for INSTALL_CHOICE.
    03-19-2013,17:33:38 : After Check for INSTALL_TYPE.
    03-19-2013,17:33:38 : After Check for INSTALL_MODE.
    03-19-2013,17:33:38 : CDlgLocalChooseCustom Pass Function end.
    03-19-2013,17:33:38 : Agent for Microsoft Exchange Server was added for evaluation
    03-19-2013,17:33:38 : Agent for Microsoft SQL Server was added for evaluation
    03-19-2013,17:33:38 : Ignoring the TSM switch.
    03-19-2013,17:33:38 : COMMAND LINE: Checking for service account values
    03-19-2013,17:33:38 : Not in Maintenance mode
    03-19-2013,17:33:38 : Getting the Silent Params.
    03-19-2013,17:33:38 : COMMAND LINE: checking for SSO values
    03-19-2013,17:33:38 : COMMAND LINE: checking for DlgChooseDBServer values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for tape drivers values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for TSM values
    03-19-2013,17:33:38 : COMMAND LINE: checking for CASO values
    03-19-2013,17:33:38 : COMMAND LINE: Checking for clone values
    03-19-2013,17:33:38 : COMMAND LINE: Checking progress settings
    03-19-2013,17:33:38 : COMMAND LINE: Checking for NOINSTALL value
    03-19-2013,17:33:38 : Setup Command Line = "D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\setup.exe"
    03-19-2013,17:33:38 : List of switches set follows:
    03-19-2013,17:33:38 : /DEST: = C:\Program Files\Symantec1\Backup Exec\
    03-19-2013,17:33:38 : /SNO: = 0930292112010690
    03-19-2013,17:33:38 : /USER: = backup
    03-19-2013,17:33:38 : /DOM: = ACCENTPRESS
    03-19-2013,17:33:38 : /PASS: = ********
    03-19-2013,17:33:38 : /TS:
    03-19-2013,17:33:38 : /TD: = ALL
    03-19-2013,17:33:38 : /DOCS:
    03-19-2013,17:33:38 : /LOADER:
    03-19-2013,17:33:38 : /AOFO:
    03-19-2013,17:33:38 : /EXCH:
    03-19-2013,17:33:38 : /SQL:
    03-19-2013,17:33:38 : /NTA:
    03-19-2013,17:33:38 : /RAULUS:
    03-19-2013,17:33:38 : /DBSERVER:
    03-19-2013,17:33:38 : /DBINSTPATH: = C:\Program Files\Microsoft SQL Server\BE\
    03-19-2013,17:33:38 : /BACKUPDATA: = 0
    03-19-2013,17:33:38 : /MAC:
    03-19-2013,17:33:38 : Command line processing complete
    03-19-2013,17:33:38 : Install set to run in UI mode
    03-19-2013,17:33:38 : CDlgPushWelcome::Pass
    03-19-2013,17:33:40 : CinstOpenDlg::ValidateData
    03-19-2013,17:33:43 : Validating license data
    03-19-2013,17:33:44 : CDlgChooseInstall::ValidateData
    03-19-2013,17:33:44 : CDlgValidationSummary::LaunchValidationTest
    03-19-2013,17:33:44 : m_bUseNativeClient = 1
    03-19-2013,17:33:44 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:33:44 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:33:44 : Connected to SQL Server.
    03-19-2013,17:33:44 : m_bUseNativeClient = 1
    03-19-2013,17:34:05 : CDlgValidationSummary::ValidateData
    03-19-2013,17:34:05 : BEOperations::BE_GetInstalledProdCodeVersion
    03-19-2013,17:34:05 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:05 : CDlgSerialNumber Pass Function.
    03-19-2013,17:34:05 : After Check for Remote_Install.
    03-19-2013,17:34:05 : After Check for RA_INSTALL.
    03-19-2013,17:34:07 : Validating serialization data
    03-19-2013,17:34:07 : CDlgLocalChooseCustom::Pass
    03-19-2013,17:34:07 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:07 : After Check for INSTALL_TYPE.
    03-19-2013,17:34:07 : After Check for INSTALL_MODE.
    03-19-2013,17:34:07 : CDlgLocalChooseCustom Pass Function end.
    03-19-2013,17:34:07 : On Init of CDlgChooseCustom
    03-19-2013,17:34:07 : Leaving Init of CDlgChooseCustom
    03-19-2013,17:34:07 : CDlgLocalChooseCustom::OnInitDialog
    03-19-2013,17:34:07 : On Init of CDlgLocalChooseCustom
    03-19-2013,17:34:07 : Leaving Init of CDlgLocalChooseCustom
    03-19-2013,17:34:12 : Validating Local Options Data
    03-19-2013,17:34:13 : Validating service account data
    03-19-2013,17:34:13 : CDlgSSO Pass Function.
    03-19-2013,17:34:13 : After Check for INSTALL_MODE.
    03-19-2013,17:34:13 : DlgChooseDBServer Pass Function.
    03-19-2013,17:34:20 : m_bUseNativeClient = 1
    03-19-2013,17:34:20 : Validating DlgChooseDBServer data
    03-19-2013,17:34:20 : Drive C:     Required: 1102 MB     Available: 37138 MB
    03-19-2013,17:34:20 : CDlgChooseTapeDrivers Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_MODE.
    03-19-2013,17:34:20 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:20 : After Check for INSTALL_TYPE.
    03-19-2013,17:34:20 : CDlgSerialNumber Pass Function.
    03-19-2013,17:34:20 : CDlgCAS Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_MODE.
    03-19-2013,17:34:20 : CDlgClone Pass Function.
    03-19-2013,17:34:20 : CDlgClone not passed.
    03-19-2013,17:34:20 : CDlgRemoteChooseCustom Pass Function.
    03-19-2013,17:34:20 : After Check for INSTALL_CHOICE.
    03-19-2013,17:34:20 : Install Summary XML File:
    03-19-2013,17:34:20 : C:\Users\ADMINI~1\AppData\Local\Temp\1\BE61998B-E5BD-4E41-B2D7-96551E6FECE0\InstallReview.xml
    03-19-2013,17:34:20 : Install Summary XSL File:
    03-19-2013,17:34:20 : D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\BE\Bin\InstallSummary.xsl
    03-19-2013,17:34:20 : Install Summary HTML File:
    03-19-2013,17:34:20 : C:\Users\ADMINI~1\AppData\Local\Temp\1\BE61998B-E5BD-4E41-B2D7-96551E6FECE0\InstallReview.htm
    03-19-2013,17:34:20 : Not Quickstart Edition
    03-19-2013,17:34:20 : Entering GetSQLAndCASOInformation
    03-19-2013,17:34:20 : Leaving GetSQLAndCASOInformation
    03-19-2013,17:34:20 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:20 : m_bUseNativeClient = 1
    03-19-2013,17:34:20 : *************** About Backing Up Exchange 2007 Servers *************** To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this
    computer.  The Management Tools can be installed during a custom install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft
    Exchange Server MAPI Client and Collaboration Data Objects package version 06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:34:21 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:34:27 : Executing InstallLiveUpdate.
    03-19-2013,17:34:40 : Installing .Net Framework 2.0 SP1.
    03-19-2013,17:34:40 : Checking for .Net Framework 2.0 SP1.
    03-19-2013,17:34:40 : Vista or Longhorn server.  Not installing .NET Frameworks.
    03-19-2013,17:34:40 : .NET Framework was detected.  Skipping install.
    03-19-2013,17:34:41 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:34:41 : m_bUseNativeClient = 1
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes;DATABASE=master
    03-19-2013,17:34:41 : SQL Server version 9
    03-19-2013,17:34:41 : SQL version returned:  9
    03-19-2013,17:34:41 : Executing SQL_GetServicePack.
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:34:41 : Connected to SQL Server.
    03-19-2013,17:34:41 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:34:41 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:34:41 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:34:41 : Connected to SQL Server.
    03-19-2013,17:34:41 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Express Edition
    03-19-2013,17:34:41 : "D:\Software\Backupexec 12.5 64bit\WINNT\INSTALL\SQLExpress\SQLEXPR.exe" /wait /qn /norestart /lv "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt" INSTANCENAME=BKUPEXEC SQLACCOUNT="NT AUTHORITY\SYSTEM" SQLPASSWORD=""
    UPGRADE=SQL_Engine,SQL_Data_Files,SQL_Replication,Client_Components,Connectivity SAPWD=**** DISABLENETWORKPROTOCOLS=0
    03-19-2013,17:34:45 : V-225-53:  ERROR: Failed to install SQL Express BKUPEXEC instance with error 1601.  ***To search for information about this error, click
    here
    03-19-2013,17:34:45 : Please review C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt for more details.
    03-19-2013,17:34:45 : Failed to install third party products.
    03-19-2013,17:37:25 : Validating install complete
    03-19-2013,17:37:25 : Success unloading BEINSTDLGS.DLL.
    03-19-2013,17:37:25 : CLEANUP: Install has removed the following files from: C:\Users\ADMINI~1\AppData\Local\Temp\1\{BE61998B-E5BD-4E41-B2D7-96551E6FECE0}
    03-19-2013,17:37:25 : Removed files:
    03-19-2013,17:37:25 : ERROR:  Installation failed with error 1603.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,17:41:16 : Windows Operating System Version: 6.1
    03-19-2013,17:41:16 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,17:41:18 : Executing managed _Setup:
    03-19-2013,17:41:18 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,17:41:18 : Loading XML from:
    03-19-2013,17:41:18 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,17:41:18 : RawsDlgSequence::CheckInstMode
    03-19-2013,17:41:18 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,17:41:19 : Launching UI Install
    03-19-2013,17:41:19 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:41:19 : m_bUseNativeClient = 1
    03-19-2013,17:41:19 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:41:20 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,17:41:20 : CopySupportFiles
    03-19-2013,17:41:20 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,17:41:20 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:41:20 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:41:20 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:41:28 : Typical install value is set to : True
    03-19-2013,17:41:29 : m_bUseNativeClient = 1
    03-19-2013,17:41:29 : Executing SQL_GetServicePack.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:41:29 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : Executing SQL_GetServicePack.
    03-19-2013,17:41:29 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:41:29 : Connected to SQL Server.
    03-19-2013,17:41:29 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:41:29 : m_bUseNativeClient = 1
    03-19-2013,17:41:51 : m_bUseNativeClient = 1
    03-19-2013,17:41:51 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:43:04 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,17:43:04 : Install is not executing as the service account.
    03-19-2013,17:43:04 : Successfully Logged on as service account.
    03-19-2013,17:43:04 : Successfully impersonated service account.
    03-19-2013,17:43:04 : EUserName value successfully written to the registry.
    03-19-2013,17:43:04 : EPassword value successfully written to the registry.
    03-19-2013,17:43:04 : EDomain value successfully written to the registry.
    03-19-2013,17:43:09 : There were no remote computers selected for install
    03-19-2013,17:43:09 : m_bUseNativeClient = 1
    03-19-2013,17:43:09 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:43:10 : Terminal Services enabled.
    03-19-2013,17:43:10 : Terminal Services server has been set to Install mode.
    03-19-2013,17:43:11 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,17:43:11 : Executing InstallLiveUpdate.
    03-19-2013,17:44:35 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,17:44:35 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:44:35 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,17:44:35 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,17:44:35 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:44:35 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,17:44:35 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:44:35 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,17:44:35 : "C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:44:36 : Starting Install
    03-19-2013,17:44:36 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,17:44:36 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:44:36 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,17:44:36 : Discovered Total Actions: 115
    03-19-2013,17:44:36 : The return code from the MSI is: 1601
    03-19-2013,17:44:36 : Cleaning up the symc status key
    03-19-2013,17:44:36 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,17:44:36 : Clean up Symantec installer keys.
    03-19-2013,17:44:37 : Terminal Services enabled.
    03-19-2013,17:44:37 : Terminal Services server has been set to Execute mode.
    03-19-2013,17:44:57 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,17:44:57 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,17:44:57 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:44:57 : Skipping push of remote servers and agents due to failed local install.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,17:45:25 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:45:28 : Gathering Telemetry items
    03-19-2013,17:45:28 : Failed to start the management service
    03-19-2013,17:45:28 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,17:45:28 : Sending Telemetry to Symantec
    03-19-2013,17:45:28 : Transmit Telemetry initialized.
    03-19-2013,17:45:28 : TelemetryRegistryHelpers initialized.
    03-19-2013,17:45:29 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,17:56:31 : Windows Operating System Version: 6.1
    03-19-2013,17:56:31 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,17:56:33 : Executing managed _Setup:
    03-19-2013,17:56:33 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,17:56:33 : Loading XML from:
    03-19-2013,17:56:33 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,17:56:33 : RawsDlgSequence::CheckInstMode
    03-19-2013,17:56:33 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,17:56:34 : Launching UI Install
    03-19-2013,17:56:35 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:56:35 : m_bUseNativeClient = 1
    03-19-2013,17:56:35 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,17:56:35 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,17:56:35 : CopySupportFiles
    03-19-2013,17:56:35 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,17:56:35 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:56:35 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,17:56:35 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,17:56:49 : Typical install value is set to : True
    03-19-2013,17:56:50 : Executing SQL_GetServicePack.
    03-19-2013,17:56:50 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:56:51 : Executing SQL_GetSQLServerEdition.
    03-19-2013,17:56:51 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : Executing SQL_GetServicePack.
    03-19-2013,17:56:51 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,17:56:51 : Connected to SQL Server.
    03-19-2013,17:56:51 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,17:57:37 : m_bUseNativeClient = 1
    03-19-2013,17:57:37 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,17:58:41 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,17:58:41 : Install is not executing as the service account.
    03-19-2013,17:58:41 : Successfully Logged on as service account.
    03-19-2013,17:58:41 : Successfully impersonated service account.
    03-19-2013,17:58:41 : EUserName value successfully written to the registry.
    03-19-2013,17:58:41 : EPassword value successfully written to the registry.
    03-19-2013,17:58:41 : EDomain value successfully written to the registry.
    03-19-2013,17:58:51 : There were no remote computers selected for install
    03-19-2013,17:58:51 : m_bUseNativeClient = 1
    03-19-2013,17:58:51 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,17:58:52 : Terminal Services enabled.
    03-19-2013,17:58:52 : Terminal Services server has been set to Install mode.
    03-19-2013,17:58:52 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,17:58:54 : Executing InstallLiveUpdate.
    03-19-2013,17:59:06 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,17:59:06 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,17:59:07 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,17:59:07 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,17:59:07 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:59:07 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,17:59:07 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:59:07 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,17:59:07 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,17:59:07 : Starting Install
    03-19-2013,17:59:07 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,17:59:07 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,17:59:07 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,17:59:08 : Discovered Total Actions: 115
    03-19-2013,17:59:08 : The return code from the MSI is: 1601
    03-19-2013,17:59:08 : Cleaning up the symc status key
    03-19-2013,17:59:08 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,17:59:08 : Clean up Symantec installer keys.
    03-19-2013,17:59:10 : Terminal Services enabled.
    03-19-2013,17:59:10 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:00:01 : The return code is: 0
    03-19-2013,18:00:01 : SUCCESS:  Installation has completed successfully.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:02:24 : Windows Operating System Version: 6.1
    03-19-2013,18:02:24 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:02:26 : Executing managed _Setup:
    03-19-2013,18:02:26 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:02:26 : Loading XML from:
    03-19-2013,18:02:26 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:02:26 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:02:26 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:02:26 : Launching UI Install
    03-19-2013,18:02:26 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:02:26 : m_bUseNativeClient = 1
    03-19-2013,18:02:26 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:02:26 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:02:26 : CopySupportFiles
    03-19-2013,18:02:26 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:02:27 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:02:27 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:02:27 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:03:11 : The return code is: 0
    03-19-2013,18:03:11 : SUCCESS:  Installation has completed successfully.
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:03:21 : Windows Operating System Version: 6.1
    03-19-2013,18:03:21 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:03:22 : Windows Operating System Version: 6.1
    03-19-2013,18:03:22 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:03:23 : Executing managed _Setup:
    03-19-2013,18:03:23 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:03:23 : Loading XML from:
    03-19-2013,18:03:23 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:03:23 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:03:23 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:03:24 : Launching UI Install
    03-19-2013,18:03:24 : Executing managed _Setup:
    03-19-2013,18:03:24 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:03:24 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:03:24 : m_bUseNativeClient = 1
    03-19-2013,18:03:24 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:03:24 : Loading XML from:
    03-19-2013,18:03:24 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:03:24 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:03:24 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:03:24 : CopySupportFiles
    03-19-2013,18:03:24 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:03:24 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:03:24 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:03:24 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:03:24 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:03:58 : Typical install value is set to : True
    03-19-2013,18:03:58 : m_bUseNativeClient = 1
    03-19-2013,18:03:58 : Executing SQL_GetServicePack.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:03:58 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : Executing SQL_GetServicePack.
    03-19-2013,18:03:58 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:03:58 : Connected to SQL Server.
    03-19-2013,18:03:58 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:03:58 : m_bUseNativeClient = 1
    03-19-2013,18:04:20 : m_bUseNativeClient = 1
    03-19-2013,18:04:20 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:05:35 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:05:35 : Install is not executing as the service account.
    03-19-2013,18:05:35 : Successfully Logged on as service account.
    03-19-2013,18:05:35 : Successfully impersonated service account.
    03-19-2013,18:05:35 : EUserName value successfully written to the registry.
    03-19-2013,18:05:35 : EPassword value successfully written to the registry.
    03-19-2013,18:05:35 : EDomain value successfully written to the registry.
    03-19-2013,18:05:36 : There were no remote computers selected for install
    03-19-2013,18:05:36 : m_bUseNativeClient = 1
    03-19-2013,18:05:36 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:05:37 : Terminal Services enabled.
    03-19-2013,18:05:37 : Terminal Services server has been set to Install mode.
    03-19-2013,18:05:37 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:05:38 : Executing InstallLiveUpdate.
    03-19-2013,18:05:50 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,18:05:50 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,18:05:50 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,18:05:50 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,18:05:50 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:05:50 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,18:05:50 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:05:50 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,18:05:50 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:05:50 : Starting Install
    03-19-2013,18:05:50 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,18:05:50 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:05:50 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,18:05:50 : Discovered Total Actions: 115
    03-19-2013,18:05:50 : The return code from the MSI is: 1601
    03-19-2013,18:05:51 : Cleaning up the symc status key
    03-19-2013,18:05:51 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,18:05:51 : Clean up Symantec installer keys.
    03-19-2013,18:05:51 : Terminal Services enabled.
    03-19-2013,18:05:51 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:06:32 : The return code is: 0
    03-19-2013,18:06:32 : SUCCESS:  Installation has completed successfully.
    03-19-2013,18:07:36 : Setup is already running.  Unable to initialize another instance of setup.
    03-19-2013,18:07:39 : Error initializing shared data
    03-19-2013,18:07:39 : ERROR:  Installation failed with error 1603. GetLastError = :0
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:13:44 : Windows Operating System Version: 6.1
    03-19-2013,18:13:44 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:13:44 : Windows Operating System Version: 6.1
    03-19-2013,18:13:44 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:13:46 : Executing managed _Setup:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:13:46 : Executing managed _Setup:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:13:46 : Loading XML from:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:13:46 : Loading XML from:
    03-19-2013,18:13:46 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:13:46 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:13:46 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:13:46 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:13:46 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:13:47 : Launching UI Install
    03-19-2013,18:13:47 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:13:48 : m_bUseNativeClient = 1
    03-19-2013,18:13:48 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:13:48 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:13:48 : CopySupportFiles
    03-19-2013,18:13:48 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:13:48 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:13:48 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:13:48 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:13:54 : Typical install value is set to : True
    03-19-2013,18:13:55 : m_bUseNativeClient = 1
    03-19-2013,18:13:55 : Executing SQL_GetServicePack.
    03-19-2013,18:13:55 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:13:56 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:13:56 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : Executing SQL_GetServicePack.
    03-19-2013,18:13:56 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:13:56 : Connected to SQL Server.
    03-19-2013,18:13:56 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:13:56 : m_bUseNativeClient = 1
    03-19-2013,18:14:41 : m_bUseNativeClient = 1
    03-19-2013,18:14:41 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:16:09 : Service account specified is not valid
    03-19-2013,18:16:09 : Unable to authenticate with the user and password information given for ACCENTPRESS\backup.
    03-19-2013,18:16:10 : Error validating service account credentials.
    03-19-2013,18:16:20 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:16:20 : Install is not executing as the service account.
    03-19-2013,18:16:20 : Successfully Logged on as service account.
    03-19-2013,18:16:20 : Successfully impersonated service account.
    03-19-2013,18:16:20 : EUserName value successfully written to the registry.
    03-19-2013,18:16:20 : EPassword value successfully written to the registry.
    03-19-2013,18:16:20 : EDomain value successfully written to the registry.
    03-19-2013,18:16:22 : There were no remote computers selected for install
    03-19-2013,18:16:22 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:16:23 : Terminal Services enabled.
    03-19-2013,18:16:23 : Terminal Services server has been set to Install mode.
    03-19-2013,18:16:23 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:16:25 : Executing InstallLiveUpdate.
    03-19-2013,18:16:37 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,18:16:37 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,18:16:38 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,18:16:38 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,18:16:38 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:16:38 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,18:16:38 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:16:38 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,18:16:38 : "C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,18:16:38 : Starting Install
    03-19-2013,18:16:38 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,18:16:38 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,18:16:38 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\1\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,18:16:39 : Discovered Total Actions: 115
    03-19-2013,18:16:39 : The return code from the MSI is: 1601
    03-19-2013,18:16:39 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,18:16:39 : Clean up Symantec installer keys.
    03-19-2013,18:16:39 : Cleaning up the symc status key
    03-19-2013,18:16:41 : Terminal Services enabled.
    03-19-2013,18:16:41 : Terminal Services server has been set to Execute mode.
    03-19-2013,18:17:08 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,18:17:08 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,18:17:08 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:17:08 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,18:17:09 : Gathering Telemetry items
    03-19-2013,18:17:09 : Failed to start the management service
    03-19-2013,18:17:09 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,18:17:09 : Sending Telemetry to Symantec
    03-19-2013,18:17:09 : Transmit Telemetry initialized.
    03-19-2013,18:17:09 : TelemetryRegistryHelpers initialized.
    03-19-2013,18:17:21 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,18:17:33 : TransmitTelemetry.TransmitMessage URL=http://statsbe.norton.com/n/p, Caught WebException The remote name could not be resolved: 'statsbe.norton.com'
    03-19-2013,18:17:33 : Telemetry transmission failed.  Data was not sent.
    03-19-2013,18:17:33 : The return code is: 1601
    03-19-2013,18:17:33 : ERROR:  Installation failed with error 1601. GetLastError = :0
    03-19-2013,18:17:48 : Setup is already running.  Unable to initialize another instance of setup.
    03-19-2013,18:17:51 : Error initializing shared data
    03-19-2013,18:53:53 : m_bUseNativeClient = 1
    03-19-2013,18:53:53 : Executing SQL_GetServicePack.
    03-19-2013,18:53:53 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:53:54 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:53:54 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : Executing SQL_GetServicePack.
    03-19-2013,18:53:54 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:53:54 : Connected to SQL Server.
    03-19-2013,18:53:54 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:53:54 : m_bUseNativeClient = 1
    Symantec Backup Exec (TM) 13 Installation Log
    03-19-2013,18:58:06 : Windows Operating System Version: 6.1
    03-19-2013,18:58:06 : GetProductInfo returned success.  Checking for CORE OS values.
    03-19-2013,18:58:08 : Executing managed _Setup:
    03-19-2013,18:58:08 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\_Setup.exe
    03-19-2013,18:58:09 : Loading XML from:
    03-19-2013,18:58:09 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\BEx64\Install\IFProducts.xml
    03-19-2013,18:58:09 : RawsDlgSequence::CheckInstMode
    03-19-2013,18:58:09 : BEOperations::BE_GetInstalledProdCodeVersion()
    03-19-2013,18:58:09 : Launching UI Install
    03-19-2013,18:58:10 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:58:10 : m_bUseNativeClient = 1
    03-19-2013,18:58:10 : MDAC 6.1.7601.17514 is installed on this system.
    03-19-2013,18:58:10 : BeSeqDlgs::DlgBERemoteConfig
    03-19-2013,18:58:10 : CopySupportFiles
    03-19-2013,18:58:10 : Saved support files to C:\ProgramData\Symantec\Backup Exec\Logs\InstallSummary
    03-19-2013,18:58:11 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:58:11 : Executing BE_SetSQLxLangVersion.  Setting language version of SQL Express BKUPEXEC instance.
    03-19-2013,18:58:11 : BKUPEXEC SQLx setup file is SQLEXPR.EXE.
    03-19-2013,18:58:15 : Typical install value is set to : True
    03-19-2013,18:58:16 : m_bUseNativeClient = 1
    03-19-2013,18:58:16 : Executing SQL_GetServicePack.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:58:16 : Executing SQL_GetSQLServerEdition.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : Executing SQL_GetServicePack.
    03-19-2013,18:58:16 : DRIVER={SQL Native Client};SERVER=ACCENTPRESSDC\BKUPEXEC;Trusted_Connection=Yes
    03-19-2013,18:58:16 : Connected to SQL Server.
    03-19-2013,18:58:16 : ACCENTPRESSDC\BKUPEXEC is a SQL Server Product Level: 'SP4'
    03-19-2013,18:58:16 : m_bUseNativeClient = 1
    03-19-2013,18:58:49 : m_bUseNativeClient = 1
    03-19-2013,18:58:49 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,18:59:43 : Currently executing as ACCENTPRESS\administrator
    03-19-2013,18:59:43 : Install is not executing as the service account.
    03-19-2013,18:59:43 : Successfully Logged on as service account.
    03-19-2013,18:59:44 : Successfully impersonated service account.
    03-19-2013,18:59:44 : EUserName value successfully written to the registry.
    03-19-2013,18:59:44 : EPassword value successfully written to the registry.
    03-19-2013,18:59:44 : EDomain value successfully written to the registry.
    03-19-2013,18:59:46 : There were no remote computers selected for install
    03-19-2013,18:59:46 : m_bUseNativeClient = 1
    03-19-2013,18:59:46 : To back up Microsoft Exchange Server 2007, you must install the Exchange Management Tools for Microsoft Exchange Server 2007 on this computer.  The Management Tools can be installed during a custom
    install of Microsoft Exchange Server 2007.  To support individual mailbox message and folder restores from Information Store backups, you must also download and install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects package version
    06.05.7888 or later on the Exchange 2007 server.  This package can be found on the Microsoft Web site.
    03-19-2013,18:59:47 : Terminal Services enabled.
    03-19-2013,18:59:47 : Terminal Services server has been set to Install mode.
    03-19-2013,18:59:47 : Checking for .Net Framework 3.5 SP1.
    03-19-2013,18:59:49 : Executing InstallLiveUpdate.
    03-19-2013,19:00:01 : The return value for Symantec LiveUpdate returned error code: 0
    03-19-2013,19:00:01 : Installing Microsoft Report Viewer Redistributable 2005
    03-19-2013,19:00:01 : The return value for Microsoft Report Viewer Redistributable 2005 returned error code: 0
    03-19-2013,19:00:01 : ==================Installing MS VC 8.0 SP1 runtimes.==================
    03-19-2013,19:00:01 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,19:00:01 : Extracting runtime installer package vcredist_x64.exe to BE support folder.
    03-19-2013,19:00:01 : D:\Software\Symantec Backup Exec 2010 32-64bit\BE\WINNT\INSTALL\VCRedist\vcredist_x64.exe /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,19:00:02 : Extracting runtime installer package VCREDI~2.EXE to BE support folder.
    03-19-2013,19:00:02 : "C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\VCREDI~2.EXE" /q:a /C /T:"C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist"
    03-19-2013,19:00:02 : Starting Install
    03-19-2013,19:00:02 : Using Command Line: REBOOT=ReallySuppress
    03-19-2013,19:00:02 : Support directory: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\
    03-19-2013,19:00:02 : Launching MSI: C:\Users\ADMINI~1\AppData\Local\Temp\2\{DD8FD4D3-F0FB-4FB2-8A34-25E2C7756A51}\VCRedist\vcredist.msi
    03-19-2013,19:00:03 : Discovered Total Actions: 115
    03-19-2013,19:00:03 : The return code from the MSI is: 1601
    03-19-2013,19:00:03 : Cleaning up the symc status key
    03-19-2013,19:00:03 : The return value for Microsoft Visual C++ 2005 SP1 Redistributable returned error code: 1601
    03-19-2013,19:00:03 : Clean up Symantec installer keys.
    03-19-2013,19:00:05 : Terminal Services enabled.
    03-19-2013,19:00:05 : Terminal Services server has been set to Execute mode.
    03-19-2013,19:00:07 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,19:00:07 : BeSeqDlgs::DlgInstallComplete
    03-19-2013,19:00:07 : AgentSeqDlgs::Misc_BE_CommonOps
    03-19-2013,19:00:07 : Skipping push of remote servers and agents due to failed local install.
    03-19-2013,19:00:10 : Gathering Telemetry items
    03-19-2013,19:00:10 : Failed to start the management service
    03-19-2013,19:00:10 : Service BackupExecManagementService was not found on computer '.'.
    03-19-2013,19:00:10 : Sending Telemetry to Symantec
    03-19-2013,19:00:10 : Transmit Telemetry initialized.
    03-19-2013,19:00:10 : TelemetryRegistryHelpers initialized.
    03-19-2013,19:00:10 : TransmitTelemetry.TransmitMessage URL=http://statsbe.hro.rnd.veritas.com/betelemetry/stats.php, Caught WebException The remote name could not be resolved: 'statsbe.hro.rnd.veritas.com'
    03-19-2013,19:00:10 : Telemetry data was successfully sent to Symantec
    03-19-2013,19:00:10 : The return code is: 1601
    03-19-2013,19:00:11 : ERROR:  Installation failed with error 1601. GetLastError = :0 
    DJH

Maybe you are looking for

  • Power Mac G5 DP1.8GHz - Bad Logic Board or Power Management Issue?

    I have a Power Mac G5 DP1.8GHz/1.5GB/80GB which I bought non-working. It has not yet been disassembled or examined by a certified tech. This is it's issue (which replicates): the computer powers on. It makes a single warning tone, then the LED flashe

  • Need some info about newest version of Illustrator

    I'm currently using my CS3 version of Illustrator, but wondering if Illustrator has grown to take in more of the great features that we used to have in Freehand. Here are the features I miss most from Freehand: 1.) Able to name artwork and modify glo

  • Infinte loop is going on how to kill the instance

    Hi friends   In leave workflow instead of wait step i added loop and a condition container when wait step condition is put inside the conditional container and loop is set a flag when set a flag come out of the loop. The condition inside the condatio

  • Cleaning unused tracks from the session audio folder.

    I'm currently cleaning up unwanted files from my computer to free up space.  I think I remember seeing a post about a program that will help me clean up the session audio file folder.  I just need someone to point me in the right direction. Thanks

  • Wide variety of new graphical problems (ATI 6470m, Catalyst 11.11)

    I'm really starting to get annoyed, and I'm hoping somebody figured out what could cause these problems. This is my setup: I'm on a HP EliteBook 8560p laptop. I have an ATI 6470m graphical card, and since the release of catalyst-11.11 I'm running fgl