Unable to complete installation - 'Toems-API Keepalive.job' username / password incorrect
-
First of all, I want to thank the developer for making software like this, I used CloneDeploy to a minor extent and although the support dropped off, I can see he was hard at work making Theopenem. If Theopenem is as good in practice as on paper, I would love to support it.
Now onto the details; when running the initial installer on Server 2016 (via the MSI installer) I get the error "An error was encountered while creating a scheduled task: 'Toems-API Keepalive.job'. Error description: The user or password is incorrect." I suspect that upon creation of the user for the scheduled task, it gets locked out, and going to lusrmgr.msc to re-enable it, the password was never set properly.
If I choose to press "Ignore" the installation will complete, but of course it isn't correct. I am able to load up the IIS website via any browser on the network, but cannot log in, claiming "Unknown Error Obtaining Token". I assume this issue is a consequence of the issue above.
My company has set a lot of weird/pointless policies, so I have no doubt it's an issue with something in the Registry or Group Policy. I have full control over both, but I don't know where to look for this issue, and online appears to have very little info on the subject.
Thanks again for being awesome enough for developing something like this!
-
In order to rule out a gpo causing issues with the install, can you try installing Theopenem before you join the computer to the domain?
-
@theopenem_admin The server is not a part of any domain as of yet, so I’d guess it’s not a GPO issue.
-
To be clear, I mean it’s not an issue of Domain authority. I’m virtually positive it’s some dumb policy that someone with a good-idea fairy turned on because it has “security” in its description somewhere.
-
Can you give this updated installer a try?
https://github.com/theopenem/Toems/releases/download/v1.2.1/Theopenem-1.2.1.msi
-
@theopenem_admin Unfortunately a similar result. I took a picture with my phone. Installing it gave the same error, while the picture shows the Repairing action with the same result. 9B2A975F-6A00-46D1-8F24-BBA678AF4336.jpeg
-
@theopenem_admin Here's the MSI logfile: package.log
The line "Error 4106" specifies what I'm talking about. As a side note, I was able to install just fine on a absolutely clean Win10 Pro, but still can't on the Server 2016. I'm still virtually positive it's in the Group Policies somewhere. I've tried the Disabled setting for "Network access: Do not allow storage of passwords and credentials for network authentication" and it didn't seem to resolve the issue. -
Can you do a clean install of Server 2016 or is this the only available server?
-
@theopenem_admin Unfortunately this is the only available image I was given.
-
Just to be clear, did you reimage this machine after I released the 1.2.1 installer, or are you trying to reinstall 1.2.1 over the failed 1.2.0?
-
@theopenem_admin I did a clean install of 1.2.1 on a fresh (as in, what I've been given) image of Server 2016.
-
The log that was posted seem like it was trying to install over 1.2.0 which will cause problems. I would try to uninstall theopenem, then remove mariadb and try deleting the toemskeepalive user and try to install again.
-
@theopenem_admin So...I'm not sure who to be upset with, myself, or the people who made this image... As it turns out, some genius in the base image UNINSTALLED .NET frameworks...
Thanks for your help, I really appreciate it. After installing .NET Framework 4.8 it installed just fine on Server 2016.
