We have identified the cause of the issue and are currently awaiting a team member to access the physical server to resolve it.