- Remove From My Forums
-
Question
-
Hi,
I have this message on a Ms-Windows 2008 R2 enterprise ed (x64).
I’ve tried to install hyper V.
I’ve ROLE : Error on the gui
and the following error in the server manager log file2264: 2010-03-08 14:50:15.629 [Provider] C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist.
2264: 2010-03-08 14:50:15.630 [CBS] IsCacheStillGood: False.
2264: 2010-03-08 14:50:15.632 [CBS] Error (Id=0) Function: ‘CreateSessionAndPackage()->CoCreateInstance’ failed: 80070422 (-2147023838)
2264: 2010-03-08 14:50:15.635 [ExceptionHandler] Error (Id=0) An unexpected exception was found:
System.Runtime.InteropServices.COMException (0x80070422): The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package)
at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo()
at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize()
at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery()
at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery()
at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType)
at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)I’ve 3 server with the same configuration, patches and installed software working without problem.
Could you please help me to fix this ?Thanks
Mick
Answers
-
Hi Mickael,
Thank you for the reply.
The CheckSUR.log does not show any error.
I noticed in the Servermanager.log file, there is any error: “C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist”.
Sometimes the C:Windowssystem32ServerManagerCache folder could be deleted by Symantec EndPoint Protection software.
If you have Symantec EndPoint Protection software, please disable or remove it first.
I suggest restoring the Cache folder to the state when CbsUpdateState.bin existed.
Open C:Windowssystem32ServerManager, right-click Cache and click Properties. On the Previous Version tab, choose a folder version which contains the CbsUpdateState.bin file and click Restore.
If the issue persists, we may need to reinstall .Net Framework components.
Tim Quan — MSFT
-
Marked as answer by
Friday, March 19, 2010 1:56 AM
-
Marked as answer by
- Remove From My Forums
-
Question
Answers
-
Tim,
The issue has been resolved; the issue was a Security Update — Microsoft .NET Framework 2.0 Service Pack 2
(KB974470) that was corrupted—however, it took us about 4 hrs to remove it—re-installed it afterwards and the Server Manager Features & Roles Summaries came right up.Thanks for your help,
Jim
-
Marked as answer by
Tim Quan
Tuesday, January 26, 2010 1:13 AM
-
Marked as answer by
All replies
-
Hi Jim,
Please run the System Update Readiness Tool first and let me know the result in %SYSTEMROOT%LogsCBSCheckSUR.log:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, for Windows 7, and for Windows Server 2008 R2
http://support.microsoft.com/default.aspx/kb/947821/en-us
Tim Quan — MSFT
-
Tim,
As instructed, please see below log—
=================================
Checking System Update Readiness.
Binary Version 6.0.6002.22202
Package Version 6.0
2010-01-07 08:06Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 248
No errors detected -
Hi,
How are things going? I have not heard back from you in a few days and wanted to check on the status of the issue. Please let me know how things turned out.
Tim Quan — MSFT
-
Sorry, both logs have been uploaded. Thanks, Jim
-
Hi Jim,
Thank you for sending me the files.
From the log files, I noticed the cause is “C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist”.
Sometimes this file could be deleted by Symantec EndPoint Protection software.
I suggest restoring the Cache folder to the state when CbsUpdateState.bin existed.
Open C:Windowssystem32ServerManager, right-click Cache and click Properties. On the Previous Version tab, choose a folder version which contains the CbsUpdateState.bin file and click Restore.
Hope it helps.
Tim Quan — MSFT
-
Tim,
No-go; the cache folder has no files inside—I even copied said file from another W2K server and that didn’t work….grrrrrrrrrr.
Thanks,
Jim
-
Hi Jim,
Thank you for the reply.
There should be two files in C:Windowssystem32ServerManagerCache:
CbsUpdateInfo.bin
CbsUpdateState.bin
Now I would like to confirm whether you have Symantec EndPoint Protection software installed. If so, please temporary remove it and restart the computer to test the result.
These two folder should be recreated automatically after restarting.
If the issue persists, let’s try Clean Boot:
Clean Boot
=======
Let’s disable all startup items and third party services when booting. This method will help us determine if this issue is caused by a loading program or service. Please perform the following steps:
1. Click the Start Button type «msconfig» (without quotation marks) in the Start Search box, and then press Enter.
Note: If prompted, please click Continue on the User Account Control (UAC) window.
2. Click the «Services» tab, check the «Hide All Microsoft Services» box and click «Disable All» (if it is not gray).
3. Click the «Startup» tab, click «Disable All» and click «OK».
Then, restart the computer. When the «System Configuration Utility» window appears, please check the «Don’t show this message or launch the System Configuration Utility when Windows starts» box and click OK.
Please test this issue in the Clean Boot environment, if the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.
Hope it helps.
Tim Quan — MSFT
-
Hi Jim,
How are things going? I have not heard back from you in a few days and wanted to check on the status of the issue. Please let me know how things turned out.
Tim Quan — MSFT
-
Give me till tomorrow please…crisis mode on something else right now…
Thanks,
Jim
-
no-go; I wonder if re-install SP2 might resolved the issue? Any thoughts?
-
Hi Jim,
As you are running Windows Server 2008 R2, you cannot install SP2 on it. Now no service pack is available to Windows Server 2008 R2.
Now I suggest removing Symantec EndPoint Protection software (if you installed) and then running System File Checker:
1. Open an elevated command prompt. To do this, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
If you are prompted for an administrator password or for a confirmation, type the password, or click Allow.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Restart the computer, keep pressing F8 to enter Safe Mode and then check whether these two files appear.
Hope it helps.
Tim Quan — MSFT
-
Tim,
No-go, receive the below error—C:Usersjrodrigu>sfc /scannow
Beginning system scan. This process will take some time.
Windows Resource Protection could not perform the requested operation.I am going to open a PSS Call; will post results—
-
Tim,
The issue has been resolved; the issue was a Security Update — Microsoft .NET Framework 2.0 Service Pack 2
(KB974470) that was corrupted—however, it took us about 4 hrs to remove it—re-installed it afterwards and the Server Manager Features & Roles Summaries came right up.Thanks for your help,
Jim
-
Marked as answer by
Tim Quan
Tuesday, January 26, 2010 1:13 AM
-
Marked as answer by
-
Hi Jim,
Thank you very much for letting me know how you resolved this issue. I believe this will benefit other people who encounter the same issue in the future.
Tim Quan — MSFT
Introduction
On certain Windows Server 2008 R2 machines you may experience theServer Manager being unable to open Roles and/or Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE).
Certain people have also reported finding that there is also an error being logged in the event log – Error 1601. Various reasons lead us to believe that this is an issue related to file corruption. More specifically, file corruption caused by failed Windows Updates.
If your Server Manager is crashing and you’re unable to add Roles or Features this article will talk you through a number of steps which may help you resolve the issue.
Step 1 – Download & Install System Update Readiness Tool (KB947821)
The first step in trying to diagnose this is to download and install KB947821 on the server which is having the problem with System Manager and generating the 0x800706BE refresh error. You can download it from http://support.microsoft.com/kb/947821
The System Update Readiness Tool, runs a onetime scan for inconsistencies that might prevent future servicing operations. This scan typically takes less than 15 minutes to run. However, the tool might take significantly longer on some computers. The Windows Update progress bar is notupdated during the scan, and progress seems to stop at 60% complete for some time. This behavior is expected. The scan is still running and you should not cancel the update. If you are prompted to restart your computer, do so.
Step 2 – Analyze KB947821 output log file
After you install KB947821 on your computer, you need to inspect the output log file it left behind. You can find the file in: C:WindowsLogsCBSCheckSUR.log
The log should show what files have been detected as corrupt or missing from/in the C:windowsservicingpackages folder. For instance, on our test machine they were shown as:
2010-10-07 09:30:43, Info CBS Failed to get session package state for package: Package_3_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2010-10-07 09:30:43, Info CBS Failed to get session package state for package: Package_2_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
You might also want to have a look at the CheckSUR.persist.log. In our case it looked like this:
=================================
Checking System Update Readiness.
Binary Version 6.1.7600.20593
Package Version 7.0
2010-04-14 09:56
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 72
Found 1 errors
CBS MUM Corrupt Total count: 1
Unavailable repair files:
servicingpackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum
servicingpackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat
(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache
We also checked the servermanager.log and found that the CbsUpdateState.bin file in the C:Windowssystem32ServerManagerCache folder is missing.
4652: 2010-10-14 17:43:53.856 [Provider] C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist. 4652: 2010-10-14 17:43:53.965 [CBS] IsCacheStillGood: False. 4652: 2010-10-14 17:44:13.356 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800706be (-2147023170) 4652: 2010-10-14 17:44:13.419 [ExceptionHandler] Error (Id=0) An unexpected exception was found: System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package) at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo() at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize() at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery() at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery() at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType) at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)
Step 3 – Copy missing or corrupt files
In order to perform this step, you’ll need access to a machine which has a working ServerManager. Copy the files listed as corrupted/missing from C:windowsservicingpackages on the working machine to the server which is exhibiting the HRESULT 0x800706BE error. You may need to change the ownership of the files on the destination machine to your user account as well as give yourself write permissions on the files before Windows allows you to overwrite them.
Once done, start Server Manager and see if that fixes the error. To be doubly sure, check the contents of the C:Windowssystem32ServerManagerCache folder – there should be two files there: CbsUpdateInfo.bin and CbsUpdateState.bin. If these files still don’t exist after ServerManager starts you haven’t completely fixed the 0x800706BE error.
Step 4 – Copy all files in C:windowsservicingpackages folder
If you’re still unable to get Server Manager started, it means that there may be other problems and we need to overwrite all the packages in the C:windowsservicingpackages folder. The first step we need to do is take ownership of all the files. To do this, launch a Command Prompt as an Administrator, and I mean right click the Command Prompt icon and select Run As Administrator. At the command prompt execute:
takeown /F c:WindowsServicingPackages /D y /R
The takeown command will give you ownership of the files, but you still need to give yourself write access to the files in order to change them. In the same command prompt window execute the following command: (replace username with your username)
cacls c:WindowsServicingPackages /E /T /C /G "username":F
Now copy all the files from the C:windowsservicingpackages folder on a working server. Make sure that the source server has been patched to the same level and has the same roles/features installed as the destination server.
Step 5 – Start Server Manager and check Cache folder
Try starting Server Manager and check if you’re still getting the error. In all our tests, the above steps have been able to resolve 99% of all Server Manger problems related to error 0x800706BE and 1601. Jus to be on the safe side, check the contents of the C:Windowssystem32ServerManagerCache folder and see that the two .bin files are now visible.
Conclusion
This article has demonstrated a quick and easy way to solve the errors associated with ServerManager and the 0x800706BE and 1601 errors that it exhibits when trying to install Roles or Features. If the problem is not resolved by applying Microsoft KB947821, we have shown a reliable way to fix the 0x800706BE and 1601 errors by copying all files in C:windowsservicingpackages from anther working Windows Server 2008 R2 server.
References
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779%28WS.10%29.aspx
Unexpected error refreshing Server Manager-errors 0x800706BE and 1601 on Window Server 2008 R2
On certain Windows Server 2008 R2 machines you may experience the Server Manager being unable to open Roles and/or Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE). You may also find that there is also Error 1601 in the Event Log.
Introduction
On certain Windows Server 2008 R2 machines you may experience the Server Manager being unable to open Roles and/or Features in the MMC. The error it usually comes back with is Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE).
Certain people have also reported finding that there is also an error being logged in the event log – Error 1601. Various reasons lead us to believe that this is an issue related to file corruption. More specifically, file corruption caused by failed Windows Updates.
If your Server Manager is crashing and you’re unable to add Roles or Features this article will talk you through a number of steps which may help you resolve the issue.
Step 1 – Download & Install System Update Readiness Tool (KB947821)
The first step in trying to diagnose this is to download and install KB947821 on the server which is having the problem with System Manager and generating the 0x800706BE refresh error. You can download it from http://support.microsoft.com/kb/947821
The System Update Readiness Tool, runs a onetime scan for inconsistencies that might prevent future servicing operations. This scan typically takes less than 15 minutes to run. However, the tool might take significantly longer on some computers. The Windows Update progress bar is not updated during the scan, and progress seems to stop at 60% complete for some time. This behavior is expected. The scan is still running and you should not cancel the update. If you are prompted to restart your computer, do so.
Step 2 – Analyze KB947821 output log file
After you install KB947821 on your computer, you need to inspect the output log file it left behind. You can find the file in: C:WindowsLogsCBSCheckSUR.log
The log should show what files have been detected as corrupt or missing from/in the C:windowsservicingpackages folder. For instance, on our test machine they were shown as:
2010-10-07 09:30:43, Info CBS Failed to get session package state for package: Package_3_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND] 2010-10-07 09:30:43, Info CBS Failed to get session package state for package: Package_2_for_KB975467~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
You might also want to have a look at the CheckSUR.persist.log. In our case it looked like this:
================================= Checking System Update Readiness. Binary Version 6.1.7600.20593 Package Version 7.0 2010-04-14 09:56 Checking Windows Servicing Packages Checking Package Manifests and Catalogs (f) CBS MUM Corrupt 0x00000000 servicingPackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum Expected file name Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum does not match the actual file name Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store Summary: Seconds executed: 72 Found 1 errors CBS MUM Corrupt Total count: 1 Unavailable repair files: servicingpackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.mum servicingpackagesPackage_for_KB976264_RTM~31bf3856ad364e35~amd64~~6.1.2.0.cat (w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache
We also checked the servermanager.log and found that the CbsUpdateState.bin file in the C:Windowssystem32ServerManagerCache folder is missing.
4652: 2010-10-14 17:43:53.856 [Provider] C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist. 4652: 2010-10-14 17:43:53.965 [CBS] IsCacheStillGood: False. 4652: 2010-10-14 17:44:13.356 [CBS] Error (Id=0) Function: 'CreateSessionAndPackage()->Session_OpenPackage' failed: 800706be (-2147023170) 4652: 2010-10-14 17:44:13.419 [ExceptionHandler] Error (Id=0) An unexpected exception was found: System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE) at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Microsoft.Windows.ServerManager.ComponentInstaller.CreateSessionAndPackage(IntPtr& session, IntPtr& package) at Microsoft.Windows.ServerManager.ComponentInstaller.InitializeUpdateInfo() at Microsoft.Windows.ServerManager.ComponentInstaller.Initialize() at Microsoft.Windows.ServerManager.Common.Provider.RefreshDiscovery() at Microsoft.Windows.ServerManager.LocalResult.PerformDiscovery() at Microsoft.Windows.ServerManager.ServerManagerModel.CreateLocalResult(RefreshType refreshType) at Microsoft.Windows.ServerManager.ServerManagerModel.InternalRefreshModelResult(Object state)
Step 3 – Copy missing or corrupt files
In order to perform this step, you’ll need access to a machine which has a working Server Manager. Copy the files listed as corrupted/missing from C:windowsservicingpackages on the working machine to the server which is exhibiting the HRESULT 0x800706BE error. You may need to change the ownership of the files on the destination machine to your user account as well as give yourself write permissions on the files before Windows allows you to overwrite them.
Once done, start Server Manager and see if that fixes the error. To be doubly sure, check the contents of the C:Windowssystem32ServerManagerCache folder – there should be two files there: CbsUpdateInfo.bin and CbsUpdateState.bin. If these files still don’t exist after Server Manager starts you haven’t completely fixed the 0x800706BE error.
Step 4 – Copy all files in C:windowsservicingpackages folder
If you’re still unable to get Server Manager started, it means that there may be other problems and we need to overwrite all the packages in the C:windowsservicingpackages folder. The first step we need to do is take ownership of all the files. To do this, launch a Command Prompt as an Administrator, and I mean right click the Command Prompt icon and select Run As Administrator. At the command prompt execute:
takeown /F c:WindowsServicingPackages /D y /R
The takeown command will give you ownership of the files, but you still need to give yourself write access to the files in order to change them. In the same command prompt window execute the following command: (replace username with your username)
cacls c:WindowsServicingPackages /E /T /C /G "username":F
Now copy all the files from the C:windowsservicingpackages folder on a working server. Make sure that the source server has been patched to the same level and has the same roles/features installed as the destination server.
Step 5 – Start Server Manager and check Cache folder
Try starting Server Manager and check if you’re still getting the error. In all our tests, the above steps have been able to resolve 99% of all Server Manger problems related to error 0x800706BE and 1601. Jus to be on the safe side, check the contents of the C:Windowssystem32ServerManagerCache folder and see that the two .bin files are now visible.
Conclusion
This article has demonstrated a quick and easy way to solve the errors associated with Server Manager and the 0x800706BE and 1601 errors that it exhibits when trying to install Roles or Features. If the problem is not resolved by applying Microsoft KB947821, we have shown a reliable way to fix the 0x800706BE and 1601 errors by copying all files in C:windowsservicingpackages from anther working Windows Server 2008 R2 server.
References
System Update Readiness Tool (KB947821)
http://support.microsoft.com/kb/947821
Advanced guidelines for diagnosing and fixing servicing corruption
http://technet.microsoft.com/en-us/library/ee619779%28WS.10%29.aspx
This entry was posted on March 16, 2011, 8:35 am and is filed under Server 2008 R2 General. You can follow any responses to this entry through RSS 2.0.
You can leave a response, or trackback from your own site.
Добрый день.
В целях проф. развития развернул Windows Server 2008 R2 SP1 x64 RUS на VMware Workstation.
Следуя задачам начальной настройки активировал ОС ключом полученным на DreamSpark, установил часовой пояс, обозвал сервер STUDY-DC, прописал статику (подключен к LAN через мост), включил автоматическое обновление важных обнов, поставил все обновления какие были, обновление IE до 11й версии вылетало с ошибкой — скрыл обновление т.к. по факту IE 11 встал и работает. Приступил к добавлению роли контроллера домена AD — вылетает ошибка, часть лога:
1248: 2015-12-27 12:22:55.167 [Provider] Error (Id=0) Sync Result — Success: False, RebootRequired: False, Id: 110
1248: 2015-12-27 12:22:55.167 [Provider] Error (Id=0) Sync Message — OperationKind: Install, MessageType: Error, MessageCode: -2146498530, Message: Не удалось установить Контроллеры домена Active Directory., AdditionalMessage: Указанный пакет неприменим (значение ошибки: 0x800F081E).
1248: 2015-12-27 12:22:55.182 [InstallationProgressPage] Sync operation completed
1248: 2015-12-27 12:22:55.182 [InstallationProgressPage] Performing post install/uninstall discovery…
1248: 2015-12-27 12:22:55.182 [Provider] C:Windowssystem32ServerManagerCacheCbsUpdateState.bin does not exist.
1248: 2015-12-27 12:22:55.182 [CBS] IsCacheStillGood: False.
Сколько не гуглил решения не нашел, будьте добры помочь советом как решить проблему. Так-же просьба порекомендовать полезную литературу касательно администрирования данной версии ОС.
Форум КриптоПро
»
КриптоПро УЦ
»
КриптоПро УЦ 1.5
»
0x8009001f ошибка при создании корневых ключей ЦС на Атликс-HSM
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
Добрый день! <Информация>: После завершения установки может потребоваться перезагрузка этого сервера. |
 |
