Код ошибки 12289

  • Remove From My Forums

  • Общие обсуждения

  • Добрый день!

    Есть несколько серверов с установленной ОС Windows 2003 R2. При выполнении резервного копирования по расписанию возникает ошибка:

    Тип события: Ошибка
    Источник события: VSS
    Категория события: Отсутствует
    Код события: 12289
    Дата:  26.08.2008
    Время:  4:00:06
    Пользователь:  Н/Д
    Компьютер: SRV-BACKUP
    Описание:
    Ошибка теневого копирования тома: Непредвиденная ошибка  OpenService (shSCManager, ‘VSS’, SERVICE_QUERY_STATUS).. hr = 0x80070005.

    Дополнительные сведения можно найти в центре справки и поддержки, в «http://go.microsoft.com/fwlink/events.asp».
    Данные:
    0000: 2d 20 43 6f 64 65 3a 20   — Code:
    0008: 20 54 52 43 54 52 43 43    TRCTRCC
    0010: 30 30 30 30 31 34 35 37   00001457
    0018: 2d 20 43 61 6c 6c 3a 20   — Call:
    0020: 42 55 45 43 58 4d 4c 43   BUECXMLC
    0028: 30 30 30 30 37 30 39 36   00007096
    0030: 2d 20 50 49 44 3a 20 20   — PID: 
    0038: 30 30 30 30 34 38 32 30   00004820
    0040: 2d 20 54 49 44 3a 20 20   — TID: 
    0048: 30 30 30 30 34 31 30 34   00004104
    0050: 2d 20 43 4d 44 3a 20 20   — CMD: 
    0058: 43 3a 5c 57 49 4e 44 4f   C:WINDO
    0060: 57 53 5c 73 79 73 74 65   WSsyste
    0068: 6d 33 32 5c 6e 74 62 61   m32ntba
    0070: 63 6b 75 70 2e 65 78 65   ckup.exe
    0078: 20 62 61 63 6b 75 70 20    backup
    0080: 22 40 43 3a 5c 44 6f 63   «@C:Doc
    0088: 75 6d 65 6e 74 73 20 61   uments a
    0090: 6e 64 20 53 65 74 74 69   nd Setti
    0098: 6e 67 73 5c 73 79 73 62   ngssysb
    00a0: 61 63 6b 75 70 5c 4c 6f   ackupLo
    00a8: 63 61 6c 20 53 65 74 74   cal Sett
    00b0: 69 6e 67 73 5c 41 70 70   ingsApp
    00b8: 6c 69 63 61 74 69 6f 6e   lication
    00c0: 20 44 61 74 61 5c 4d 69    DataMi
    00c8: 63 72 6f 73 6f 66 74 5c   crosoft
    00d0: 57 69 6e 64 6f 77 73 20   Windows
    00d8: 4e 54 5c 4e 54 42 61 63   NTNTBac
    00e0: 6b 75 70 5c 64 61 74 61   kupdata
    00e8: 5c 44 61 69 6c 79 57 53   DailyWS
    00f0: 55 53 2e 62 6b 73 22 20   US.bks»
    00f8: 2f 6e 20 22 44 61 69 6c   /n «Dail
    0100: 79 57 53 55 53 2e 62 6b   yWSUS.bk
    0108: 66 20 20 20 20 20 2d 20   f     —
    0110: 55 73 65 72 3a 20 4d 49   User:
    0118: 52 4e 4b 5c 73 79 73 62   sysb
    0120: 61 63 6b 75 70 20 2d 20   ackup —
    0128: 53 69 64 3a 20 20 53 2d   Sid:  S-
    0130: 31 2d 35 2d 32 31 2d 37   1-5-21-7
    0138: 37 36 35 36 31 37 34 31   76561741
    0140: 2d 35 38 33 39 30 37 32   -5839072
    0148: 35 32 2d 37 32 35 33 34   52-72534
    0150: 35 35 34 33 2d 31 37 31   5543-171
    0158: 36 37 20 20 20 20 2d 20   67    —
    0160: 45 72 72 6f 72 3a 20 4f   Error: O
    0168: 70 65 6e 53 65 72 76 69   penServi
    0170: 63 65 20 28 73 68 53 43   ce (shSC
    0178: 4d 61 6e 61 67 65 72 2c   Manager,
    0180: 20 27 56 53 53 27 2c 20    ‘VSS’,
    0188: 53 45 52 56 49 43 45 5f   SERVICE_
    0190: 51 55 45 52 59 5f 53 54   QUERY_ST
    0198: 41 54 55 53 29 20         ATUS)  

    Backup выполняется от учетной записи являющиеся членом Группы BackupOperators. Если выполнить Backup интерактивно от имени этой учетной записи, то ошибка не появляется, а при выполнении по расписанию ошибка появляется на всех серверах. Кто знает с чем может быть связанна данная ошибка??

    • Изменен тип

      6 декабря 2010 г. 15:55

