Prev: Portal 2003 Indexing Error
Next: Cannot start device DCLoadBalancer
From: CC-Gov-Mat on 14 Aug 2006 16:44
Steve,

I verified that the application pool account has full permissions in AD for
that OU. Do you think it matters that I am using NTLM instead of Kerberos for
authentication?(I am grasping at straws at this point) I don't seem to have
any trouble creating object in the OU directly using the AD management
console running as the app pool user. Any thoughts on why MOSS does not seem
to be able to create the contact in AD?

Mat

"Steve Smith" wrote:

> Couple of things. Try going through my whitepaper on
> www.combined-knowledge.com , look for the sharepoint 2007 downloads. Also
> make sure that the Application Pool account that you are using has create
> object right on the OU in AD.
>
> Steve Smith
> www.combined-knowledge.com
>
>
>
> "chawki" <chawki(a)discussions.microsoft.com> wrote in message
> news:596D604F-3C42-46FF-B71D-804733717BF6(a)microsoft.com...
> > Hi,
> >
> > I am trying to enable incoming mail for lists in SharePoint 2007 beta 2
> > installed on a single server.
> >
> > Steps taken:
> > Created SharePoint2007 OU in AD
> > -eXenon.local
> > ---SharePoint2007
> >
> >
> > Installed SMTP on MOSS server (exenon2.Exenon.local)
> >
> >
> > configured SMTP to accept relay from exchange server
> > (exenonserver.eXenon.local)
> >
> >
> > set "Central administration > Operations > Active Directory settings for
> > E-mail Web Service > Active Directory Container Object" to:
> > OU=SharePoint2007DC=eXenon,DC=local
> >
> >
> > set "Central administration > Operations >Incoming E-Mail Settings" as
> > follows:
> > -Enable sites on this server to receive email - Yes
> > -Settings mode - Advanced
> > -Connect to a Sharepoint directory management service - Yes
> > -Directory management service URL -
> > http://exenon2:5190/_vti_bin/sharepointemailws.asmx
> > -E-mail server address - exenon2.eXenon.local
> > -Does this directory management service manage distribution lists - Yes
> > -Should distribution lists accept mail only from authenticated senders -
> > Yes
> > -E-Mail server display address - myl ...@eXenon.local
> > -E-Mail drop folder - C:\InetPub\mailroot\Drop
> >
> > I then create a new doc library and enable receive email and set email
> > address to projectmail(a)eXenon.local
> >
> >
> > Receive pages that says "The list was created successfully, but could not
> > be
> > assigned an e-mail alias because of the following error: Error in the
> > application."
> >
> >
> > Am I missing a step that gives SharePoint the permissions to create a
> > contact in AD?
> >
> > Hope that you can help me.
> >
> > Thanks
> >
>
>
>
From: Jerry Rasmussen on 21 Aug 2006 17:24
The problem is not that you are using NTLM. I think you are in the
wrong place. Go to Central administration > Operations > In comming
email setting. Click enable then go to Incoming E-Mail Server Display
Address add the domain name at the end in your case that would be
Exenon.local. That was the easy part.

Depending you your DNS and Exchange infrastructure you will need to add
an MX record to dns to point to this server. Or configure routing in
exchange to forward SMTP email to this server.