WWW |
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
Из ServerManager.log: name : Службы сертификации Active Directory |
|
|
WWW |
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
name : Центр сертификации 4352: 2013-05-16 18:46:10.345 [Sync] Calling sync provider of Центр сертификации … 4352: 2013-05-16 18:46:32.997 [Provider] Sync Result — Success: True, RebootRequired: False, Id: 200 |
|
|
WWW |
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
4352: 2013-05-16 18:46:36.086 [CBS] Update: DesktopExperience, Restart: CbsRestartRequired, Parents: InkSupport |
|
|
WWW |
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
Похоже проблем с КриптоПро CSP, скорее всего со считывателями. В CSP установлены считыватели cha CARDOS V4.3B, cha JCOP, но по инструкции для HSM нужны GemPC433 SL 00 00 и HDIMAGE. Помогите, пожалуйста, решить проблему с установкой ЦС с ключами на HSM. |
|
|
WWW |
|
denis.s |
|
|
Статус: Новичок Группы: Участники
|
Поле CN корневого сертификата укажите только латинскими буквами. |
|
|
|
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
Согласно инструкции ЖТЯИ.00067 02 90 02 «КриптоПро УЦ Руководство по установке» п.5.1.3: Согласно ей я делал: CN=УЦ ООО РК |
|
|
WWW |
|
denis.s |
|
|
Статус: Новичок Группы: Участники
|
А при этом клиент Atlix HSM устанавливает соединение с HSM? Во вкладке параметры HSM отображается информация ? |
|
|
|
|
Pocomaxa |
|
|
Статус: Активный участник Группы: Участники Поблагодарили: 2 раз в 2 постах |
Да, соединение устанавливается с HSM нормально, показывает: |
|
|
WWW |
|
denis.s |
|
|
Статус: Новичок Группы: Участники
|
Это у Вас тестовая машина ? Если да, попробуйте поменять имя компьютера и заново поднять службу. Поле CN задайте только латиницей. |
|
|
|
| Пользователи, просматривающие эту тему |
|
Guest |
Форум КриптоПро
»
КриптоПро УЦ
»
КриптоПро УЦ 1.5
»
0x8009001f ошибка при создании корневых ключей ЦС на Атликс-HSM
Быстрый переход
Вы не можете создавать новые темы в этом форуме.
Вы не можете отвечать в этом форуме.
Вы не можете удалять Ваши сообщения в этом форуме.
Вы не можете редактировать Ваши сообщения в этом форуме.
Вы не можете создавать опросы в этом форуме.
Вы не можете голосовать в этом форуме.
Как правило, такие BIN ошибки возникают из-за повреждённых или отсутствующих файлов CbsUpdateState.bin, а иногда — в результате заражения вредоносным ПО в настоящем или прошлом, что оказало влияние на Microsoft Windows Server 2008 Standard SP2. В большинстве случаев скачивание и замена файла BIN позволяет решить проблему. Кроме того, регулярная очистка и оптимизация реестра Windows предотвратит создание неправильных ссылок на пути к файлам BIN, поэтому мы настоятельно рекомендуем регулярно выполнять сканирование реестра.
Наша коллекция файлов CbsUpdateState.bin для %%os%% представлена в списках ниже. К сожалению, в настоящее время в нашей базе могут отсутствовать некоторые версии файлов CbsUpdateState.bin, но их можно запросить, нажав на кнопку Request (Запрос). Если вы не нашли необходимую вам версию файла в нашей базе, представленной ниже, мы рекомендуем обратиться непосредственно к Dell.
Несмотря на то, что в большинстве случаев после размещения файла CbsUpdateState.bin в надлежащем месте на жёстком диске, сообщения об ошибках, связанных с этим файлом, больше не выводятся, следует выполнить быструю проверку, чтобы окончательно в этом убедиться. Повторно запустите Microsoft Windows Server 2008 Standard SP2, чтобы убедиться в успешном решении проблемы.
| CbsUpdateState.bin Описание файла | |
|---|---|
| Расширение: | BIN |
| Категория: | Documentation,Operating System,Software |
| App: | Microsoft Windows Server 2008 Standard SP2 |
| ID: | 2009 |
| Компания: | Dell |
| Имя файла: | CbsUpdateState.bin |
| KB: | 19890 |
| SHA-1: | cb2a35dcc66a43bcdab31a5276d9ae6ce58fea7b |
| MD5: | 8e59020c9a3a766a1fe11a1857982343 |
| CRC32: | 3d160ffd |
Продукт Solvusoft
Загрузка
WinThruster 2023 — Сканировать ваш компьютер на наличие ошибок реестра в CbsUpdateState.bin
Windows
11/10/8/7/Vista/XP
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
BIN
CbsUpdateState.bin
Идентификатор статьи: 522802
CbsUpdateState.bin
| File | Контрольная сумма MD5 | Байт | Загрузить | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| + CbsUpdateState.bin | 8e59020c9a3a766a1fe11a1857982343 | 19.42 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | e11f308ee704c1d4d3016d5fbcbe6d6b | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 1aa4aed445ba645e22e49f514d912722 | 19.52 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 3cbc9e144a8ca2350c96e5ab4d1fcd6a | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | c3e59e0811518b48979780704e3a7e2e | 20.30 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | bf660e1f589ee74036e0b5e1df4ae32b | 20.30 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | c3e59e0811518b48979780704e3a7e2e | 20.30 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | c3e59e0811518b48979780704e3a7e2e | 20.30 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 8e59020c9a3a766a1fe11a1857982343 | 19.42 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | e11f308ee704c1d4d3016d5fbcbe6d6b | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 3cbc9e144a8ca2350c96e5ab4d1fcd6a | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 8e59020c9a3a766a1fe11a1857982343 | 19.42 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | e11f308ee704c1d4d3016d5fbcbe6d6b | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 3cbc9e144a8ca2350c96e5ab4d1fcd6a | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 8e59020c9a3a766a1fe11a1857982343 | 19.42 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | e11f308ee704c1d4d3016d5fbcbe6d6b | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 3cbc9e144a8ca2350c96e5ab4d1fcd6a | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 8e59020c9a3a766a1fe11a1857982343 | 19.42 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | e11f308ee704c1d4d3016d5fbcbe6d6b | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 1aa4aed445ba645e22e49f514d912722 | 19.52 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 3cbc9e144a8ca2350c96e5ab4d1fcd6a | 20.20 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 6fadb54bc054e97343ad6a663257c5ef | 13.13 KB | ||||||||||||||||
|
||||||||||||||||||
| + CbsUpdateState.bin | 6fadb54bc054e97343ad6a663257c5ef | 13.13 KB | ||||||||||||||||
|
Ошибки CbsUpdateState.bin
Вопросы, связанные с CbsUpdateState.bin и Microsoft Windows Server 2008 Standard SP2:
- «Ошибка: CbsUpdateState.bin. «
- «CbsUpdateState.bin перемещен или отсутствует. «
- «Отсутствует файл CbsUpdateState.bin.»
- «Не удалось загрузить файл CbsUpdateState.bin. «
- «Ошибка регистрации CbsUpdateState.bin. «
- «Ошибка времени выполнения Microsoft Windows Server 2008 Standard SP2: CbsUpdateState.bin»
- «Ошибка загрузки CbsUpdateState.bin.»
Как правило, ошибки CbsUpdateState.bin возникают во время процесса установки оборудования или программного обеспечения, связанного с Microsoft Windows Server 2008 Standard SP2s, во время загрузки драйвера, связанного с Dell, или во время завершения работы или запуска Windows. При появлении ошибки CbsUpdateState.bin запишите вхождения для устранения неполадок Microsoft Windows Server 2008 Standard SP2 и чтобы HelpDell найти причину.
Причины проблем CbsUpdateState.bin
Проблемы CbsUpdateState.bin могут быть отнесены к поврежденным или отсутствующим файлам, содержащим ошибки записям реестра, связанным с CbsUpdateState.bin, или к вирусам / вредоносному ПО.
В частности, проблемы CbsUpdateState.bin, созданные:
- Раздел реестра CbsUpdateState.bin поврежден.
- Вирус или вредоносное ПО поврежден CbsUpdateState.bin.
- Другая программа злонамеренно или по ошибке удалила файлы, связанные с CbsUpdateState.bin.
- Другое программное обеспечение, конфликтующее с Microsoft Windows Server 2008 Standard SP2, CbsUpdateState.bin или общими ссылками.
- Поврежденная установка или загрузка Microsoft Windows Server 2008 Standard SP2 (CbsUpdateState.bin).