Manage Email Signatures Centrally - For All Users

djbart0n · Not too shy to talk Joined: 10 Apr 2008 Posts: 8

Hi,

When running signowa.exe for the 1st time i get the following error:

C:\signowa>signowa.exe -v
Using the url: https://server/exchange/
An OLE DB Provider was not specified in the ConnectionString. An example would be, 'Provider=SQLOLEDB;'.

Below is the connection string in the registry

"Settingsdatabase"="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\server\eMailSignature\settings.mdb"

Any help would be much appreciated

bchecketts · Posted: Thu Jul 10, 2008 2:09 pm Post subject:

Whilst i cant offer any help, i am having the exact same issue!

This is my string, maybe i am going mad!!
"Settingsdatabase"="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=s:\owa\settings.mdb"

Dave Culley · Posted: Thu Jul 10, 2008 3:26 pm Post subject:

Hi,

I have been looking at your queries on OWA deployment, and the issue seems to lye with using '\' symbols. You will need to amend these in the registry.

Please follow the instructions in this post and let me know if this does not resolve your issues.

Thanks

bchecketts · Posted: Thu Jul 10, 2008 4:23 pm Post subject:

Thanks for the tip. i habe replaced \ with \\ and i still get the same result

Bjarne Mess · Posted: Fri Jul 11, 2008 2:34 pm Post subject:

If you write '\' characters to registry you need to add an extra.

E.g:
\\server\share\settings.mdb

would be

\\\\server\\share\\settings.mdb

You can also write directly in the registry, but then you don't need any doubles. You only need that if you add the entries in a script.

djbart0n · Not too shy to talk Joined: 10 Apr 2008 Posts: 8

Hi,

I've also made the following amendment but its made no difference.

"Settingsdatabase"="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\\\server\\eMailSignature\\settings.mdb"

Any further thoughts on the issue?

Thanks

Dave Culley · Posted: Thu Jul 17, 2008 8:23 am Post subject:

These errors have occured due to the registry settings for OWA being slightly wrong. Please check your registry settings are OK and point to your server/exchange rather than a generic one, and ensure the settings database string is also cortrect.

I know the 2 customers having this issue are now solved, this is purely for future reference!