Widget Tag cloud not found.

Unable to cast object of type 'ASP.widgets_tag_cloud_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget RecentPosts not found.

Unable to cast object of type 'ASP.widgets_recentposts_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget Search not found.

Unable to cast object of type 'ASP.widgets_search_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Widget Visitor info not found.

Unable to cast object of type 'ASP.widgets_visitor_info_widget_ascx' to type 'App_Code.Controls.WidgetBase'.X

Shell Hardware Detection Service stops automatically in Windows 2008 R2 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.

Troubleshooting for Services issue on Windows 2008 R2

7.Oct.2011 | by Gusac | Filed in: Articles

  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.   Additionally, If the Firewall console still give you error code 0x5d, follow these steps: · 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 following registry key: HKLM\System\CurrentControlSet\Services\MPSSvc · Grant full permission to the local account NT Service\MPSSvc 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   5. Network Location Awareness service fail to start with Access Denied error Solution: · Navigate to the following registry key: HKLM\System\CurrentControlSet\Services\NlaSvc · Grant full permission to the NT Service\NlaSvc account on the above mentioned key. · Also ensure that the following subkey is inheriting permission for BFE account: HKLM\System\CurrentControlSet\Services\NlaSvc

Base Filtering Engine service fails to start with error code 5 along with other services

28.Jul.2011 | by Gusac | Filed in: Articles, Troubleshoot

Symptoms: On Windows 2008 R2 server, Base Filtering Engine service fails to start and throws error code 5. Following services which are directly or indirectly dependent on BFE also fail. They are: IPsec Policy Agent (PolicyAgent) Windows Firewall IKE and AuthIP IPsec Keying Modules Internet Connection Sharing (ICS) Routing and Remote Access You cannot ping the server and when you ping from inside, it gives error Transmit Failed     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 inherits permission for BFE account: \BFE\Parameters\Policy\Persistent

How file and folder permissions are handled while moving or copying files on Windows 2008 R2 and Windows 7

8.Apr.2011 | by Gusac | Filed in: Articles, Tutorials

There is just some logic with which Windows handles the file level permissions while moving or copying files from one location to another. Depending on the destination, be it the parent folder, same volume or a different one, the Access control Entries (ACE) are added or replaced from the file Access Control List (ACL) The way Windows 7 or Windows 2008 R2 handles the permissions while move/copy operation is different from previous version of Windows. This article talks only about how Windows 7 and Windows 2008 R2 server handles The table below has the source and destination folder with the type of operation performed. The result is provided against each operation Source Destination Operation Result         Child Folder Parent Folder Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Chid Folder Parent Folder Move Explicit permissions are retained only and destination folder permissions are inherited. Same Volume       Same Volume, Folder A Same Volume, Folder B Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Same Volume, Folder A Same Volume, Folder B Move All implicit and explicit permissions are retained. Destination parent folder permissions are NOT inherited. Different Volume       Folder A Folder B Copy Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited. Folder A Folder B Move Both explicit and implicit Permissions are NOT retained. Permissions of destination parent folder are inherited.

Overview of Printer Driver Isolation

23.Mar.2011 | by Gusac | Filed in: Articles, Tutorials

