Sharepoint resources

I’ve been doing some sharepoint stuff.  I hope to have this post be a growing list of resources.  If you have any that are unique, please let me know or post and I’ll add to it.

‘Explains a DCOM error {61738644-F196-11D0-9953-00C04FD919C1}

‘ListServ on Sharepoint.

Yahoo groups

Webbased newsgroups
MS Newsgroups general
MS Newsgroup Setup and Configuration

Google Groups

IIS Team releases more cool modules

The IIS Team has been releasing some really cool modules of late.  Check them out.  Also, keep an eye on for all the latest news!

  • URLRewrite module

  • Web Playlists

  • FTP 7 Update (x86) Installation Package 

  • FTP 7 Update (x64) Installation Package

  • WebDAV Update (x86) Installation Package



CDOSYS and Windows Server 2008, 80070005 Description Access is denied

I got a question from Bradley J. Dinerman about getting Aspmail working on Windows Server 2008.  I’ve yet to figure out how to get AspEmail working on Windows Server 2008,  I tried x64 and x86 of Windows Server 2008.  I got the following error.  Process monitor and enabling auditing didn’t turn up anything. 

  • error ‘800703e6’

  • /asp.asp, line 8

  • Line 8 is the Set mailer = Server.Createobject(“SMTPsvg.Mailer”)

Brad mentioned he was getting an error trying to switch to CDOSYS. Here is the error. The error for CDOSYS is: ASP_LOG_ERROR LineNumber 7 ErrorCode 80070005 Description Access is denied  The problem ended up being the anonymous user didn’t have write permissions on the c:\inetpub\mailroot\pickup folder.  I thought I would pass this along as an FYI.

Two things to configure on the SMTP Service (At least I do)

  • Configure appropriate (write) permissions on c:\inetpub\mailroot\pickup

  • Configure to allow to be relayed Internet Manager 6 > SMTP Virtual Server > Properties > Access Tab > Relay Restrictions > Relay button > Click Add and type

‘Link Brad passed along

Thanks Brad for passing along the post and solution.



IIS6 to IIS7 migration tips / tricks.

Here are a few gotcha’s that I personally came across both in the forums and migrations I’ve done from IIS6 to IIS7.   A lot of the confusion I see in the forums is Classic ASP and ‘native’ applications using COM+ trying to move to IIS 7.   A classic ASP.NET 1.1 and 2.0 applications should migrate with little or no issues, that is my experience.  You’ll need to install .NET 1.1 on Windows Server 2008.  The biggest change is to try Integrated Application Pools first, then switch to classic mode.  That is probably the biggest recommendation to think about in your migration. 

I was involved in migrating a few sites recently with popular content engines.  We used the migration tool MSDeploy provided by MS, the one thing that we needed to adjust was the Anonymous Authentication module.  We had to adjust so the virtual directory inherited the application pool user account instead of IUSR.   I highly recommend using the deployment tool.  The one item that IIS 7 manager doesn’t match up to IIS 6 is SSL certificate management.  It seems more mature in IIS 6 manager IMO. 

Another common confusion point with IIS 7.0 is the modular architecture.  In previous versions of IIS, most everything was installed or not too many options to have a module install.  This was completely redone and thankfully, for the better in IIS 7.0.  I’m not a Apache admin, but my limited experience, Apache is VERY modular.  You have to know what you want so stuff will work. Like any new software, IIS 7.0 takes some getting used to, but once you get the swing of it, you won’t want to go back to IIS6, which is a pretty decent platform.

Here is my list with some links to articles..  If you have a tip, add it to the comments section or email me at

1) CDONTS running in 64 bit boxes with 32 bit app pools.  This applies to other components running in mixed bitness mode.

2) Integrated vs. Classic Mode application pools.

3) Modules not being installed by default (Classic ASP, SMTP service (which is a feature now))

4) 32 bit app pools running on a 64 bit box and when you download a 64 bit installer, the application / isapi doesn’t work since most are running 32 bit app pools.  Mixed ‘bitness’ ( I think that is the new cool term ).

5) Microsoft Access databases and older MDAC installs.   Access databases in general and not having the right permissions, and / or correct versions of libraries not installed.  I wrote a blog on Access 2007 not being installed.

7) RDS (remote data services), which was part of MDAC, older versions don’t seem to migrate.

8) 3rd party COM+ not being installed or not being transfered to new systems.  COM+ is still there, the component services MMC snap-in needs to be added.

9) UserLoadProfile = False instead of True.  I think the default False.

10) Disable Double Escape

11) SMTP service not logging

12) Classic ASP tips by Bill S.

13) 3rd party vendors apps, especially native ones.  Make sure they have a 64 bit and 32 bit version available.  This will depend on your app pool preference.

14) Install .NET 1.1 w/sp1 on Windows Server 2008.


Steve Schofield
Microsoft MVP – IIS