These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Citadel Access Rights Issue?
Author
Previous Topic Next Topic
Victor Bastion
Danger Management
#1 - 2016-12-03 20:28:08 UTC
Has anyone else had any issues with access rights to a Citadel since last night's downtime?

The problem is this: The citadel I speak of is owned by a friendly corp. Before downtime last night everything was fine. I could undock and redock and had access to all services and could control the Citadel. Now I find I cannot and another member of the corp who owns the citadel is having the same issues.

Any attempt to undock gives a warning that the owner does not like me. The member of the owning corp gets the same message.

I suspect that somehow the access list has become disassociated from the Citadel. But to my knowledge no one that could do that has been online since before downtime when it was working.

In the past similar things have happened but we assumed we had done something wrong ourselves. This time though, there was no one around that could have made changes.

Bug?

What am I missing?
Victor Bastion
Danger Management
#2 - 2016-12-03 22:27:03 UTC
Update: The CEO of the corp who owns the Citadel and is Admin just logged in to find that he also has the same issue.

Other issues that I have found today that are unrelated but may indicate some serious issues.

1.) On another character I swapped clones in a HS base. After doing so I found that his training queue was halted and the queue on his PI alt had been started. I had to log out and back in as the alt to stop that queue before I could restart the main.

2.) On a totally different account I just logged in I found that the last 28 or so days of his training time had not been applied at all.

Something's up folks.
Victor Bastion
Danger Management
#3 - 2016-12-03 22:48:00 UTC
Update: First issue solved. The CEO of the corp found all access lists had been disconnected from services as we had thought. No telling how as no one who had access to do that had been on. But reconnecting them fixed it.