Computer stops responding when it is resumed from standby mode

Operating system

Windows Server 2003

Problem

When we resume the computer from standby mode, the computer may stop responding. Sometimes it may also see the "Applying Personal Settings" message box for up to an hour before the desktop appears.
Typically, when you resume a Windows Server 2003-based computer from standby, the computer is locked. Therefore, you must log on to the computer before you can access the desktop. However, when this problem occurs, the computer is not locked, and the Windows Server 2003 logon screen does not appear.

Solution

We found the following event messages may be logged in the application event log on the domain controller after restart the Windows Server 2003-based computer:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted. For more information, see Help and Support Center at http://support.microsoft.com.
or
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ).

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Description: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine. For more information, see Help and Support Center at http://support.microsoft.com.

When we turn on user environment (Userenv) logging, domain Distributed File System (DFS) services may not work after the computer resumes from standby. Additionally, you may receive messages that resemble the following messages in the %SystemRoot%\Debug\UserMode\Userenv.log file.
According to Microsoft this problem may occur if the Winlogon process tries to process group policies before other components are running. However, there are several other scenarios that may cause this problem. Make sure that the following components are started and that they are configured correctly Netlogon and DFS services are started.

• Domain controllers have the read and apply rights to the Domain Controllers Policy.
• NTFS file system permissions and share permissions are set correctly on the Sysvol share.
• DNS entries are correct for the domain controllers.

Method 1:

Microsoft released one Fix Microsoft Fix it 50615 for the above problem. The download link available from the below

http://go.microsoft.com/?linkid=9763079

Method 2:

Update latest Service Pack for the server operating system.

Method 3:

Open the registry editor and locate the below path

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Create the DWORD value If the WaitForNetwork, if the value is not exists. Set the value to 1.

Close the registry editor and restart the computer

Error message 0x80070057 when backup files in windows

Operating system

Windows 7

Scenario

When we trying to backup files using the windows inbuilt backup utility called Windows Backup, the backup process fails and showing the below error

An internal error has occurred: The parameter is incorrect: (0x80070057).

Solution

Method 1:

Microsoft released the Fixit Microsoft Fix it 50719 for the above issue. The same will be available from the below link

http://go.microsoft.com/?linkid=9777176

Method 2:

Change the decimal symbol setting

This problem can occur if the decimal symbol is not set to '.' (dot). This is common in languages and locales other than English (United States), such as German (Germany).
To change the decimal symbol setting, follow these steps:

1. Open Control Panel, click Clock, Language, and Region, and then click Region and Language.
2. Click the Formats tab, and then click Additional settings.
3. In the Decimal symbol field, type . (dot), and then click OK two times.
4. Restart the computer.

Method 3:

Open the registry editor by typing the regedit.exe command and locate the below path.

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\System.

Create a DWORD value CopyFileBufferedSynchronousIo and modify the value to 1.Close the registry editor and reboot the computer.

Less Disk Space issue in windows vista due to increase size in WINSXS folder

Operating system:

Windows Vista SP1&SP2

Solution:

1.Check Pchealth folder exceeding its size.
2.Checked program files and users folders.
But in windows folder, there is a folder named  WINSXS showing couple of GB size.

SxS means Side-by-side technology and it is a solution integrated in recent Windows versions by Microsoft in a attempt to reduce DLL hell. The problem with this solution is that the system keeps all versions of installed components in order to be able to serve them to asking application. As a downside, you will notice that this folder grows up very quickly and this can quickly became a very serious issue for your computers

Common sizes for the WinSxS folder:

- Windows 2003 : WinSXS = 25 MB / 05 GB (total Windows)
- Windows 2008 : WinSXS = 05 GB / 10 GB (total Windows)

The only safe way to reduce the size of the WinSxS folder on the disk is to remove the packages that installed the original components. This can be achieved by uninstalling superseded versions of packages.

On Windows Vista, Service Pack 1 contains VSP1CLN.EXE. Running VSP1CLN.EXE will make the Service Pack package permanent and not removable.

The tool is automatically installed as part of the SP1 upgrade, and you can find it under %windir%\system32\vsp1cln.​exe.

