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

• http://support.microsoft.com/?id=267904
• http://blogs.msdn.com/b/carloc/archive/2006/09/20/unable-to-get-the-private-bytes-memory-limit-for-w3wp-exe-process.aspx
• http://support.microsoft.com/?id=812614
• http://forums.iis.net/t/1057159.aspx

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

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.

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.

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

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"

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

You can simply add Silverlight support to your IIS6 webserver running on Windows Server 2003.

To enable IIS 6.0 in Windows Server 2003 or IIS7 in Windows Vista RTM with the appropriate MIME Types, add:

• .xap     application/x-silverlight-app
• .xaml    application/xaml+xml
• .xbap    application/x-ms-xbap

Adding MIME Types by a simple VB script:

• Here is a VBS script you could run to enable each of these types:


Const ADS_PROPERTY_UPDATE = 2
'
if WScript.Arguments.Count < 2 then
WScript.Echo "Usage: " + WScript.ScriptName + " extension mimetype"
WScript.Quit
end if
'
'Get the mimemap object.
Set MimeMapObj = GetObject("IIS://LocalHost/MimeMap")
'
'Get the mappings from the MimeMap property.
aMimeMap = MimeMapObj.GetEx("MimeMap")
'
' Add a new mapping.
i = UBound(aMimeMap) + 1
Redim Preserve aMimeMap(i)
Set aMimeMap(i) = CreateObject("MimeMap")
aMimeMap(i).Extension = WScript.Arguments(0)
aMimeMap(i).MimeType = WScript.Arguments(1)
MimeMapObj.PutEx ADS_PROPERTY_UPDATE, "MimeMap", aMimeMap
MimeMapObj.SetInfo
'
WScript.Echo "MimeMap successfully added: "
WScript.Echo " Extension: " + WScript.Arguments(0)
WScript.Echo " Type: " + WScript.Arguments(1)

• If you copy and paste the code above into a VBS file and save it as ADDMIMETYPE.VBS the syntax to add each type would be:

ADDMIMETYPE.VBS .xap application/x-silverlight-app ADDMIMETYPE.VBS .xaml application/xaml+xmlADDMIMETYPE.VBS .xbap application/x-ms-xbap

or you could add it very simple over the IIS Manager.

Tonight I did a bigger P2V (physical 2 virtual) migration. I virtualized an older Windows Server 2003 SP1 with MS SQL Server 2005 and WSS 3.0. This can be used as a step by step how-to guide.

• First I created a Image of the old server with Symantec Backup Exec System Recovery 2010, this could be done online. I just stopped all the Sharepoint, SQL and Web Services so that no new data could be written in the time I created this Image.
• After I moved this Image to the Microsoft Hyper-V Host Server, I started to convert the v2i Image with Symantec Backup Exec System Recovery 2010 to a Microsoft VHD.
• I created a new Virtual Machine on the Hyper-V Server and added this existing VHD. (Important here: I tried to create the same Hardware environment for the VM which I had as physical Hardware before. (Dual Core with 2048MB memory) So I had basically no problem to start the Virtual Machine.
• Now its time to install the Hyper-v integration components (the VM Drivers) which can only be installed on Windows Server 2003 with SP2 or later. I turned off the Virtual Machine again and attached the VHD File offline on my Hyper-v Server, so I had file access to the Virtual Hard Disk. I simply added the Servicepack 2 file to the root of the VHD.
• After unmounting the VHD, I started my Virtual Machine again and installed the Servicepack 2 and the Hyper-v Integration components.
• Now I added more Hardware to the Virtual Machine (Quad-Core and 4GB memory). I also change the Legacy Network Adapters to normal Network Adapters (higher Network performance)

The performance of the new Hyper-v is just pretty impressive.

Today I got a error message from our monitoring that Rsync Service on one of our server doesn’t run. Reinstalling the service does not solve the problem. I could start the service but after some seconds the service stopped again.

The Event Log shows the following information:

==============================

Event Type: Information

Event Source: RsyncServer

Event Category: None

Event ID: 0

Date: 22.12.2009

Time: 08:30:52

User: WEB-WIN-xxx-xxx\SvcCWRSYNC

Computer: WEB-WIN-xxx-xxx

Description:

The description for Event ID ( 0 ) in Source ( RsyncServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: RsyncServer: PID 1856: `RsyncServer’ service stopped, exit status: 11.

==============================