Skip to main content
To homepage To homepage
Solved

Graphical bug or authorisation issue? Certain functionalities missing or disabled.

M
Explorer

Hello,

My organisation recently had to redeploy our development virtual machine and reinstall timextender / odx on it. 

Since then I am not allowed to click on certain buttons inside the application, and options are missing when I right-click on certain objects.

For example I am not allowed to click on the [Stop Task] button in the ODX Execution Queue window. And when I right-click on an object in the Manage ODX tab, all I can see it ‘View Properties’ and not any of the many other options that used to be there.

I do have these functions available in our other environments. And my collegues have no issues on our dev machine.

I have tried the following so far:

  • Enable/disable Deprecated Features.
  • Delete the hidden Default.rdp file and create a new rdp connection to the machine. 

Any tips?

Best answer by rory.smith

Hi @Mvest ,

 

could it be that you used the User password to connect to the ODX Server instead of the Admin password?

View original
Did this topic help you find an answer to your question?

4 replies

rory.smith
TimeXtender Xpert
Forum|alt.badge.img+7
  • rory.smith
  • TimeXtender Xpert
  • 698 replies
  • Answer
  • March 27, 2024

Hi @Mvest ,

 

could it be that you used the User password to connect to the ODX Server instead of the Admin password?

daniel
TimeXtender Xpert
Forum|alt.badge.img+7
  • daniel
  • TimeXtender Xpert
  • 192 replies
  • March 27, 2024

Dear @Mvest ,
You need to input the Admin password to be able to change the settings in the ODX server. Right now you are able to use the ODX as a user which limits your settings.

daniel
TimeXtender Xpert
Forum|alt.badge.img+7
  • daniel
  • TimeXtender Xpert
  • 192 replies
  • March 27, 2024

Or you can set the permissions in the portal. it depends on the version that you use. The 20.10 is with a password. for the v65 you need to do this in the portal.

In the portal you need to give yourself (and maybe others) the rights to work with the instance. 

First you need to have a user to be able to login (you already have that but other might not)
 



Then you need to grand access to that user in the ODX instance:
 


Does this fix it?

M
1 person likes this
  • M
    Mvest
M
Explorer
  • Mvest
  • Author
  • Explorer
  • 9 replies
  • March 27, 2024

Fixed. It was the user/admin password. Thanks all!

Reply


Most helpful members this week

Terms and ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings