Description

When I batch convert DNGs to JPEGs in Portfolio, the JPEGs look pixelated or blurry.

Solution

Portfolio Server uses Adobe’s DNG Converter tool when converting DNGs to JPEG. The tool simply extracts the JPEG preview that’s been embedded into the DNG.

To get better looking JPEGs from your DNGs, make sure that you save them with Full Size Previews from Adobe’s Lightroom, Photoshop, etc…

You will need to resave DNGs if they were saved with lower resolution previews, or none at all.

Description

This article explains how to move Portfolio Server 11 from one server to another.

Solution

The instructions below are compatible with Portfolio Server 11, for instructions on migrating earlier versions use this article. You can use the steps below to migrate to a new server during an upgrade to a new version, or to simply migrate between identical versions.

Note:

• This article does not describe the migration process for Portfolio Server 9 and 10.
• You should only migrate to the same version of Portfolio Server or newer. Migrating to an older version is not supported
• This article does not cover migration of MSSQL, MySQL or Oracle servers. Please consult your administrator or documentation for guidance

The steps that follow will list the items that you need to copy from one Portfolio Server system to another. Do not install Portfolio Server on the new server until after you’ve copied the required files. The files that need to be moved are your FDB catalogs or SQL catalog pointers, as well as your user database. If you’ve customized your Quickfind.xml, MediaRich scripts, or created custom Catalog Types, you’ll be shown how to move them as well.

If the old server is running Windows:

1. Make an inventory of all file shares that Portfolio needs access to.
   • Open each catalog using Portfolio Desktop Client
   • In the ‘Folders’ pane, right click on each top-level Autosync folder and select ‘Explore’
   • Make note of the full path to the folder(s) that just opened
   • Repeat as needed with your other catalogs
2. On the old server, you’ll need to stop all services related to Portfolio Server.
   • Go to the ‘Start’ menu and type services.msc into the search field
   • In the Services manager, and stop the following services in this order:
     1. Portfolio Server
     2. Portfolio Server Admin
3. Once the services are stopped, make a copy of the following:
   • Your catalogs folder:
     C:\Program Files\Extensis\Portfolio Server\applications\native-server\Catalogs
   • Your user database: C:\ProgramData\Extensis\Portfolio\data
   • Quickfind.xml file (If you’ve customized your Quickfind settings): C:\Program Files\Extensis\Portfolio Server\data\quickfind.xml
   • Catalog Types (in case you’ve created any):
     C:\Program Files\Extensis\Portfolio Server\data\catalog-settings\English\catalog-types
   • MediaRich scripts (in case you’ve customized yours):
     • C:\Program Files\Extensis\Portfolio Server\applications\media-engine\Shared\Originals\Scripts
     • C:\Program Files\Extensis\Portfolio Server\data\media-scripts.xml
4. Create a matching folder structure on the new server and move the copied files into their respective locations
5. If you intend to copy any Autosync folders from the old server, go ahead and copy them to the new server. You may want to use a tool such as Robocopy to transfer the files with correct attributes. You will need to update the paths in catalogs that are watching those folders after everything’s been migrated. If you don’t know how this is done, please contact Technical Support.
6. You can start the Portfolio Server services again, if needed.
7. Install Portfolio Server on the new server:
   1. Verify the System Requirements. Make sure your server and desktop systems meet or exceed the specifications listed in the System Requirements.
   2. Install prerequisite software on your server:
      • Make sure that Flash player is installed so that you can administer Portfolio Server and use the Web Client.
      • You also need to have QuickTime installed on your server. Make sure that you launch it before installing Portfolio Server. You may receive a dialog which states “Some of the file type associated with QuickTime applications are currently associated with other applications. Should I restore these file types associations to QuickTime?”. You may select either ‘Yes’ or ‘No’ to close the dialog.
      • You should also install the Adobe DNG Converter so that Portfolio can export Camera Raw images in Adobe’s Digital Negative (DNG) format.
      • If you are migrating to Portfolio Server 10.1 or earlier, you also need to install Open Office 3.3.. If you do need to install Open Office, make sure that you launch it before installing Portfolio Server.
   3. Configure your firewall. If there is a firewall between your server and users that need to connect to it, you must open some ports on the firewall to allow Portfolio Server to communicate with its client software. If your firewall is on your server, open these ports to allow others on your network to access the server; if your firewall is between your network and the Internet, open these ports to allow users outside your network to access your server. You should make sure these ports are open before installing Portfolio Server. Consult the Portfolio Server Administration Guide, found here for specific details on what ports are required
   4. Install Portfolio Server: Important! Determine in advance whether you need to use the Domain User account option or the Local System account option. See “Installing Portfolio Server” in the Portfolio Server Administration Guide, foundhere for more installation details.
   5. Enter your Portfolio Server serial number.
      1. Open the Portfolio Server Admin application.
      2. From the main menu, click Licenses.
      3. Click the [ + ] button to add a new license.
      4. Enter a valid license number and click Add License.
   6. Verify that the migration was successful:
      • Open the Portfolio Server Admin application.
      • From the main menu, click on ‘Catalogs’. Verify that your catalogs are listed and available to the same users as on the previous server
      • Open your catalogs using the Portfolio Desktop or Web Client to make sure that things look and work the way they’re supposed to

If the old server is running MacOS X:

1. Make an inventory of all file shares that Portfolio needs access to.
   • Open each catalog using Portfolio Desktop Client
   • In the ‘Folders’ pane, right click on each top-level Autosync folder and select ‘Reveal in Finder’
   • Make note of the full path to the folder(s) that just opened
   • Repeat as needed with your other catalogs
2. On the old server, you’ll need to stop all services related to Portfolio Server. Note: The second Terminal command is only required with Portfolio Server 9.0 and 9.1.
   • Open Terminal from /Applications/Utilities
   • Type in each command on a separate line, then hit ‘Return’. Authenticate with an administrator password when prompted:
     • sudo SystemStarter stop ExtensisDamServer
     • sudo launchctl unload /Library/LaunchDaemons/com.extensis.dam-server.web.admin.launchd.plist
