12.Dec.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
This part came while working in Windows server 2008 R2 edition. Features page in Server manager started throwing up this error with hexadecimal code 0x800706BE. Notice there could be several reasons to this issue, hence the parts (-I) to this blog. If ever I found another cause, I would come up with next part (II). For now, lets stick to what happened on my box.
Every time I clicked on Server manager Features page, it gave ‘Error’. click on ‘Error details’ would bring up a dialog box shown in the screenshot below. The error reads:
Unexpected error refreshing Server Manager: The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
Click on the image enlarge
Troubleshooting:
Download and install Microsoft System Update Readiness Tool(CheckSUR) for Windows 2008 R2 (As mentioned in beginning I error came on Windows 2008 R2 but you can try on other OS as well)
CheckSUR is 315MB tool to download, once you install it, it generates a CheckSUR.LOG log file at %windir%\Logs\CBS\ location.
In my case, I log read:
----------------------------------------------------------------------------------------------------
Unavailable repair files:
servicing\packages\Package_for_KB2564958_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB2564958_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
(w) Unable to get system disk properties 0x0000045D IOCTL_STORAGE_QUERY_PROPERTY Disk Cache
--------------------------------------------------------------------------------------------------
The log file show that the one of the file related to KB 2564958 is either corrupt or missing, most likely the latter one. So, the next to download update KB 2564958 from Microsoft support site.
Download the update from http://support.microsoft.com/kb/2564958 site. When I downloaded and tried to install, it gave me another error at installation with code: 0x80240009
Extracted the fix KB2564958 by following command: EXPAND Windows6.1-KB2564958-x64.msu –F:* C:\Temp
It will extract the CAB files. Identify the files mentioned in the log files and copy them over to the location mentioned in the log file, that is: %Windir%\Servicing\Packages\
Started the Server Manager Features page again, this time it came up just fine!
Hope this blog is informative, I would write another part soon.
Write me your feedback at inbox at gusac.net
11.Dec.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
Just had an issue when I noticed that Windows Automatic updates service was missing in Service Console. The service registry was also missing:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\wuauserv
One of solution known to is to reinstall the component from its configuration file. The command used:
%windir%\System32\rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %windir%\inf\au.inf
Hope it helps!
11.Dec.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
Issue: A RemoteApp application does not retain settings when users have roaming profile.
To reproduce the issue: Start the application, make changes and exit out. Next time you start it, it will not retain the settings.
Solution: Remoteapp default setting is to disconnect the session whenever a user closes out the application by click on the X at top right corner. The best thing is to exit the Remoteapp program from its menu (Ex: File > Exit)
Or, Group Policy can be configured to change the default behaviour of Remoteapp.
Enabled the following policy on your Windows 2008 Terminal Server:
Computer configuration > Administrative templates > Windows component > Terminal
Services > Terminal server > Session Time Limit = ‘Immediately’
Set the value to 'Immediately'
Explanation:
This policy setting allows you to specify how long a user's RemoteApp session will remain in a disconnected state before the session is logged off from the terminal server. By default, if a user closes a RemoteApp program, the session is disconnected from the terminal server. If you enable this policy setting, when a user closes a RemoteApp program, the RemoteApp session will remain in a disconnected state until the time limit that you specify is reached. When the time limit specified is reached, the RemoteApp session will be logged off from the terminal server. If the user starts a RemoteApp program before the time limit is reached, the user will reconnect to the disconnected session on the terminal server.
If you disable or do not configure this policy setting, when a user closes a RemoteApp program, the session will be disconnected from the terminal server.
11.Dec.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
In Windows 2008 R2 server, Shell Hardware Detection service stops starts and stops automatically on its own gracefully. If you check the event logs, it registers the information logs showing no issues.
Reason:
In Windows 2008 R2 server system, the behavior of this service was changed to to stop automatically after sometime a user logs off and starts when a users logs in. This was done to prevent minimize surface attacks. This is by design.
18.Nov.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
There could be several reason for a printer to show the status as OFFLINE. But the most common that I have come around is due to the SNMP option in its properties.
It is quite possible that printer does not support SNMP or SNMP is not enable/installed on the print server and yet SNMP option is enabled. Now due to this the print server tries to communicate with print device over SNMP. The server never gets the response and shows the printer status as offline.
The simple solution is to disable the SNMP feature in printer properties. It does not have any affect on printing functionality of the printer.
Open Printer and Faxes or Devices and Printers
Right click on the problem printer and go to Printer properties
In Printer properties window, go to the Ports tab
On Ports tab, click on the button that says Configure Port…
In the new page, clear the checkbox that says SNMP Status Enabled and click OK to exit.
Refresh the page, it should show status as Read now.
7.Oct.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
Here are few of the issues related to service failures on Windows 2008 R2 servers. The most likely solutions and methods are provided below.
1. Diagnostic Policy Service fails with Access Denied
Solution:
· Navigate to the following key: HKLM\System\CurrentControlSet\Control\WDI\Config
· Grant full permission to the ‘NT Service\DPS’ account on the key.
Note: This is a Local account and not on domain. You need to change the location from domain to local while searching for the accounts.
2. Firewall service fail to start with Error Code 5
Run Procmon.exe and you would notice access denied logs on the following keys:
HKLM\System\CurrentControlSet\Services\SharedAccess\Epoch
HKLM\System\CurrentControlSet\Services\SharedAccess\Epoch2
Solution:
· Navigate to the keys and grant full permission to the following accounts:
NT Service\MPSSVC and NT Authority\Network Service
Note: These are Local accounts and not on domain. You need to change the location from domain to local while searching for the accounts.
· Start the Firewall Service. It should start successfully.
3. Windows Event Log service fail to start with Access Denied error
Again, Procmon.exe shows that we have access denied on C:\Windows\System32\WinEvt folder.
Solution:
· Navigate to the above mention folder and edit permissions
· Grant full permission to the local account NT Service\EventLog
Note: These are Local accounts and not on domain. You need to change the location from domain to local while searching for the accounts.
4. Multiple Services fail to start with dependency failure error
or Access denied while starting Base Filtering Service
Multiple Services on Windows 2008 R2 fail to start with dependency failure error. The following services fail to start:
IPsec Policy Agent (PolicyAgent) Windows Firewall IKE and AuthIP IPsec Keying Modules Internet Connection Sharing (ICS) Routing and Remote Access
Reason: These services are directly or indirectly dependent on Base Filterning Agent service, which is failing with Access Denied Error. We need to fix Base Filtering Agent first.
Solution:
· Navigate to the following registry key: HKLM\System\CurrentControlSet\Services\BFE
· Grant full permission to the NT Service\BFE account on the above mentioned key.
· Also ensure that the following subkey is inheriting permission for BFE account:
HKLM\System\CurrentControlSet\Services\BFE\Parameters\Policy\Persistent
22.Sep.2011 |
by Gusac |
Filed in: Articles, Tutorials
Overview of Fallback printer driver policy and how it is configured [More]
19.Sep.2011 |
by Gusac |
Filed in: Articles, Troubleshoot
Although, Performance Logs and Alerts service aka ‘Perfmon service’ is an on-demand service, meaning it starts when it is needed; you would get a generic message whenever you try to start it. The message simply says that the service started and stopped because it has nothing to do.
However, you do get error while starting Perfmon service, like I did. Here is the error description:
The Performance Logs and Alerts service terminated with service-specific error 2003 (0x7D3).
If you go ahead and use ERR.exe utility to understand the the Hex code 0x7D3, you would get the description: ERROR_METAFILE_NOT_SUPPORTED
The solution: Incorrect permission on the registry.
Registry: HKLM\system\CCS\Services\SysmonLog\Log Queries.
Simply add the Network Service account on the above mentioned registry location and give write access.
Try again, service should start or at least give you the generic message.
18.Sep.2011 |
by Gusac |
Filed in: Articles, Tutorials
Recently Microsoft released pre-beta version of Windows 8 for developers. Following are the
The pre-beta version was installed on a virtual machine which was used for Windows 7. Below are the minimum system requirements for installing Windows 8
System Requirements
Windows Developer Preview works great on the same hardware that powers Windows Vista and Windows 7:
1 gigahertz (GHz) or faster 32-bit (x86) or 64-bit (x64) processor
1 gigabyte (GB) RAM (32-bit) or 2 GB RAM (64-bit)
16 GB available hard disk space (32-bit) or 20 GB (64-bit)
DirectX 9 graphics device with WDDM 1.0 or higher driver
Taking advantage of touch input requires a screen that supports multi-touch
To run Metro style Apps, you need a screen resolution of 1024 X 768 or greater
Screenshot:
15.Sep.2011 |
by Gusac |
Filed in: Articles, Tutorials
Terminal Server Easy Print Overview [More]