Источник

  • #1

Привет коллеги, на одном из контроллеров домена в логах появляется ошибка с event id 12289 источник vss :

Код: 

Ошибка теневого копирования тома: Непредвиденная ошибка DeviceIoControl(\?fdc#generic_floppy_drive#6&2bc 13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 0000000000000274,0x00560000,0000000000000000,0,000 000000041D340,4096,[0]).. hr = 0x80070001, Неверная функция.
Операция:
Предоставление восстановленных томов
Поиск LUN теневых копий
Событие PostSnapshot
Выполнение асинхронной операции

Контекст:
Устройство: \?fdc#generic_floppy_drive#6&2bc13940&0&0#{53f56 30d-b6bf-11d0-94f2-00a0c91efb8b}
Проверка обнаруженного тома: Existing - \?fdc#generic_floppy_drive#6&2bc13940&0&0#{53f56 30d-b6bf-11d0-94f2-00a0c91efb8b}
Контекст выполнения: Provider
Имя поставщика: VMware Snapshot Provider
Версия поставщика: 1.0.0
Код поставщика: {564d7761-7265-2056-5353-2050726f7669}
Текущее состояние: DoSnapshotSet

Возможно это как то связано с плановым резервным копированием, если у кого было подскажите как победить проблему.

  • #2

Это известный косяк, могут так же проскакивать в журналах и такие ошибки:

Код: 

   Event ID: 50 NTFS Warning
    {delayed write failed} Windows was unable to save all the data for the file. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere
    Event ID: 57 NTFS Warning
    The system failed to flush data to the transaction log. Corruption may occur.
    Event ID: 137 NTFS Error
    The default transaction resource manager on volume \?Volume{806289e8-6088-11e0-a168-005056ae003d} encountered a non-retryable error and could not start. The data contains the error code.
    Event ID: 140 NTFS Warning
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId:<> DeviceName: DeviceHarddiskVolume<>.(A device which does not exist was specified.).
    Event ID: 157 Disk Warning
    Disk x has been surprise removed.

Проверьте что служба теневого копирования работает, через services.msc.
Вмваре говорит что пока решения нет, но в качестве временного решения адресует на статьи http://support.microsoft.com/kb/2853247 и http://support.microsoft.com/kb/885688
Посмотрите так же логи на сервере бэкапов, скорее всего это из за бэкапа.

Источник

Event ID 12289 — Volume Shadow Copy Service Operations

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Volume Shadow Copy Service (VSS) provides the ability to create a point in time image (shadow copy) of one or more volumes that can be used to perform backups. The service is also used during restores of applications.

Event Details

Product: Windows Operating System
ID: 12289
Source: VSS
Version: 6.1
Symbolic Name: VSS_ERROR_UNEXPECTED_ERRORCODE
Message: Volume Shadow Copy Service error: Unexpected error %1. hr = %2. %3

Resolve
Determine the cause of the error condition and contact the appropriate vendor

This event indicates that an unexpected Volume Shadow Copy Service (VSS) error has occurred.

To troubleshoot this error condition, you need to determine what caused it by using the Event Viewer and then contact the vendor that created the Vdata protection application that uses VSS. Also, you should check that the VSS service is enabled.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Open Event Viewer and view events related to VSS requester applications

To open Event Viewer and view events related to VSS requester applications:

  1. Click Start, click Run, type eventvwr.msc, and then click OK. If the User Account Control dialog box appears, ensure that the action it displays is what you want, and then click Continue
  2. In Event Viewer, expand Windows Logs, and then click Application.
  3. To filter the events so that only events with a Source of VSS are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources drop-down list, select the checkbox for VSS. Select other options as appropriate, and then click OK.
  4. Click the Date and Time column heading to sort the events based on date and time.
  5. Review the events that have a similar date and date as this event.
  6. Click the related event, and then click Event Log Online Help at the bottom of the General tab.
  7. Follow the instructions to resolve the error. If the error cannot be resolved, contact the vendor whose application caused the error. If the vendor is Microsoft, contact Microsoft Customer Service and Support. For more information, see http://go.microsoft.com/fwlink/?LinkId=102491. You should provide the entire event log message as it appears in the Event Viewer.

Check that the VSS service is enabled

To check that the VSS service is enabled:

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In the results pane, double-click Volume Shadow Copy.
  3. Ensure that Startup type is set to Manual.
  4. Click OK.

Verify

To verify that the Volume Shadow Copy Service (VSS) is operating correctly, retry the previous VSS operation.

Related Management Information

Volume Shadow Copy Service Operations

File Services

Источник

Hello ,

I am getting very strange error since past few days.

I noticed this error may occurred when AppAssure performs backups/VSS Snap.  I have perform few test. The results are below.

Event Log Start 

Event Identifier : 12289

Event description : Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded
the maximum supported limit.  hr = 0x80042409.

Operation:

   PostSnapshot Event

Context:

   Maximum supported sessions: 64

   Completed sessions: 8

   Active sessions: 64

   Aborted sessions: 0

   Writer failed sessions: 0

   New snaphot set: {412e716b-31c7-4bf2-b3cb-da231c98a8e3}

   Old snapshot set: {2b09a554-54f0-469b-87b3-f476e1047db1}

   Old operation: 1013

   Old state: 5

   Old failure: 0

   Execution Context: Writer

   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Name: System Writer

   Writer Instance ID: {ecfc724c-eb64-4ce3-a924-82cca693f89d}

Event log End

I checked VSS service is Manual and Started. I did restarted as well.

Here the result of VSS Writers List

vssadmin 1.1 — Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2005 Microsoft Corp.

Writer name: ‘System Writer’
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {ecfc724c-eb64-4ce3-a924-82cca693f89d}
   State: [1] Stable
   Last error: No error

Writer name: ‘SqlServerWriter’
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d1b57cb1-c0ff-4f76-99b4-4e2d3ca61f22}
   State: [1] Stable
   Last error: No error

