SuperContainer and Citrix XenApp

[Todd Weller]

Has anyone attempted this? I'm running FileMaker Pro 11.0v1 on a Citrix XenApp 6.0 farm. I've installed the plugin and run it on my XenApp account without issue. Now when another user launches FileMaker the plugin isn't loading. Under preferences when I check mark the SuperContainer plugin to enable it I get the following message:

"SuperContainer Companion Plugin" could not be enabled.

Not very descriptive..... I did attempt to give other users full admin rights to the server but that didn't help ether.

Any ideas?

A.J.

[Smef]

We haven't tried this in-house (because we don't have a citrix environment), but I know that other people have gotten this working. My guess is that this is a permissions issue for some directory that the plugin is trying to write to when you check the box to enable it.

Can you post your plugin logs after you try to enable the plugin next time? Plugin logs can be found at:

OS X

/Users/userName/Library/Logs/360Plugin Logs/

/Users/userName/Library/Logs/360Plugin Logs/360Works FM WPE

/Users/userName/Library/Logs/360Plugin Logs/360Works FM Pro

Windows

DriveLetter:Documents and SettingsMy Documents360Plugin Logs

DriveLetter:Documents and SettingsAll UsersDocuments360Works FM Pro

DriveLetter:Documents and SettingsAll UsersDocuments360Works FM WPE

Vista: DriveLetter:UsersDocuments360Plugin Logs

[Todd Weller]

I checked all my Cirtix user documents accounts and found that there is no log being written to any of these accounts. Now, the local Administrator RDP (non citrix) account which I opened FM on does have the log files and the plugin runs as it should.

I did find that the 1st Citrix account I opened FM up on with the plugin freshly installed works as it should too. All other accounts I get this error on.

Does the FileMaker client app write a log somewhere that I can take a look at also?

FYI this is a 2008 R2 Datacenter Windows server.

A.J.

[Todd Weller]

FYI if you want you can get a free 90 day trial of XenApp by opening a My Citrix account and grabbing a trial license.

:-)

[Todd Weller]

Sorry for the delay. Here is some of the text in the log files that one of our guys was able to capture. If you need to see something, please let us know and we'll try and grab it.

- - - - - - - - - - - - - - - - - - - - - - -

Writing logs to temp Dir '

C:UsersjsmithAppDataLocalTemp3

---Started temp log at Thu Jul 08 13:39:19 2010 for Unknown / Unknown---

(C++ Thu Jul 08 13:39:19 2010) Writing to log file at 360Plugin Logsmiscellaneous.log

(C++ Thu Jul 08 13:39:19 2010) Could not open log file at 360Plugin Logsmiscellaneous.log because of error code 9

---Started temp log at Thu Jul 08 13:39:19 2010 for SuperContainer Companion Plugin / Unknown---

(C++ Thu Jul 08 13:39:19 2010) Writing to log file at 360Plugin Logsmiscellaneous.log

(C++ Thu Jul 08 13:39:19 2010) Could not open log file at 360Plugin Logsmiscellaneous.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for Unknown / Unknown---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at 360Plugin Logsmiscellaneous.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at 360Plugin Logsmiscellaneous.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / Unknown---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at 360Plugin Logsmiscellaneous.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at 360Plugin Logsmiscellaneous.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at (C++ Thu Jul 08 13:39:31 2010) Could not open log file at ---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at 360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at 360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at (C++ Thu Jul 08 13:39:31 2010) Could not open log file at ---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at V360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at V360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at V360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at V360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at V360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at V360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at V360Plugin Logs360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at V360Plugin Logs360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at V360Plugin Logs360Plugin Logs360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log

(C++ Thu Jul 08 13:39:31 2010) Could not open log file at V360Plugin Logs360Plugin Logs360Plugin Logs360Plugin Logs360Plugin LogsSuperContainer Companion Plugin_FMAdvanced.log because of error code 9

---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at (C++ Thu Jul 08 13:39:31 2010) Could not open log file at ---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at (C++ Thu Jul 08 13:39:31 2010) Could not open log file at ---Started temp log at Thu Jul 08 13:39:31 2010 for SuperContainer Companion Plugin / FMAdvanced---

(C++ Thu Jul 08 13:39:31 2010) Writing to log file at (C++ Thu Jul 08 13:39:31 2010) Could not open log file at

- - - - - - - - - - - - - - - - - -

Thank you for your quick response, and again we apologize for not getting this log information back to you sooner. Have a great day.

[Smef]

It looks like you are having permissions issues for the directory where the log files are supposed to be written. Check and make sure that your users have read and write permission for those directories listed in the log.

[Todd Weller]

Just found another directory in C:/360Plugin Logs/ on the server. Looks like this folder is in use so when another person logs in the plugin can't write to the same folder because it is locked by the other process.

Any reason it is writing files to the root of the C drive?

A.J.

[Todd Weller]

Added full control permissions to the "Users" group for the C:/360Plugin Logs directory and so far the plugin is loading every time.

Any ideas why the plugin is using the root of C to dump logs?

A.J.

[Smef]

I believe that this is a backup location to write logs to if the plugin cannot write logs to the user's documents directory. If you unlock that directory it may stop the plugin from writing logs to your root.