3. Once the services are stopped, make a copy of the following:
   • Your catalogs folder:
     /Applications/Extensis/Portfolio Server/applications/native-server/Catalogs/
   • Your user database:
     /Library/Extensis/Portfolio/pgsql
   • Quickfind.xml file (If you’ve customized your Quickfind settings): /Applications/Extensis/Portfolio Server/data/quickfind.xml
   • Catalog Types (in case you’ve created any):
     /Applications/Extensis/Portfolio Server/data/catalog-settings/English/catalog-types/
   • MediaRich scripts (in case you’ve customized yours):

     /Applications/Extensis/Portfolio Server/applications/media-engine/Shared/Originals/Scripts

     /Applications/Extensis/Portfolio Server/data/media-scripts.xml

4. Create a matching folder structure on the new server and move the copied files into their respective locations
5. If you intend to copy any Autosync folders from the old server, go ahead and copy them to the new server. You may want to use a tool such as rsync to transfer the files with correct attributes. You will need to update the paths in catalogs that are watching those folders after everything’s been migrated. If you don’t know how this is done, please contact Technical Support.
6. You can start the Portfolio Server services again, if needed. Note:The first command is only needed for Portfolio Server 9.0 and 9.1.
   • Open Terminal from /Applications/Utilities
   • Type in each command on a separate line, then hit ‘Return’. Authenticate with an administrator password when prompted:
     • sudo launchctl load /Library/LaunchDaemons/com.extensis.dam-server.web.admin.launchd.plist
     • sudo SystemStarter start ExtensisDamServer
7. Install Portfolio Server on the new server:
   1. Verify the System Requirements. Make sure your server and desktop systems meet or exceed the specifications listed in the System Requirements.
   2. Install prerequisite software on your server:
      • Make sure that Flash player is installed so that you can administer Portfolio Server and use the Web Client.
      • You should also install the Adobe DNG Converter so that Portfolio can export Camera Raw images in Adobe’s Digital Negative (DNG) format.
      • If you are migrating to Portfolio Server 10.1 or earlier, you also need to installOpen Office 3.3.. If you do need to install Open Office, make sure that you launch it before installing Portfolio Server.
   3. Configure your firewall. If there is a firewall between your server and users that need to connect to it, you must open some ports on the firewall to allow Portfolio Server to communicate with its client software. If your firewall is on your server, open these ports to allow others on your network to access the server; if your firewall is between your network and the Internet, open these ports to allow users outside your network to access your server. You should make sure these ports are open before installing Portfolio Server. Consult the Portfolio Server Administration Guide, found here for specific details on what ports are required
   4. Install Portfolio Server: Important! When you install Portfolio Server, be sure to log in to the computer using the same account you used to install the Adobe DNG Converter software. See “Installing Portfolio Server” in the Portfolio Server Administration Guide, foundhere for more installation details.
   5. Enter your Portfolio Server serial number.
      1. Open the Portfolio Server Admin application.
      2. From the main menu, click Licenses.
      3. Click the [ + ] button to add a new license.
      4. Enter a valid license number and click Add License.
   6. Verify that the migration was successful:
      • Open the Portfolio Server Admin application.
      • From the main menu, click on ‘Catalogs’. Verify that your catalogs are listed and available to the same users as on the previous server
      • Open your catalogs using the Portfolio Desktop or Web Client to make sure that things look and work the way they’re supposed to

Description

I would like to combine two or more Portfolio Catalogs into one. How do I do that?

Solution

Portfolio catalogs can be combined with a bit of effort. The instructions below are valid for Portfolio 8.5 – 11.x.

Recover your catalogs

It’s a good idea to recover Portfolio’s native FDB catalogs before combining them. The Recover command cleans out unused or damaged data, which can get in the way of copying things between catalogs. This is not necessary with MySQL, MS-SQL, or Oracle catalogs.

• This article explains how to recover Portfolio Server FDB catalogs.
• This article explains how to recover Portfolio Standalone catalogs.

Combining Catalogs

Use the Portfolio Desktop Client or Portfolio Standalone for the instructions that follow.

Note: Catalog A refers to the catalog that you will be copying from and Catalog B refers to the one you’ll be copying to.
Custom Fields

Before you transferring items between catalogs, you need to make sure that Catalog B has custom fields for any metadata you want to transfer from Catalog A. If you only keep metadata in standard catalog fields, such as Keywords or Description, then you can skip this section.

1. Open both Catalog A and B
2. In both catalogs:
3. Select Catalog -> Access Level to open the Access Level dialog.
4. Set the Access Level to Administrator, then click on OK. Note: If it’s a served catalog, anyone else who has this catalog open will lose access while you’re using Administrator access.
5. Select Catalog -> Custom Fields

6. Make an inventory of the custom fields in both catalogs. If Catalog B is missing a field that contains data in Catalog A, you’ll need to create it with the same name and settings in Catalog B.

   This article explains how to create custom fields.

Saved Finds

Saved Finds are finds that were saved in a catalog to help you perform the same search repeatedly.

1. In Catalog A, open the Find dialog
2. Go down the list of Saved Finds in the upper right corner of the Find dialog
3. From the list, select a Saved Find that needs to be recreated. The Find dialog will display its settings.
4. Switch to Catalog B
5. Select “Save Find As…” in the Saved Finds menu. Name the Find and click on Save.
6. Repeat as necessary to recreate other Saved Finds

Galleries and Thumbnails

Now it’s time to recreate Galleries from Catalog A in Catalog B, then transfer the thumbnails via drag and drop between the catalogs.

1. Open both Catalog A and B
2. If Catalog A includes any galleries besides All Items, Last Cataloged, or Find Results, arrange the two catalogs’ windows so that both of their Galleries panes are visible.
3. Create a new gallery in Catalog B for every gallery that you want to copy over from Catalog A.
4. In Catalog A, click the All Items gallery. Highlight a thumbnail or record and click Edit > Select All to select every item in the catalog.
5. Drag and drop the selected group of items right on top of Catalog B’s All Items gallery. This will copy all thumbnails and associated metadata to Catalog B.
6. Select the next gallery that you want to copy over. Highlight a thumbnail or record and click Edit > Select All to select every item in the gallery. Drag and drop the group of items onto the corresponding gallery in Catalog B.
7. Repeat the last step until all galleries have been copied.

Master Keyword List

Master Keyword Lists are easy to export and transfer to another catalog.

1. In Catalog A, click Catalog > Administration. Switch to the Keywording tab to display the master keywords list for your catalog.
2. If any master keywords are listed, click Export… and save the list to a memorable location such as the Desktop.
3. In Catalog B, click Catalog > Administration and switch to the Keywording tab.
4. Click Import… and browse to the file you saved in step 2.

Note: If there are any duplicate keywords in the exported Master Keyword List, they will be ignored when imported into Catalog B to prevent duplicate entries.

Recreate Categories

If Catalog A uses Categories, you’ll need to manually recreate them in Catalog B.

1. In Catalog A, select Window > Show Categories to display the Categories palette
2. Double-click on a Category. If Portfolio displays any thumbnails, they are associated with the Category that you clicked on./li>
3. Switch to Catalog B
4. Click on New… in the Categories pallete, then enter the name of the one you’re copying over.
5. Select the thumbnails from that Category in Catalog A, then drag and drop them onto the same Category in Catalog B.
6. Repeat as necessary for all other Categories that you want to copy over.

Description

When I add PDFs, Word documents or Text files to Portfolio Server, it is not indexing the text from the files.

Solution

If you are running Portfolio Server 11.2.0, you should upgrade to version 11.2.1. 11.2.0 has a bug that prevents it from indexing document text.

Here are direct links to Portfolio Server 11.2.1:

• Windows Installer
• Mac Installer

If you have Portfolio Server 11.2 installed, you also need to make sure that Index Document Text is turned on in your catalog. If this setting is disabled, Portfolio Server will not extract text from any documents.

To enable it:

1. Open the catalog in Portfolio Desktop Client.
2. Select Catalog -> Advanced Options…
3. Click on the Properties tab
4. Click the ‘Index Document Text’ checkbox, then click ‘OK’

Description

I’ve recovered my FDB catalog but it still has problems. What can I do?

Solution

If you have already tried repairing your catalog using the recover command, but there are still issues, you can manually rebuild your catalog.

The Recover command works by creating a new catalog based on your existing catalog’s configuration, and copying the previous catalog’s data into it – ideally leaving behind any corruption which existed in the old catalog’s structure. Sometimes bad data gets pulled over as well, which necessitates a manual rebuild.

The following steps will help you to determine and reproduce your catalog’s configuration. For clarity, “Catalog A” will refer to your old catalog, and “Catalog B” will be a newly created catalog into which we will transfer your assets.

Make a Catalog Type for Catalog A:

This will create a catalog template that includes all custom metadata fields that are in the original catalog.

1. Open the original catalog (Catalog A) in the Portfolio Desktop Client.
2. Choose File > Save Catalog Type…
3. Enter the catalog name for the catalog type and click ‘OK’.
4. Browse to Catalog Type directory:
   • Windows: C:\Users\\My Documents\Portfolio\Catalog Types\
   • Macintosh:~/Documents/Portfolio/Catalog Types/
5. Copy the folder that has the same name as the Catalog Type that you saved previously, and paste it into:
   • 64-bit Windows:C:\Program Files (x86)\Extensis\Portfolio Server\data\catalog-settings\English\catalogtypes\
   • 32-bit Windows:C:\Program Files\Extensis\Portfolio Server\data\catalog-settings\English\catalog-types\
   • Macintosh:/Applications/Extensis/Portfolio Server/data/catalog-settings/English/catalog-types/
6. Log back in to the Portfolio Server Administration application.
7. Restart Portfolio Server, so that it recognizes the new Catalog Type.

Create a New Catalog

1. After Portfolio Server has restarted, log back into Administration and click on ‘Catalogs’
2. Click on ‘Add New Catalog’, then select the new Catalog Type.
3. Select ‘Native FDB’ and give the catalog a name.

Transfer the master keywords list:

1. In Catalog A, click Catalog > Administration. Switch to the Keywording tab to display the master keywords list for your catalog.
2. If any master keywords are listed, click Export… and save the list to a memorable location such as the Desktop.
3. In Catalog B, click Catalog > Administration again and switch to the Keywording tab.
4. Click Import… and browse to the file you saved in step 2.

Transfer Catalog A’s Categories:

1. With Catalog A open, select Window > Show Categories to display the Categories palette
2. If any categories are listed, click the black triangle button in the palette’s upper-right corner and choose Export…. Save the file to a memorable location such as the Desktop.
3. Switch to Catalog B, click the black triangle again, and choose Import…. Browse to the file you saved in step 2.

Copy Saved Finds

1. In Catalog A, open the Find dialog
2. Go down the list of Saved Finds in the upper right corner of the Find dialog
3. From the list, select a Saved Find that needs to be recreated. The Find dialog will display its settings.
4. Switch to Catalog B
5. Select “Save Find As…” in the Saved Finds menu. Name the Find and click on Save.
6. Repeat as necessary to recreate other Saved Finds

Recreate Galleries from Catalog A in Catalog B.

1. If Catalog A includes any galleries beyond All Items, Last Cataloged, or Find Results, arrange the two catalogs’ windows so that both their Galleries panes are visible.
2. Create a new gallery in Catalog B for every gallery that you want to copy to Catalog A.

Copy Catalog Records from Catalog A in Catalog B.

In the following steps, you will sort Catalog A by the Item ID field, which is a unique number for each item in a catalog. Sorting by Item ID allows you to select the catalog records sequentially, from oldest to newest. This can be help you keep track of what items you’ve copied when rebuilding larger catalogs.

1. In Catalog A, click the All Items gallery.
2. Select View -> Customize
3. Put a check next to the Item ID field, then put a check next to “Show Field Name for this Field”. Click ‘Done’ when you’re finished.
4. In the top right of the catalog, select Item ID from the Sort menu. This will sort the catalog by Item ID
5. Select about 10,000 thumbnails in the All Items gallery and drag them into the All Items gallery in Catalog B.
6. Drag the selected group of items into Catalog B’s window, and drop them into the All Items gallery.
7. Repeat the previous two steps until all thubmnails are copied into the Catalog B
8. Repeat the above steps with all of your custom galleries, until every gallery in Catalog B has the same contents as its counterpart in Catalog A.

When you’re done, all catalog records and associated metadata, will be in Catalog B. Some items may not transfer if their data is damaged in the original catalog.

Description

This article gives steps for upgrading from Portfolio Server 8.5 to 10.

Solution

The following steps assume that you will be upgrading Portfolio Clients and Server 8.5 to 10 on the same systems that they are currently installed on.

