Jump to content

Todd Weller

Members
  • Posts

    12
  • Joined

  • Last visited

About Todd Weller

  • Birthday 09/27/1970

Profile Information

  • Title
    Senior Data Systems Architect
  • Gender
    Male

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Sierra

FileMaker Partner

  • Certification
    10
    11
    12
    13
    14
    15
    16
  • Membership
    FileMaker TechNet
    FIleMaker Platinum Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Todd Weller's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Thanks to a post in a different forum, I found my issue. In an effort to be efficient, I had created a new layout with only the fields needed for my export and re-insert automated, looping script. When I created the new layout, I forgot to check the field formatting options of the container field. In layout mode, simply go to Inspector > Data > Data Formatting, and select "Optimize for Interactive Content." Once I did that, it worked exactly as expected since my manual process script had been working for a week or so. I hope this helps someone else so you don't think you're going crazy. Have a good one. TW
  2. I am in the process of updating a container field built in FileMaker 11 to make use of the interactive content now available in FileMaker 12. To do that, I've written a script to export the field contents (the PDF file) to the temporary directory and then re-insert the PDF using the "Insert PDF" script step so that the content is interactive. I'm using variables to store the two file paths I need: $ExportPath = filemac:/Macintosh_HD/TempoaryPath/FileName.pdf $InsertPath = imagemac:/Macintosh_HD/TemporaryPath/FileName.pdf Originally, this process was to be run by the users in our Sales and Customer Service departments, but they started getting Error 3 - "Command is unavailable (for example, wrong operating system, wrong mode, etc.)" Since they are using iMacs and networked home directories, I blamed a file system permission setting as the source of the problem. I began to experiment with the script again today and now I'm starting to have the same issue running on a local account on a laptop. I've updated the script to export to desktop instead of the temporary directory but still get the same error. Has anyone else experienced this problem? The files are hosted using FiileMaker Server Advanced 12 on an XServe running Mac OSX Server 10.6. On the client side, i'm running FileMaker Pro Advanced 12 on a MacBook Pro running Mac OSX 10.6. Any assistance that can be provided would be greatly appreciated. Best regards, TW Also, I forgot to add that I am error trapping to verify that the "Export Field Contents" script step is successful before attempting to insert the exported PDF using the "Insert PDF" script step. When I changed the script to use the Desktop, the file definitely appeared on my desktop so I believe that the file does exist when Insert step is executed. Could it be as simple as adding a "Pause" script step?
  3. 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.
  4. 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.
  5. 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.
  6. 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. :-)
  7. 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.
  8. 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.
  9. After posting this problem here, I did some more searching and found a thread for this exact same problem at FileMaker Forum. This issue is related to networked home directories in Mac OS X 10.6. At this point, it appears the only work around involves deleting the FileMaker Preferences folder/file from the Library folder before opening FileMaker Pro. Again, if anyone has any additional insight, it would be greatly appreciated.
  10. Our company (in the IT department) has been testing FileMaker Pro 10 and FileMaker Pro 10 Advanced running on Max OS X 10.6 for several months with great success. We just upgraded the rest of the office users to 10.6 and are now experiencing a problem we've not encountered before. Whenever any setting is changed in the "Preference" dialog, FileMaker Pro immediately crashes, and cannot be reopened unless we delete the FileMaker Preferences folder/file from the OS X Library Folder. The primary difference in the install from our test scenario to the production environment is the type of user account. In the IT office, we are primarily laptop users with local accounts. The rest of the office is iMac computers with networked accounts and Open Directory logins. We have already tried making the user a local administrator on the computer. We've also created several brand new home directories and logins with no success. The file server, home directories and user logins authenticate against our 10.6 LDAP. The FileMaker logins continue to authenticate against our 10.5 LDAP system as we transition everything over to 10.6. Any insight that can be offered would be greatly appreciated. As long as our users don't touch the preferences, FileMaker behaves and performs as expected. System info is as follows: Client: Mac OS X - 10.6.2 FMP 10: FM Server: Mac OS X Server - 10.5.7 FM Server Adv. - 10.0.2.206
  11. Thank you for the clarification, David. I thought this might be the case but wanted to make sure I wasn't missing something obvious.
  12. I'm in the process of determining if I'm doing something wrong, or if this is just how the system is designed to work. Our system is for digital storage of packing slips, receiving reports and similar documents on our primary file server. These documents are either scanned from the physical printouts or generated by FileMaker's internal PDF engine. All documents are uploaded to the server using the Companion Plug-in so that we can control the document name once it hits the server. Using the SuperContainer/Files/... file path, the web viewer displays the document name, size and upload date. The only way I can get a "preview" image to display in the web viewer is by using the SuperContainer/RawData/... file path. While I loose the interaction with the web viewer, I wasn't concerned about this "fix" since I was already using the plug-in to upload my documents. This is running very well in our office on our Mac OS 10.5 desktop machines and a few 10.6 machines we are evaluating before upgrading all departments. The problem comes when dealing with our external sales offices. In all cases, they remotely access a Windows terminal server over a VPN connection. Once connected to the terminal server, they access FileMaker, which makes them appear as "local" user to the FileMaker server. In the database files where we are using SuperContainer, when the tab containing the web viewer becomes active, Adobe Acrobat is launched to show the preview of the document, rather than showing the preview in the web viewer as it does on the Macs. The only way I can stop this from happening is to revert the web viewer path back to the default "Files" version of the file path, but then I'm back to having no preview available for the user. Is this scenario a limitation of our install - Tomcat install on a file server instead of local or FileMaker Server install? Or is there a way to generate the thumbnails when the file is uploaded with the plug in? Or can the web viewer properties be changed so that this external Acrobat window does not come up unless the user explicitly wants to see the preview? Any insight and/or assistance into this issue would be greatly appreciated. Thank you, kindly. Here is some software installation information: File Server: Mac OS X Server 10.5.7 ; Apache Tomcat Ver. 6.0.18 FileMaker Server: Mac OS X Server 10.5.7 ; FileMaker Server Advanced 10.0.2.206 Typical Office Computer: Mac OS X 10.5.8 ; FileMaker Pro 10.0v3 Development Computer: Mac OS X 10.6.1 ; FileMaker Pro Advanced 10.0v3 Terminal Server (Remote Office Access): Windows XP ; FileMaker Pro 10.0v3
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.