:::: MENU ::::

ACS Facility Scheduler on TS User Update Crashes

As I have discussed before, Northwoods uses ACS Facility Scheduler as the primary application for all facility calendaring, global ministry calendaring and also the data source to populate our website calendar (web calendar is still in development). 

We deploy this application, as previously documented,  to our users via a terminal server.  The Terminal Server environment allows us to install the application in on place and let everyone on the network use it. Note: We are still using Server 2003 for this application so no need to comment on the use of TS in place of Remote Desktop Server Most of the time this works without much of an issue but a recent update to Facility Scheduler started causing us some problems. For future sanity I am documenting the problem as well as the solution.

ACS released Facility Scheduler 2010.1 earlier in March, for the most part the built in updater ran without an issue and all existing terminal server users were able to choose update and login without any issue. 

But after the update we started to notice users who had not ever logged into the terminal server before (new network accounts) weren’t able to launch facility scheduler.  The individuals would login to the Terminal server  launch the Facility Scheduler application and then be prompted to update to 2010.1.  The update would complete and the login would display.  After the update they would enter their login credentials for the application and the loading animated icon would appear but wouldn’t be animated. 

After 1-2 minutes of waiting the application would close. This process happened every time the user tried to launch Facility Scheduler.  Further digging revealed this only happened after a user local profile had been deleted from the Terminal Server or the user was logging into the Terminal Server for the first time.

FS

 

The Problem:
Since we installed FS on the terminal server and put the Application Data in the default user profile that application data was several revisions out of date (2008.1.9.6). Since there is no auto update feature for the “default’ user profile it was forgotten when everyone else updated.  This resulted in new user’s profile being created with the outdated version of FS and the updater couldn’t apply 2010.1, causing the login to crash.

Solution when One User Impacted:

  • Confirm the Affected user is not logged into the Terminal Server
  • Login as a user who has the latest version of Facility Scheduler installed and navigate to:
    C:Documents and Settings“Username”Local SettingsApplication Data
    (where “Username” is the network username of the user you are logged in as)
  • Copy the ACSTechnologies folder to
    C:Documents and Settings”Username”Local SettingsApplication Data
    (Where “Username” is the network username of the user who cannot launch Facility Scheduler.
  • Have user login and launch Facility Scheduler

Solution when Multiple Users Impacted

  • Confirm the Affected users are not logged into the Terminal Server
  • Login as a user who has the latest version of Facility Scheduler installed and navigate to:
    C:Documents and Settings“Username”Local SettingsApplication Data
    (where “Username” is the network username of the user you are logged in as)
  • Copy the ACSTechnologies folder to
    C:Documents and SettingsDefaultLocal SettingsApplication Data
  • Delete the User Profile(s) for the user account(s) that aren’t able to launch Facility Scheduler.
  • Have user login and launch Facility Scheduler.

So, what do you think ?

UA-2932131-1