• Portfolio Server:
  1. Verify the system requirements:

     Make sure that your server meets or exceeds the specifications found here. Please note that on Mac systems, PPC processors are no longer supported. If you are using Portfolio Server with MS SQL, MySQL, or Oracle, there is a good chance that the version that you’re using with 8.5 won’t work with version 10. Please consult your database vendor for upgrade assistance.

     Please be aware that due to Java dependencies, Portfolio Server 10 must be installed on the boot drive of the server that it is being installed on. Native (FDB) catalogs must be stored on the same volume. You can specify other factors that affect disk usage in the Global Settings dialog – such as where logs and screen previews are stored.

  2. Third-Party Components:

     Make sure that you have the following installed before upgrading to Portfolio Server 10:

     • Quicktime version 7.6.6 or newer (required for cataloging some file formats)
     • Open Office 3.3

       Note:This is not required for Portfolio Server 10.2, only for Portfolio Server 10.1 and lower. In those versions it is used for cataloging Office documents and text files. You must launch Open Office after its installation is complete and before installing Portfolio Server.This registers it with the operating system, which is required for Portfolio Server to take advantage of the software.

     • Flash Player 10 or newer. Required on any computer that will be used to administer Portfolio Server.
     • Adobe DNG Converter If you intend to convert RAW images to DNG, you must install this prior to installing Portfolio Server 10.
  3. Make backups of your existing catalogs and site folders:

     Create a copy of your Portfolio Server catalog files and, if applicable, NetPublish site folders:

     • Windows
       1. Stop both the Portfolio Server and Portfolio NetPublish services:
          • Select Start > All Programs > Administrative Tools > Services.
          • Right-click “Portfolio Server” and choose “Stop”.
          • Right-click “Portfolio NetPublish” and choose “Stop”.
       2. Create backup copies of the following folders and their contents:
          • C:\Program Files\Extensis\Portfolio Server 8.5\Catalogs\
          • C:\Program Files\Extensis\Portfolio NetPublish\WebRoot\sites\
       3. If custom Catalog Types were created, they will need to be copied from the following location on the client machine that created them:
          C:\Program Files\Extensis\Portfolio 8.5\Locale\*\Support\Catalog Types

          * This folder number varies depending on the language version of Portfolio

     • Mac OS X
       1. Stop both Portfolio Server and Portfolio NetPublish using the Portfolio Server and NetPublish Server Launchers:
          • Open /Applications/Extensis Portfolio Server 8.5/Server Launcher Portfolio.
          • Click “Stop”
          • Quit the Server Launcher.
          • Open /Applications/WebRoot/app/NetPublish Launcher.
          • Click “Stop”
          • Quit the NetPublish Launcher.
       2. Create backup copies of the following folders and their contents:
          • /Applications/Extensis Portfolio Server 8.5/Catalogs
          • /Applications/Portfolio NetPublish Server/WebRoot/sites/
       3. If custom Catalog Types were created, they will need to be copied from the client machine that created them, from the following location:

          /Applications/Extensis Portfolio 8.5/Locale/English/Catalog Types

  4. Service Permissions:
     • If installing the upgrade on a Windows system, open the Services console, via Start > Programs > Administrative Tools > Services, and determine what account Portfolio Server and Portfolio Server Admin are running under.
     • On Mac systems, make sure that you’re logged in with the same user account that installed the previous version of Portfolio Server. You can check what account Portfolio Server is running under by opening the Activity Monitor (found in /Applications/Utilities) and looking at the User column.
  5. Network Ports:

     With previous versions you had to have TCP port 2903 open in order for Portfolio Client to be able to communicate with Portfolio Server. With Portfolio Server 10, you also need to open the following TCP ports:

     • 8090 (required for the Portfolio Web Client)
     • 8091 (required for the Portfolio Server Administration)
     • 9877 (required by the media engine)
  6. Installation:
     1. Run the Portfolio Server 10 installer. (Windows only) When it gets to the step where it asks for the “Service User”, use the same account setting that you looked up in Services in the step above.

        The installer will update the existing version to 10. When Portfolio Server starts, all Native (FDB) catalogs will be automatically upgraded to version 10. SQL catalogs will be updated after the Portfolio Enterprise Module license is entered (see below). If you have questions about this and other configurations, please refer to the Server Administration Help. It is recommended that you restart the server at the end of the upgrade installation.

     2. When you are ready to proceed, log into the Server Admin web interface using a web browser. To connect, use the server’s IP address with port 8091. For example, if the server’s IP address is 10.9.88.22, use the following: http://10.9.88.22:8091. If you’re on the same server, you can use the loopback address: http://localhost:8091 or http://127.0.0.1:8091
  7. Serialize and change default passwords:

     Portfolio Server and SQL Connect are serialized and administered using the Server Admin web interface.  Use the following instructions to serialize each licensed component, and change the default administration password.

     1. Open the Portfolio Server administration website: http://localhost:8091
     2. Enter the default username administrator, and the default password password
     3. Select “USERS”
     4. Select the “administrator” account
     5. In the “User Details” pane, enter and confirm a new password
     6. Click “Apply”
     7. Select “LICENSES”
     8. Select “Add New License”

        NOTE: You must first enter your Portfolio Server license code before applying other license codes.

     9. Enter your Portfolio Server license code. In Portfolio 10, the server license includes the licenses (concurrent seat count) for the desktop and web clients
     10. Click “Add License”
     11. If you have additional licenses, repeat the 3 previous steps to enter them.

     If you need additional info on configuring the Enterprise Module or NetMediaMax, please refer to the Portfolio Server Administration Help or the Portfolio Server Administration Guide Guide.

  8. Global Settings

     You do not need to make any changes to your existing catalogs if you do not want to, but be aware that in Portfolio Server 10, the Server Administration allows you to configure the following under “Global Settings”:

     • Central repository for Autosync folders
     • Central repository for Previews (Note: As of version 9.5, this location no longer needs to be shared, unless using NetMediaMax on another server)
     • Location for Work folder (this is a temp folder used for image processing and caching of Web Client download requests)
     • Location for Logs

     For more information on the Global Settings or managing users and catalogs, check the Portfolio Server 10 Administration Guide or click the “Help” link in the Server Admin web

  9. User Accounts:

     To access a Portfolio served catalog, users must have an account. Administrators create user accounts and give users access to catalogs in the Portfolio Server Admin web interface. User accounts can be used to access served catalogs with either the Portfolio Desktop or Web Client.

     Portfolio 10 catalogs only support “user-based” access, and no longer allow “level-based” access. Administrators upgrading “level-based” catalogs to Portfolio 10 will need to manually create and apply user accounts to the catalog. If catalogs with user-based accounts are being upgraded, those account mappings will automatically appear in Portfolio Server 10.

     • Account Creation:

       The steps below can be used in any edition of Portfolio Server 10. If you have the Professional or Enterprise edition, you can import users from your company’s Active or Open Directory server. For details on how to use this feature, please refer to the Portfolio Server Administration Guide.

       Use the following steps to create Portfolio Server user accounts:

       1. Open the Portfolio Server administration website: http://localhost:8091
       2. Enter the administrator username and password
       3. Select “USERS”
       4. Click on “Add New User”
       5. Enter an “Account Name”
       6. Enter and confirm a password
       7. If you wish to add the user to all existing catalogs, enable the “Add user to all catalogs as:” checkbox and select the maximum access level for that user
       8. Click on the “Create” button
       9. Repeat the above steps for each Portfolio user
     • Catalog Membership:

       Use the following steps to grant users membership on served catalogs:

       1. Open the Portfolio Server administration website: http://localhost:8091
       2. Enter the administrator username and password
       3. Select “CATALOGS”
       4. Select a catalog
       5. Click on “Manage Catalog Membership”
       6. Select an account name
       7. Select an access level
       8. Click on “Apply”
       9. Repeat the above steps for each catalog and related user accounts
  10. Catalog Types:

      If you have custom catalog types that you saved from your Portfolio 8.5 clients, copy them to the following location:

      • Mac OS X: /Applications/Extensis/Portfolio Server/data/catalog-settings/English/catalog-types/
      • Windows: \Program Files\Extensis\Portfolio Server\data\catalog-settings\English\catalog-types\

      Portfolio Server will need to be restarted in order for the Catalog Types to become available.

