Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread EWBSRVR.EXE windows service won't run
Thu, Feb 4 2021 9:47 AMPermanent Link

Reijo Pitkanen

I tried to run Elevate Web Builder 3 Web Server windows service, both 32 bit and 64 bit versions with similar results. Starting the service from Computer Management console gives messagebox:
---------------------------
Services
---------------------------
The Elevate Web Builder 3 Web Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
---------------------------
OK   
---------------------------
Windows Event log gets error event ID: 0 with event data:
Service failed on start: '00:00:00' is not a valid time

EVBSRVR writes to system elog :
{ "Time": "2021-02-04T15:33:36.363Z", "Category": "Info", "ID": "ServerStop", "Details": { "Description": "Elevate Web Builder 3 Web Server", "Name": "EWBSRVR" } }

There is only one EVBSRVR instance installed at a time in this windows 10 pro computer.
The service is installed in admin command window like this:
c:\Program Files (x86)\Elevate Web Builder 3\bin\ewbsrvr\win32>ewbsrvr.exe /install

Service installed successfully

Command line ewbsrvr.exe runs just fine.

I don't know how to fiqure out what is wrong, any suggestions?
Thu, Feb 4 2021 2:21 PMPermanent Link

Anthony

Reijo Pitkanen wrote:

<<Service installed successfully

Command line ewbsrvr.exe runs just fine.

I don't know how to fiqure out what is wrong, any suggestions?>>

I had a problem with the ewbsrvr starting and immediately stopping tuned out to be another program using the same ports. I discovered this by copying the ewbsrvr.exe cmdline version overwriting the ewbsrvr installed as a service and running from an elevated command prompt. This then output the error message which I was able to resolve and then replace the executable with the win64 service.
Thu, Feb 4 2021 2:33 PMPermanent Link

erickengelke

Avatar

Anthony wrote:

Reijo Pitkanen wrote:

<<Service installed successfully

>> Command line ewbsrvr.exe runs just fine.

>> I don't know how to fiqure out what is wrong, any suggestions?>>

> I had a problem with the ewbsrvr starting and immediately stopping tuned out to be another program using the
> same ports. I discovered this by copying the ewbsrvr.exe cmdline version overwriting the ewbsrvr installed as a
> service and running from an elevated command prompt. This then output the error message which I was able to
> resolve and then replace the executable with the win64 service.

You can resolve that by running the following command in a CMD owned by Administrator:
netstat -ab | more

it will show ports open by various programs.

Erick
EWB Programming Books and Component Library
http://www.erickengelke.com
Thu, Feb 4 2021 10:10 PMPermanent Link

Alvaro

Hello, I am investigating the same problem with no results. I use the same cmdline server configuration as you do, and I get the following error:
{"Time": "2021-02-05T00: 00: 07.328Z", "Category": "Warning", "ID": "Authentication", "Details": {"Message": "The password for the Administrator user is still set to the default password "," Name ":" Administrator "}}.

Regarding the default password, the manual says the following:
"You should not deploy instances of the web server into production without first ensuring that such
instances have been properly configured so that the default Administrator password has been changed. For
both the 32-bit and 64-bit web server services, but not the console version of the web server included for
development purposes, the web server will log a warning into the system log if the default password is still
set for the pre-defined Administrator user. Please see the Web Server Logging topic for more information. "

I tried to change the password, so that it is stored in the database .db file, but without results.
How to do then to change the password?
Thank you!!
Thu, Feb 4 2021 10:41 PMPermanent Link

Alvaro

Apparently the problem is the localhost certificate. I managed to start the ewbsrvr service, leaving blank:
Certificate Name =
in ewbsrvr.ini.
Of course, without the name of the certificate, https does not respond.
The manual explains that the localhost certificate is for development purposes, it also clarifies that localhost was not issued by a certifying authority, so it is not used for production purposes, but except for the browser's warning, it should work the same as it works with the ewbsrvr.exe cmdline .
I do not get it......
Fri, Feb 5 2021 3:06 AMPermanent Link

Anthony

Alvaro wrote:

<<Apparently the problem is the localhost certificate. I managed to start the ewbsrvr service, leaving blank:>>

You can leave the Certificate Name blank or localhost but only the local computer browser will display the webpage without a certificate warning it can be viewed on other computers but will display a warning of this certificate is not trusted.

For deployment for use without a browser warning message you would need to purchase a signed certificate for myewb.mycustomdomain.com which can be installed in the Windows certificate store, allowing any external use to access the website of the chosen domain name without error. There is also an option to use LetsEncrypt for free certificates but I do not have experience of this
Fri, Feb 5 2021 6:00 AMPermanent Link

Reijo Pitkanen

erickengelke wrote:

>You can resolve that by running the following command in a CMD owned by Administrator:
>netstat -ab | more

I didn't find any port conflicts with netstat.
This is also supported by the fact that the command line server uses the same ports and runs smoothly on this same pc.
I wonder this  Windows event log event:
 "ID 0: Service failed on start: '00: 00: 00 'is not a valid time"
if this could be due to system country settings (Finland)? No it isn't, I changed the region settings to UK with the same result: the service starts and stops immediately, and the event "ID 0: Service failed on start: '00: 00: 00 'is not a valid time" is added into the windows event log .
I copied the 32-bit ewbsrvr.exe, ewbsrvr.ini and files related to my web service to another windows 7 pc, installed the ewbsrvr service and voila the service starts and works as it should.
What could I try next?
Fri, Feb 5 2021 11:03 PMPermanent Link

Alvaro

Hi all. Finally I found what was the problem for the ewbsrvr.exe service to work.
Everything related to the localhost certificate was installed as administrator.
The ewbsrvr.exe cmdline is also run as administrator.
The IDE is also run as administrator.
Well what was I missing ??
The service. Although the installation was done as administrator, I did not take into account that the initiation of it, is also configured as administrator.
In properties of the service, parameterize that the start was as administrator and finally the problem was solved.
Now, I don't know if it should work like this by design, or is it a particular situation in my Windows configuration.
I hope it helps.
greetings
Alvaro
Mon, Feb 8 2021 2:51 AMPermanent Link

Reijo Pitkanen

Thank you Alvaro! Great job!
I confirm that this solved the ewbsrvr.exe service startup problem. I changed the service to log in with my own credentials and now its up and running.
Better method would be to install a self-signed "localhost" certificate for the default local machine store,where the certificate will be usable by the EWB Web Server when running under Local System account .
Thu, Feb 11 2021 11:02 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Reijo,

<< I confirm that this solved the ewbsrvr.exe service startup problem. I changed the service to log in with my own credentials and now its up and running. >>

This is the first good lead on this issue.  I'll check it out and see if I can replicate the problem.

<< Better method would be to install a self-signed "localhost" certificate for the default local machine store,where the certificate will be usable by the EWB Web Server when running under Local System account. >>

The self-signed certificate is only for use with the IDE's Internal web server and the external command-line 32-bit web server for testing purposes.  It really shouldn't be used with the Windows service during any type of deployment.

Tim Young
Elevate Software
www.elevatesoft.com
Image