Troubleshooting Tips when running OOOCTA 3.5

by Andy Grogan on October 31, 2011 · 0 comments

in Exchange Programming .NET, OOOCTA, Out of Office, Powershell, Quick Tips

The Out of Office Configuration Tool Assistant (OOOCTA) was released over 6 months ago and is one of my most favourite tools that I have written, however I accept that it can be a little difficult to setup and get working particularly as there are so many diverse environments out there.

Given the above I have decided to write a quick post that goes through some of the more common problems that I have been made aware of.

Make sure that you are running the latest version

It is very important to make sure that you are running the latest version of the OOOCTA – there have been a number of patches since the RTP version – this can be found in the Downloads section of the site.

Please note that the patches are NOT cumulative (not yet) you must install them in order (e.g. RTP Release, Patch 1, Patch 2 – etc).

Running the correct EWS Version Mode

The EWS is the heart of the OOOCTA and it is key to ensure that you have selected the correct version of Exchange to execute the EWS against.

  • If you are running OOOCTA on an Exchange 2010 Server or on a Management Server with the Exchange 2010 Management tools installed you should ensure that the Exchange Version is set to “Exchange2010” in the [ System Admin ] menu – see below

oooctaTps001

  • If you are running OOOCTA in an “Interop” environment (e.g. with Exchange 2010 and Exchange 2007) – install OOOCTA on the Exchange 2007 Server – or on a management server with the Exchange 2007 Management tools installed and then ensure that the EWS version is set to “Exchange2007_SP1” – see below

oooctaTps002

The OOOCTA will still function against Exchange 2010 based mailboxes in this configuration.

  • If you are running OOOCTA against Exchange 2007 – ensure that you have set the EWS functional level to “Exchange2007_SP1

Ensure that the svcOOOCTA_DOM Service account has the proper permissions when using Exchange 2010

The OOOCTA Setup manual explains how to configure the svcOOOCTA_DOM service account for Exchange 2007 – but does not explain in great detail how to do the same in the context of Exchange 2010.

In order to ensure that the service account has the correct permissions you will (after you have created the service account mailbox) to assign the Organization Management role via the ECP.

Before you can configure the Organization Management role, you will need to be logged onto your Exchange 2010 server with the correct permissions (an account that has Organization Management rights already for example). You will them need to Open Internet Explorer and navigate to https://<YouCASServer>/ecp

Once you have logged into the ECP you will need to click on the “Roles & Auditing” option on the right – see below

oooctaTps003

Then double click on the “Organization Management” option – see below

oooctaTps004

Then add the svcOOOCTA_DOM account into the members list – see below

oooctaTps005

Then click on the “Save” button.

Make sure that SQL is configured to allow mixed authentication

Some people have reported to me that after installing the OOOCTA, the “OOOCTA Command Processor” service hangs on start-up.

When trying to manually start the service they are presented with the following error message:

oooctaTps006

In the event log, the following entry can then be found:

Faulting application name: outofofficeservice.exe, version: 3.5.0.1, time stamp: 0x4dfda869
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e21213c
Exception code: 0xe053534f
Fault offset: 0x000000000000cacd
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

Furthermore, when trying to view the [ System Log ] in the management interface they are presented with the following error:

oooctaTps007

These issues are almost always caused by:

  1. The OOOCTA Command Processor and Management Interface not being able to connect to the Database
  2. The SQL Server does not allow for Mixed Authentication (NTML and SQL passwords)

In the case of the latter – you must enable mixed mode authentication on your SQL server.

Make sure that SQL Server Network configuration is setup to allow connections to the Database

The most common problem however is the OOOCTA not being able to connect to the SQL database.

How you choose to configure this will be very much down to your own environment, but by default OOOCTA will attempt to connect to the SQL Database server stipulated in its configuration files using:

  • Localhost\<InstanceName>
  • <InstanceName>

If the SQL Database is installed on the same server as the OOOCTA you will need to have configured SQL to accept connections to 127.0.0.1 – this is accomplished using the [ SQL Server Configuration Manager –> SQL Server Network Configuration –> Protocols for SQLExpress ] – see below

oooctaTps009

Double click on the TCP/IP entry (make sure that it is enabled) – and from the dialog box that appears click on the IP Addresses tab and locate the 127.0.0.1 address – make sure that it is also enabled – see below

oooctaTps008

For reference the configuration files for OOOCTA which govern the SQL Server properties are located in:

<Install Path>\Interface\Web.config

<Install Path>\Service\OutOfOfficeService.exe.config

I hope that the above helps some people out, and encourages more folks to download the software. I do try my very best to offer as much support as I can for the tool and apologise to those whom I have not had the chance to contact back – I am hoping that this post will assist you.

Social

{ 0 comments… add one now }

Leave a Comment

Previous post:

Next post: