Why you want…you NEED to be a Microsoft Partner…because you get resources like this…




Issue 1:


Memory leak issues



Problem Symptom 1:


Memory leak & Allocated memory alert



Some of them are caused by the SQL memory processing mechanism:


Memory leak caused by the Lsass.exe process:

821008 Windows Server 2003-Based Computer Becomes Slow and Unresponsive

After – http://support.microsoft.com/?id=821008

829993 Memory Leak Occurs in the Lsass.exe Process on a Windows Server –



Other memory leak issues is most likely related to VSS (while be used with some 3rd party backup program, such as Veritas, Ultrabac.) What you expect to see in this kind of issue may be any of the following:


Poor and gradually declining system performance

Out-of-memory errors

VSS errors


If you do see the symptom listed above, I would suggest the following hotfixes be installed on the server, or you may want to apply SBS 2003 SP1 directly.


826751 Backup Program Causes Gradually Declining Performance –


838864 A backup or a restore operation of Exchange 2003 storage groups

fails – http://support.microsoft.com/?id=838864

867667 The Beremote.exe process uses up to 100 percent of CPU resources –


870973 A memory leak occurs in an application using the Volume Shadow Copy –


831112 You cannot import a transportable shadow volume in Windows Server 2003


833167 A Volume Shadow Copy Service (VSS) update package is available for –



After the SBS 2003 SP1 installation, you still receive the memory allocation alert to indicate that store.exe is using an abnormal amount of memory.

This is actually the same issue described in the following KB: ‘867628 Monitoring programs report that the Store.exe process consumes –



To completely fix this:

You can re-run the Configure Monitoring Wizard and it will also disable the store alert. Note that you need to choose ‘Reinstall Monitoring features’

when running MCW (Monitoring Configuration wizard or disable the alert manually from the Health Monitoring page.


Issue 2:


Slow Shutdown issues on Exchange 2003 (installed on a Windows 2003 DC)


Problem Symptom


When you shut down a Microsoft Windows Small Business Server 2003-based computer, the shutdown process takes longer than expected to finish.




The problem of slow shutdowns is not actually a SBS specific one. It exists for every server which is both a domain controller and an Exchange server.

When you shut down the Windows Small Business Server 2003-based computer, the Active Directory directory service shuts down at the same time that the

Microsoft Exchange Server services shut down. Therefore, Active Directory becomes unavailable when the Exchange Server services shut down. For

example, this problem causes Exchange Directory Service Access (DSAccess) searches to time out and to return errors. Additionally, the DSAccess

searches sleep and then restart several times. Therefore, the Exchange Server services that wait for the DSAccess searches to finish are delayed.




Apply SBS 2003 SP1, as mentioned in the KB article


or  If you don’t want to apply SBS 2003 SP1 currently, please get the Hotfix

887539 from CSS.

or Manually workaround this issue by either modifying the

WaitToKillServiceTimeout value


or scripting the Shutdown sequence



Issue #3 – Hot Issue


S2S PPTP VPN gets disconnected after SBS 2003 SP1 Premium (ISA 2004)



Problem Symptom


Site to Site (S2S) PPTP VPN connection gets disconnected after the SBS 2003 SP1 (ISA 2004) installation. The scenarios we’ve seen so far are listed


Linux VPN server <à SBS 2003

Linksys VPN ß> SBS 2003

Netopia VPN ß> SBS 2003

Watchguard ß> SBS 2003




The key things to zero in on are the GRE Call IDs (that control data flow) and whether the PPTP Echo Reques/Reply process over TCP port 1723 is working

(which keeps the connections connected). We encourage you to get a Netmon trace from the VPN server to try and figure out if there is GRE Call-ID

mapping going on upstream from the ISA server. It will turns out that the remote device is not following the RFC 2647. So we fail because ISA’s

pptpfltr.dll is being strict with RFC.




1) Don’t use the NAT module in the router. Get a .252 block address from their ISP that allows then to set up routing rather than use NAT. (This

should give you one IP address for the router, one for the ISA server and a network and broadcast address)

2) Contact the router vendor and get an updated firmware that fixes the NAT problem. (That is if one exist) You can always try the latest firmware.

3) Buy another router that does not have this NAT/PPTP compliance issue


Appendix 1 – Why Windows XP doesn’t have the same issue

You may find that you can make solid PPTP connections through the router by placing the client PC (XP SP2) on the network that is connected to the

EXTERNAL ISA interface and the INTERNAL router interface – effectively the DMZ for this network. It’s because the PPTP module in the Windows RAS client

has a different design, it does not check the Call ID in the packet. It just accepts it.


Appendix 2 – RFC 2637

RFC 2637 – http://www.faqs.org/rfcs/rfc2637.html:


Appendix 3 – If it’s a ISA 2000 box, not a ISA 2004


Make sure the you have ISA SP2 applied which contains the hotfix 831531. In addition, according to the hotfix ‘FIX: Outbound PPTP connections may

disconnect after 60 seconds if the ISA Firewall Service is running – http://support.microsoft.com/?id=831531′, the problem should be fixed without changing the binding order.


If remote is not an ISA server, change the local value InactivityIdleSeconds to 30 seconds to ensure that the server’s timer always expires first. (See

Q262990 for instructions): ‘262990 RRAS VPN Dial-On-Demand Failover Mechanism – http://support.microsoft.com/?id=262990 ‘.

840654 Your VPN connection is disconnected after several minutes in Windows XP – http://support.microsoft.com/?id=840654


Comments are closed.