• Portfolio Desktop Client:
  1. Verify the system requirements:

     Make sure that your client machine meets or exceeds the specifications found here:

  2. Installation:

     Run the Portfolio 10 Desktop Client installer and it will upgrade the existing  8.5 application. There is no need to serialize it, since the client serialization is now handled in the Server Admin web interface. Please do not attempt to connect your Portfolio 10 client to an older version of Portfolio Server.

• NetPublish Server:
  • Mac:
    • Uninstall Netpublish 8.5 by running the Portfolio NetPublish Uninstaller.app inside of the Portfolio NetPublish Server/app directory.
    • Run the NetPublish Server 10 installer. It will install the new Portfolio NetPublish Server directory under /Applications/Extensis.
    • Copy over the site folders that were in /Applications/Portfolio NetPublish Server/WebRoot/sites/ to /Applications/Extensis/Portfolio NetPublish Server/WebRoot/sites/
    • Don’t forget to start Netpublish Server, using the NetPublish Launcher app in /Applications/Extensis/Portfolio NetPublish Server/WebRoot/app.
  • Windows:
    • Run the NetPublish Server 10 installer. On Windows the installer will upgrade the existing NetPublish Server 8.5 automatically and copy over existing sites.
• Finish setting up:
  1. After the installation is complete, launch Portfolio Desktop Client 10 and go to ‘File -> Administer NetPublish’
  2. In the NetPublish Administration dialog, click to highlight your server, then click on the “Administer” button
  3. In the dialog that opens, click on the Server Settings tab, then click on “Serialize”
  4. Enter your license number in the dialog box and click “OK”, then click on “OK” and “Exit” to close the remaining dialogs.
