Skip to Content (Press Enter)
2023-03-16 18-12-52
Michael Chu
966Views
16Comments
Solved
Lifetime: Admin Doesnt Have a Role
Question

Hi Guys,

I recently installed the lifetime.oap in our dev environment. I am currently encountering below issue.

Basically what I did was:

1. Set-up the Platform Service. 

2. Login to Service Center for the first time and change the Password.

3. Upload the License.

4. Create Users and Assign Role to the developers

5. Install the lifetime oap that is located at the Outsystems Installed Directory.

6. Access the lifetime url "servername/lifetimesdk", and redirected to the login page

7. Input the admin credential of the service center and I am getting this error. I have check the service center and the lifetime is already publish and the service center admin user has full control of it.




Any inputs appreciated.

Thank you



0
0
25 Sep 2018
Copy Link
2020-10-27 09-20-27
John Salamat
 
MVP
Solution

Posting here the instruction that was provided to me by Support when I experienced this issue


since you are not being able to login to LifeTime with admin credentials (admin doesn't have a role), it seems like something didn't go as expected when bootstrapping LifeTime's users.


This bootstrap operation is performed by a timer of the LifeTimeEngine eSpace at publishing time, in order to try to overcome this issue please proceed as follows:

  1. Restart the Scheduler Service because after the restart it will pick all the missing timers and run them;
  2. Access Service Center and go to the LifeTimeEngine eSpace;
  3. Select the Timers tab;
  4. Left click on the Bootstrap-timer;
  5. Activate the timer by pressing the 'Activate' button;
  6. Run the timer by pressing the 'Run Now' button;
  7. Check the timer log for this Bootstrap-timer and see if it finished executing without any errors.

You may also need to run the GrantAlllRolesToAdmin Timer manually (Users eSpace).


John

See solution in context
0
0
10 May 2019
Copy Link
2019-08-30 00-53-55
Tony Wang

Hi there.

Did your issue was fixed?

We installed the newest version and met the same question. It seems didn't be fixed.

We have performed the bootstrap operation and found that bootstrap is not working.

"Timer BootStrap error (inside action 'BootStrap'). Timer duration = 0 secs: The request failed with HTTP status 404: Not Found. [retry 3 of 3 scheduled]"

Tony

0
0
29 Oct 2019
Copy Link
2020-03-04 14-50-24
Armando Gomes

Hello,

Take a look at this documentation. Also, take a look at this post.


Cheers!

0
0
27 Sep 2018
Copy Link
2023-03-16 18-12-52
Michael Chu

Armando Gomes wrote:

Hello,

Take a look at this documentation. Also, take a look at this post.


Cheers!

Armando,

Right now are as a temporary solution we manually publish the code to the QQ/UAT Environment.

The project just started(license was bought September 2018) and I notice that the dev environment has unlimited AO and is about to expire in November while the QA/UAT Environment has 500AO Limit.

I think the dev environment license if I am not mistaken is a developer edition. Does it have something to do with this?

I also check the table mention in the thread the AUTH something table and currently it has no record at all since we never had the chance to login to lifetime(not even once) because of the issue.


0
0
29 Sep 2018
Copy Link
2020-07-21 19-28-50
Rajat Agrawal
Champion

Hi MIchael,


The project just started(license was bought September 2018) and I notice that the dev environment has unlimited AO and is about to expire in November while the QA/UAT Environment has 500AO Limit.

I think the dev environment license if I am not mistaken is a developer edition. Does it have something to do with this?

------> This is part of the license, they are providing you unlimited AO in dev but for QA/Prod you have 500AO limit.

OS license contains this features.


Thanks,

Rajat Agrawal

1
0
29 Sep 2018
Copy Link
2019-11-12 17-31-26
Justin James
 
MVP

We had the same problem. We worked with OutSystems support, there was a bug in the Lifetime solution. I do not know how the fix will be distributed (as a separate Lifetime fix or as a new version of the Platform Server), but the fix is there.

Suggest you reach out to OutSystems support for assistance to get up and running.

J.Ja

0
0
30 Sep 2018
Copy Link
2023-03-16 18-12-52
Michael Chu

Justin James wrote:

We had the same problem. We worked with OutSystems support, there was a bug in the Lifetime solution. I do not know how the fix will be distributed (as a separate Lifetime fix or as a new version of the Platform Server), but the fix is there.

Suggest you reach out to OutSystems support for assistance to get up and running.

J.Ja

Thank you for all your help guys. I will coordinate this issue with outsystems support.


0
0
01 Oct 2018
Copy Link
2020-10-27 09-20-27
John Salamat
 
MVP
Solution

Posting here the instruction that was provided to me by Support when I experienced this issue


since you are not being able to login to LifeTime with admin credentials (admin doesn't have a role), it seems like something didn't go as expected when bootstrapping LifeTime's users.


This bootstrap operation is performed by a timer of the LifeTimeEngine eSpace at publishing time, in order to try to overcome this issue please proceed as follows:

  1. Restart the Scheduler Service because after the restart it will pick all the missing timers and run them;
  2. Access Service Center and go to the LifeTimeEngine eSpace;
  3. Select the Timers tab;
  4. Left click on the Bootstrap-timer;
  5. Activate the timer by pressing the 'Activate' button;
  6. Run the timer by pressing the 'Run Now' button;
  7. Check the timer log for this Bootstrap-timer and see if it finished executing without any errors.

You may also need to run the GrantAlllRolesToAdmin Timer manually (Users eSpace).


John

0
0
10 May 2019
Copy Link
2019-08-30 00-53-55
Tony Wang

Hi there.

Did your issue was fixed?

We installed the newest version and met the same question. It seems didn't be fixed.

We have performed the bootstrap operation and found that bootstrap is not working.

"Timer BootStrap error (inside action 'BootStrap'). Timer duration = 0 secs: The request failed with HTTP status 404: Not Found. [retry 3 of 3 scheduled]"

Tony

0
0
29 Oct 2019
Copy Link
2019-04-04 15-41-14
Michael de Guzman

Hi,

I also had the same problem.  John's solution solved it:

"

This bootstrap operation is performed by a timer of the LifeTimeEngine eSpace at publishing time, in order to try to overcome this issue please proceed as follows:

  1. Restart the Scheduler Service because after the restart it will pick all the missing timers and run them;
  2. Access Service Center and go to the LifeTimeEngine eSpace;
  3. Select the Timers tab;
  4. Left click on the Bootstrap-timer;
  5. Activate the timer by pressing the 'Activate' button;
  6. Run the timer by pressing the 'Run Now' button;

"

Thank you.

0
0
18 Dec 2019
Copy Link
2024-05-03 14-03-28
Sudip Dey

Hi ,

I suggest to make a support ticket and it will be resolve first. 


Thank you,
Sudip

1
0
18 Dec 2019
Copy Link
2018-09-22 14-36-02
Kurt Vandevelde
 
MVP

Indeed, still the same issue as described above with the latest LifeTime platform version. I'll contact support also

0
0
05 Jan 2020
Copy Link
UserImage.jpg
Gayan De Saram

Hi

I'm getting the same issue, with Bootstrap timer :

HTTP status 404: Not Found

http://127.0.0.1/LifeTimeEngine/_TimerHandler.asmx (Method: POST)

Lifetime version is a bit old - 11.5.3.372

Checked IIS file is there and binding is set to 127.0.0.1 so not sure where the issue is
Before i ask support anyone know what the issue is ?

Thanks
Gayan

0
0
22 Jul 2020
Copy Link
2018-09-22 14-36-02
Kurt Vandevelde
 
MVP

To be sure, you tried to run the timer from the LifeTime service center? 

Are other timers running?

0
0
22 Jul 2020
Copy Link
UserImage.jpg
Gayan De Saram

Kurt Vandevelde wrote:

To be sure, you tried to run the timer from the LifeTime service center? 

Are other timers running?

 Hi

Yup, double checked if other timers are running and by the looks of things. It's a solid no All Lifetime Engine timers seem to have the same issue. 

 Thanks

0
0
22 Jul 2020
Copy Link
2018-09-22 14-36-02
Kurt Vandevelde
 
MVP

Did you already try to publish the lifetime solution again? That might also trigger some stuff again. Have my doubts but ti's worth the try.

0
0
23 Jul 2020
Copy Link
UserImage.jpg
Gayan De Saram

Kurt Vandevelde wrote:

Did you already try to publish the lifetime solution again? That might also trigger some stuff again. Have my doubts but ti's worth the try.

 Hi

Sorry for the late reply ,i have done a re-publish but the issue seems to persist, Will raise a support ticket and post the answer back here.

Thanks

0
0
26 Jul 2020
Copy Link
UserImage.jpg
Gayan De Saram

Gayan De Saram wrote:

Kurt Vandevelde wrote:

Did you already try to publish the lifetime solution again? That might also trigger some stuff again. Have my doubts but ti's worth the try.

 Hi

Sorry for the late reply ,i have done a re-publish but the issue seems to persist, Will raise a support ticket and post the answer back here.

Thanks

 This fixed the issue , answer from outsystems :

In the screenshot that you have shared with us, that the HTTP binding is set to 127.0.0.1, which means that the environment will only accept HTTP connections from the environment itself.

Could you please change this value to 'All Unassigned' (in all the environments) and try to run the "BootStrap" timer again?
The Bindings configuration in IIS should look like this:

Thanks
Gayan

0
0
17 Aug 2020
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.