Print spooler crash isn't a rare phenomenon in IT Administration world. It is something that leaves an admin scratching his head, figuring out what is causing it. Most of the time it's due to some faulty printer driver and bigger the environment, harder it is to identify the culprit driver. But that's going to be the thing of past now. With Windows 2008 R2 and Windows 7 comes the Printer Driver Isolation. As the name suggests, Printer Driver Isolation or PDI isolate the printer drivers files into a different process than Print spooler (spoolsv.exe). The isolated printer drivers are not loaded in the process space of spoolsv.exe but instead a different process. So, if any problem that occurs in the faulty drivers will cause the process they are loading in to fail instead of spoolsv.exe, hence preventing the production down time for Print servers. The process that host the isolated printer driver files is PrintIsolationHost.exe. This process host the printer drivers which are set to be run isolated. If anything goes wrong with these drivers, they will cause PrintIsolationHost.exe to crash and not spoolsv.exe. The purpose of the driver isolation feature is to prevent print drivers that fail or behave badly from adversely affecting the print spooler process There are three modes of Printer Driver Isolation: None - Printer drivers are loaded in the spooler process, just like before. Shared - Printer drivers set to run in a single shared instance of PrintIsolationHost.exe process, separated from the spooler process. This is the default mode. Isolated - Each Printer driver is set to run in its own separate instance of PrintIsolationHost.exe process. To check if Printer Driver support PDI: Navigate to the following registry location: HKLM\SYSTEM\CurrentControlSet\Control\Print\Environments\<environment>\Drivers\Version-3\<driver>\PrinterDriverAttributes Possible values: 0: Printer driver does not support PDI 2: Printer driver supports PDI If the value is missing, it defaults to 0, that is, the driver does not support PDI   How to change the Printer Driver Isolation mode There are three ways to determine Isolation mode for Printer drivers: INF files associated with the printer driver Print Management Console (PMC) Group Policy   INF files associated with the printer driver The printer driver inf files advertises whether the driver supports PDI or not. The inf files contains a the keyword DriverIsolation to indicate its support for the PDI. As mentioned above, value 0 indicates that the driver does not support PDI and the value 1 indicates it supports it. So, in an inf file, it should look like: DriverIsolation=0 DriverIsolation=2 Again, If the keyword is not there then it defaults to 0       Print Management Console (PMC) The print management console or PMC lets you manage the driver isolation easily. If you open the PMC and go to the Drivers for the print server you want to manage, it will list all the print drivers installed on that server along with their Isolation state. Below is the screenshot for your reference: To change the Driver isolation, right click on the printer driver and select the option 'Set Driver Isolation. The drop down menu will all the available options. Please note: The System Default option is the setting defined in the driver itself by default or by group policy. If group policy ‘Execute Print drivers in isolated processes’ is Disabled, then you cannot change the isolation mode. Registry value for PDI settings: The driver names, for which PDI mode was set explictly, are stored in registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\ [PrintDriverIsolationGroups] The value data is stored in a format to differentiate the Isolation state. the format is: <None>\<None>\\<Shared>\<Shared>\\<Isolated>\<Isolated> The three groups (None, Shared & Isolated) are separated by double slashes ‘\\’ and within each group, drivers are separated by single slash ‘\’ Please note: For drivers which have Driver Isolation state as System Default, will not be listed in the registry. The registry contains names for the drivers for which PDI mode was change explicitly. If you do not have any driver in one group then it will be left as it is but double slashes \\ would still be there.   Group Policy There are two group policies for PDI ad they can be found under: Computer Configuration\Administrative Templates\Printers. The Group policies are: Execute print drivers in isolated processes Override print driver execution compatibility setting reported by print driver Policy: Execute print drivers in isolate processes: This policy setting determines whether the print spooler will execute print drivers in an isolated or separate process. When print drivers are loaded in an isolated process (or isolated processes), a print driver failure will not cause the print spooler service to fail. If you enable or do not configure this policy setting, the print spooler will execute print drivers in an isolated process by default. If you disable this policy setting, the print spooler will execute print drivers in the print spooler process. Notes: -Other system or driver policy settings may alter the process in which a print driver is executed. -This policy setting applies only to print drivers loaded by the print spooler. Print drivers loaded by applications are not affected. -This policy setting takes effect without restarting the print spooler service.   Policy: Override print driver execution compatibility setting reported by print driver: This policy setting determines whether the print spooler will override the Driver Isolation compatibility reported by the print driver. This enables executing print drivers in an isolated process, even if the driver does not report compatibility. If you enable this policy setting, the print spooler will ignore the Driver Isolation compatibility flag value reported by the print driver. If you disable or do not configure this policy setting, the print spooler will use the Driver Isolation compatibility flag value reported by the print driver. Notes: -Other system or driver policy settings may alter the process in which a print driver is executed. -This policy setting applies only to print drivers loaded by the print spooler. Print drivers loaded by applications are not affected. -This policy setting takes effect without restarting the print spooler service.

How to turn Windows 7 or Windows 2008 R2 as WiFi Access point

4.Aug.2010 | by Gusac | Filed in: Articles, Tutorials

How to make Windows 7 or Windows server 2008 R2 computer system as a WiFi access point or hotspot for other wireless devices. [More]

How to install Remote and Routing Service (RRAS) on Windows Server 2008

19.Sep.2009 | by Gusac | Filed in: Articles, Tutorials

How to install Remote and Routing Service (RRAS) on Windows Server 2008 [More]