Skip to main content

Hello,

I have an Universe 11.3.1.6017 on a Windows Server 2019 installed from April 2023. All was ok.

Since November 2023, uvsh.exe or uv.exe no longer works. Maybe after the last KB from Windows Update, but Im not sure.

But uvapi (rest server) still works.

When I try to connect in telnet, or trying to execute uvsh.exe / uv.exe in cmd, there is an error (see attachment) :

"The Universe start up process has not yet completed. The use of Universe is currently disabled"

I've checked :

  • Universe log files : no information
  • Eventvwr Universe traces : no informations
  • UAC is totaly disabled
  • Approbation mode is disabled

I've tried the following solutions, without success : 

  • Re-register licenses 
  • Reboot server
  • Relaunch Universe services
  • With another local admin account (with very complex and very simple password)
  • With another domain admin

I'm out of ideas :(

It's a production server, and it's not easy to reinstall Universe.

Can you help me ?

Thanks,

Corentin

Hello,

I have an Universe 11.3.1.6017 on a Windows Server 2019 installed from April 2023. All was ok.

Since November 2023, uvsh.exe or uv.exe no longer works. Maybe after the last KB from Windows Update, but Im not sure.

But uvapi (rest server) still works.

When I try to connect in telnet, or trying to execute uvsh.exe / uv.exe in cmd, there is an error (see attachment) :

"The Universe start up process has not yet completed. The use of Universe is currently disabled"

I've checked :

  • Universe log files : no information
  • Eventvwr Universe traces : no informations
  • UAC is totaly disabled
  • Approbation mode is disabled

I've tried the following solutions, without success : 

  • Re-register licenses 
  • Reboot server
  • Relaunch Universe services
  • With another local admin account (with very complex and very simple password)
  • With another domain admin

I'm out of ideas :(

It's a production server, and it's not easy to reinstall Universe.

Can you help me ?

Thanks,

Corentin

Hi Corentin,

That message typically indicates that a flag in shared memory is indicating something hasn't completed during the UV startup process.

If this was due to error went starting UV, rebooting the server and/or stopping and restarting services should cleared the value.

Can you try stopping UV services and then in the uvhome folder issue the command binshrdump to ensure there are no shared memory segments displayed?

And then after restarting the UV services, issue the 'smat -x' command and look for the system_ready_flag. It should appear as:

system_ready_flag: 1

Thanks,

Neil

Hello,

I have an Universe 11.3.1.6017 on a Windows Server 2019 installed from April 2023. All was ok.

Since November 2023, uvsh.exe or uv.exe no longer works. Maybe after the last KB from Windows Update, but Im not sure.

But uvapi (rest server) still works.

When I try to connect in telnet, or trying to execute uvsh.exe / uv.exe in cmd, there is an error (see attachment) :

"The Universe start up process has not yet completed. The use of Universe is currently disabled"

I've checked :

  • Universe log files : no information
  • Eventvwr Universe traces : no informations
  • UAC is totaly disabled
  • Approbation mode is disabled

I've tried the following solutions, without success : 

  • Re-register licenses 
  • Reboot server
  • Relaunch Universe services
  • With another local admin account (with very complex and very simple password)
  • With another domain admin

I'm out of ideas :(

It's a production server, and it's not easy to reinstall Universe.

Can you help me ?

Thanks,

Corentin

Hello Neil,

No segment visible when I run shrdump (see attachment).

When I run smat-x, system_ready_flag = 0 (see atachement)

Hello,

I have an Universe 11.3.1.6017 on a Windows Server 2019 installed from April 2023. All was ok.

Since November 2023, uvsh.exe or uv.exe no longer works. Maybe after the last KB from Windows Update, but Im not sure.

But uvapi (rest server) still works.

When I try to connect in telnet, or trying to execute uvsh.exe / uv.exe in cmd, there is an error (see attachment) :

"The Universe start up process has not yet completed. The use of Universe is currently disabled"

I've checked :

  • Universe log files : no information
  • Eventvwr Universe traces : no informations
  • UAC is totaly disabled
  • Approbation mode is disabled

I've tried the following solutions, without success : 

  • Re-register licenses 
  • Reboot server
  • Relaunch Universe services
  • With another local admin account (with very complex and very simple password)
  • With another domain admin

I'm out of ideas :(

It's a production server, and it's not easy to reinstall Universe.

Can you help me ?

Thanks,

Corentin

I have found the source of the problem (but no explanation) : system_ready_flag = 0, because Universe Resource Service can't start uvdlockd.exe.

uvdlockd.exe says  'must be superuser to start/stop cleanup daemon'. Impossible to launch uvdlockd.exe with 'Local service', or local administrators accounts. It only works with the administrator built-in account (account created on Windows Server installation).

To by pass our problem in our production server, I've set up this administrator account as Universe Resource Service/Uni RPC Service identity. But it's just a by pass, I'm looking for the explanation :)

Can you explain me how uvdlockd.exe check if current account is 'super user' ?

Thanks,

Corentin

Hello,

I have an Universe 11.3.1.6017 on a Windows Server 2019 installed from April 2023. All was ok.

Since November 2023, uvsh.exe or uv.exe no longer works. Maybe after the last KB from Windows Update, but Im not sure.

But uvapi (rest server) still works.

When I try to connect in telnet, or trying to execute uvsh.exe / uv.exe in cmd, there is an error (see attachment) :

"The Universe start up process has not yet completed. The use of Universe is currently disabled"

I've checked :

  • Universe log files : no information
  • Eventvwr Universe traces : no informations
  • UAC is totaly disabled
  • Approbation mode is disabled

I've tried the following solutions, without success : 

  • Re-register licenses 
  • Reboot server
  • Relaunch Universe services
  • With another local admin account (with very complex and very simple password)
  • With another domain admin

I'm out of ideas :(

It's a production server, and it's not easy to reinstall Universe.

Can you help me ?

Thanks,

Corentin

Hi Corentin,

Thanks for that update. After your last response, I was going to have you check again to see if there was some error message somewhere. The indication was that something was failing during the startup process which stopped it from setting the system_ready_flag to 1. And you discovered there was a failure during the starting of uvdlockd.exe.

The uvdlock executable is expecting to be started by the  super user which would correspond to a uid of 0. I'm guessing something did change on your system since you indicated this had worked in the past?

Thanks,

Neil

Terms & ConditionsAccessibility statement