#290 Davmail 4.7.3 service does not start on 64 bit server

[Cristiano Guadagnino]

Since updating to v4.7.3 the service does not start anymore.
This is on Windows Server 2008 R2 Standard.

Trying to start davmailservice64.exe from the command line gives this:

C:\Program Files (x86)\DavMail>davmailservice64.exe

C:\Program Files (x86)\DavMail>[info] Module Name: C:\Program Files (x86)\DavMail\davmailservice64.exe
[info] Module INI: C:\Program Files (x86)\DavMail\davmailservice64.ini
[info] Module Dir: C:\Program Files (x86)\DavMail\
[info] INI Dir: C:\Program Files (x86)\DavMail\
[info] Configured vm.location: (null)
[info] Found VM: C:\Program Files\Java\jre7\bin\server\jvm.dll
[info] Generated Classpath:
[info] VM Args:
[info] vmarg.0=-Djava.class.path=
[info] Registering natives for Native class
[warn] Could not find Native class
 [err] No main class specified

Java version:

C:\Program Files (x86)\DavMail>java -version
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)

Please help

Cris

[Mickael Guessant]

Indeed, for some reason the ini config file was missing
=> should be fixed in subversion at:
https://svn.code.sf.net/p/davmail/code/trunk/src/winrun4j

[Markus Borst]

Placing the davmailservice64.ini in the davmail directory allows the service to run.
I did not test the new version of davmail64.exe, since it is not available on the official download site of the project.

Just to clarify: There never was a davmailservice64.ini (nor a davmailservice.ini) file in the distribution, at least I cannot find such a version. Therefore the ini file was apparently optional and still is with the 32bit version.

[Cristiano Guadagnino]

Mickael, using the files from subversion trunk works for me.
Thank you!!
Cris

[Mickael Guessant]

A bit more information on this: DavMail exe files are just Winrun4j with updated icon and embedded ini file => for some reason ini file was not embedded during upgrade.

WinRun4J can also run with a separate ini file instead of the embedded one.
=> that's the reason why downloading the ini file fixed your issue.