Skip to content
Rorymon Logo
  • Blogroll
  • About
  • Contact
Menu
  • Blogroll
  • About
  • Contact
Twitter
Linkedin
Rss
  • All Articles
  • Applications
    • App Compatibility
    • App Deployment
    • App Virtualization
      • App-V
        • Decision Matrix
        • App-V 4.x Recipes
        • App-V 5.x Recipes
        • App-V Videos
      • AppSense StrataApps
      • Cameyo
      • Evalaze
      • Frame
      • Numecent CloudPaging
      • P-Apps
      • ThinApp
      • Turbo
      • Workspace Streaming
      • XenApp Profiling
    • Containers
    • Layering
      • App Volumes
      • Citrix App Layering
      • FlexApp
      • Unidesk
  • Citrix
    • AppDNA
    • Citrix App Layering
    • Citrix Monitoring
    • Citrix Profiling
    • Citrix XenApp
  • Microsoft
    • ACT
    • Azure
    • BitLocker
    • Hyper-V
    • inTune
    • MDOP
      • AGPM
      • APP-V
      • DaRT
      • MBAM
      • MED-V
    • RDS
    • System Center
      • SCCM
      • SCOM
    • WDS
    • Windows
      • Windows 7
      • Windows 8
      • Windows 10
      • Windows Server 2012
  • VMware
    • App Volumes
    • ThinApp
  • Downloads
  • Podcast

Citrix Director: The system is currently unavailable. Please try again later or contact your administrator.

  • Rory Monaghan
  • June 13, 2017
Share on reddit
Share on facebook
Share on twitter
Share on linkedin
Citrix Monitoring

I recently encountered the error:

The system is currently unavailable. Please try again later or contact your administrator.

I found a couple of suggested fixes on the Citrix forums and also a great article by Ralph Jansen.

A theme throughout what I was reading was that many who encountered the issue had upgraded from 6.5 to 7.6.  My situation was a little different. I had not upgraded and had Director working for over a year without issue. It just stopped working all of a sudden.

 

 

 

 

 

I discovered the names of all my controllers were blank. In the forum I saw a suggestion about removing and re-adding controllers, I decided to just reboot my controllers one by one. In my environment, we had more than enough controllers to handle the load. Sure enough, rebooting the controllers ensured the names become populated again within Studio AND then Director started to work again.

The system is currently unavailable. Please try again later or contact your administrator.
PrevPreviousApplication packaging options for SCCM
NextTechnical Review: Deep Citrix Monitoring and Troubleshooting with GoliathNext
Rory Monaghan

Rory Monaghan

Microsoft MVP. Citrix CTA. IGEL Insider. VMware EUC Champion & vExpert.
Twitter
Linkedin
Rss
Vimeo
Youtube
Soundcloud

Get the App-V Decison Matrix and Interactive Tool.

See what the right deployment option for your applications is.
Let's Go!
FREE TOOL
Further Reading

Windows 10 Migration Checklist

Application packaging and virtualization services.
Learn More

Let's make virtualization EASIER!

Be amongst the first to know when I publish new reviews, guides and tools to simplify your virtualization projects.

Categories
  • All Articles
  • Application Compatibility
  • Application Virtualization
  • Containers
  • Citrix XenApp
  • Application Layering
Connect
  • Blogroll
  • About
  • Contact
Twitter
Linkedin
Rss
Vimeo
Youtube
Soundcloud
© Copyright Rorymon.com. All rights reserved 2021.
Privacy   |   Cookies
Marketing Services by Riabro.