Use this information to help diagnose any problems when using Alfresco Office Services (AOS).
- Issue with Online Editing
- Error message: "The address is not valid" when connecting to http://server:port/alfresco/aos
- Error or blank screen when accessing web server
- Missing version history and check in/ check out options in Office
- Extra files created when mounting AOS using WebDAV and Mac Finder
- Microsoft path length limitation
- File dialog in Microsoft Office shows file listing instead of graphical view
- Check in failure
- Property mapping failure with Office 2013 and Windows
- Values of date fields in OLE documents not stored
- Problems deploying AOS on JBoss
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.back to top
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 Alfresco Office Services AMP file, which deploys the _vti_bin.war file that is required for AOS to work correctly.back to top
Error or blank screen when accessing web server
Access to this web server is disabled by default because it is controlled by basic authentication and does not use Secure Socket Layer (SSL).If you are running an old version of Office, you might see nothing after entering the URL in the Office file dialog.
To rectify this problem, we strongly recommend that you activate SSL when using Alfresco Office Services. For more information, see Configuring SSL. Alternatively, if you need to use a non-SSL connection, you must edit the Mac or Windows registry for every client machine as specified in Setting up Alfresco Office Services using a non-SSL connection.back to top
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 Alfresco Office Services AMP file, if you have installed Alfresco 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 Alfresco!.
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 Alfresco! 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 Alfresco 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 Alfresco Office Services AMP.back to top
Extra files created when mounting AOS using WebDAV and Mac Finder
Do not mount the AOS repository root (alfresco/aos or any sub folder) as a WebDAV folder with Mac Finder. Otherwise you might see extraneous files in Alfresco Share; for example, files prefixed with the characters ._
Microsoft path length limitation
- Office reports that a document cannot be registered and OLE linking is deactivated (due to the path length limitation in OLE)
- The browser plug-in does not open a document
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.back to top
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.
- On each client machine, in Internet Options or Internet Accounts, add the server in the list of trusted sites
- On your local intranet, modify the rules used to identify servers to include your server
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 Alfresco 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.back to top
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 Alfresco repository server to the list of trusted sites.back to top
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.back to top
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>This ensures that the JSF deployer in JBoss uses its own bundled JSF version.