On Windows Vista, after Windows SP2 you can use COMPCLN.EXE to clean up WinSxS folder. This tool is installed as part of the SP2 upgrade, and you’ll find it under \%windir%\system32\compcln.​exe.

As with vsp1cln.exe, executing compcln.exe will make SP2 not removable.

Other third part solutions to reduce WinSxS size are:

WINSXSLITE

VLITE

VOPTIMIZER

if your problem is with %windir%\winsxs\ManifestCache\ growing too much, you can refer to this procedure to remove the files under the %windir%\winsxs\ManifestCache\ and to release some disk space that the WinSXS folder is taking:

Net stop trustedinstaller
Takeown /f %windir%\winsxs\ManifestCache\​*
Icacls %windir%\winsxs\ManifestCache\​* /GRANT administrators:F
Del /q %windir%\winsxs\ManifestCache\​*

Server hanging at Applying Computer Settings stage of the logon process

Operating system

Windows server 2008,
Windows 7,
Windows Vista

Problem

When we start a computer it stops responding and appears to hang at the "Applying User Settings" or "Applying Computer Settings" stage of the logon process.

Solution

As per the Microsoft articles this issue typically occurs after install a server certificate and then configure Secure Sockets Layer (SSL) on the computer. For example, we install a SSL server certificate in Internet Information Services (IIS) 7.0 and then enable HTTPS on your website to use the certificate.

This issue occurs because of a deadlock in the Service Control Manager database. The Service Control Manager tries to start the HTTP.sys service and then puts a lock in place in the Service Control Manager database. Then, HTTP.sys makes a call that requires Cryptographic Services during startup. Then, a request is sent to start Cryptographic Services. However, a lock is already in place in the Service Control Manager database. Therefore, a deadlock occurs.

Method1

Microsoft released a Hot fix for this issue it is available from the below link http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2379016&kbln=en-us

Method 2

To resolve this issue, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys depend on crytosvc service to be started first.

Open the registry editor by typing the command regedit.exe with administrative privilges.

Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP

On the Edit menu, point to New, and then click Multi-string Value. Type DependOnService, and then press ENTER. Modify the value by typing the CRYPTSVC, and then click OK. Exit Registry Editor.

Restart the computer.

Method 3:

Microsoft Fixit team released the fix Microsoft Fix it 50564 for solving this issue.

How to verify Global Catalog Server Readiness in Windows server 2008

          

Operating System

Windows server 2008, Windows Server 2003.

Scenario

After enabled the global catalog role on a domains controller, we might want to ensure that it is properly functioning as a global catalog server before clients and services start querying the global

catalog partition on this server.

 How To

When a global catalog server has satisfied replication requirements, the isGlobalCatalogReady rootDSE attribute is set to TRUE and the global catalog is ready to serve clients.

To perform the following procedures you must be a member of the Domain Users group.

To verify global catalog server readiness by using LDP, perform the following steps:

1. Log on to a domain controller.

2. Click Start, click Run, type LDP, and click OK.

3. On the Connection menu, select Connect.

4. In the Connect box, type the name of the server whose global catalog readiness want to verify, as shown in Figure below

 

5. In the Port box, if 389 is not showing, type 389.

6. If the Connectionless box is selected, clear it and then click OK.

7. In the details pane, verify that the isGlobalCatalogReady attribute has a value

 of TRUE, as shown in Figure below.

 

Verify Global Catalog Server Readiness by using NLTest

To verify global catalog server readiness by using NLTest, perform the following steps:

1. Log on to a domain controller.

2. Click Start, and click Command Prompt.

3. In the Command Prompt window, type the following command:

nltest /server:servername /dsgetdc:domainname

 (where servername is the domain controller you want to validate global catalog readiness and domainname is the name of the domain to which the domain controller belongs).

4. Verify that GC is listed under the Flags section of the results, as shown in below figure.

 

Configuring TS Web Access in windows 2008 server

                       

Operating System

Windows server 2008

How To

