Ошибка 129 0x81

  • Remove From My Forums
  • Question

  • Hi, i have searched everywhere for a solution but cannot find one. I have this error in services.msc which is not letting me install my printer. My printer — kodak all in one 5210 — was working fine then it just disappeared. I tried to reinstall from
    the disc but it get to a particular stage and cannot continue the install because the printer spool cannot be started. In services i get the message «windows could not start the print spooler on local computer error code 129: 0x81. If i go to properties on
    the print spooler, in the description it says «failed to read description. error code 1812. What do i need to do?

    Thanks

    Since then i did SCF /Scannow and i have many printspooler corrupt files i can show logfile if required.

Answers

  • Hi,

    This issue may occur due to printer driver crashing the service. It is suggested to uninstall printer driver first then reinstall the latest driver to check.

    For the logfile, you can upload the collected files to SkyDrive, and let me know the URL by replying this thread. For detailed steps on how to upload files with SkyDrive, please refer to:

     
    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     
    The above Windows Live ID is ONLY for collecting troubleshooting information. Please do NOT send your questions to it. For any new questions, please post in the forums so that more MSFT, MVP and community members can help you.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    • Marked as answer by

      Friday, June 3, 2011 7:56 AM

  • Sigurd

    Hi,

    Could you try to do this:

    1-Remove any bonded peripherals in the bluetooth settings.
    2-Uninstall your version of nRF Toolbox.
    3-Install nRF Toolbox from the app store.
    4-Restart phone.
    5-Launch nRF Toolbox. Try the DFU process again.

  • ikeliang

    I follow your steps, but the problem still exists…

  • Sigurd

    Do you see the same issue with other phones ?

  • ikeliang

    I have a phone (HuaWei nova 2i), the phone sometime can’t connect the device(error 133), but retry can OK.

    The phone (HUAWEI P9 Lite) always can’t connect devices that are in DFU mode.

  • Sigurd

    Please try to enable packet receipt notification and set the number of packets to ‘1’ 

    You might also want to enable «Keep bond information».

Vrogue

Dfu gatt connection error(0x81 0x85) nordic q a devzone file error · issue #237 nordicsemiconductor/android library 129: invalid price??? day trading strategies general mql5 crc cellphone can connect to nrf52 dk but show 133 (0x85) when services discovered 129 (0x81) and 【android】ble状态码(status code)参照表 紫豪的blog mode fix 9006 download iphone information ksz8794cnxic pdf文件 pdf文件在线浏览页面【65/124】 天天ic网 mqtt v3和v5的区别 mqttv3 parismoor的博客 csdn博客 secure error: got unexpected extra argument (private key) (0x85): how add service existing code getting remote data size exceeds limit euros león: leer archivos csv en python (solución al 52832 ota 流程源码分析(一) 程序员大本营 nrfutil failed open for over ble ivms 4200 1602 09/2021 qt install target was tun? (computer android programmieren) read from controller via rs485 modbus rtu arduino stack fatal log:setting vector table bootloader: 0x00078000 ni community an unknown (1601) what s on 4013

  • Remove From My Forums
  • Question

  • Hi, i have searched everywhere for a solution but cannot find one. I have this error in services.msc which is not letting me install my printer. My printer — kodak all in one 5210 — was working fine then it just disappeared. I tried to reinstall from
    the disc but it get to a particular stage and cannot continue the install because the printer spool cannot be started. In services i get the message «windows could not start the print spooler on local computer error code 129: 0x81. If i go to properties on
    the print spooler, in the description it says «failed to read description. error code 1812. What do i need to do?

    Thanks

    Since then i did SCF /Scannow and i have many printspooler corrupt files i can show logfile if required.

Answers

  • Hi,

    This issue may occur due to printer driver crashing the service. It is suggested to uninstall printer driver first then reinstall the latest driver to check.

    For the logfile, you can upload the collected files to SkyDrive, and let me know the URL by replying this thread. For detailed steps on how to upload files with SkyDrive, please refer to:

     
    http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65

     
    The above Windows Live ID is ONLY for collecting troubleshooting information. Please do NOT send your questions to it. For any new questions, please post in the forums so that more MSFT, MVP and community members can help you.

    Regards,


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    • Marked as answer by

      Friday, June 3, 2011 7:56 AM

Добрый день. Есть сервер на платформе R1208GZ4GC. У него Raid контроллер intel C600. В нем крутиться два зеркала. Два SSD на 500гб, модель не известна, это \Device\RaidPort0. Два SSD на 800гб, это SDSC2BX800G401, порт \Device\RaidPort1.
Вот как раз после установки второй рейда, начались проблемы. Примерно через 23 часа активной работы, в журнали ОС начинают сыпаться ошибки

Был произведен возврат к устройству \Device\RaidPort1.

Код ошибки 129.

Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="iaStorS" /> 
  <EventID Qualifiers="32772">129</EventID> 
  <Level>3</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2015-09-21T21:25:54.420981100Z" /> 
  <EventRecordID>61362</EventRecordID> 
  <Channel>System</Channel> 
  <Computer>sql09</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>\Device\RaidPort1</Data> 
  <Binary>0F001800010000000000000081000480040000000000000000000000000000000000000000000000000000000000000008020000810004800000000000000000</Binary> 
  </EventData>
  </Event>

В итоге все что крутилось на этом диске — намертво виснит, включая служб. Помогает только полный ребут системы и помогает примерно на 20-23 часа, а потом по новой.
Версия драйвера C600 Chipset SAS RAID (SATA mode): 3.8.0.1106

Сейчас я зеркало переставил в другой гнездо для эксперемента и обновил драйвер чипсета, но боюсь сейчас через 23 часа опять вылезит.

Intel SSD Toolbox говорит, что у SSD самая актуальная прошивка.

Понравилась статья? Поделить с друзьями:
  • Ошибка 128s214 01
  • Ошибка 1286 мурано
  • Ошибка 1289 кайрон дизель
  • Ошибка 1288 форд фокус
  • Ошибка 1285 out of memory майнкрафт