Writer name: ‘ASR Writer’
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {3748865d-8f83-4c83-92f6-edc3e9407bf6}
   State: [1] Stable
   Last error: No error

Writer name: ‘FSRM Writer’
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {eccb76ce-39a5-41bb-9c51-ae93ee682086}
   State: [1] Stable
   Last error: No error

Writer name: ‘IIS Metabase Writer’
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {76ba0b62-6d61-46ec-bab7-2fb5e17e747b}
   State: [1] Stable
   Last error: No error

Writer name: ‘Registry Writer’
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {77df5d3d-fd0a-4123-a607-8c9e40712650}
   State: [1] Stable
   Last error: No error

Writer name: ‘Microsoft Exchange Writer’
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {6c1501e5-33d4-4cf5-96a7-914bc5205eaa}
   State: [1] Stable
   Last error: No error

Writer name: ‘Certificate Authority’
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {a3ed867d-18aa-40f3-b675-ff37980278ee}
   State: [1] Stable
   Last error: No error

Writer name: ‘COM+ REGDB Writer’
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {24f988e7-da6b-43e2-bd7e-6c9fb73f6bc3}
   State: [1] Stable
   Last error: No error

Writer name: ‘NPS VSS Writer’
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {85a90748-3881-40a9-b7ab-3fe5b45ddca1}
   State: [1] Stable
   Last error: No error

Writer name: ‘Shadow Copy Optimization Writer’
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {f82419a7-8e89-45b0-a3da-d5832dddb260}
   State: [1] Stable
   Last error: No error

Writer name: ‘IIS Config Writer’
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {e221a0c9-b065-4339-ad66-26c5ca9c2d62}
   State: [1] Stable
   Last error: No error

Writer name: ‘BITS Writer’
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {fd77a6aa-6b64-49e6-ab96-47601050a57a}
   State: [1] Stable
   Last error: No error

Writer name: ‘WMI Writer’
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {50fe72f0-c819-4b7d-a4e2-89127f6f9db5}
   State: [1] Stable
   Last error: No error

Writer name: ‘FRS Writer’
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {8a9c538e-ee8a-46ef-8cd1-a136c0571338}
   State: [1] Stable
   Last error: No error

Writer name: ‘NTDS’
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {c098b618-e2a7-417b-8272-8a85b54dc90f}
   State: [11] Failed
   Last error: Non-retryable error

Writer name: ‘Dhcp Jet Writer’
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {3b082226-0fb3-486f-a191-f6cae0cf9627}
   State: [1] Stable
   Last error: No error

Here the list of Providers

vssadmin 1.1 — Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Provider name: ‘Microsoft Software Shadow Copy provider 1.0’
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

Thanks for your time.

Sainyam Aggarwal MCTS

  • Edited by

    Wednesday, March 14, 2012 3:39 AM

Источник

Понравилась статья? Поделить с друзьями:
  • Код ошибки 1226
  • Код ошибки 1224
  • Код ошибки 1222 тойота
  • Код ошибки 1220
  • Код ошибки 12175 dr web windows 7