LocalDatabase has not created. Greylist test has not catch e-mail. RSS Back to forum
Hi Jason,
usually the local database gets created, after you enabled the test _and_ started the ORF Service. After that it should be there. If you like to use an external SQL Database, just use the SQL Database Whitepaper here:
http://vamsoft.com/support/docs/how-tos#activatetab-2
What kind of Exchange 2013 Deployment do you use?
http://vamsoft.com/support/docs/knowledge-base/deploy-exchange-2013
Regards
Norbert
@NorbertFe:
"usually the local database gets created, after you enabled the test _and_ started the ORF Service. After that it should be there"
It hasn't.
http://vamsoft.com/support/docs/how-tos#activatetab-2
I've used Guide for Microsoft® SQL Server 2008.
"What kind of Exchange 2013 Deployment do you use?"
Scenario B
@jasont:
Actually, the local database file (called greylist.abs) is created by the ORF service on demand, i.e., when the first email is Greylisted and the first record needs to be added to the database. I am not sure why this fails on your system, but one possible explanation is that the account running the ORF Service has insufficient rights to write the location configured to store the Greylisting database.
By default, the ORF Service runs under the LocalSystem account, have you changed this by any chance? What does the Windows Services snap-in shows for the ORF Service?
Have you changed the default location of the Greylisting database file? If so, does it point to a local folder, or a remote one?
As for the "DataBase Provider not exists" error: do you have the SQL Native Client package installed (which the connection string refers to)? E.g., if your connection string begins with "Provider=SQLNCLI11" you will need to have SQL Server Native Client 11.0 OLE DB Provider installed.
@Krisztián Fekete (Vamsoft):
"SQL Native Client"
Thanks. Miss this point.
"By default, the ORF Service runs under the LocalSystem account, have you changed this by any chance? What does the Windows Services snap-in shows for the ORF Service?"
Ok. I've will try.
"Have you changed the default location of the Greylisting database file? If so, does it point to a local folder, or a remote one?"
Change on another local disk. But nothing happens.
@jasont: Have any emails (which should have been Greylisted) arrived since you changed the Greylisting database location and saved the configuration? Have you switched back the External Database option to the Private Local Database one? Did ORF log anything related to the Greylisting test or database since, i.e., does it still say it cannot create the database file?
@Krisztián Fekete (Vamsoft):
No. No one email hasn't catch to greylist.
Use admin user to run service. Database not created.
Filters "before arriving" had not write to log file. I gess filters "Before Arriving" not work or not catch emails.
External database connect and work, but empty.
@jasont:
Before Arrival filtering will work only if ORF receives all emails directly. If there is another host in between the sender and ORF (e.g., non-transparent proxy/firewall) with an intranet IP address, ORF will skip all Before Arrival tests. In this scenario, the Greylisting test cannot be used. For more information, see these articles
http://vamsoft.com/r?o-orf-101
http://vamsoft.com/r?o-hto-fltrpointconcept
http://vamsoft.com/r?o-hto-adm-intermediatehostlist
By default, ORF logs blacklistings only at Before Arrival. You can enable logging of all events for troubleshooting in the Administration Tool (System / Log, ORF Text log - Configure, check everything on the Events tab).
Thank you wery much.
It really do. In test configuration our host relly emails from himself.
This problem "LocalDatabase has not created. Greylist test has not catch e-mail." on Windows 2012 Server Std. and Exchange 2013 Server. ORF trial.
Try to connect to external database(connect to installed on another machine SQL SERVER), but I has given error, what DataBase Provider not exists.
Help, please.