Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1124
  • Last Modified:

Internet Connection Wizard won't complete - fails at email config

I have just installed a new server with SBS 2003.
When I run the ICW, all goes well until the last stage - the emnail configuration. At that point the configuration fails.

The internet is available so firewall and broadband connection have obviously worked. But no clients can see the Exchange server. And the Exchange server doesn't seem to be picking up external email either.

The errors in the log quote error code 8000500d.

Is there any way to configure manually? Everything I have found says "run the ICW" - fine if it works, but useless if it fails!

  • 4
  • 3
1 Solution
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If it's showing an error you need to fix what's wrong.  Manually configuring would just allow whatever is causing the error to persist... which obviously isn't the right thing to do.

Can you please post the entire error lines from the log?  Just posting the "8000500d" doesn't help much.

NickRamseyAuthor Commented:

As the new server is not permanently online, I took the shortcut of mentioning the error code, fully expecting that if anyone had seen it they may have a clue, but if not I would have to post the actual lines.
Below, I have cut out most of the preamble (all the successful bits) and just put in the error lines with some of the surrounding log. If you need  the full log I can post it?
Like you, I don't like applying "workarounds", but sometimes the fault is the script not what's actually being done. If I can configure manually the things that the script tries to do, without errors, then I will have fixed the root and script errors are irrelevant to me. It remains toi be seen....

Here's the actual section:

calling SetInternetOptions ((null), (null), (null)).
Call to InternetSetOptionA () returned ok.
Call to SetInternetOptions () returned ok.
calling InternetSetOption_AutodialConnection ().
Call to InternetSetOption_AutodialConnection () returned ok.
calling InternetSetOption_AutodialMode (4).
Call to InternetSetOption_AutodialMode () returned ok.
calling InternetSetOption_DisableAutodial (0).
Call to InternetSetOption_DisableAutodial () returned ok.
Call to ConfigureIE () returned ok.
Call to Configuring IE for router connection () returned ok.
Call to Notifying client setup for Default gateway as the router () returned ok.
calling RegisterMSBOExchangeBP (0).
Error 0x1 returned from call to RegisterMSBOExchangeBP().
Call to Unregistering the smtp sink () returned ok.
Call to GetLocalDomainName () returned ok.
Call to Reading in the local domain name () returned ok.

Call to Setting SMTPSVC to start up automatically () returned ok.
calling CAttachCommiter::Commit (0x12762f0).
calling CAttachCommiter::Commit:ReadVariant(GUID_ATTACH_CONFIG) (0x0).
calling CAttachCommiter::Commit:m_spDoc.CoCreateInstance (0x0).
calling CAttachCommiter::Commit:m_spDoc->loadXML (0x0).
calling CAttachCommiter::Commit:WriteConfigFile (0x0).
calling CAttachCommiter::WriteConfigFile (0x40000003).
calling CAttachCommiter::WriteConfigFile:_GetSBSInstallDir (0x0).
calling CAttachCommiter::WriteConfigFile:m_spDoc->save (0x0).
Call to CAttachCommiter::WriteConfigFile () returned ok.
calling CAttachCommiter::Commit:ShouldEnableSink (0x0).
calling CAttachCommiter::ShouldEnableSink (0x40000003).
calling CAttachCommiter::ShouldEnableSink:m_spDoc->selectSingleNode (0x40000003).
calling CAttachCommiter::ShouldEnableSink:spEnabledNode->get_text (0x40000003).
Error 0x1 returned from call to CAttachCommiter::ShouldEnableSink().
calling CAttachCommiter::Commit:pSink.CoCreateInstance(SecAttsEventSink) (0x1).
calling CAttachCommiter::Commit:pSink->Unregister (0x0).
Error 0x1 returned from call to CAttachCommiter::Commit().
calling EnableSMTPConnector (0x12762f0, \\ato-dell-server.ATO-MAIN.local, DC=ATO-MAIN,DC=local, ATO-MAIN).
calling DoRecipientPolicy (0x12762f0).
calling ReadString (0x12762f0, 01637C90-B142-41C4-8520-6B2E0F891BE7).
Call to ReadString () returned ok.
The out param of ReadString() is ramsey.uk.net.
calling FinalValidateHostName (ramsey.uk.net).
Call to FinalValidateHostName () returned ok.
calling GetDefaultPolicy (0x7f3cc).
Call to GetDefaultPolicy () returned ok.
calling GetPostmasterProxyAddresses ().
Call to GetPostMasterProxyAddresses () returned ok.
calling UpdatePostmasterAddress (0x24da518, ramsey.uk.net).
Error 0x8000500d returned from call to UpdatePostmasterAddress().
Error 0x8000500d returned from call to DoRecipientPolicy().
Error 0x8000500d returned from call to EnableSMTPConnector().
Error 0x8000500d returned from call to CEMailCommit::Commit().
calling GetBOConnector ().
Call to GetBOConnector () returned ok.
calling spADs->PutEx (ADS_PROPERTY_CLEAR, msExchSmtpOutboundSecurityPassword).
Call to spADs->PutEx () returned ok.
calling spADs->SetInfo ().
Call to spADs->SetInfo () returned ok.

Thanks for any help.

NickRamseyAuthor Commented:
Seems there's no answer to this. Maybe a paid incident with Microsoft Support is the answer?

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
No, I just missed that you posted back the log entries.

This is normally caused because: The administrator account does not have an
associated mailbox.

To resolve the issue try to Create a mailbox for the Administrator account
and re-run the CEICW.

Steps To resolve this issue:
1 - Launch Active Directory Users and Computers
2 - Expand the Users container
3 - Right click the Administrator's mailbox
4 - Click Exchange Tasks and select the Create mailbox option.
5 - Rerun the CEICW.


NickRamseyAuthor Commented:

Now I know why you're rated "wizard" !!  :)
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Not for long!  :-)

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I might point out... by the way... regarding your comment, "sometimes the fault is the script not what's actually being done".

This may be true of VB scripts you find here and there... however the SBS Wizards are proven scripts, that help to keep the server configured within the best practices model.  In ALL cases, if an SBS wizard (script) errors, you need to find out what's causing the error before moving on.  Manual configuration in an SBS environment can be detrimental to the operational structure of your server.  The reason is that this is a unified server installation that has a number of interdependencies.  Failure to configure all items which are dependent on eachother will cause you problems... the wizards handle this so you don't have to manually configure seven things simultaneously.


Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now