OOOCTA 3.5.1–Patch Release 1…
Today I have released a slightly ahead of schedule “Patch Release 1” for the OOOCTA 3.5 Out of Office configuration tool.
I say that it is ahead of schedule, as I have had some feedback from members of the user community about a couple of bugs which, although whilst not serious – do impede the functionality of the tool and I felt compelled to get a patch release out as quickly as possible.
I have to admit some of the problems reported I did not see in the original release version, but I was able to recreate them in my development lab – so perhaps I do need to focus on some tighter “source control” – one of the problems was very embarrassing as I had not included a column within a SQL table – which caused an entire module not to function as expected.
The only defence that I can offer up at this stage would be – that for the most part I am the only person doing the testing – therefore I can become “code blind” – so if there are any folks out there whom would like to be testers let me know.
Anyhow – the patch is available for download below – and contains fixes for the following reported issues:
OOOCTA Interface Fixes
When using the OOOCTA application to set an Out of Office for a user – and you enter in a ‘ (single quote) in either the Internal or External message boxes – the following error is thrown by the application:
Server Error in '/OOOCTA_Interface' Application. Incorrect syntax near the keyword 'in'. Unclosed quotation mark after the character string ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: Incorrect syntax near the keyword 'in'. Unclosed quotation mark after the character string ')'. Source Error: Line 258: Line 259: myConnection.Open(); Line 260: myCommand.ExecuteNonQuery(); Line 261: } Line 262:
This problem was caused by the SQL logic not stripping single quotes from the Execution query – and therefore adds an additional column to the SQL stream – causing an unhandled exception to be raised.
The SQL logic has been updated to handle single quotes in the SQL stream.
When trying to set an OOF for a user – you enter in the name of the user and click on the check button and nothing happens.
Although this issue does not seem to affect all configurations, the issue stems from the OOOCTA interface not properly handling values from Active Directory which are not populated (e.g. Department).
In this update the code has been updated to handle blank values from Active Directory.
When using the Disable OOF for a given user – when clicking on the confirmation button (after checking for the existence of the user) nothing happens.
Due to a missing column within the tbl_DisableOOFUser table in the OOOCTA_DB – clicking on the confirm button produced a hidden exception and therefore not completing the SQL transaction which adds the user to the database.
The update contains a SQL file which upgrades the OOOCTA_DB so that the column is present – therefore fixing the issue.
After installing the application – when accessing the System Log or the Audit log – the following unhandled exception was thrown by the OOOCTA_Interface:
Server Error in '/OOOCTA_Interface' Application. The connection name 'oofSampleConnectionString' was not found in the applications configuration or the connection string is empty. Source Error: Line 192: Line 193: Line 194: Source File: c:\Program Files\OOOCTA35\Interface\SystemLogging.aspx Line: 194
Both the System Logging and Audit ASPX files contained a pre-release data source entry entitled “oofSampleConnectionString” – as well as the RTP “CoreCS” connection string. The “oofSampleConnectionString” was not present in the RTP web.config file as it was not required.
The erroneous connection entry has been removed from the pages contained within the within the patch.
When scheduling a report on an existing set of OOF settings for a user – the only way to view the results was via e-Mail.
Not strictly a problem – but more of an inconvenience. In essence you could only view OOF reports via e-mail.
The patch contains a new ASPX page, that allows for users to view the contents of the tbl_User_OOFEnabled table within the database. In addition the OOOCTA Command Processor Service has been modified to not clear this table automatically.
Please note – this is a patch release, not the full version of the product – you will need to have the RTP (Release to Public) version of OOOCTA installed before applying this patch.
Download the above patch to your OOOCTA Server.
Double click on the “ooocta351-Patch1.msi” and follow the installation wizard through (see below). When asked for an install location ensure that you have chosen the original installation location of the OOOCTA 3.5 RTP binaries as there are a number of files that need to be overwritten by the patch with new versions.
NOTE: Before you update the OOOCTA with Patch 1 you MUST stop the OOOCTA Command Processor Service from within the Windows Service manager – if you do not do this, the service binary will not be updated to the latest version.
The installation of the patch is pretty straight forward, and involves a simple setup wizard – and the execution of a batch file to update the OOOCTA_DB SQL database – detailed steps are below.
After you have double clicked on the “ooocta351-Patch1.msi” setup file – you will be presented with the following screen:
Click on the “Next” button
You will be asked for the location of the EXISTING OOOCTA installation (by default this is c:\program files\ooocta35\) – if you changed the default path when you originally setup OOOCTA you will need to browse the installation location. When you have located the path of the original location – click on the “Next” button.
You will be asked to confirm your settings – click on the “Next” button.
When the OOOCTA Patch setup has completed – you will be presented with the installation complete dialog (above) – click on the Finish button to exit the wizard.
When the binary setup is completed, you will need to navigate to the SQL folder which is located within the root directory of the OOOCTA binary files (this is by default c:\program files\OOOCTA35\SQL\) – see below
From within this location you will see a file entitled “SQLEXPRESS-updateOOCTADB.cmd” – if you are using SQL Express and your instance name is “localhost\SQLEXPRESS” double click on this file to update the OOOCTA DB – see below;
You will be asked to press “any key” to continue before the update takes place – hit the space bar to begin the update process.
When the Database has been updated you will be presented with the following screen:
You can now restart the OOOCTA Command Processor Service.
NOTE: If you are not using SQL Express or the default SQL instance is not localhost\sqlexpress – you will need to open the “ModifyOOCTADB.sql” file in SQL Management studio (after connecting to the correct SQL instance) and execute the file.
I would like to thank Stan Cooper and Andrew Pretty for their support and valued feedback which has contributed to the updates provided in Patch 1 – and I urge anyone whom is experiencing problems with OOOCTA to let me know. If I am made aware of issues I will endeavour to fix them as soon as I can.