Manage Email Signatures centrally from your Desktop - For All Users

mlouie · Just can't stay away Joined: 19 Jul 2007 Posts: 46

I am trying to set up SignOWA on the Exchange Server. We are running Exchange Server 2007 SP1 on Windows Server 2003 R2 SP2, 64-bit. When I run "signOWA.exe -v" at the command prompt, I get the following output:

C:\SignOWA>signOWA -v
SignOWA, Version=7.0.0.0, Culture=neutral, PublicKeyToken=56390b2257d4df72
11/2/2009 1:14:32 PM

Unhandled Exception: System.InvalidOperationException: The 'Microsoft.Jet.OLEDB.
4.0' provider is not registered on the local machine.
at System.Data.OleDb.OleDbServicesWrapper.GetDataSource(OleDbConnectionString
constr, DataSourceWrapper& datasrcWrapper)
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString cons
tr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOpti
ons options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection o
wningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbC
onnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection ow
ningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection ou
terConnection, DbConnectionFactory connectionFactory)
at System.Data.OleDb.OleDbConnection.Open()
at OA.SignOWA.OleDbDataGateway.GetSettings()
at SignOWA.Program.Main(String[] args)

C:\SignOWA>

I have been following the steps in the Installation Guide for the OWA Module, manual version 7.2. The only posting here I could find that was related to this error was someone getting the error "The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine." on SBS 2008. We are not running SBS 2008 but Windows Server 2003 64 bit (as 64-bit is required for Exchange 2007).

You told them to enable 32-bit on IIS but I could not find any option to do that in the version of IIS that I have. You also told them to check that their MDAC and jet drivers are up to date. I checked and mine are up to date. I have msjet40.dll version 4.0.9505.0 which is the version for Server 2003 SP2. I have MDAC 2.8 SP2, which is the latest. I also tried putting double slashes in the Cockpit connection string, as you suggested. And I tried mapping a drive letter to the location of the settings.mdb on the network instead of using the UNC to it. I do not know what else to try.

Bjarne Mess · Posted: Fri Feb 12, 2010 7:33 am Post subject:

There is unfortunately no native 64 bit JET provider for Access included in 64-bit versions of Windows server, so that is why you see this error. You would probably have to upgrade to SQL Express or run signOWA on a 32 bit server if you want to continue using Access.

Thanks.
Bjarne

mlouie · Just can't stay away Joined: 19 Jul 2007 Posts: 46