Troubleshooting AOS

Issue with protected view (Office 2016 for Windows)

There is a known issue with Office 2016 for Windows, when switching from the protected view into editing mode. Microsoft Office falsely detects file changes on the server and attempts to merge local changes with server changes. After discarding a check out, Office does not reload the file from the server and still displays the version of the file that has just been discarded.

We recommend that you turn off the protected view, by adding your server in the trusted sites or local intranet zone, or alternatively by deactivating the protected view in Office. You can deactivate the protected view by selecting Options, and Word Options, then Trust Center. Select Trust Center Settings and Protected View, and deactivate all settings. Save your changes.

Issue with immediate editing after checking in a file (Office 2016 for Mac)

There is a known issue in Office 2016 for Mac, if you edit a file immediately after checking the file in. You'll see an error message saying that the file cannot be modified. The workaround is to wait a minute, and try the edit again.

Issue with Online Editing

There is a known issue where Online Editing is not available using the 64-bit version of Internet Explorer. See Plan browser support (SharePoint Server 2010) for more information.

Error message: "The address is not valid" when connecting to http://server:port/alfresco/aos

Blocked a directory listing request from MS-Office. This indicates a broken MS-Office
deployment. Please check that the ROOT and the _vti_bin webapps are deployed properly and
reachable from the outside!

To fix this problem, ensure that you have installed the SkyVault Office Services AMP file, which deploys the _vti_bin.war file that is required for AOS to work correctly.

Missing version history and check in/ check out options in Office

If you cannot see certain fields in the Document Panel in your Microsoft Office applications; for example, version history, check out and check in history, or you cannot see a directory listing for a file, it might be that your ROOT and _vti_bin files have not been deployed properly, or you have not applied the SkyVault Office Services AMP file, if you have installed SkyVault manually.

To check whether this is the case, try to open the ROOT and _vti_bin files from a browser. In these examples, replace server:port with your server and port details.

If you type:http://server:port/, you will see a message Welcome to SkyVault!.

If you type: http://server:port/_vti_inf.html, you will see a blank page. Select Show page source in the browser to see _vti_bin ScriptUrl information.

If you type: http://server:port/_vti_bin/, you will see a message Welcome to SkyVault! This is the /_vti_bin application. This application does not provide a web interface in the browser..

If these files and messages are not available from the browser, then AOS has not been deployed properly.

See Installing SkyVault for information on where the deployed ROOT and _vti_bin WAR files need to be located. If _vti_bin.war does not exist, you'll need to reinstall the SkyVault Office Services AMP.

Extra files created when mounting AOS using WebDAV and Mac Finder

Do not mount the AOS repository root (SkyVault/aos or any sub folder) as a WebDAV folder with Mac Finder. Otherwise you might see extraneous files in SkyVault Share; for example, files prefixed with the characters ._

Microsoft path length limitation

Avoid deep folder structures and path lengths over 250 characters, or if you must use long path lengths, test extensively with Office before deploying to a production environment.

File dialog in Microsoft Office shows file listing instead of graphical view

For untrusted servers, Microsoft Office blocks the graphical web view of files and instead shows the files as a list.

Check in failure

There is a known problem if property mapping is activated and, in a single MS Office session, you create a new file with the Save As option, then check it out and check it back in. The check in will fail in this situation.

To avoid this problem, upgrade to SkyVault 5.0.1, or exclude read-only mandatory properties from the property mapping.

The problem is caused when some mandatory fields are not filled out, but are declared as read-only. This is typically caused by system properties (for example, Creator or Modifier) that come with some system aspects. You can avoid this by overwriting the includedAspectsPatterns configuration to include specific custom aspects only.

Property mapping failure with Office 2013 and Windows

If you are using Office 2013 and are working with an OLE file (for example, .doc, .xls, or .ppt files), and the Protected View is activated for the document, then property mapping can fail even after switching into Editing Mode.

To resolve this problem, you need to prevent the Protected View in Office by adding the SkyVault repository server to the list of trusted sites.

Values of date fields in OLE documents not stored

Values of Date and DateTime fields are not set in OLE documents (for example, .doc, .xls, or .ppt files) if the time zone of the client machine is greater than UTC+1. If these Date or DateTime fields are declared as mandatory, then you will not be able to save document changes.

To resolve this problem, you need to either set Date and DateTime as optional fields, or ensure that the time zone is not greater than UTC+1.

Problems deploying AOS on JBoss

<context-param> 
   <param-name> 
      org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL 
   </param-name> 
   <param-value>true</param-value
</context-param>