Показать полную графическую версию : Ошибка печати на терминальном сервере
Страниц :
1
2
3
4
5
6
7
[
8]
9
10
11
12
13
Petya V4sechkin
11-10-2016, 10:24
mirage., сбой на
C:\Windows\System32\spool\drivers\x64\3\CNLB0MUI_DC662.DLL
Это Canon.
Petya V4sechkin,
Спасибо!
FARmator
02-11-2016, 10:33
Помогите пожалуйста с анализом дампа, проблема аналогичная. http://dropmefiles.com/maQ8b
Petya V4sechkin
02-11-2016, 10:57
FARmator, сбои на
C:\Windows\System32\spool\drivers\x64\3\CNAB4MUI.DLL
Относится к Canon.
FARmator
02-11-2016, 11:52
Спасибо большое, это старенькие Canon LBP2900. В принципе на них и грешили, но теперь хоть уверенность есть. А не подскажете, можно ли запустить этот драйвер в режиме изоляции или , насколько я понял, он его не поддерживает?
FARmator
02-11-2016, 18:30
Вопрос снят, режим изоляции работает и как временное решение вполне подходит.
Добрый день! Procmon висел целую неделю но так и не записал лог во время падения принтеров, вот что я достал из cmd :
[10:50:53] Exception: 00000721
[10:51:10] Exception: 00000721
[10:56:38] Exception: 000006D9
[10:57:09] Exception: 00000721
[11:03:26] Exception: 000006BA
[11:03:26] Exception: 000006BA
[11:06:28] Exception: 00000721
[11:12:02] Exception: 00000005
[11:12:03] Exception: 00000005
[11:14:17] Exception: 000006BA
[11:14:38] Exception: 000006BA
[11:17:20] Exception: 00000721
[11:26:06] Exception: 00000721
[11:27:01] Exception: 00000005
[11:27:01] Exception: 00000005
[11:30:07] Exception: 00000005
[11:30:07] Exception: 00000005
[12:17:59] Exception: 000006D9
[12:17:59] Exception: 000006D9
[12:19:11] Exception: 000006D9
[12:19:11] Exception: 000006D9
[12:24:29] Exception: 000006BA
[12:24:29] Exception: 000006BA
[12:24:30] Exception: 000006BA
[12:24:30] Exception: 000006BA
[12:27:47] Exception: 000006BA
[12:27:47] Exception: 000006BA
[12:27:58] Exception: 000006BA
[12:27:58] Exception: 000006BA
[12:28:27] Exception: 000006BA
[12:28:27] Exception: 000006BA
[12:29:00] Exception: 000006BA
[12:29:00] Exception: 000006BA
[12:29:13] Exception: 000006BA
[12:29:13] Exception: 000006BA
[12:42:07] Exception: 000006BA
[12:42:07] Exception: 000006BA
[12:42:07] Exception: 000006BA
[12:42:07] Exception: 000006BA
[12:42:59] Exception: 00000005
[12:42:59] Exception: 00000005
[12:48:38] Exception: 000006BA
[12:48:38] Exception: 000006BA
[12:48:38] Exception: 000006BA
[12:48:38] Exception: 000006BA
[12:50:47] Exception: 000006BA
[12:50:47] Exception: 000006BA
[12:52:13] Exception: 000006BA
[12:52:13] Exception: 000006BA
[12:53:40] Exception: 000006BA
[12:53:40] Exception: 000006BA
[12:57:15] Exception: 000006BA
[12:57:15] Exception: 000006BA
[12:57:15] Exception: 000006BA
[12:57:15] Exception: 000006BA
[12:59:24] Exception: 000006BA
[12:59:24] Exception: 000006BA
[13:00:50] Exception: 000006BA
[13:00:50] Exception: 000006BA
[13:06:11] Exception: 000006BA
[13:06:11] Exception: 000006BA
[13:06:11] Exception: 000006BA
[13:06:11] Exception: 000006BA
[13:08:19] Exception: 000006BA
[13:08:19] Exception: 000006BA
[13:09:46] Exception: 000006BA
[13:09:46] Exception: 000006BA
[13:12:10] Exception: 000006D9
[13:12:10] Exception: 000006D9
[13:26:56] Exception: 000006BA
[13:26:56] Exception: 000006BA
[13:26:56] Exception: 000006BA
[13:26:56] Exception: 000006BA
[13:32:34] Exception: 000006BA
[13:32:34] Exception: 000006BA
[13:32:34] Exception: 000006BA
[13:32:34] Exception: 000006BA
[13:34:01] Exception: 000006BA
[13:34:01] Exception: 000006BA
[13:36:45] Exception: 000006BA
[13:36:45] Exception: 000006BA
[13:36:45] Exception: 000006BA
[13:36:45] Exception: 000006BA
[13:38:06] Exception: 000006BA
[13:38:06] Exception: 000006BA
[13:38:12] Exception: 000006BA
[13:38:12] Exception: 000006BA
[13:38:30] Exception: 000006BA
[13:38:30] Exception: 000006BA
[13:44:23] Exception: 000006BA
[13:44:23] Exception: 000006BA
[13:44:45] Exception: 00000005
[13:44:45] Exception: 00000005
[13:44:45] Exception: 00000005
[13:44:45] Exception: 00000005
[13:45:09] Exception: 000006BA
[13:45:09] Exception: 000006BA
[13:45:31] Exception: 00000005
[13:45:31] Exception: 00000005
[13:45:31] Exception: 00000005
[13:45:31] Exception: 00000005
[13:48:07] Exception: 000006BA
[13:48:07] Exception: 000006BA
[13:48:07] Exception: 000006BA
[13:48:07] Exception: 000006BA
[13:49:33] Exception: 000006BA
[13:49:33] Exception: 000006BA
[13:52:02] Exception: 000006BA
[13:52:02] Exception: 000006BA
[13:52:10] Exception: 000006BA
[13:52:10] Exception: 000006BA
[13:52:47] Exception: 000006BA
[13:52:47] Exception: 000006BA
[13:55:10] Exception: 00000721
[13:55:40] Exception: 000006BA
[13:55:40] Exception: 000006BA
[13:57:06] Exception: 000006BA
[13:57:06] Exception: 000006BA
[14:00:00] Exception: 000006BA
[14:00:00] Exception: 000006BA
[14:00:00] Exception: 000006BA
[14:00:00] Exception: 000006BA
[14:13:12] Exception: 000006BA
[14:13:12] Exception: 000006BA
[14:13:19] Exception: 000006BA
[14:13:20] Exception: 00000005
[14:13:20] Exception: 00000005
[14:13:40] Exception: 000006BA
[14:14:38] Exception: 000006BA
[14:14:38] Exception: 000006BA
[14:16:04] Exception: 000006BA
[14:16:04] Exception: 000006BA
[14:16:10] Exception: 00000005
[14:16:10] Exception: 00000005
[14:16:12] Exception: 000006BA
[14:16:33] Exception: 000006BA
[14:17:31] Exception: 000006BA
[14:17:31] Exception: 000006BA
[14:18:57] Exception: 000006BA
[14:18:57] Exception: 000006BA
[14:20:23] Exception: 000006BA
[14:20:23] Exception: 000006BA
[14:24:57] Exception: 000006BA
[14:24:57] Exception: 000006BA
[14:26:24] Exception: 000006BA
[14:26:24] Exception: 000006BA
[14:27:40] Exception: 00000721
[14:27:50] Exception: 000006BA
[14:27:50] Exception: 000006BA
[14:29:16] Exception: 000006BA
[14:29:16] Exception: 000006BA
[14:29:41] Exception: 00000005
[14:29:42] Exception: 00000005
[14:30:43] Exception: 000006BA
[14:30:43] Exception: 000006BA
[14:32:09] Exception: 000006BA
[14:32:09] Exception: 000006BA
[14:35:53] Exception: 00000721
[14:36:29] Exception: 00000005
[14:36:30] Exception: 00000005
[14:53:18] Exception: 000006BA
[14:53:18] Exception: 000006BA
[14:53:18] Exception: 000006BA
[14:53:18] Exception: 000006BA
[14:56:12] Exception: 000006BA
[14:56:12] Exception: 000006BA
[14:56:12] Exception: 000006BA
[14:56:12] Exception: 000006BA
[14:58:20] Exception: 000006BA
[14:58:20] Exception: 000006BA
[15:00:01] Exception: 000006BA
[15:00:01] Exception: 000006BA
[15:00:01] Exception: 000006BA
[15:00:01] Exception: 000006BA
[15:05:19] Exception: 000006BA
[15:05:19] Exception: 000006BA
[15:05:19] Exception: 000006BA
[15:05:19] Exception: 000006BA
[15:05:23] Exception: 000006BA
[15:05:23] Exception: 000006BA
[15:05:23] Exception: 000006BA
[15:05:23] Exception: 000006BA
[15:07:47] Exception: 000006BA
[15:07:47] Exception: 000006BA
[15:08:02] Exception: 000006D9
[15:08:03] Exception: 000006D9
[15:09:14] Exception: 000006BA
[15:09:14] Exception: 000006BA
[15:10:40] Exception: 000006BA
[15:10:40] Exception: 000006BA
[15:12:29] Exception: 000006BA
[15:12:29] Exception: 000006BA
[15:14:53] Exception: 000006BA
[15:15:14] Exception: 000006BA
[15:17:22] Exception: 000006BA
[15:17:22] Exception: 000006BA
[15:17:46] Exception: 000006BA
[15:18:07] Exception: 000006BA
[15:27:07] Exception: 00000005
[15:33:19] Exception: 00000721
[15:55:19] Exception: 00000721
[15:58:42] Exception: 000006BA
[15:58:42] Exception: 000006BA
[16:01:00] Exception: 000006BA
[16:01:00] Exception: 000006BE
[16:01:00] Exception: 00000006
[16:01:05] Exception: 000006BA
[16:01:05] Exception: 000006BA
[16:01:13] Exception: 000006BA
[16:01:13] Exception: 000006BA
[16:01:32] Exception: 00000005
[16:01:32] Exception: 00000005
[16:01:32] Exception: 00000005
[16:01:32] Exception: 00000005
[16:01:38] Exception: 000006BA
[16:02:05] Exception: 000006BA
[16:02:38] Exception: 000006BA
[16:03:09] Exception: 00000005
[16:03:09] Exception: 00000005
[16:03:09] Exception: 00000005
[16:03:09] Exception: 00000005
[16:22:15] Exception: 00000005
[16:22:15] Exception: 00000005
[16:22:15] Exception: 00000005
[16:22:15] Exception: 00000005
[16:29:32] Exception: 00000005
[16:29:32] Exception: 00000005
[16:29:32] Exception: 00000005
[16:29:32] Exception: 00000005
[17:05:02] Exception: 00000005
[17:05:02] Exception: 00000005
[17:22:50] Exception: 00000005
[17:22:50] Exception: 00000005
[17:22:50] Exception: 00000005
[17:22:50] Exception: 00000005
[17:28:56] Exception: 00000005
[17:28:56] Exception: 00000005
[17:28:56] Exception: 00000005
[17:28:56] Exception: 00000005
[18:20:25] Exception: 00000005
[18:20:25] Exception: 00000005
[18:27:55] Exception: 00000005
[18:27:55] Exception: 00000005
[18:32:02] Exception: 00000005
[18:32:02] Exception: 00000005
[18:36:08] Exception: 00000005
[18:36:08] Exception: 00000005
[18:44:15] Exception: 00000005
[18:44:15] Exception: 00000005
[18:44:15] Exception: 00000005
[18:44:15] Exception: 00000005
[18:44:33] Exception: 00000005
[18:44:34] Exception: 00000005
[18:44:34] Exception: 00000005
[18:44:34] Exception: 00000005
[19:50:14] Exception: 00000005
[19:50:14] Exception: 00000005
[19:50:14] Exception: 00000005
[19:50:14] Exception: 00000005
[19:50:44] Exception: 00000005
[19:50:44] Exception: 00000005
[19:50:44] Exception: 00000005
[19:50:44] Exception: 00000005
[19:51:36] Exception: 00000005
[19:51:36] Exception: 00000005
[19:51:36] Exception: 00000005
[19:51:36] Exception: 00000005
[19:51:59] Exception: 00000005
[19:51:59] Exception: 00000005
[19:51:59] Exception: 00000005
[19:51:59] Exception: 00000005
[19:53:09] Exception: 00000005
[19:53:09] Exception: 00000005
[19:53:09] Exception: 00000005
[19:53:09] Exception: 00000005
[19:53:36] Exception: 00000005
[19:53:36] Exception: 00000005
[19:53:36] Exception: 00000005
[19:53:36] Exception: 00000005
[19:53:54] Exception: 00000005
[19:53:54] Exception: 00000005
[19:53:54] Exception: 00000005
[19:53:54] Exception: 00000005
[19:54:15] Exception: 00000005
[19:54:15] Exception: 00000005
[19:54:15] Exception: 00000005
[19:54:15] Exception: 00000005
[06:59:40] Exception: 00000721
[07:01:02] Exception: 000006BA
[07:01:02] Exception: 000006BA
[07:10:14] The process has exited.
[07:10:14] Dump count not reached.
Проблема очень глобальная а решение я найти так и не могу.
ruslan...
09-11-2016, 22:59
iminbox,
Нужен дамп.
Я понимаю, но как я его пришлю если он не пишется?
Twenty one
17-11-2016, 12:17
Доброго дня. Все принтеры установлены на общественном сервере, один установлен непосредственно на личном ПК, служба принтеров выключается через каждый 3 секунды после её включения. Проблема началась после установки нового принтера Canon LBP7010C/7018C. Операционная система Windows 7 Домашняя базовая. Дамп в файлообменнике. http://файлообменник.рф/74322c0ub1vb/spoolsv.exe_161117_105522.dmp.html
Petya V4sechkin
17-11-2016, 12:42
Twenty one, сбой на
C:\Windows\System32\spool\drivers\x64\3\CNACBMUI.DLL
относится к Canon.
Twenty one
18-11-2016, 16:59
Petya V4sechkin, в чём состоит решение данной проблемы?
ruslan...
18-11-2016, 17:09
в чём состоит решение данной проблемы? »
вот такие у Canon драйверы (причем у многих моделей аналогичные проблемы).
Люди советуют разные варианты:
включить "изоляцию драйверов";
включить перезапуск службы "Диспетчер печати" при сбое;
использовать Easy Print. »
Дополнительно Вам в помощь Изоляция драйвера принтера в Windows 7 & Server 2008 R2 (http://dimsan.blogspot.ru/2009/08/windows-7-server-2008-r2.html)
Angry Demon
19-11-2016, 09:26
в чём состоит решение данной проблемы?
Не использовать подобные недо-принтеры. Только устройства с нормальной поддержкой PCL.
kolyanovak@vk
25-11-2016, 11:01
https://drive.google.com/file/d/0B_wlA1OBX9ZrUHZsWmNDU2NhWHc/view?usp=sharing файл дампа , подскажете в каком драйвере причина.
Petya V4sechkin
25-11-2016, 11:06
kolyanovak@vk, сбой на
C:\Windows\System32\spool\drivers\x64\3\CNLB0MUI_DAD22.DLL
относится к Canon.
kolyanovak@vk
27-11-2016, 09:35
kolyanovak@vk, сбой на
C:\Windows\System32\spool\drivers\x64\3\CNLB0MUI_DAD22.DLL
относится к Canon. »
подскажете как вы прочитали дамп ?
я открыл дамп с помошью "Debugging Tools for Windows", но какой именно драйвер сбой вывел не нашел =(
Petya V4sechkin
27-11-2016, 09:37
kolyanovak@vk, команда !analyze -v или просто k.
kolyanovak@vk
28-11-2016, 01:20
Petya V4sechkin, при выполнении !analyze -v получаю вот это 0:028> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: $ntdllsym!_CONTEXT ***
*** ***
*************************************************************************
***** OS symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_CONTEXT ***
*** ***
*************************************************************************
DUMP_CLASS: 2
DUMP_QUALIFIER: 400
CONTEXT: (.ecxr)
rax=000000000000e6a0 rbx=000000eff62ce930 rcx=000000000000001c
rdx=000000000000a230 rsi=0000000000000000 rdi=0000000000000000
rip=00007ff93e050f20 rsp=000000eff62ceb40 rbp=0000000000000000
r8=0000000000000001 r9=00007ff93d4a13d2 r10=000000eff62ce6a8
r11=00007ff93e08dda8 r12=0000000000000001 r13=0000000000000001
r14=0000000000000008 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000200
ntdll+0xf0f20:
00007ff9`3e050f20 eb00 jmp ntdll+0xf0f22 (00007ff9`3e050f22)
Resetting default scope
FAULTING_IP:
ntdll+f0f20
00007ff9`3e050f20 eb00 jmp ntdll+0xf0f22 (00007ff9`3e050f22)
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff93e050f20 (ntdll+0x00000000000f0f20)
ExceptionCode: c0000374
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 00007ff93e08dd40
BUGCHECK_STR: 550F4336
WRONG_SYMBOLS_TIMESTAMP: 550f4336
WRONG_SYMBOLS_SIZE: 1ac000
FAULTING_MODULE: 00007ff93df60000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 550f4336
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols. ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
ANALYSIS_SESSION_HOST: DESKTOP-B228LQI
ANALYSIS_SESSION_TIME: 11-28-2016 08:14:41.0953
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
STACK_TEXT:
00000000`00000000 00000000`00000000 WRONG_SYMBOLS!WRONG_SYMBOLS+0x0
STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** ; kb
THREAD_SHA1_HASH_MOD_FUNC: 2a06fe893fc51638e55bcc8ee02bcdf6f10cbc26
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 214d5e958d92c59434e5414a89d1e95c2f82d12a
THREAD_SHA1_HASH_MOD: 79d1e41e8e0e291e73ec18352c568efa4ef4b5ab
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
EXCEPTION_CODE: (NTSTATUS) 0x550f4336 - <Unable to get error code text>
EXCEPTION_CODE_STR: 550F4336
EXCEPTION_STR: PRIVATE_SYMBOLS
PROCESS_NAME: ntdll.wrong.symbols.dll
IMAGE_NAME: ntdll.wrong.symbols.dll
MODULE_NAME: ntdll_wrong_symbols
SYMBOL_NAME: ntdll_wrong_symbols!550F43361AC000
BUCKET_ID: PRIVATE_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_150322-223326
DEFAULT_BUCKET_ID: PRIVATE_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_150322-223326
PRIMARY_PROBLEM_CLASS: PRIVATE_SYMBOLS
FAILURE_BUCKET_ID: PRIVATE_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_150322-223326_550F4336_ntdll.wrong.symbols.dll!550F43361AC000
FAILURE_EXCEPTION_CODE: 550F4336
FAILURE_IMAGE_NAME: ntdll.wrong.symbols.dll
BUCKET_ID_IMAGE_STR: ntdll.wrong.symbols.dll
FAILURE_MODULE_NAME: ntdll_wrong_symbols
BUCKET_ID_MODULE_STR: ntdll_wrong_symbols
FAILURE_FUNCTION_NAME: 550F43361AC000
BUCKET_ID_FUNCTION_STR: 550F43361AC000
BUCKET_ID_OFFSET: 0
BUCKET_ID_MODTIMEDATESTAMP: 0
BUCKET_ID_MODCHECKSUM: 0
BUCKET_ID_MODVER_STR: 0.0.0.0
BUCKET_ID_PREFIX_STR: PRIVATE_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_150322-223326
FAILURE_PROBLEM_CLASS: PRIVATE_SYMBOLS_X64_6.3.9600.17031_(winblue_gdr.140221-1952)_TIMESTAMP_150322-223326
FAILURE_SYMBOL_NAME: ntdll.wrong.symbols.dll!550F43361AC000
TARGET_TIME: 2016-11-24T23:02:05.000Z
OSBUILD: 9600
OSSERVICEPACK: 17415
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 2
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
OSEDITION: Windows 8.1 LanManNt TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2014-10-29 12:45:30
BUILDDATESTAMP_STR: 140221-1952
BUILDLAB_STR: winblue_gdr
BUILDOSVER_STR: 6.3.9600.17031
ANALYSIS_SESSION_ELAPSED_TIME: 209
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:private_symbols_x64_6.3.9600.17031_(winblue_gdr.140221-1952)_timestamp_150322-223326_550f4336_ntdll.wrong.symbols.dll!550f43361ac000
FAILURE_ID_HASH: {3273423f-2672-1930-547a-adba955934cc}
Followup: MachineOwner
---------
упоминания о "C:\Windows\System32\spool\drivers\x64\3\CNLB0MUI_DAD22.DLL" не вижу
Petya V4sechkin
28-11-2016, 08:06
kolyanovak@vk, в меню File -> задайте Symbol File Path и Image File Path:
srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
и создайте папку C:\Symbols (туда по мере необходимости будут скачиваться debug symbols с сайта Microsoft).
© OSzone.net 2001-2012
vBulletin v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.
Available in ZeroNet 1osznRoVratMCN3bFoFpR2pSV5c9z6sTC