Hi there,

I recently updated to 1.5.0 and now I think we are experiencing a bug. We've never had this problem before 1.5.0.

We don't register our devices, we just do unregistered deployments/uploads.

After we network boot using ipxe bootloader, log in and select upload or deploy, we immediately get an error message:

** An Error Has Occurred **

...... Not Authorized

** Rebooting in One Minute **

This seems to happen sporadically.

Is there anything that I can do?

Here is a screenshot of the error:

Thanks!

@eruthon Me as well, so far so good! I've got two sessions running right now. I haven't tested anything else yet.

@theopenem_admin Thank you!

@theopenem_admin I think we are on to something.

One of our techs started deploying an image. I tried to PXE boot and start a task and it is giving me "Not Authorized" again. It's only happening whenever 1 other task is running.

@theopenem_admin Is it possible that if a task is currently running, starting a new task will not start/queue up in the task list? We're suspecting this might be the case and are going to test it shortly.

Nobody is using the system right now and I've not had any problem getting in.

@theopenem_admin Sure, here's a compilation of the web.config in each folder.

toec-API:

• web.config 4.8
  Toems-API:
• web.config: 4.8
• web.config.mysql: 4.6
• web.config.sqlserver: 4.6
  toems-UI:
• web.config 4.8

Should the web.config.mysql and web.config.sqlserver files be 4.8?

I attempted again using the newly created account that worked before and it gave me "Not authorized" this time. I also regenerated the Imaging token under settings > security.

@theopenem_admin I did not regenerate any tokens. I can try this.

I just ran into the problem again with the admin account.

I tried changing the password for admin, same problem.

I tried one of our techs accounts, no change.

I tried using a newly created account and it worked.

@theopenem_admin I just doublechecked the server and .NET 4.8 is installed. I didn't make any changes to it before or after install theopenem 1.5.0.

@eruthon I personally haven't messed with customizing the boot menu with Theopenem. I did back when we used Clonedeploy. This is on a new server.

@theopenem_admin All of our techs log in with a normal user account that are members of a group that gives them access to only image. Myself, I normally just log in with the admin account. I've had it happen to myself just once, but I've had at least three techs report they've had the problem, to the point where they retry 3-4 times and give up.