Windows Server 2008 Terminal Services bundled with a service called TS Web Access. TS Web Access service  enables users to access a web page running on the system hosting the Terminal Server to obtain a list of desktops and remote applications which are available for remote access.

Here is the step by step to configure the TS Web Access in windows 2008 server.

Open the server manager by selecting the start/Administrative Tools. Open Roles Tab. On right pane select Add roles. Select the Terminal Service Role from the list.

 

Select next and continue. On next page select the Terminal server and TS Web Access services. Click next and continue with the default settings. TS Web Access requires a number of other roles, like IIS web server role. Click on the Add Role Services to ensure that these services are also installed. Click the Next button to review information about the services being installed. Click next to review the IIS services being installed. Click Next once again to move to the confirmation screen and click on Install to initiate the installation.

 

After restart open the Browser and follow the link

        http://systemID/ts

where the systemID is the IP address or system name of the Terminal server. On successful connection the browser will prompt for the user and password credentials..

Once entered, the TS Web Access page will appear, listing any remote applications available for access on the local system.

 To configure applications such that they can be launched from the Windows Server 2008 TS Web Access page they must first be installed for use with Terminal Services and then configured as RemoteApps.

Start -> All Programs -> Terminal Services -> TS Remote App Manager or by running remoteprograms.msc in a Run dialog or command prompt. Once launched, the manager will appear as follows.

To configure an application as a RemoteApp, begin by clicking on the Add RemoteApp Programs link in the Actions panel located in the top right hand corner of the TS RemoteApp Manager screen. This will display the RemoteApp wizard containing a list of currently installed applications. One or more applications may be selected from the list before pressing the Next button.

It is essential that any RemoteApps be configured for access via TS Web Access. To ensure this is the case, select the appropriate application from the list and click on the Properties button to open the RemoteApp Properties dialog as shown below. Within this dialog, make sure that the RemoteApp is available through TS Web Access box is checked.

 

Click OK to close the RemoteApp Properties dialog and then click Next in the wizard to proceed to the Review Settings screen and Finish to complete the configuration. Upon completion the applications will be listed under RemoteApp Programs s shown below.

With the RemoteApp applications configured they will now appear on the TS Web Access page ready to be invoked by a remote user..

 

When launched, these applications will appear within their own windows on the client desktop just as if they are locally installed applications

Transport service is getting failed in Exchange server 2007

Operating system

Microsoft Exchange server 2007 SP1
Windows server 2003 Standard Edition R2  64 bit with SP 2

Problem

While booting the exchange server error showing Exchange Application Error 17003. While starting the service manually the error coming Exchange Application Error 5000.
Event log 17003 and 5000 created as shown in below 

                                                                                     

  Solution

 Backup the current database files first
To repair the specified database, follow these steps:
 Verify that the Microsoft Exchange Transport service is stopped.

Run the Eseutil /P utility on the specified database.
The repair can take a long time on a large database. If the affected database is the message queue database, you can move the database files to another location, and then start the Microsoft Exchange Transport service to create a new message queue database. This lets you perform the database repair without any loss of functionality on the Hub Transport server or Edge Transport server. After the message queue database has been repaired, you can use any other HubTransport server or Edge Transport server to deliver the messages that are trapped inside the repaired database.
Start the Microsoft Exchange Transport service.
( If the Microsoft Exchange Transport Service still does not start because of database corruption errors, you must move or delete the specified database and allow a new copy of the database to be created)
Delete the specified database and the corresponding transaction logs. A new copy of the database and the transaction logs is created automatically. Use this option if you don't care about the contents of the specified database.
To delete the specified database and corresponding transaction logs, follow these steps:
Verify that the Microsoft Exchange Transport service is stopped.
Delete the specified database files and the corresponding transaction log files. The database files and the transaction log files are described in the following list:

Mail.que or IpFiltering.edb	The main database file
Trn.chk	The checkpoint file
Trn*.log	The transaction logs
Trnres*.jrs	The reserved transaction logs that serve as placeholders
Temp.edb	A sample database file that is used to verify the database schema. Although this is not a transaction log file, it is always kept with the transaction logs.

If the database files are not recoverable allow a new copy of the database to be created.