• Test Functionality:

  After performing a Portfolio Server 10 upgrade, test the following components to ensure the system is functioning correctly:

  • Portfolio Desktop Client:

    Open each served catalog with the Portfolio Desktop Client. Verify that items are added correctly when manually cataloged or when synchronized using AutoSync folders. Check newly cataloged items for thumbnails, previews (if enabled), and metadata extraction.

  • NetPublish:(if applicable)

    The biggest difference between NetPublish 8.5 and NetPublish 10 is that the latter requires a username and password for each site. Older versions did not require this.

    The easiest way to fix the site is to republish it in Portfolio 10. If for some reason you cannot (for example, if the site was customized after publishing), you can publish a test site from the same catalog (using any template, no need to make changes to it). Use the next steps to copy the necessary data into the existing NetPublish sites.

    1. Open the alias.properties file for the test site (located in the NetPublish application folder, under /webroot/sites/;  and look for a section that looks something like this:

       catalog.1.password = [hashed string containing password]

       catalog.1.path = portfolio://10.0.0.45/Catalog.fdb

       catalog.1.user = jsmith

    2. Copy the ‘catalog.1.password’ and ‘catalog.1.user’ lines and then replace the matching lines in the alias.properties file for the existing site. After that, the existing site should function normally.
    3. Finally, load each of your Netpublish sites in a web browser and verify that they are functioning properly. Do some test searches and verify that previews and original images (if applicable) are available.

Description

When I try to launch Suitcase Fusion, I get an error message that says, “Alert: Could not open the Font Vault at the location “”.”

Solution

This error message means Suitcase Fusion 5 is unable to create a font vault in your home folder. This can be caused by bad permissions on your home folder or a bad hosts file.

Here are some things you can try to resolve this issue.

Check Permissions

If the permissions on your home folder are misconfigured, Suitcase Fusion will have trouble starting.

• Go to your home folder located on your hard drive at: [Macintosh HD]/Users/[UserName]
• Choose File > Get Info on your home folder (the one with the house icon)
• At the bottom, under “Sharing & Permissions” verify that you (the owner) have “Read & Write” access
• If not, click the padlock icon (bottom right corner of window) and type in your Macintosh administrator password
• Change your privilege to “Read & Write”
• Click the gear shaped icon at the bottom of the window and choose “Apply to enclosed items”
• Press OK
• When you’re done, your permissions should look like this:
• Restart your Mac
• Launch Suitcase

Check Hosts File

If you still get the same error message, then:

• Open Applications/Utilities/Terminal
• Type, or copy and paste the following command into Terminal, then hit [Return]:

  cat /private/etc/hosts

Here is what a default Mac OS X hosts files should contain:

##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost

If you get a response that says:
/etc/hosts: No such file or directory
then the hosts file is missing.

If the response is missing any of the above lines, then the hosts file has been modified in a way that will prevent Suitcase from working.

Additional entries are usually fine.

To fix your hosts file:

• Click here to download a default hosts file
• Move it to your desktop and unzip it
• Type, or copy and paste the following command into Terminal, then hit [Return]:
  sudo cp /Users/$USER/Desktop/hosts /private/etc/hosts
• Enter your Macintosh password and press [Return] when prompted to authenticate.
  NOTE: The cursor will not move and your password will not be displayed when you type. That’s OK. Just type carefully and press [RETURN] when you’re done.
• Type, or copy and paste the following command into Terminal, then hit [Return]
  sudo killall -HUP mDNSResponder
• Quit Terminal
• Choose Apple Menu > Log Out
• Log back into your Mac
• Launch Suitcase Fusion

For additional info, see “OS X Daily – How to Edit the Hosts File in Mac OS X with Terminal”

Description

How do I set up Single Sign On (SSO) for Portfolio?

Solution

Portfolio allows you to configure single-sign-on for connections from Portfolio Web. This will work if the following is true:

1. Portfolio is installed on a supported Windows Server OS.
2. Portfolio is running in an Active Directory environment that supports Kerberos 5 and is properly configured.
3. The domain user has been imported into the Portfolio.
4. The Portfolio Web user is logged into a device that is recognized by the domain and is using a supported web browser.

If these conditions are met, then the Portfolio Web will detect the identity of the user, bypass the login window, and show the user the catalogs to which he or she has access.

Server Configuration

In order for single sign-on to work:

1. Portfolio needs to be installed on a Windows server in a Windows domain
2. The domain needs to be configured to use Kerberos authentication
3. An SPN must be configured for the Portfolio machine

Create an SPN

First, you need an AD account for the SPN. You can create a dedicated account, or use the one that the Portfolio services run under. The account name must be unique, and it has to have a non-expiring password

Next, you also need to know the hostname of the server that Portfolio is installed on. The hostname must be the canonical hostname (myserver.domain.com) returned from a reverse lookup in DNS. If you know the Portfolio’s IP address, you can use the nslookup command to find out its hostname.

Now you can create the SPN. This is done on the AD controller with the Windows setspn.exe tool.

On the domain controller, open a Command Prompt.

The syntax for the command is as follows: setspn.exe -a HTTP/myserver.domain.com:8090 domain\username

For example, if you created an AD account named PortfolioSPN, and Portfolio’s canonical hostname is portfolio.extensis.com, then the command will look like this:
setspn.exe -a HTTP/portfolio.extensis.com:8090 domain\PortfolioSPN
Add Account to Portfolio

1. Log into Portfolio Administration
2. Click on Global Settings -> Single Sign-on Credentials
3. Enter the Account Name and Password that was used for the SPN in the steps above.
4. Click on ‘Apply’

The credentials for the server’s “preauthorization” account will be stored in the Portfolio preferences. The password will be encrypted with a public key generated at first run, and stored in its keystore.

Client-side Browser Configuration

Below are steps to configure the client-side web browsers so that SSO works with Portfolio Web.

Note: Before attempting Kerberos authentication with a browser on a Mac client, you need to properly join the Mac to the same AD domain that Portfolio is in.

Supported Web Browsers

The following web browsers are currently supported:

• Chrome (Mac and Win)
• Firefox (Mac and Win)
• Internet Explorer 9 and 10 (Win only)
• Safari (Mac only)

Google Chrome (Mac and Win)

Google Chrome needs to be started with the command line option --auth-server-whitelist="server.domain.com"
Windows:

1. Open the Command Prompt

2. Type in the path to Google Chrome and add the --auth-server-whitelist="server.domain.com" switch, replacing server.domain.com with the Portfolio hostname.

   Using the portfolio.extensis.com example from above, the command would look like this:

   "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --auth-server-whitelist="portfolio.extensis.com"

Mac:

1. Open Terminal.app

2. Type in the path to Google Chrome and add the --auth-server-whitelist="server.domain.com" switch, replacing server.domain.com with the Portfolio hostname.

   Using the portfolio.extensis.com example from above, the command would look like this:

   open -a /Application/Google\ Chrome.app --args --auth-server-whitelist="portfolio.extensis.com"

For more details, please see this article, under the heading Integrated Authentication.

Firefox (Mac and Win)

1. In the address bar, type about:config and then hit enter. You may be prompted with a warning. Click on “I’ll be careful, I promise!” to proceed.
2. In the search text box, type negotiateand hit enter
3. Double-click network.negotiate-auth.allow-non-fqdn to set it to true.
4. Double-click network.negotiate-auth.trusted-uris. When prompted, add the last part of the canonical Portfolio hostname used in the SPN, and preceded by a period. For example, .portfolio.extensis.com

Internet Explorer 9 and 10 (Win)

1. Go to your Start Menu -> Control Panel -> Internet Options.
2. In Internet Properties, choose the Security tab.
3. Choose the “Local Intranet” zone
4. Click the “Sites” button.
5. Uncheck “Automatically detect intranet network” if it is checked.
6. Check “Include all sites that bypass the proxy server”.
7. Click the Advanced button.
8. Add a full http url for the Portfolio machine. For example, “http://portfolio”, or “http://portfolio.extensis.com”. Adding both is a good idea.
9. Click close.
10. Recheck “Automatically detect intranet network” if it was originally checked.
11. Click OK.
12. Click OK again to dismiss Internet Properties dialog.

Safari (Mac)

If the Mac client machine is properly connected to the AD domain, no configuration is required for Safari .

Description

How do I upgrade from Portfolio Server to Portfolio?

Solution

The instructions below will guide you in upgrading from Portfolio Server to Portfolio.

What’s Changed?

Be sure to review this list of changes that you should be aware of before upgrading from Portfolio Server to Portfolio. Because of these changes, we recommend that you try out Portfolio in a test environment before upgrading your production setup.

We do have sales engineers who can perform this upgrade for you. For more information, please contact your sales representative.

Portfolio Desktop Client:

Portfolio comes with Portfolio Web, which is its web client app. It contains most of the features that were found in Portfolio Desktop Client, but not all. To drag and drop images from a catalog into another application, use Portfolio Express.

Here’s a list of changes to that you should be familiar with:

• All Catalog administration is now done in the Portfolio Administration web app.
• Drag and drop into other applications is now done with Portfolio Express.
• It is no longer possible to export metadata from Portfolio.
• Copying records between catalogs is currently not possible.
• Bulk-editing paths via script is currently not possible.

Catalog Limits

Each edition of Portfolio has limits on the number of assets it will manage.

• Portfolio Enterprise – up to 10 Million assets, across unlimited number of catalogs.
• Portfolio Professional – up to 500,000 assets, across unlimited number of catalogs
• Portfolio Studio – up to 50,000 asset in its one catalog

Netpublish:

Portfolio uses completely new technology for its Netpublish feature. This means that you will need to re-create any existing sites that you’ve created in previous versions.

External Databases:

Portfolio does not support external database connections. If you used external databases in Portfolio Server, including MS-SQL, MySQL, and Oracle, you will be able to migrate their data into Portfolio.

Again, we strongly recommend that you test out Portfolio before upgrading your production setup.

Moving to a Different Server

If you want to install Portfolio on a new server, see this article on how to migrate Portfolio Server 11 to a new system before proceeding.

Requirements:

You must be running Portfolio Server 11.2 before upgrading to Portfolio. If you have an older version installed, see this KB article on how to upgrade.

Make sure that your system meets the recommended requirements:

Windows:
http://www.extensis.com/downloads/system-requirements/portfolio-1-windows/
Mac OS X:
http://www.extensis.com/downloads/system-requirements/portfolio-1-mac/

Catalog Recovery

If you have FDB catalogs, they should be recovered before upgrading to Portfolio. This KB article explains how to do that.

Catalog Backup

Before proceeding, you should make a backup of your catalogs. First, stop Portfolio Server. Next, copy the contents of /applications/native-server/catalogs to a safe location. If you have MS SQL, MySQL, or Oracle based catalogs, have your database administrator back them up.

Uninstall Portfolio Server 11.2

Portfolio Server 11 needs to be uninstalled before running the Portfolio installer.

Windows

Before you uninstall on Windows, you need to find out what account Portfolio Server is running under.

Open the Services console found in your Control Panels, under Administrative Tools.

Look in the Name column for Portfolio Server, then look in the Log On As column for the domain and account name. Make a note of this because you will need it later.

1. Go to Start -> Control Panel -> Programs and Features
2. Select ‘Extensis Portfolio Server’
3. Right-Click on it and choose ‘Uninstall’ and click through the prompts
4. Do not delete the files that are left behind!

Restart the server after uninstalling

Mac OS X

1. Open /Applications/Extensis/Portfolio Server/applications/Uninstaller
2. Launch the Portfolio Server Uninstaller.pkg and follow the prompts
3. Keep the files and folders that are left behind!

Install Prerequisites:

Portfolio requires Flash Player for Portfolio Administration and for Portfolio Web. It also requires Quicktime Player for some video formats, and Adobe DNG Converter if you intend to work with DNG files. If you are upgrading from Portfolio Server, you should already have these items installed. Here are links to the latest installers, in case you need them:

• Flash Player
• Quicktime
• Adobe DNG

Install Portfolio

Launch the installer for Portfolio and follow the prompts. On Windows, you will be prompted to enter a service user. Enter the account credentials from the previous uninstall steps. When the installation is done, the Portfolio Administration app will launch in your web browser.

Login with the username administrator and the corresponding password you previously used for Portfolio Server administration.

Once you’re logged in, you’ll need to enter your license keys.

Migrate Catalogs

Portfolio comes with a DBMigrator tool, which will convert existing FDB, MySQL, MS SQL and Oracle catalogs into the new database format that Portfolio uses. Please be aware that the larger your catalogs are, the longer the tool will need to convert it. Please be patient!

Run the DBMigrator tool:

Before proceeding, make sure that Portfolio is running and that you’ve entered your license keys.

In case there are errors during the migration, set Portfolio logging to ‘Error’ under Global Settings in Administration.

In the commands below, replace [password] with your Portfolio administration password and replace [catalogname] with your actual catalog names.

Windows

1. Open the Command Prompt
2. Type in:
   cd "C:\Program Files (x86)\Extensis\Portfolio Server\applications"

• To list catalogs
  DBmigrator -p [password] -l
• To import all Catalogs
  DBmigrator -p [password]
• To import specific catalogs:
  DBmigrator -p [password] [catalogname]

Note: If the catalog name has spaces in it, surround its name with quotes: i.e.: DBmigrator -p password "Nuts & Bolts.fdb"

Mac OS X

1. Open the Terminal
2. Type in:
   cd /Applications/Extensis/Portfolio\ Server/applications

• To list catalogs
  ./DBmigrator.sh -p [password] -l
• To import all Catalogs
  ./DBmigrator.sh -p [password]
• To import specific catalogs:
  ./DBmigrator.sh -p [password] [catalogname]

Note: If the catalog name has spaces in it, surround its name with quotes: i.e.: ./DBmigrator.sh -p password "Nuts & Bolts.fdb"

The DBMigrator will display “Import Complete” when it’s finished.

Note: If the DBmigrator displays errors when attempting to migrate a catalog, there’s a possibility that the catalog is damaged. Contact Extensis Technical Support if you encounter a problem with catalog migration.

You can delete the contents of the /applications/native-server/catalogs folder when the catalog migration is complete.

Description

How do I import metadata into a Portfolio catalog?

Solution

This article explains how to import metadata from a text file into a Portfolio catalog. Please note that these instructions are not valid for Portfolio Server 11 and earlier.

Enable Access Level

Before you can import metadata into a Portfolio catalog, you have to enable the ‘Import Metadata’ permission. The permission is on by default for users with Administrator privileges, but needs to be enabled for Editor and Publisher level users. The ‘Import Metadata’ permission cannot be enabled for Readers.

Note: This is a powerful feature and should only be made available to users who understand it. Mistakes can cause the catalog’s metadata to get erased or incorrectly overwritten.

Here’s how to enable Import Metadata:

• Log into Portfolio Administration
• Click on Access Levels in the strip on the left
• Select Editor or Publisher
• Put a check into the ‘Import Metadata’ option

Create a Text File

Portfolio can import metadata from a tab delimited text file. You can create such a text file with any decent text editor or spreadsheet program. If you have Microsoft Excel, save the file select ‘Text (Tab Delimited)’ from the ‘Save As Type’ list.

Here’s a list of requirements for the metadata import from a text file to be successful:

• A column is required for each metadata field that you will be importing.
• Each column must be separated by a tab, i.e. ‘Tab Delimited’
• Each row must be separated by a Carriage Return, i.e. by hitting the Enter or Return key.
• The field names in the text file need to be identical to the ones in your catalog.
• A column is required for Filename, which lists the name of each file that you’re importing data for. This field acts as a key value, i.e. it is used to link up the text data with the files in your catalog.
• If a field has multiple values, such as Keywords, each value needs to be separated by the | character, i.e. ‘pipe symbol’. Example: apples|bananas|oranges
• Field types in Portfolio determine what type of data they can hold:
  • String or Text Block fields can hold any type of data.
  • Boolean, Date/Time, Decimal, Number, and URL fields can only contain data specific to that field type.

To help illustrate, here’s a screenshot of a simple Excel spreadsheet with two fields: Filename and Keywords:

Note how the multi-value field Keywords uses the | symbol to separate each value.

Here’s a screenshot of the same file after it’s been saved as tab delimited text:

Note the tabs between the Filename and Keyword columns, and the pipe symbol between each keyword

Back up the Catalog

Important! It’s wise to make a backup of a catalog before importing metadata, just in case there’s a mistake in the text file. The Backup/Restore instructions in Portfolio’s online help will show you how.

Import The Text File

Before you import a text file, note the following:

• All existing field values are overwritten.
• Multi-value field data will be replaced.
• If duplicate filenames exist in the catalog, they will all get the same metadata as the first one in the catalog.
• If a field with a predefined list allows additional values, it will allow data to be imported. However, the import will not add new values to the predefined list.
• If a field with a predefined list does not allow additional values, values that are not in the list will be ignored during import.

Note: It’s a best practice to do a test import with only a few lines of data before importing a large text file. If the test is successful, you can import all of the metadata.

Here are the steps for importing metadata when you’re ready:

• Log into Portfolio Web with a user account that has permission to Import Metadata.
• Pick a catalog from the Catalog list in the strip on the left.
• Right-Click (Win) or Control-Click (Mac) on the ‘All Items’ gallery, then select ‘Import Data’.
• Select your text file in the dialog that opens up.
• Portfolio will then process the text file and add its metadata to your catalog. You can monitor progress by clicking on the ‘Show Jobs’ option.

Description

When using Portfolio Express on the Mac, I get an error that states “The share ‘sharename’ is not mounted.” and am unable to drag and drop items into Finder or other applications.

Solution

This can happen if Portfolio Server is on Windows and Portfolio Express is being used on a Mac.

To work around this, unmount the Portfolio share and remount it with the drive letter C$.

Example: If the files are on a server named Portfoliobox and on its C:\ drive, use the following in your Mac’s Connect to Server dialog:

smb://Portfoliobox/C$

Description

How many user accounts can I add to Portfolio?

Solution

Portfolio supports up to 5000 unique user accounts per installation.

Description

My Portfolio backup sizes don’t decrease after I delete catalogs.

Solution

In the current version of Portfolio, deleting a catalog does not delete its data from Portfolio’s PostgreSQL database.

If you want to remove the deleted catalog data from the PostgreSQL database to reclaim disk space and decrease backup size, you can use the following steps:

• Log into Portfolio Administration
• Stop the Portfolio Server
• On Mac OS X:
  • Open Terminal
  • Type in the following and hit Return:

    /Library/Extensis/Portfolio/pgsql/bin/psql -h localhost -p 25432 -W -c ‘vacuum full’ portfolio portfolio

• The command will prompt for a password. Type in esp and hit Return
• On Windows:
  • Open the Command prompt
  • Type in the following and hit Enter:

    "C:\Program Files (x86\)Extensis\Portfolio Server\applications\pgsql\bin\psql" -h localhost -p 25432 -W -c ‘vacuum full’ portfolio portfolio

  • The command will prompt for a password. Type in esp and hit Return

If you need assistance with this, feel free to contact technical support for assistance.

Description

I got logged out of Portfolio Administration when restoring a large backup. When I try to log back in, an “IdentitySeiUnavailable” error is displayed and then I am unable to log into Portfolio Administration.

Solution

Restoring large backups can take a bit of time. If you try to log in to Portfolio Administration before the backup is completely restored, you will get the “IdentitySeiUnavailable” error.

Wait until the restore is complete, then you should be able to log in.

Description

I removed some file or folder exclusions from Portfolio Administration. Files and folders that match the deleted exclusions are not being cataloged by Autosync.

Solution

This issue exists in the initial release of Portfolio. There are two workarounds:

1. Restart Portfolio
   • Log into Portfolio Administration
   • Click on ‘Status’ at the top of the left column
   • Click on ‘Restart Portfolio’
   • You can close Portfolio Administration when you’re done
2. Remove and re-add the watch folder after the exclusion rule has been removed.
   • Log into Portfolio Web with an Administrator level account
   • Choose the catalog you are working with
   • Double-click on the folder that is going to be removed. The Update Watch Folder dialog will display
   • Click on the ‘Options’ tab and make a note of the settings. Click ‘Cancel’ when you’re done
   • Select the folder you want to remove and click on the – (minus) symbol below it. You will be asked to confirm, so click on ‘OK’
   • Click on the + symbol below the Folders pane and select ‘New Watch Folder’. The New Watch Folder dialog will appear
   • Click on ‘Browse’ and select the folder that you just removed, then click on the ‘Select Folder’ button
   • Change any of the remaining settings, then click on ‘OK’.

Both workarounds will force Portfolio to acknowledge the exclusion changes that you were made.

Description

Some users have encountered an error that states “Suitcase Fusion Client has encountered an unexpected error. 83914764″ after upgrading to Mac OS 10.8 and were also unable to activate fonts.

Solution

There are a few ways you can help to resolve this issue:

Before you upgrade your OS:

If you are about to upgrade to Mac OS X 10.8 you will need to stop the FMCore first by doing the following:

1. Open Suitcase Fusion 4
2. Go to the ‘Suitcase Fusion 4′ menu
3. Choose ‘Preferences’
4. Click on the ‘Type Core’ tab
5. Click on the ‘Stop Type Core…’ button

If you’ve already upgraded to Mountain Lion:

If you are already getting the “83914764″ error you can resolve it by doing the following:

Restart the Type Core

1. Open Suitcase Fusion 4
2. Go to the ‘Suitcase Fusion 4′ menu
3. Choose ‘Preferences’
4. Click on the ‘Type Core’ tab
5. Click on the ‘Stop Type Core…’ button
6. Relaunch Suitcase Fusion 4

If the issue still persists after the above steps, check out additional assistance at this article.

Please fill out the form below, being as specific as possible about the nature of your problem. Our technical support team can help you with technical issues related to the installation and/or use of your Extensis product.

Please do not use this form if you require Customer Service. Instead please fill out the proper form to contact Customer Service.

Please fill out the form below, being as specific as possible about the nature of your problem. Our customer service team can help you with account related issues.

Please do not use this form if you require Technical Support. Instead please fill out the proper form to contact Technical Support.