Unable To Create Mailboxes In New Organizations

Question

Hi everyone,

We're running WSP 1.2.0 with Exchange 2010 SP2 and are unable to create mailboxes in new organizations only. New organizations CAN create user accounts though. Existing organizations can create mailboxes without issue. The specific error received is:

Error creating mailbox. See audit log for more details.

Server was unable to process request. ---> Error executing 'CREATE_MAILBOX' task on '' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Server was unable to process request. ---> Execution result does not contain any object.

I did some searching and found the multiple other posts regarding this issue and various recommendations (check account permissions, check public folder and OAB generation server, etc) and all of those are correct in our case. I know SP2 isn't "officially" supported with WSP but I'm hoping someone else has seen this same problem and may have a workaround handy.

Thanks!

Answer 1

A bit more information:

Our two NLB CAS/HT servers are running the portal and server components and we have a dedicated server running the enterprise component. As a test I installed both other roles (server and portal) on the dedicated enterprise server and I get the following when I try to create a mailbox in a new organization:

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'CREATE_USER' task on '' ORGANIZATION ---> System.Exception: Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> System.Exception: Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Execution result does not contain any object at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at WebsitePanel.Providers.Exchange.ExchangeServer.ExtendToExchangeOrganization(String organizationId, String securityGroup) at WebsitePanel.EnterpriseServer.ExchangeServerController.ExtendToExchangeOrganization(Organization& org) --- End of inner exception stack trace --- at WebsitePanel.EnterpriseServer.ExchangeServerController.ExtendToExchangeOrganization(Organization& org) --- End of inner exception stack trace --- at WebsitePanel.EnterpriseServer.ExchangeServerController.ExtendToExchangeOrganization(Organization& org) at WebsitePanel.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress) --- End of inner exception stack trace --- at WebsitePanel.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress) at WebsitePanel.EnterpriseServer.esExchangeServer.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress) --- End of inner exception stack trace ---

Answer 2

Update... I upgraded to 1.2.1 and I still have the same problem.

Answer 3

New update:

After double checking all my AD permissions, OU permissions, Exchange permissions, and some other settings I discovered the Mailbox Database Name was referring to a nonexistent database. I set that to the correct name and now I get a different error:

Server was unable to process request. ---> Error executing 'CREATE_MAILBOX' task on '' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Server was unable to process request. ---> Value cannot be null. Parameter name: serverSettings ---> Value cannot be null. Parameter name: serverSettings

Answer 4

OK, I've gotten a bit further. After setting the WSP server application pool on all my servers to run as the domain account rather than a local system account I get the following error:

Server was unable to process request. ---> Error executing 'CREATE_MAILBOX' task on '' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Error executing 'CREATE_ORG' task on 'FlyinDog' EXCHANGE ---> Server was unable to process request. ---> Cannot bind parameter 'VirtualDirectories'. Cannot convert value "EXCHFE01\OAB (Default Web Site),EXCHFE02\OAB (Default Web Site)" to type "Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter". Error: "'EXCHFE01\OAB (Default Web Site),EXCHFE02\OAB (Default Web Site)' is not a valid value for the identity. Parameter name: Identity" ---> Cannot convert value "EXCHFE01\OAB (Default Web Site),EXCHFE02\OAB (Default Web Site)" to type "Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter". Error: "'EXCHFE01\OAB (Default Web Site),EXCHFE02\OAB (Default Web Site)' is not a valid value for the identity. Parameter name: Identity" ---> 'EXCHFE01\OAB (Default Web Site),EXCHFE02\OAB (Default Web Site)' is not a valid value for the identity. Parameter name: Identity

EXCHFE01 and EXCHFE02 are my two frontend Exchange servers (CAS/HT) running the portal and server components. It seems like it is trying to mail-enable the organization upon creating the first mailbox and gets stuck at trying to create the OAB.

Any suggestions? I'm about out of ideas.

Answer 5

Anybody?

This is causing a major production stoppage for us. If we have to call Microsoft for support we will but I'm not sure if they would support WSP anyhow. We're still stuck at the error when trying to create the first mailbox in a new Exchange organization (which effectively mail-enables the organization):

I'd be extremely grateful for any kind of assistance or suggestion on how we can possibly get this resolved.

Thanks!

Answer 6

For full Ex.2010 SP2 support with ABP without /hosting installation switch (the only supported solution for SP2 and all future versions) you have to download the latest beta 1.2.1.6, apply necessary web.config modifications and define Exchange Virtual Server in WSP the same way which was used for Exchange 2007. Can you confirm you did this?

---

-- Radek Dolezel

Answer 7

I have 1.2.1.6 installed. What web.config changes do I need to make? Where do I define the Exchange Virtual server in WSP?

Answer 8

Any other suggestions? What web.config changes do I need to make to get this working? Where do I define the Exchange Virtual server in WSP?

Answer 9

OK, I think I figured out what web.config changes needed to be made. I added the following to my two CAS/HT servers that run the portal and server components of WSP and to both of my WSP Enterprise servers (just for good measure):

<add key="WebsitePanel.Exchange.ClearQueryBaseDN" value="true" />
<add key="WebsitePanel.Exchange.enableSP2abp" value="true" />

I ran iisreset on all 4 servers but still get the same error when I try to mail-enable a new organization.

Any other ideas? I'm really desperate to get this working. Help!

Answer 10

Look at this - http://www.websitepanel.net/exchange-2007-2010-module/hosted-exchange-solution-pre-deployment-tasks. Rollback "Modifying Address Lists Containers" if you applied it earlier. You can't use this for Exchange 2010 SP2 with ABP support.

After that read this - http://www.websitepanel.net/exchange-2007-2010-module/hosted-exchange-solution-installation-tasks. "The main Exchange service in WSP Exchange solution is on server with Mailbox role or some another server with Exchange Administrative tools which manages mailbox server.
...
When you will be setting up Virtual Server you will need to add only main WSP Exchange service. You should not add Exchange 2007 or 2010 services for Hub Transport and Client Access servers to WSP Virtual Server, as they will be managed by main WSP Exchange service."

---

-- Radek Dolezel

Answer 11

I'm not sure which change fixed the problem but I re-enabled inheritance on all the address list containers, set my virtual server to only use my Exchange 2010 mailbox server (running the Hosted Exchange 2010 module), and removed the CAS/HT servers from the Hub Transport Service and Client Access Service settings on the mailbox server's hosted exchange 2010 module.

It's working now. Thank you very much for your help.

Answer 12

We had the same issue with WSP 1.2.1 and Exchange 2007, removing the CAS/HT servers from the Hub Transport Service and Client Access Service settings on the mailbox server's hosted exchange 2007 module solved the problem.

Answer 13

Hi,

I can also confirm that removing the CAS/HT service from WSP exchange server fixed this issue for us.

Thanks Alonso / Jason and all that contributed to fix.

Richard

Answer 14

Hi Guys,

I can confirm to fix this we had to do the following:-
Login to WSP
Navigate to Configuration >> Servers
Select the Mailbox Server role on the affected server
Remove the Client Access Servers from the Mailbox Server Role.
Update the changes

We ONLY had to remove the Client Access Service servers from the Mailbox Server role and this fixed the issue we were having on WSP v1.2.1

---

Regards, Datatech UK www.datatechuk.com