Office Integration issues are a challenge to resolve. This post is written as a progression to help you step through the workflow to resolve these issues. Test each step before moving to the next one.
This post is written using Word as the example and applies to all the Office Integrated apps, such as Excel.
Note: This is a living document if you discover something that resolves your issue and it isn't in this document, please add it.
Opening a Second or Third .XLS (old format) in ProjectWise
When opening an Excel .xls (old format) in ProjectWise, you cannot open another “second or third” .xls. No Error message is given. However, you may open a .xlsx, and then open 6 or 7 other .xlsx other ProjectWise integrated Excel spreadsheets. This is a known issue. You may also open a .xls, then open 6 or 7 .xlsx files in ProjectWise.
Note: ProjectWise Explorer Client 10.00.03.167 allows multiple Excel files to be opened without regard to version.
Before trouble shooting make sure that all the Office updates are installed.
Depending on the version of ProjectWise Explorer Client (PWE) that was installed, the office integration may need a separate install module or a new installation.
To check for Office integration:
If there is no ProjectWise Ribbon, there is no integration. If integration is missing you will need to install it.
If the ProjectWise ribbon is present in the ribbon bar, but the ProjectWise variable dialog doesn’t display, then integration may not be fully installed.
At this point if the PWE login dialog doesn’t open (integration isn’t working) open a Service Request.
When an office document doesn’t open from PWE the first thing to check is the ProjectWise application association.
ProjectWise application associations can be set Globally or for a User.
Global ProjectWise associations: Global Associations are set-up by an Administrator using the ProjectWise Administrator client. To setup Global associations, Install the ProjectWise Administrator on a system that has all the programs the client will use. This makes it easier to setup the class paths for the program associations.
User ProjectWise Associations: Some clients may have the software in a different path and thus will need a user specific program association. The most common case is when a user from one organization is logging in another organization’s datasource.
To check the application associations:
If there is a user association, it needs to be removed.
Removing User Application Associations
If the file opens correctly the user association was the problem.
If the file still doesn’t open correctly, then try creating a new user association.
Creating a User Application Association
NOTE: If the program group is not found you will need to follow the reinstall instruction above.
If the file opens correctly the global association was the problem.
If changing the application associations doesn’t resolve the issue it may be that the Com object is unloading.
To Check the ProjectWise com objects:
Look in the Add-ins Dialog for the ProjectWise Com Objects.
There are several reasons why ProjectWise integration add-ins could be disabled; including:
If the add-in has been disabled by Office as a precaution you may need to re-enable the appropriate add-in. But before you do that, make sure that the Bentley add-ins are trusted.
Checking that Bentley is trusted:
If the folders are not there then they need to be added. The paths listed may vary depending on your configuration.
Setting Bentley Folders as trusted:
If Word stops on the blank file again check if the ProjectWise com objects are disabled. If they are then manually re-enable the com objects.
Manually enabling the com objects.
If this selection doesn’t “stick” the next thing to try is to disable the Resiliency registry key.
NOTE: It is highly recommended to use this method as a last resort since removing the disabling of registry keys can have adverse effects on application stability and security.
Please check with your system administrator or IT department for proper direction before changing any registry keys.
Removing the disabling of the com objects in the registry.
The file should now open directly in Office. If you are still getting the blank first page and you are using ProjectWise Explorer V8i - 8.11.11.xx open a Service Request.
If you are using ProjectWise Explorer CE – 10.00.0x-xx the CURVER registry key may need to be edited.
The Attribute Exchange options are grayed out under the ProjectWise tab.Both Com Objects ProjectWise iDestop integration and ProjectWise iDestop integration for Attribute Exchange are selected.
There was another Com Object listed, PWAdminOfficeConnectProxy.
Try deleting the PWAdminOfficeConnectProxy add-in from the Coms Add-ins dialog.
Deleting legacy registry key
When opening Word in ProjectWise, it does not open in Integrated fashion. Can check to see if Load Behavior is set properly in the registry.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Word\Addins\PWOfficeAddIn.ConnectProxy_15 Load behavior should have a value of "3" (ConnectProxy_15 is for office 2013 ConnectProxy_16 is for Office 2016) If using Office 2016, sometimes removing ConnectProxy_15 for Office 2013 will improve the integration with Office 2016.
Is ProjectWise getting a valid license:
A user reported an issue where they double clicked an office file in ProjectWise, the file copied out but then he would get Error 50002: Cant start application for specified document....
ProjectWise requires a valid license and a connection to the SelectServer to report usage. If the SelectServer has not reported usage, and or the ProjectWise integration server had not been able to report usage to the SelectServer and is running in eval mode, or with X amount of days left to report, or if the client is getting its own license from a SelectServer that is not functioning properly, you may see an issue with Office files hanging during the open process. Once the user resolved the licensing issue, Office products opened with no issues.
If this doesn’t resolve the issue open a Service Request