Tag: Windows Server 2003

Error: IIS6 Error EventID 1059 and 1021

Just a had a problem with an application pool which always crashed after start. The application pool worked some days ago without any problems. After watching den System Eventlog I got the Error with Event ID 1059 and a Warning with Event ID 1021.
I had this problem on a Windows Server 2003 SP2 with all the latest patches
EventID 1059
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1059
Date: 27.05.2011
Time: 11:49:31
User: N/A
Computer: WEB-WIN
Description:
A failure was encountered while launching the process serving application pool 'www.domain.ch'. The application pool has been disabled.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

EventID 1021
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1021
Date: 27.05.2011
Time: 11:50:01
User: N/A
Computer: WEB-WIN
Description:
The identity of application pool, 'www.domain.ch' is invalid. If it remains invalid when the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2e 05 07 80 ...€

The Solution for this problem is very simple. Just reset the password of the specific IUSR and don’t forget to reset the password for the application pool identity.


Error: Unable to get the private bytes memory limit for the W3WP process

Error

==================
Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: None
Event ID: 1093
Date: 13.01.2011
Time: 11:11:50
User: N/A
Computer: Server01

Description:

Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error: 0x80070005

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
==================

Environment

  • Windows Server 2003
  • IIS 6
  • .NET 2.0 and 1.1

Summary

This Error is caused by the a know issue with permissions of the IIS metabase. The metabse ACL’s do not include the IIS_WPG group on the W3SVC/AppPools part in the metabase.

Solution

  • Download metaacl.vbs
  • Run the following command:
    cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE

More Information



Install and configure IPv6 on Windows Server 2003

On Microsoft Windows Server 2003 there is no GUI to configure IPv6. So this article should show you how to configure IPv6 on a Windows Server 2003.

  1. Install the IPv6 Protocol in the Network Adapter Properties or Control Panel
  2. Open the console
  3. Type “netsh” this is a command line program to configure network adapters
  4. Here are some demo configurations

int ipv6
reset
add dns interface=”<Interface Name>” address=<IPv6 primary DNS IP Address>
add dns interface=”<Interface Name>” address=<IPv6 secondary DNS IP Address>
add route prefix=::/0 interface=”<Interface Name>” metric=0 nexthop=<IPv6 Gateway IP Address>
add address interface=”<Interface Name>” address=<IPv6 IP Address>

int ipv6
reset
add dns interface=”Local Area Connection” address=fec0:0:0:0:ffff::1
add dns interface=”Local Area Connection” address=fec0:0:0:0:ffff::2
add route prefix=::/0 interface=”Local Area Connection”metric=0 nexthop=fe80::1
add address interface=”Local Area Connection” address=fe80::2

int ipv6
reset
add dns “Local Area Connection” fec0:0:0:0:ffff::1
add dns “Local Area Connection” fec0:0:0:0:ffff::2
add route ::/0 “Local Area Connection” fe80::1
add address”Local Area Connection” fe80::2



Pagefile size limits on Windows Server 2003

Some moths ago I posted a Blogpost called “Pagefile size bigger than 4095MB on Windows Server 2003“. In this post I wrote about the pagefile size limit of 4096MB. Today I got a comment on this post which shows another solution for this.

If you use the /PAE (Wikipedia Link: Physical Address Extension) switch, the pagefile is not limited to 4096MB anymore. Using the PAE switch limits the pagefile to 16TB, this should be enough for the most Windows Server 2003 32-bit systems. If you don’t use PAE the limit of the Pagefile remains 4GB.

By the way, Windows Server 2003 x64 can also have pagefiles up to 16TB and Windows Server 2003 for IA64 systems can have pagefiles up to 32TB. And for all versions, Windows Server 2003 supports up to 16 pagefiles.

For more information on memory limits in Windows Server 2003 check out this TechNet Blog post.

Thank goes to Ethan Anderson for giving me this information.



Pagefile size bigger than 4095MB on Windows Server 2003

UPDATE: If you can use PAE on your Windows Server 2003 you should check out this post: Pagefile size limits on Windows Server 2003

The pagefile size on Windows Server 2003 x86 and other Windows x86 platforms is limited to 4095 MB per pagefile. But a lot of Windows Server 2003 systems already have 4GB RAM and are using PAE (Physical Address Extension) to use them. So it would be useful to create more than 4 GB pagefiles.

Microsofts solution for this is to create multiple pagefiles. You can now create multiple pagefiles on different partitions. If you don’t have enough partitions or you just have one, you can create multiple pagefile in different folders by using the Windows Registry.

Pagefiles

  1. Create the folders on the drive where the pagefiles should be located. For example, C:\Pagefile1, C:\Pagefile2, and C:\Pagefile3.
  2. Open regedit.exe
  3. I would recommend to create a backup of the registry
  4. locate this key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
  5. Edit the value “PagingFiles”
  6. Remove the existing values and add the following values:
    C:\Pagefile1\pagefile.sys 4096 4096
    C:\Pagefile2\pagefile.sys 4096 4096
    C:\Pagefile3\pagefile.sys 4096 4096
  7. Save this

Note: It’s still recommended to have the Pagefiles on the same partition as the system

You can get more information in this Microsoft Knowledge Base entry: How to overcome the 4,095 MB paging file size limit in Windows

How to do this with Powershell: Powershell: Changing registry key value



Solved: Cannot download File from IIS6 FTP

Today we a ticket which was escalated by the second level support to the engineering. A customer could not download, remove or rename the file via FTP. The Hosting is running on a Windows Server 2003 R2 with IIS6. After checking the file on the filesystem I saw that the filename had a space in before.

Normalfilename:

“filename.html”

Wrongfilename:

” filename.html”

You cannot really name a file like that with a windows machine. But Linux and Unix systems like Mac OS X allow this.

After renaming the file to a normal Windows filename, the customer you download the file again.

Btw you can simple rename the file with powershell

Rename-Item " filename.html" "newfilename.html"



Active Directory Schema Versions

The list of Active Directory Schema versions:

  • Windows 2000 RTM with all Service packs = Schema version 13
  • Windows Server 2003 RTM with all Service packs = Schema version 30
  • Windows Server 2003 R2 RTM with all Service packs = Schema version 31
  • Windows Server 2008 RTM with all Service packs = Schema version 44
  • Windows Server 2008 R2 RTM with all Service packs = Schema version 47

Check the schema version in the Registry:

HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\<Schema Version>

Check the schema version with dsquery:

dsquery * CN=Schema,CN=Configuration,DC=Root-Domäne -Scope Base -attr objectVersion