CC-Gov-Mat wrote:
> Steve,
>
> I verified that the application pool account has full permissions in AD for
> that OU. Do you think it matters that I am using NTLM instead of Kerberos for
> authentication?(I am grasping at straws at this point) I don't seem to have
> any trouble creating object in the OU directly using the AD management
> console running as the app pool user. Any thoughts on why MOSS does not seem
> to be able to create the contact in AD?
>
> Mat
>
> "Steve Smith" wrote:
>
>> Couple of things. Try going through my whitepaper on
>> www.combined-knowledge.com , look for the sharepoint 2007 downloads. Also
>> make sure that the Application Pool account that you are using has create
>> object right on the OU in AD.
>>
>> Steve Smith
>> www.combined-knowledge.com
>>
>>
>>
>> "chawki" <chawki(a)discussions.microsoft.com> wrote in message
>> news:596D604F-3C42-46FF-B71D-804733717BF6(a)microsoft.com...
>>> Hi,
>>>
>>> I am trying to enable incoming mail for lists in SharePoint 2007 beta 2
>>> installed on a single server.
>>>
>>> Steps taken:
>>> Created SharePoint2007 OU in AD
>>> -eXenon.local
>>> ---SharePoint2007
>>>
>>>
>>> Installed SMTP on MOSS server (exenon2.Exenon.local)
>>>
>>>
>>> configured SMTP to accept relay from exchange server
>>> (exenonserver.eXenon.local)
>>>
>>>
>>> set "Central administration > Operations > Active Directory settings for
>>> E-mail Web Service > Active Directory Container Object" to:
>>> OU=SharePoint2007DC=eXenon,DC=local
>>>
>>>
>>> set "Central administration > Operations >Incoming E-Mail Settings" as
>>> follows:
>>> -Enable sites on this server to receive email - Yes
>>> -Settings mode - Advanced
>>> -Connect to a Sharepoint directory management service - Yes
>>> -Directory management service URL -
>>> http://exenon2:5190/_vti_bin/sharepointemailws.asmx
>>> -E-mail server address - exenon2.eXenon.local
>>> -Does this directory management service manage distribution lists - Yes
>>> -Should distribution lists accept mail only from authenticated senders -
>>> Yes
>>> -E-Mail server display address - myl ...@eXenon.local
>>> -E-Mail drop folder - C:\InetPub\mailroot\Drop
>>>
>>> I then create a new doc library and enable receive email and set email
>>> address to projectmail(a)eXenon.local
>>>
>>>
>>> Receive pages that says "The list was created successfully, but could not
>>> be
>>> assigned an e-mail alias because of the following error: Error in the
>>> application."
>>>
>>>
>>> Am I missing a step that gives SharePoint the permissions to create a
>>> contact in AD?
>>>
>>> Hope that you can help me.
>>>
>>> Thanks
>>>
>>
>>
From: CC-Gov-Mat on 22 Aug 2006 13:52
Jerry,

Thank you for the ideas, but the problem appears to be at the AD/SharePoint
level. The incoming email server display is set to the fully qualified domain
for the organization and the DNS setup is fine. I have even made it the point
where i can worry about email routing because the contact or distribution
list creating is erroring out when SharePoint tries to create them in the OU
when email enabling the list.

Do you have email enabled lists working in MOSS B2? If so, may I inquire on
how you setup permissions in AD and for what user you set them up for? I have
repeated this same problem on fresh development sandbox using just the
instructions from www.combined-knowledge.com.

Thanks for the response,
Mat

"Jerry Rasmussen" wrote:

