EAccessViolation/Access violation at address - ORF Forums

EAccessViolation/Access violation at address RSS Back to forum

1

Seems like in the Past week or so I've been getting the following Notifications. The only thing that's changes are I've added some entries to the Sender White List. I get about 20 at a time when it happens. This last was a Span of less then 2 Minutes. 8:31pm, no Backups running anywhere. Sometimes they are at 11:30PM or 1:40am.

Looks like it cannot communicate with a DC??


NOTIFICATION - ORF Enterprise Edition
===================================================================

The following event has occurred:

Server :
Class : System
Action : -
Severity : Error
Source : MSEXCHANGE
Filtering point : BeforeArrival
Related IP : 123.24.99.188
Sender :
Recipient(s) :
Email Subject : -

Description:
=================
Error validating the recipient "" (source: Active Directory). Getting rootDSE failed. EAccessViolation/Access violation at address 005A1C14 in module 'orfeesvc.exe'. Read of address 00000000.

by Scooter133 8 years ago
2

@Scooter133: This error is logged if ORF cannot detect the default Active Directory LDAP path (a.k.a. rootDSE) for the Active Directory-based Recipient Validation feature, thus it cannot check the valid recipient addresses. This should work automatically if the server ORF runs on is a domain member, but if it does not, you can work this around by setting the LDAP path manually:

1. Start the ORF Administration Tool
2. Expand Configuration / Tests / Recipient Validation in the left navigation tree
3. Click the "Configure selected" button under "Validation source: Microsoft Active Directory"
4. On the Directory tab select "Use the LDAP root specified below" and submit your LDAP root string.

If you have multiple domains (or child domains), using a GC:// instead of LDAP:// in the LDAP path will be needed (e.g. GC://servername/DC=domain,DC=com where servername is the name of your global catalog server). In case you have multiple domains in the same forest rather than child domains, the LDAP root should be GC://servername.

5. Set the authentication info (if your Active Directory requires authentication) on then Authentication tab

Note that the user name format required may depend on your AD settings, for example, it can be DOMAIN\user, [email protected] or user. If none of them works, try with blank user name and password fields or with authentication disabled

6. Finally, click OK and save your settings by pressing Ctrl + S (or select Configuration | Save Configuration from the main menu)

by Krisztian Fekete (ORF Team) 8 years ago
(in reply to this post)

3

It only happens for 2 minutes or so in a day and maybe 1-2 times a week if that. We get 40-60k e-mails a month and it is working otherwise...

So maybe the roodDSE that it thinks is the right one is busy?

by Scooter133 8 years ago
4

@Scooter133: It is hard to tell. I guess something happens with the AD server periodically (it syncs with another server, or getting updated, or something like that) and it is unavailable for these short periods. I'd cross reference the ORF logs with the Windows Event Log messages to check what was going on the AD server when ORF logged these errors.

by Krisztian Fekete (Vamsoft) 8 years ago
(in reply to this post)

5

Does ORF log the server it is trying to Sync with? We have several AD DCs and it would be easier if I could narrow it down.

Thanks,

by Scooter133 8 years ago
6

@Scooter133: ORF does not log the server name, but you can easily identify it by downloading our AD test tool from http://www.vamsoft.com/downloads/adtest.zip, extracting it to a folder on the server ORF is installed to, running the executable called "adtest.exe", and clicking the "Get LDAP root" button. This will show you the very same LDAP path ORF detects automatically (and uses for Recipient Validation).

by Krisztian Fekete (ORF Team) 8 years ago
(in reply to this post)

New comment

Fill in the form below to add a new comment. All fields are required. If you are a registered user on our site, please sign in first.

It will not be published.
hnp1 | hnp2