running Beta2 on ExchangeServer 2007 (Windows 2003 R2 X86)

Just installed the software and did my basic 5-step configuration like described in the help file. Testing the disclaimer failed. Tried to restart the service (I think, it was running right after installation), but restart aborted.

Now I'm getting following errors in my eventlog while trying to start the "DisclaimIt Management Service" manually:

Event-ID: 5000

EventType clr20r3, P1 netal.disclaimit.rtfprocessor, P2 4.0.360.0, P3 488370c9, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp .

Event-ID: 5000

EventType clr20r3, P1 hdkmnqfkc3fcehfya4bzeg2aykvno151, P2 4.0.360.0, P3 488370c7, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp .

please perform the following steps:

1. Open Task Manager, select Processes and look for a process with the name Netal.DisclaimIt.RtfProcessor.exe. If the process exists, kill it (End Process).

2. Uninstall Beta 2. Afterwards verify that the installation directory has been completely removed. If not, delete it manually.

3. Download the final version released today and install it.

4. Configure it and test it out. Tell me of any problems you experience.

-Franz

did like described above - with no luck.

The stated process wasn't in process list and isn't after fresh installation. Service won't start, but now, there are three messages in event log on service start.

Event ID 5000

EventType clr20r3, P1 netal.disclaimit.rtfprocessor, P2 4.0.400.0, P3 48b5925b, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

Event ID 5000

EventType clr20r3, P1 hdkmnqfkc3fcehfya4bzeg2aykvno151, P2 4.0.400.0, P3 48b59259, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

Event ID 5000

EventType clr20r3, P1 netal.disclaimit.rtfprocessor, P2 4.0.400.0, P3 48b5925b, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

- Jörn

1.

- Enable diagnostics logging to file for all categories with log level Maximum (DisclaimIt Manager->Server properties->Diagnostics).

- Edit the file Netal.DisclaimIt.RtfProcessor.exe.config, by replacing '<add key="LogLevel" value="None"/>' with '<add key="LogLevel" value="Maximum"/>'.

- Start Netal.DisclaimIt.RtfProcessor.exe in File Explorer. What happens? Is a windows displayed for some seconds? An error message displayed?

- Start the service.

- If there are log files in <InstallDir>\Diagnostics\TraceLogs, please send them to me (franzk@netal.com).

2. Please check the NTFS-permissions of <InstallDir> and below. Has the SYSTEM account full control on all directories and files?

3. Because you mentioned in your first post that you're running on Windows 2003 R2 X86, I assume that you are evaluating DisclaimIt on an MXS test system (32bit), possibly running in a virtual machine. Do you have the option to try DisclaimIt on another MXS 2007 server?

-Franz

thanks a lot for the quick responses!

1. Did like described:

The Netal.DisclaimIt.RtfProcessor.exe doesn't start. No Window, no error dialog. Only another Event-Log entry:

Event ID 5000

EventType clr20r3, P1 netal.disclaimit.rtfprocessor, P2 4.0.400.0, P3 48b5925b, P4 mscorlib, P5 2.0.0.0, P6 471eb8e7, P7 5395, P8 62, P9 n51cffzwz1gffvslvrub5uxq1gvd0txu, P10 NIL.

The Service won't start as before. The TraceLogs directory is filled with three files. Only the "MessageProcessor" has a size with more than 0 Bytes. It's on the way to the stated address.

2. Permissions are given. Admins and System have full access rights.

3. I'm sorry for my favorite typo. It's a productive environment with a W2K3 R2 *x64* System.

Thanks a lot so far

Jörn

Jörn (thank you very much) helped me to find a bug which went undetected during the beta phase:

The service DisclaimIt Management fails to start if DisclaimIt 4.0 is installed on a non-English version of Windows.

A new build (4.0.401) of DisclaimIt 4.0, which resolves this issue, has been released yesterday. If you are already using the first released build (4.0.400) of DisclaimIt 4.0 on an English version of Windows, there's no need to uninstall 4.0.400 and then install 4.0.401.

-Franz

thanks for the new version.

Service is now starting, rtfprocessor-process is in tasklist ... but (sorry):

Added again a 5-step configuration and activated it for one sender. All debug logs on maximum. The "ignored" debug directory is filled as estimated. The "processerd" (both "Before" and "After") directories aren't. In event log for every message that should be processed by the transoprt rule an event is generated:

----------------

Event ID: 3000

An exception occurred in the message handler: An error occurred while processing the request on the server: System.Security.SecurityException: Ein anonymer Sicherheitsebenentoken kann nicht geöffnet werden.

at System.Security.Principal.WindowsIdentity.GetCurrentInternal(TokenAccessLevels desiredAccess, Boolean threadOnly)

at System.Security.Principal.WindowsIdentity.GetCurrent()

at System.Runtime.Remoting.Channels.Ipc.IpcServerTransportSink.ServiceRequest(Object state)

The Zone of the assembly that failed was:

MyComputer

----------------

In MessageProcessor.log, the messages occurs like:

------------------

2008-09-01 09:34:43 (#4960): A new agent has been successfully initialized.

2008-09-01 09:34:43 (#4960): The message handler was called by the MS Exchange Transport to process a routed message.

2008-09-01 09:34:43 (#4960): An exception occurred accessing the rich text management object: An error occurred while processing the request on the server: System.Security.SecurityException: Ein anonymer Sicherheitsebenentoken kann nicht geöffnet werden.

at System.Security.Principal.WindowsIdentity.GetCurrentInternal(TokenAccessLevels desiredAccess, Boolean threadOnly)

at System.Security.Principal.WindowsIdentity.GetCurrent()

at System.Runtime.Remoting.Channels.Ipc.IpcServerTransportSink.ServiceRequest(Object state)

The Zone of the assembly that failed was:

MyComputer

2008-09-01 09:34:43 (#4960): The message does not contain a status header.

------------------

The mails got send, but without disclaimer - and no logging in any message directory.

Regards

Jörn

thank you very much for pointing out this new bug, which I introduced (I'm really sorry about it) when fixing your initial problem.

This new bug was fixed in the meantime (build 402 is already available for download).

To save you the effort of configuring DisclaimIt again after uninstalling build 401 and installing 402, you can save the content of <InstallDir>\Data\Configuration\Settings to a backup location before uninstalling build 401. After installing build 402, copy the saved files back to <InstallDir>\Data\Configuration\Settings.

-Franz

Thanks a lot for your fast and non-complicated help, Franz.

Now I got another issue with html messages, but I will start another thread for it.

Jörn