Yes, I’m one of those “Windows Users”! 
Where, exactly are the instructions for installing Backendless Pro (Community Edition) on a Windows Server 2019 server?
Docker Desktop does not run on a Windows Server, and I remember previously that there was a dedicated installer just for Windows in the past.
Also, if there are any instructions for us poor Windows users, that would be extremely appreciated!
Thanks!
Mike
Hi Mike,
Docker Desktop is required to install Backendless Pro. You can find the Docker Desktop requirements for Windows here:
Btw, Windows Server 2019 has reached its end of life and is no longer supported by Microsoft:
Regards,
Mark
Thanks @mark-piller
I’m going to upgrade the Windows Server 2019 server to Windows Server 2022 eventually
I managed to get Docker Desktop and Backendless Pro 7.0.14.1 installed (On Windows 11) but I’m getting a bunch of errors on MySQL, RT Server, TaskMan, Redis, MongoDB, Server, and CodeRunner-JS on a fresh deployment.
On the console, all of the services I just mentioned won’t transition out of “Changing”.
I’m getting the following errors for MySQL, which I figured is a pretty good place to start:
2024-07-11T14:13:54.799657110Z [Entrypoint] MySQL Docker Image 8.0.32-1.2.11-server
2024-07-11T14:13:54.861165663Z [Entrypoint] Initializing database
2024-07-11T14:13:54.875369016Z 2024-07-11T14:13:54.868046Z 0 [Warning] [MY-011068] [Server] The syntax ‘–skip-host-cache’ is deprecated and will be removed in a future release. Please use SET GLOBAL host_cache_size=0 instead.
2024-07-11T14:13:54.875393213Z 2024-07-11T14:13:54.868068Z 0 [Warning] [MY-011070] [Server] ‘Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it’ is deprecated and will be removed in a future release.
2024-07-11T14:13:54.875397892Z 2024-07-11T14:13:54.868337Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.32) initializing of server in progress as process 17
2024-07-11T14:13:54.875401379Z 2024-07-11T14:13:54.873699Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-07-11T14:13:54.875404666Z 2024-07-11T14:13:54.875213Z 0 [ERROR] [MY-010187] [Server] Could not open file ‘/var/log/mysql/mysqld.log’ for error logging: Permission denied
2024-07-11T14:13:54.875408052Z 2024-07-11T14:13:54.875268Z 0 [ERROR] [MY-013236] [Server] The designated data directory /var/lib/mysql/ is unusable. You can remove all files that the server added to it.
2024-07-11T14:13:54.875703930Z 2024-07-11T14:13:54.875273Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-11T14:13:54.875714320Z 2024-07-11T14:13:54.875373Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.32) MySQL Community Server - GPL.
Connection to the pod is ended. Please disconnect and try reconnect again
What are the procedures for correcting this issue in a Docker-based deployment?
Hi Mike,
You would need to purchase support so we can assist you with the product. Once the support is purchased, the procedure is to post a private support incident and our team provides assistance.
Regards,
Mark
Hello @mark-piller
You mean the product that’s supposed to work out-of-the-box?
Following your posted procedures for installing it?
Mike
Yes, that’s exactly what I mean. Our product does work out of the box, however there is a ton of other things that may go wrong or be misconfigured. Welcome to the wonderful world of sysadmins
I just want to verify that these are the most up-to-date procedures for installing: GitHub - Backendless/pro-manager
I’m following the instructions for AWS - Windows
Thanks
Mike
Hello @Michael_Kadron,
Apologies for the inconvenience. We have successfully reproduced the issue with starting Backendless PRO on Windows. Our team is currently working on a fix, and we will update you as soon as it’s resolved.
Thank you for your patience.
Best regards,
Serhii
hello @Michael_Kadron
we have fixed the issue with installation. I have tested it for Windows 11. You should totally remove the installation, reset kubernetes and remove the mount folder. The install again.
That’s much better!
But I’m still getting an error for bl-server:
java.sql.SQLException: Access denied for user ‘root’@‘10.1.0.114’ (using password: YES)
2024-07-12T23:26:22.830109311Z at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130)
And this error for bl-taskman:
2024-07-12T23:28:52.602876447Z at com.backendless.taskman.TaskManager.main(TaskManager.java:71)
2024-07-12T23:28:52.603033557Z 23:28:52.602 [INFO] WaiterService - SQL database ‘main_backendless’ is not accessible. Error message: Access denied for user ‘root’@‘10.1.0.113’ (using password: YES). Waiting for 3000 millis before retry…
BTW, I got my server upgrade finished and I’m running Docker Desktop on Windows Server 2022 now.
Mike
hello @Michael_Kadron
looks like you have not removed the folder of pro manager, before re-install. So you have to:
Hello @sergey.kuk,
That worked perfectly, thanks!
I have another issue now, the license key that I was emailed doesn’t work in Pro-Manager when I try to add it.
What’s interesting, is I’ve never actually gotten this far on all of my previous tries.
The license starts with: 50D745CA-8C56-4C4B…
How does the licensing work with the “Community Edition” version that Mark talked about on that previous video? He said that it would be free for a single instance.
Do we have to request an additional license every month?
Mike
Hello, @Michael_Kadron.
Can you please give more information about your issue? Which error do you receive and where this error occurs?
Regards, Nikita.
When I launched the Web Console for the first time, a popup appears asking for the license key.
I don’t receive an error when I click on “Save License Key” to save the entered license.
Nothing happens at all.
I tried refreshing the page and trying several times.
Mike
Can you show bl-server’s logs pls?
@Michael_Kadron as you have reset kubernetes, the cluster id has been changed. That is why the system decide that you are trying to install backendless on the other cluster with the same license, I have added your cluster id to your license. Just restart bl-server and everything should be fine