Some customers reported that they got error 0x80080005 on their WSUS client. A simple fix is adding the following registry key:
HKLM\SYSTEM\CurrentControlSet\Control
Key = RegistrySizeLimit
Type = DWORD
Value = 4294967295
If the above solution can not resolve your failure, please send me the log files.
Customers reported that their CA restore failed. The symptom is:
When migrating the issuing CA using keys which protected by the nCiphers Security World Module Key it works using the existing certificate after first importing the certificate and assignment of private key using certutil -repair.
If private key requires interaction with the desktop, then associated certificate won't appear in the certificates list.
Resolution:
It seems to be a known issue.
There is a workaround:
1) Verify that the certificate is truly functional by running certutil -verifystore my
2) Check in the output that the key is protected by the nCipher Enhanced CSP and passes all tests
3) When you run the wizard, state that you want to use an existing private key (yes this creates a new certificate)
4) After restore, either restore the previous registry from the other CA, or modify the following registry key to use the original certificate's thumbprint:
hklm\system\currentcontrolset\services\certsvc\Configuration\CAName\CACertHash
Symptom:
A few customers reported the following issue:
Environment:
DPM 2010 installed on Windows2008 R2 SP1 with hyper-v enabled.
When the customers go to create a protection group that includes Hyper-V protection, they get an error message (ID: 31313) that you need to install the patch from KB975354. The problem is when installing this hotfix, it said “the update is not applicable to your computer”, then it is stuck and the users are unable to setup the backup for the Hyper-V guest VMs.
But the KB975354 is included in Service Pack 1.
Resolution:
The workaround is to fudge the DB, let DPM believes the windows 2008 R2 hotfix has been applied:
Run the below SQL proc by opening SQL Enterprise Manager 2008 and create a new query. Put the FQDN of the DPM server in the query where specified.
use dpmdb
Update tbl_am_installedagent
Set ServerAttributes = 31
Where deleted = 0 and serverid in (select Serverid from
tbl_am_server where serverName = ‘RELACE_FQDN_HERE’)
After running this proc, try creating the PG. Note that this field will be reverted back again by the 30 min refresh job, but should not affect protection for data sources already
being protected.
More information:
Recently some customers reported then got event 315 with error 2114 on every system startup. The printers and the system both work fine. The only problem is the event with error when the system starts up each time.
The detailed log is similar as following:
Log Name: Microsoft-Windows-PrintService/Admin
Source: Microsoft-Windows-PrintService
Date: 6/10/2011 4:47:13 PM
Event ID: 315
Task Category: Sharing a printer
Level: Error
Keywords: Classic Spooler Event,Printer
User: SYSTEM
Computer: BobbyC-PC
Description:
The print spooler failed to share printer HP Photosmart C7200 series BT with shared resource name HP Photosmart C7200 series. Error 2114. The printer cannot be used by others on the network.
Event Xml:
< Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
<EventID>315</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>30</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000820</Keywords>
<TimeCreated SystemTime="2011-06-10T20:47:13.118441500Z" />
<EventRecordID>12</EventRecordID>
<Correlation />
<Execution ProcessID="1612" ThreadID="1568" />
<Channel>Microsoft-Windows-PrintService/Admin</Channel>
<Computer>BobbyC-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<ShareFailed xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
<Param1>2114</Param1>
<Param2>HP Photosmart C7200 series BT</Param2>
<Param3>HP Photosmart C7200 series</Param3>
</ShareFailed>
</UserData>
< /Event>
Root cause:
The spooler just uses the Server Service for sharing the printers. If the server service has not fully initialized when the spooler initializes and wants to share the printers, the error will be logged.
Resolution:
Check the server service and make sure there are no dependent services that have been changed from default settings.
In addition, make sure the printer driver is up to date.
More information:
I know that Lexmark has used DCOM in the past for monitor software and had issues. If you have a bunch of Lexmark devices, I'd check for DCOM errors (no clue if these are in the System event logs any more) and also verify if the Lexmark devices are using monitor software.
Symptom:
Sometimes you may be unable to upgrade Virtual PC Integration Components with error “Setup Interrupted”.
Resolution:
In most of cases, the Kernel mode driver framework files wdf01000.sys and wdfldr.sys may be the cause of this issue from the following workaround:
1. Unistall Virtual PC Components
2. Remove the device that is unrecogonized from the device manager
3. Rename the following 2 files
C:\WINDOWS\system32\DRIVERS\wdf01000.sys and
C:\WINDOWS\system32\DRIVERS\wdfldr.sys
4. Restart the system
5. Install the Integration components
6. When the hardware wizard comes, select to manully to install, enter the path in the first option - C:\Program Files\Virtual PC Integration Components and click next. it should recogonize the unrecogonized device
7. Restart and enable the Integration features