Unable to login after windows 10 update

LogicalDOC has many interesting features, but requires some configuration process to show its full potential.

Moderator: car031

Post Reply
alcombo
Posts: 1
Joined: Mon May 08, 2017 11:54 am

Unable to login after windows 10 update

Post by alcombo » Tue May 09, 2017 9:49 am

Dear All,
I'm a fairly newbie on LogicalDoc (and associated software), but I successfully installed some time ago "LogicalDoc Community 7.5.3" edition on a Windows 10 machine. Everything worked fine, until a ("unsolicited") Window10 update.
After that the tomcat server no longer start on windows startup (but I was able to start it manually)... and recently the system stopped altogether because I started to get a message of "Access Denied" on ANY of the user accounts.

If I can´t recover this, I could try to re-install LogicalDoc... but i really would like to recover stored docs.

Can someone help me identify (and solve) the problem?

Running "logicaldoc start" I have the following prompt (partial):
Please note the initial warning (first line) regarding 64-bit server and the following
log4j:WARN No appenders could be found for logger (com.logicaldoc.util.config.XMLBean).
log4j:WARN Please initialize the log4j system properly.
that I think may be causing this problem.

Thank you for your attention.

Code: Select all

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
08-May-2017 11:28:36.686 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.0.35
08-May-2017 11:28:36.688 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          May 11 2016 21:57:08 UTC
08-May-2017 11:28:36.688 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.0.35.0
08-May-2017 11:28:36.688 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Windows 10
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            10.0
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             C:\Program Files\Java\jdk1.8.0_121\jre
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_121-b13
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         S:\Web\LogicalDoc\tomcat
08-May-2017 11:28:36.689 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         S:\Web\LogicalDoc\tomcat
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx1400m
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=128m
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.net.preferIPv4Stack=true
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dorg.apache.el.parser.COERCE_TO_ZERO=false
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.awt.headless=true
08-May-2017 11:28:36.690 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
08-May-2017 11:28:36.691 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=S:\Web\LogicalDoc\tomcat\conf\logging.properties
08-May-2017 11:28:36.692 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
08-May-2017 11:28:36.692 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=S:\Web\LogicalDoc\tomcat\endorsed
08-May-2017 11:28:36.693 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=S:\Web\LogicalDoc\tomcat
08-May-2017 11:28:36.693 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=S:\Web\LogicalDoc\tomcat
08-May-2017 11:28:36.694 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=S:\Web\LogicalDoc\tomcat\temp
-----
08-May-2017 11:28:37.202 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.35
08-May-2017 11:28:37.212 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory S:\Web\LogicalDoc\tomcat\webapps\ROOT
08-May-2017 11:28:51.318 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
log4j:WARN No appenders could be found for logger (com.logicaldoc.util.config.XMLBean).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Instantiate concrete PluginRegistry: com.logicaldoc.util.plugin.DefaultPluginRegistry
Searching for plugins in S:\Web\LogicalDoc\tomcat\webapps\ROOT\WEB-INF\lib
Found plugin file: logicaldoc-cmis-7.5.3-plugin.jar
Found plugin file: logicaldoc-core-7.5.3-plugin.jar
Found plugin file: logicaldoc-dropbox-7.5.3-plugin.jar
Found plugin file: logicaldoc-gui-7.5.3-plugin.jar
Found plugin file: logicaldoc-webdav-7.5.3-plugin.jar
Found plugin file: logicaldoc-webservice-7.5.3-plugin.jar
Succesfully registered 6 plugins
.....
plugin located: jar:file:S:\Web\LogicalDoc\tomcat\webapps\ROOT\WEB-INF\lib\logicaldoc-core-7.5.3-plugin.jar!/plugin.xml
Activated plugin logicaldoc-core
08-May-2017 11:29:01.639 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory S:\Web\LogicalDoc\tomcat\webapps\ROOT has finished in 24,426 ms
08-May-2017 11:29:01.645 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
08-May-2017 11:29:01.652 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-bio-8443"]
08-May-2017 11:29:01.652 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 24473 ms


car031
Posts: 154
Joined: Tue Apr 17, 2012 8:27 am

Re: Unable to login after windows 10 update

Post by car031 » Tue May 09, 2017 2:04 pm

Look at the log file S:\Web\LogicalDoc\repository\logs\dms.log looking for some kind of errors

agaspa
Posts: 514
Joined: Tue Apr 20, 2010 8:24 am

Re: Unable to login after windows 10 update

Post by agaspa » Tue May 09, 2017 2:08 pm

Hi alcombo,
most probably you run manually or an automatical update occurred of the Java virtual machine installed into the system (Windows).

So dependening on the configuration of the LogicalDOC system service it has stopped working because it can't correctly locate the position of native library jvm.dll

You should open a shell (command prompt) as Administrator, change dir to LogicalDOC\tomcat\bin directory and run the commands

Code: Select all

cd S:\Web\LogicalDoc\tomcat
tomcat8w.exe //MS/LogicalDOC-Community
then select the Java tab and adjust the location of Java Virtual Machine
see the attached image
Attachments
ScreenHunter_1002 May. 09 15.02.gif
JVM path
ScreenHunter_1002 May. 09 15.02.gif (41.12 KiB) Viewed 674 times

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest