I am a general supervisor and am trying to enable a Universe that a user trying to access (the universe has a red ‘x’ by it and is disabled). However, we I try to do this, nothing happens. I have done this at both the group level and the individual user level, to no avail.
Any ideas? 
indy (BOB member since 2004-04-08)
Seen it. wrote it off as some strage quirk (technical term for “not sure why it is doing this” 
). Trying logging out of Super and back in or try doing this from another machine. What version of Supervisor are you running?
jswoboda 
(BOB member since 2002-06-20)
Could it be that the universe is in a domain to which the user does not have access?
Nick Daniels 
(BOB member since 2002-08-15)
When we saw it is was happening to 1 Supervisor but when I logged into my machine everything was OK. It turns out he has been doing a lot of maint work disabling/enabling docs, users, unvs, ectt… and something just got hosed (another technical term). Once he logged out and back in I think the issue was resolved.
jswoboda (BOB member since 2002-06-20)
We’re running 5.1.8. Unfortunately, another machine and logging in and out did not work.
I’m not sure about the domain issue. I am unable to even view the universe (I’m a general supervisor) when I try to import it from designer. However in Supervisor, when I check the connection, I receive a ‘success’ response.
Still baffled. 
indy (BOB member since 2004-04-08)
Check the database Drivers on each machine. I have noted that some drivers (especially ODBC and MS drivers) handle date/time stamps differently. If the driver is different then the timestamps are not handled correctly and access is determined based on comparing the TS as it was written to the .lsi file and the repository.
digpen (BOB member since 2002-08-15)
Thanks for the suggestion digpin, but I’m not sure how that effects the enable/disabling of the universe that is disabled. For other documents, universes, we are able to successfully enable and disable.
indy (BOB member since 2004-04-08)
Is this a new universe or pre-existing? Do you have local copy or was it published by someone else? My first thought, although you may have already tried this is a Scan/Repair/Compact to try and rule out any corruption issues. Secondly, if it is a new universe perhaps if you delete it out of the Repo, SRC, then re-export and see if the problem still persist.
jswoboda 
(BOB member since 2002-06-20)
Thanks for the input jeffrey,
this is a pre-existing universe. Unfortunately, I do not have a local copy, it was published by someone else. The scan, compact, and repair has also already been run.
This is a tough one, but I think it’s something really easy that I’m missing. 
indy (BOB member since 2004-04-08)
That’s a clue. If you log in as General Supervisor and cannot see the universe from designer, then something is messed up.
That, unfortunately, is meaningless. A connection is not part of the universe, it is stored in a separate record. A connection is then assigned to a universe. So the fact that you can test the connection successfully does not tell you anything about the universe.
When you log in to Supervisor as GS, click the Universe tab (on the bottom of the screen) do you see the universe there? What domain is it located in? Are there other universes in the same domain? Can you create a new universe and export it to that domain?
Dave Rathbun (BOB member since 2002-06-06)
I have the same problem. 
Strange but true:
Even after this procedure the problem persists…
Mayo 
(BOB member since 2004-04-08)
Jo – your workflow is different. You deleted the universe and then did a scan and repair to completely get rid of it.
What exactly is your problem now that you’ve exported the universe (with a new internal universe-id and new internal object-ids)?
Anita Craig (BOB member since 2002-06-17)
Indeed. By removing the universe and doing a scan and repair I hoped to remove all references to the old universe. But… it seems some references are still left in the security and/or universe domain. 
When I link the (new) universe to a group, this universe is immediatly “disabled”. Nothing happens when I click on “disable/enable universe”… 
Mayo (BOB member since 2004-04-08)
I’ve found the solution for my problem (and probably yours too).
The universe remainded disabled because the universe domain was disabled: I noticed the text “(Disabled)” after the long name of the universe. 
Before you can enable a universe you have to link the universe domain to the group. After this there’s no problem anymore to enable/disable a universe. 
[/u]
Mayo (BOB member since 2004-04-08)
Did you ever get a answer to this question. I am running 5.1.6 and cannot enable/disable universes. I have tried everything.
k685828 (BOB member since 2004-12-15)
Just to check, I assume that includes the solution given, whereby the domain had to be enabled/linked?
Nick Daniels 
(BOB member since 2002-08-15)