NET HELPMSG 3547
Posted: Thu Oct 19, 2017 4:52 pm
Hello there,
This is partially related to ticket "Cannot connect to MSSQL Server" as it is next step in its solution... but as this new issue seems as new and not much related to the original MS SQL Problemproblem, I am setting new topic. If I'll manage to resolve it, then the old ticket can be closed also later on.
Basically I cannot start the LogicalDoc services. Below is the content of the installation.log file... the More help is available by typing NET HELPMSG 3547. message just keeps repeating beyond the copied content of the log below... Not sure where should I type it as the message is found in log...
Please, help.
Thu Oct 19 10:28:37 SGT 2017 - INFO - Checking Java availability for architecture 64bit
Thu Oct 19 10:28:37 SGT 2017 - INFO - Unable to find a JDK in the registry, check the fileaystem
Thu Oct 19 10:28:37 SGT 2017 - INFO - Search for java into C:\Program Files\Java
Thu Oct 19 10:28:37 SGT 2017 - INFO - Found JDK home: -
Thu Oct 19 10:28:38 SGT 2017 - INFO - Java output:
java version "1.8.0_144"
java(tm) se runtime environment (build 1.8.0_144-b01)
java hotspot(tm) client vm (build 25.144-b01, mixed mode, sharing)
Thu Oct 19 10:28:38 SGT 2017 - INFO - Architecture of Java C:\Program Files (x86)\Java\jre1.8.0_144: 32bit
Thu Oct 19 10:28:39 SGT 2017 - INFO - Java output:
java version "1.8.0_144"
java(tm) se runtime environment (build 1.8.0_144-b01)
java hotspot(tm) client vm (build 25.144-b01, mixed mode, sharing)
Thu Oct 19 10:28:39 SGT 2017 - INFO - Architecture of Java C:\Program Files (x86)\Java\jre1.8.0_144: 32bit
Thu Oct 19 10:28:39 SGT 2017 - INFO - Unable to find a JRE in the registry, check the fileaystem
Thu Oct 19 10:28:39 SGT 2017 - INFO - Search for java into C:\Program Files\Java
Thu Oct 19 10:28:39 SGT 2017 - INFO - Found JRE home: -
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\conf\context.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\conf\build.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\tomcat\conf\server.xml
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\loader\build.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\loader\build.xml
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\tomcat\bin\service.bat
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\bin\logicaldoc.bat
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\bin\logicaldoc.sh
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\update-wd\service.bat
Thu Oct 19 10:28:53 SGT 2017 - INFO - Using architecture: 64bit
Thu Oct 19 10:28:53 SGT 2017 - INFO - Activating UserNo: 0001-6B4D4E6F-9DE5-4CA0-8D44-3B4F92D86A9C
Thu Oct 19 10:28:53 SGT 2017 - ERROR - Got LM response: 200 - OK
Thu Oct 19 10:28:54 SGT 2017 - INFO - License activation: ok
Thu Oct 19 10:29:33 SGT 2017 - INFO - out:The LogicalDOC service is starting.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:The LogicalDOC service could not be started.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:A service specific error occurred: 1.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:More help is available by typing NET HELPMSG 3547.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:36 SGT 2017 - INFO - out:The LogicalDOC Update service is starting.
Thu Oct 19 10:29:36 SGT 2017 - INFO - err:The LogicalDOC Update service could not be started.
This is partially related to ticket "Cannot connect to MSSQL Server" as it is next step in its solution... but as this new issue seems as new and not much related to the original MS SQL Problemproblem, I am setting new topic. If I'll manage to resolve it, then the old ticket can be closed also later on.
Basically I cannot start the LogicalDoc services. Below is the content of the installation.log file... the More help is available by typing NET HELPMSG 3547. message just keeps repeating beyond the copied content of the log below... Not sure where should I type it as the message is found in log...
Please, help.
Thu Oct 19 10:28:37 SGT 2017 - INFO - Checking Java availability for architecture 64bit
Thu Oct 19 10:28:37 SGT 2017 - INFO - Unable to find a JDK in the registry, check the fileaystem
Thu Oct 19 10:28:37 SGT 2017 - INFO - Search for java into C:\Program Files\Java
Thu Oct 19 10:28:37 SGT 2017 - INFO - Found JDK home: -
Thu Oct 19 10:28:38 SGT 2017 - INFO - Java output:
java version "1.8.0_144"
java(tm) se runtime environment (build 1.8.0_144-b01)
java hotspot(tm) client vm (build 25.144-b01, mixed mode, sharing)
Thu Oct 19 10:28:38 SGT 2017 - INFO - Architecture of Java C:\Program Files (x86)\Java\jre1.8.0_144: 32bit
Thu Oct 19 10:28:39 SGT 2017 - INFO - Java output:
java version "1.8.0_144"
java(tm) se runtime environment (build 1.8.0_144-b01)
java hotspot(tm) client vm (build 25.144-b01, mixed mode, sharing)
Thu Oct 19 10:28:39 SGT 2017 - INFO - Architecture of Java C:\Program Files (x86)\Java\jre1.8.0_144: 32bit
Thu Oct 19 10:28:39 SGT 2017 - INFO - Unable to find a JRE in the registry, check the fileaystem
Thu Oct 19 10:28:39 SGT 2017 - INFO - Search for java into C:\Program Files\Java
Thu Oct 19 10:28:39 SGT 2017 - INFO - Found JRE home: -
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\conf\context.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\conf\build.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\tomcat\conf\server.xml
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\loader\build.properties
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configurations into C:\LogicalDoc\loader\build.xml
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\tomcat\bin\service.bat
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\bin\logicaldoc.bat
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\bin\logicaldoc.sh
Thu Oct 19 10:28:52 SGT 2017 - INFO - Save configuration into C:\LogicalDoc\update-wd\service.bat
Thu Oct 19 10:28:53 SGT 2017 - INFO - Using architecture: 64bit
Thu Oct 19 10:28:53 SGT 2017 - INFO - Activating UserNo: 0001-6B4D4E6F-9DE5-4CA0-8D44-3B4F92D86A9C
Thu Oct 19 10:28:53 SGT 2017 - ERROR - Got LM response: 200 - OK
Thu Oct 19 10:28:54 SGT 2017 - INFO - License activation: ok
Thu Oct 19 10:29:33 SGT 2017 - INFO - out:The LogicalDOC service is starting.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:The LogicalDOC service could not be started.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:A service specific error occurred: 1.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:More help is available by typing NET HELPMSG 3547.
Thu Oct 19 10:29:33 SGT 2017 - INFO - err:
Thu Oct 19 10:29:36 SGT 2017 - INFO - out:The LogicalDOC Update service is starting.
Thu Oct 19 10:29:36 SGT 2017 - INFO - err:The LogicalDOC Update service could not be started.