Hi everyone, I haveWSS 3.0 SP3configured, up and running a site. I've configured the Outgoing and Incoming e-mail using Steve Smith's white paper as a guide. Outgoing is working great now but I can't seem to get SP to create lists and other such things in it's AD OU. I'm guessing it's a permissions issue somewhere as it only errors out with "Error in the application" when I try and activate incoming e-mail. Are there any diagnostic utilities that can help me find specifically what is hanging up the creation of distributions lists, etc.?

Hi there, Theres a few possible causes: Do you have exchange installed in your Active Directory? If not this will throw an error like thiswhen you enable it Does the account (timer account) have rights to the OU? What you can try is when you enable incoming emailset "Use the SharePoint Directory Management Service to create distribution groups and contacts" to "No" Georg

My apologies I missed that last sentence!!! To create the distributions list aside from having Exchange installed, you need to ensure that your timer account has Delegated rights in Active directory to create/delete objects (ie contacts, groups, etc) or it wont work If you right click the OU in AD and select Delegate, and then pick the timer service account and designate appropriately this should fix the problem.

My setup is currently consists of 3 machines: SQLBOX - Running MS SQL 2005, and IIS 6 w/ WSS3 SP1 (I know this isn't recommended but we're on a tight budget until July at which point we're getting a full blown webserver for our intranet.) MAILBOX - Running Exchange 2003 DCBOX - Domain Controller with DNS I've created a Domain account, IWAM_SQLBOX, and added it to the Domain Admins, Enterprise Admins, and Admins groups, as well as given the account Local Admin on the SQLBOX. The IWAM_SQLBOX account is what is being used as the Application Pool Identity account in IIS and the Service accounts in WSS3.

What is the account that runs as the Windows SharePoint Timer Services (in Services.msc) - that account needs to have the rights

It's the IWAM_SQLBOX account I created. It has full delegation to the OU and is a member of all of the administrative groups.

Ok, also do get more details on the error (aside from the event log), you can try editing the web.config for the application (ie Central Admin) to display more detailed errors Backup the original web.config, and then make the following changes: Find this line: <SafeMode MaxControls="50" CallStack="false"/> Set false to true And this line: <customErrors mode="On"/> Set to On to Off

I've enabled the more detailed error messages and tried enabling lists again and this is the resulting error. Code Block Error in the application. at Microsoft.SharePoint.SPList.UpdateDirectoryManagementService(String oldAlias, String newAlias) at Microsoft.SharePoint.SPList.Update(Boolean bFromMigration) at Microsoft.SharePoint.SPList.Update() at Microsoft.SharePoint.ApplicationPages.EmailSettingsPage.SubmitButton_Click(Object sender, EventArgs args) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Is this even an Error I can deal with or is it a code problem that MS is going to need to fix? I'm at an impass as we need the incoming e-mail functionality of WSS3 to work or we're going to have to go with another product. I'm currently on a deadline to have a full test site up and running for our executives by the end of January and this seems to the the only thing stopping that from happening at the moment.

Just to verify you are running Exchange in yourforest, and have SMTP installed on the MOSS box also?

That is correct. The MOSS box isnew and isn't running anything other than IIS, WSS3, and SQL for the sole purpose ofrunning WSS3 so I've wiped it out and I'm starting over from scratch. This is just too weird and I have a feeling that something was fubar'ed during the setup and configuration.

If you run across an SPN issue, please, check out http://social.technet.microsoft.com/wiki/contents/articles/service-principal-names-spns.aspx to help you with understanding and troubleshooting SPN issues. Also, feel free to add information or point out missing information in the article.