> The problem is not that you are using NTLM. I think you are in the
> wrong place. Go to Central administration > Operations > In comming
> email setting. Click enable then go to Incoming E-Mail Server Display
> Address add the domain name at the end in your case that would be
> Exenon.local. That was the easy part.
>
> Depending you your DNS and Exchange infrastructure you will need to add
> an MX record to dns to point to this server. Or configure routing in
> exchange to forward SMTP email to this server.
>
> CC-Gov-Mat wrote:
> > Steve,
> >
> > I verified that the application pool account has full permissions in AD for
> > that OU. Do you think it matters that I am using NTLM instead of Kerberos for
> > authentication?(I am grasping at straws at this point) I don't seem to have
> > any trouble creating object in the OU directly using the AD management
> > console running as the app pool user. Any thoughts on why MOSS does not seem
> > to be able to create the contact in AD?
> >
> > Mat
> >
> > "Steve Smith" wrote:
> >
> >> Couple of things. Try going through my whitepaper on
> >> www.combined-knowledge.com , look for the sharepoint 2007 downloads. Also
> >> make sure that the Application Pool account that you are using has create
> >> object right on the OU in AD.
> >>
> >> Steve Smith
> >> www.combined-knowledge.com
> >>
> >>
> >>
> >> "chawki" <chawki(a)discussions.microsoft.com> wrote in message
> >> news:596D604F-3C42-46FF-B71D-804733717BF6(a)microsoft.com...
> >>> Hi,
> >>>
> >>> I am trying to enable incoming mail for lists in SharePoint 2007 beta 2
> >>> installed on a single server.
> >>>
> >>> Steps taken:
> >>> Created SharePoint2007 OU in AD
> >>> -eXenon.local
> >>> ---SharePoint2007
> >>>
> >>>
> >>> Installed SMTP on MOSS server (exenon2.Exenon.local)
> >>>
> >>>
> >>> configured SMTP to accept relay from exchange server
> >>> (exenonserver.eXenon.local)
> >>>
> >>>
> >>> set "Central administration > Operations > Active Directory settings for
> >>> E-mail Web Service > Active Directory Container Object" to:
> >>> OU=SharePoint2007DC=eXenon,DC=local
> >>>
> >>>
> >>> set "Central administration > Operations >Incoming E-Mail Settings" as
> >>> follows:
> >>> -Enable sites on this server to receive email - Yes
> >>> -Settings mode - Advanced
> >>> -Connect to a Sharepoint directory management service - Yes
> >>> -Directory management service URL -
> >>> http://exenon2:5190/_vti_bin/sharepointemailws.asmx
> >>> -E-mail server address - exenon2.eXenon.local
> >>> -Does this directory management service manage distribution lists - Yes
> >>> -Should distribution lists accept mail only from authenticated senders -
> >>> Yes
> >>> -E-Mail server display address - myl ...@eXenon.local
> >>> -E-Mail drop folder - C:\InetPub\mailroot\Drop
> >>>
> >>> I then create a new doc library and enable receive email and set email
> >>> address to projectmail(a)eXenon.local
> >>>
> >>>
> >>> Receive pages that says "The list was created successfully, but could not
> >>> be
> >>> assigned an e-mail alias because of the following error: Error in the
> >>> application."
> >>>
> >>>
> >>> Am I missing a step that gives SharePoint the permissions to create a
> >>> contact in AD?
> >>>
> >>> Hope that you can help me.
> >>>
> >>> Thanks
> >>>
> >>
> >>
>
From: Jerry Rasmussen on 22 Aug 2006 15:03
No I do not have that setup. I will take a look at it today and see
what I can come up with.
CC-Gov-Mat wrote:
> Jerry,
>
> Thank you for the ideas, but the problem appears to be at the AD/SharePoint
> level. The incoming email server display is set to the fully qualified domain
> for the organization and the DNS setup is fine. I have even made it the point
> where i can worry about email routing because the contact or distribution
> list creating is erroring out when SharePoint tries to create them in the OU
> when email enabling the list.
>
> Do you have email enabled lists working in MOSS B2? If so, may I inquire on
> how you setup permissions in AD and for what user you set them up for? I have
> repeated this same problem on fresh development sandbox using just the
> instructions from www.combined-knowledge.com.
>
> Thanks for the response,
> Mat
>
> "Jerry Rasmussen" wrote:
>
>> The problem is not that you are using NTLM. I think you are in the
>> wrong place. Go to Central administration > Operations > In comming
>> email setting. Click enable then go to Incoming E-Mail Server Display
>> Address add the domain name at the end in your case that would be
>> Exenon.local. That was the easy part.
>>
>> Depending you your DNS and Exchange infrastructure you will need to add
>> an MX record to dns to point to this server. Or configure routing in
>> exchange to forward SMTP email to this server.
>>
>> CC-Gov-Mat wrote:
>>> Steve,
>>>
>>> I verified that the application pool account has full permissions in AD for
>>> that OU. Do you think it matters that I am using NTLM instead of Kerberos for
>>> authentication?(I am grasping at straws at this point) I don't seem to have
>>> any trouble creating object in the OU directly using the AD management
>>> console running as the app pool user. Any thoughts on why MOSS does not seem
>>> to be able to create the contact in AD?
>>>
>>> Mat
>>>
>>> "Steve Smith" wrote:
>>>
>>>> Couple of things. Try going through my whitepaper on
>>>> www.combined-knowledge.com , look for the sharepoint 2007 downloads. Also
>>>> make sure that the Application Pool account that you are using has create
>>>> object right on the OU in AD.
>>>>
>>>> Steve Smith
>>>> www.combined-knowledge.com
>>>>
>>>>
>>>>
>>>> "chawki" <chawki(a)discussions.microsoft.com> wrote in message
>>>> news:596D604F-3C42-46FF-B71D-804733717BF6(a)microsoft.com...
>>>>> Hi,
>>>>>
>>>>> I am trying to enable incoming mail for lists in SharePoint 2007 beta 2
>>>>> installed on a single server.
>>>>>
>>>>> Steps taken:
>>>>> Created SharePoint2007 OU in AD
>>>>> -eXenon.local
>>>>> ---SharePoint2007
>>>>>
>>>>>
>>>>> Installed SMTP on MOSS server (exenon2.Exenon.local)
>>>>>
>>>>>
>>>>> configured SMTP to accept relay from exchange server
>>>>> (exenonserver.eXenon.local)
>>>>>
>>>>>
>>>>> set "Central administration > Operations > Active Directory settings for
>>>>> E-mail Web Service > Active Directory Container Object" to:
>>>>> OU=SharePoint2007DC=eXenon,DC=local
>>>>>
>>>>>
>>>>> set "Central administration > Operations >Incoming E-Mail Settings" as
>>>>> follows:
>>>>> -Enable sites on this server to receive email - Yes
>>>>> -Settings mode - Advanced
>>>>> -Connect to a Sharepoint directory management service - Yes
>>>>> -Directory management service URL -
>>>>> http://exenon2:5190/_vti_bin/sharepointemailws.asmx
>>>>> -E-mail server address - exenon2.eXenon.local
>>>>> -Does this directory management service manage distribution lists - Yes
>>>>> -Should distribution lists accept mail only from authenticated senders -
>>>>> Yes
>>>>> -E-Mail server display address - myl ...@eXenon.local
>>>>> -E-Mail drop folder - C:\InetPub\mailroot\Drop
>>>>>
>>>>> I then create a new doc library and enable receive email and set email
>>>>> address to projectmail(a)eXenon.local
>>>>>
>>>>>
>>>>> Receive pages that says "The list was created successfully, but could not
>>>>> be
>>>>> assigned an e-mail alias because of the following error: Error in the
>>>>> application."
>>>>>
>>>>>
>>>>> Am I missing a step that gives SharePoint the permissions to create a
>>>>> contact in AD?
>>>>>
>>>>> Hope that you can help me.
>>>>>
>>>>> Thanks
>>>>>
>>>>
From: Jerry Rasmussen on 22 Aug 2006 15:15
This maybe nothing but you are missing a comma
OU=SharePoint2007DC=eXenon,DC=local
OU=SharePoint2007,DC=eXenon,DC=local
CC-Gov-Mat wrote:
> Jerry,
>
> Thank you for the ideas, but the problem appears to be at the AD/SharePoint
> level. The incoming email server display is set to the fully qualified domain
> for the organization and the DNS setup is fine. I have even made it the point
> where i can worry about email routing because the contact or distribution
> list creating is erroring out when SharePoint tries to create them in the OU
> when email enabling the list.
>
> Do you have email enabled lists working in MOSS B2? If so, may I inquire on
> how you setup permissions in AD and for what user you set them up for? I have
> repeated this same problem on fresh development sandbox using just the
> instructions from www.combined-knowledge.com.
>
> Thanks for the response,
> Mat
>
> "Jerry Rasmussen" wrote:
>
>> The problem is not that you are using NTLM. I think you are in the
>> wrong place. Go to Central administration > Operations > In comming
>> email setting. Click enable then go to Incoming E-Mail Server Display
>> Address add the domain name at the end in your case that would be
>> Exenon.local. That was the easy part.
>>
>> Depending you your DNS and Exchange infrastructure you will need to add
>> an MX record to dns to point to this server. Or configure routing in
>> exchange to forward SMTP email to this server.
>>
>> CC-Gov-Mat wrote:
>>> Steve,
>>>
>>> I verified that the application pool account has full permissions in AD for
>>> that OU. Do you think it matters that I am using NTLM instead of Kerberos for
>>> authentication?(I am grasping at straws at this point) I don't seem to have
>>> any trouble creating object in the OU directly using the AD management
>>> console running as the app pool user. Any thoughts on why MOSS does not seem
>>> to be able to create the contact in AD?
>>>
>>> Mat
>>>
>>> "Steve Smith" wrote:
>>>
>>>> Couple of things. Try going through my whitepaper on
>>>> www.combined-knowledge.com , look for the sharepoint 2007 downloads. Also
>>>> make sure that the Application Pool account that you are using has create
>>>> object right on the OU in AD.
>>>>
>>>> Steve Smith
>>>> www.combined-knowledge.com
>>>>
>>>>
>>>>
>>>> "chawki" <chawki(a)discussions.microsoft.com> wrote in message
>>>> news:596D604F-3C42-46FF-B71D-804733717BF6(a)microsoft.com...
>>>>> Hi,
>>>>>
>>>>> I am trying to enable incoming mail for lists in SharePoint 2007 beta 2
>>>>> installed on a single server.
>>>>>
>>>>> Steps taken:
>>>>> Created SharePoint2007 OU in AD
>>>>> -eXenon.local
>>>>> ---SharePoint2007
>>>>>
>>>>>
>>>>> Installed SMTP on MOSS server (exenon2.Exenon.local)
>>>>>
>>>>>
>>>>> configured SMTP to accept relay from exchange server
>>>>> (exenonserver.eXenon.local)
>>>>>
>>>>>
>>>>> set "Central administration > Operations > Active Directory settings for
>>>>> E-mail Web Service > Active Directory Container Object" to:
>>>>> OU=SharePoint2007DC=eXenon,DC=local
>>>>>
>>>>>
>>>>> set "Central administration > Operations >Incoming E-Mail Settings" as
>>>>> follows:
>>>>> -Enable sites on this server to receive email - Yes
>>>>> -Settings mode - Advanced
>>>>> -Connect to a Sharepoint directory management service - Yes
>>>>> -Directory management service URL -
>>>>> http://exenon2:5190/_vti_bin/sharepointemailws.asmx
>>>>> -E-mail server address - exenon2.eXenon.local
>>>>> -Does this directory management service manage distribution lists - Yes
>>>>> -Should distribution lists accept mail only from authenticated senders -
>>>>> Yes
>>>>> -E-Mail server display address - myl ...@eXenon.local
>>>>> -E-Mail drop folder - C:\InetPub\mailroot\Drop
>>>>>
>>>>> I then create a new doc library and enable receive email and set email
>>>>> address to projectmail(a)eXenon.local
>>>>>
>>>>>
>>>>> Receive pages that says "The list was created successfully, but could not
>>>>> be
>>>>> assigned an e-mail alias because of the following error: Error in the
>>>>> application."
>>>>>
>>>>>
>>>>> Am I missing a step that gives SharePoint the permissions to create a
>>>>> contact in AD?
>>>>>
>>>>> Hope that you can help me.
>>>>>
>>>>> Thanks
>>>>>
>>>>
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Portal 2003 Indexing Error
Next: Cannot start device DCLoadBalancer