I am considering entering myself for “plonker of the year” award.

I have been working with a chap called Aaron whom e-mailed me stating that he was getting the following error when trying to configure the service account within the ASP setup for the OOOAA tool:

The following error occurred: Provider is not specified and there is no designated default provider. 3753 setup did not complete.

This at first perplexed me as during my testing the tool worked just fine (it always does for some reason) – however after a little research it would appear that when running ASP applications on Windows 2003 x64 that use Jet to update databases (the OOOAA tool uses Jet to modify the OOO database) this is a common error.

Of course when I developed the application and indeed tested it at home I have been using x32 Windows 2003 with the x32 bit version of Exchange server 2007 – therefore everything did work correctly .

Never the less I am looking into a fix for this issue and will provide and update very soon.

**** UPDATE – 6/07/2008 ****

I have done some more detailed investigation into the issue and, alas it appears a little more in depth than I thought.

Although Windows 2003 x64 (which you CAS servers will be running as a minimum) does have a x32 ODBC drivers set which will allow you to “mangle” the ASP and Database backend to work - the PS Execution script will not talk with the database under any circumstances as the Powershell code executes under the x64 environment.

Anyway the long and shot of this is that there is far to much messing around with a production server to warrant this version to be used – so I have pulled it from the site.

I am currently working on a redesign of the tool which I hope to have available soon. Many apologies for this screw up.