Problem

After running Dmsconv, then logging into datasource for the first time, it prompts me to create tables. I click yes, but get a message “Spatial version record mismatch” and it fails to update\create spatial tables.

After running Dmsconv, then logging into datasource for the first time, it prompts me to create tables. I click yes, but get a message “Spatial tables creation Failed” and it fails to update\create spatial tables.

Followed by Last Error [58199] Cannot Login to the Datasource. Database Version Mismatch. One or more custom tables need conversion. The ProjectWise DMSCONV conversion application and the ProjectWise Administrator must be used before logging into the Datasource.

Solution

The issue is not the DMSCONV process, it is more related to the mounting of a datasource to a new ProjectWise environment and it not having access to the ProjectWise storage area that holds the dmsSystem folder to create the necessary files and tables for Spatial.

If you are in a test environment, Create a test storage area.

Before running DMSconv, log into ProjectWise explorer and determine which storage area holds the dmsSystem folders.  Click on the dmsSystem folder and view the folder properties.

Log into ProjectWise administrator and change the storage area for this storage to your test storage area in your test environment.

Now Run the Dmsconv.

When completed and if successful, log into the ProjectWise administrator, create the Datasource and log in.

You will be prompted to create Spatial tables. Check the box to convert tables, then click Convert

Contacting and engaging Bentley Professional Services is highly recommended for site assessment, installation, and configuration services in support of the upgrade process.

Our global Professional Services organization provides discreet project services to optimize user software and business workflows via a number of managed solutions. Learn more about the various offerings for software plus services, OnDemand operational resourcing, and OnPremise resident engineers

Upgrading from pre-V8 versions of ProjectWise generally requires assistance from Bentley Professional Services due to the complexity of the upgrade.

Articles:

• • Configuring ProjectWise on a Windows 2003 Server [TN]
  • Converting ProjectWise 3.8 to ProjectWise V8 XM Edition [TN]
  • DMS Convert & Installation Issues [TN]
  • ProjectWise 2004 Edition Requirements [TN]
  • ProjectWis SELECTSeries 2 Compabilitiy [TN]
  • ProjectWise SELECTSeries 3 Database Upgrade Time
  • ProjectWise V08.09.04.Xx Modules - Supported Operating Systems [TN]
  • ProjectWise V8 XM Edition New Feature List [TN]
  • ProjectWise V8i Installation - Error 1720
  • Uninstalling a ProjectWise Service That Will Not Uninstall [TN]
  • Upgrading to a New Minor Version of ProjectWise 08.09.04.Xx to .08.09.04.Xx [TN]
  • Upgrading to SS3 08.11.09.91+ & Original Admin User is Deleted TN
  • User Microsoft Installer Technology [TN]
  • Using ProjectWise Explorer V8i Against ProjectWise Integration Server V8i (SELECTSeries 1) [TN]
  • XM Edition Requirements [TN]
  • Spatial version record mismatch failed or Spatial tables creation Failed

FAQ's:

• • ProjectWise 2004 FAQ
  • ProjectWise Explorer V8i (SELECTSeries 1) Client Compatibility [FAQ]

Error or Warning Message

While attempting to import Microstation Configuration files to a ProjectWise Managed Configuration Setting block:

'Could not convert [path] to a long path equivalent.'

Problem Explanation

The Microstation workspace configuration root is currently set to use a mapped drive letter.  The 'GetLongPath' method cannot resolve this to a local volume path, or a network/UNC (\\) path.

How to Correct

The user will need to modify the Microstation configuration saved in that location so that it refers to the location using a UNC path, instead of a drive letter.  

(i.e.. Using \\Server\Share\Folder\ will work, but M:\Folder\ will not.)  

Once the user has made the necessary changes to the configuration, verify that the change has taken effect. 

Workspace> About Workspace...

Verify that the location listed is in a UNC format, not a mapped drive letter.

Close Microstation and retry the import operation in ProjectWise Administrator.

Error or Warning Message

Error 58057 Error creating new document.

Document name is already used in this folder. Use a different name and try again

Explanation

Dragging a document into a folder, after being prompted to create a new version because the document name already exists, but then prompted with the error message.

Older versions of the document exist in the folder, but the name had been changed, so there is no current version of this document.

How to Avoid

Rename document being copied, or rename current version of the document so they match

Original Question: ProjectWise Design Integration v10.00.02.265 by Bob Hanson

We are running ProjectWise Integration Server 10.00.01.67.  I have installed ProjectWise Explorer v10.00.02.265 over the top of v01.00.01.67 on my local windows 10 PC.  I also have ProjectWise Administrator 10.00.01.67 installed.  When I open ProjectWise Administrator I no longer see any users, there is a message that states - "there are no items to show in this view".  I can add a new user, it displays for about a second and then disappears.  Why would that be since I have done nothing to Administrator?  Reviewing the other items in ProjectWise Administrator it appears only the users is affected.

Verified Answer: RE: ProjectWise Design Integration v10.00.02.265 by Kevin van Haaren

I'd revert your Explorer, and probably do a repair install on your admin. ProjectWise CONNECT servers seem really picky about versions of software on admin computer matching what's on the server.  Even though your Admin version matches having a newer Explorer and older Admin probably isn't recommended.

Question: RE: ProjectWise Design Integration v10.00.02.265 by JROD

Same thing just happened to me, I installed PWE 10.00.02.265 on top of PWE 01.00.01.67 and I can no longer see Users in PW admin module v08.11.11.590. Did you end up upgrading your PW admin module to match PWE?

Suggested Answer: RE: ProjectWise Design Integration v10.00.02.265 by Vickie.Hewitt

Kevin gave the correct answer. You cannot mix versions of ProjectWise on a client machine. Also you should always use the same version of PW Admin as the Integration Server. Many people run a VM for the Admin or remote into the server to run it.

It is because of a schema change the users don't show up. There are other problems caused by the mix of 10.00.01.67 and 10.00.02.265 if you look at help about it is help help. Whos knows what else.

Question: RE: ProjectWise Design Integration v10.00.02.265 by Bob Hanson

No, I followed Kevin's recommendation and installed 10.00.02.265 on another PC without Admin.  We are talking about upgrading all but it seems new versions are being introduced faster than we can plan.

Thanks everyone for your quick responses

Error 112219 "Invalid filename"

	Product(s):	ProjectWise Explorer Client
	Version(s):	10.00.02.96
	Environment:	N\A
	Area:	Document Creation
	Subarea:	Rename file

Background

Trying to rename file to CON.doc and getting error:

 

How to avoid it:

Windows reserved names:

CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9

Do not use this names.

Microsoft article about it:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247

 

 

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.

Is Office Up to Date?

Before trouble shooting make sure that all the Office updates are installed.

Is Office Integration 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:

• Open Word from the desktop.
• Select the blank template.
• Select the ProjectWise ribbon.

If there is no ProjectWise Ribbon, there is no integration. If integration is missing you will need to install it.

Install Integration:

• For ProjectWise Explorer V8i - 8.11.11.xx install the appropriate Office Integration Module version add-in.
• For ProjectWise Explorer CE – 10.00.0x-xx Uninstall ProjectWise Explorer and remove any residual files, then reinstall the latest release of ProjectWise Explorer CE – 10.00.02.xx or higher.
• Do a custom install and enable Office integration.
• Launch Word, then select File Open and the ProjectWise login dialog will display.

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.

Reinstall Integration:

• Uninstall ProjectWise and remove any residual files.
• Use a registry cleaner of your choice
• Repair the Office Installation from Programs and Features.
• The best option is to then install the latest release of ProjectWise Explorer CE – 10.00.02.xx or higher. It will deliver the latest integration available for Office.
• Open Word and select File Open. The ProjectWise login dialog will display.

At this point if the PWE login dialog doesn’t open (integration isn’t working) open a Service Request.

ProjectWise Application Associations

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:

• Open PWE and login to the datasource as the user having the issue
• Select Tools à Associations à Programs
• Switch the View to User Associations
• Look at the Application that is not opening correctly
• Expand Open.

If there is a user association, it needs to be removed.

Removing User Application Associations

• Follow the steps above to view the user association.
• Right Click on the Open path and Un-associate it.
• Close the dialog and open a file from ProjectWise.

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

• Select Tools à Associations à Programs
• Change the drop down menu in All Associations (Global and User) to User Associations.
• Select the Application that matches what the file is using.
• Right-click on Open and select Add Association
• Select ProjectWise-integrated Microsoft Word, notice the program group is Word.Document.PW. (This program group was created by the installer.) Select OK to use this program for the association.

NOTE: If the program group is not found you will need to follow the reinstall instruction above.

• Now open a file from ProjectWise.

If the file opens correctly the global association was the problem.

COM Objects

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:

• Open Word.
• Select File àOptionsàAdd-ins

Look in the Add-ins Dialog for the ProjectWise Com Objects.

1. If the ProjectWise com objects are disabled continue to the next step.
2. If the ProjectWise com objects are enabled and Word is still opening to a blank file jump to the final section of this document.
3. If the ProjectWise com objects are missing, go to the first section on reinstallation.

There are several reasons why ProjectWise integration add-ins could be disabled; including:

• The Bentley add-in(s) are not trusted
• Disabled by Office as a precaution
• Disabled as a policy

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.

Trust Relationships

Checking that Bentley is trusted:

• Open Word.
• Select File àOptionsà Trust Center
  • Select Trust Center Settings
  • Select Trusted Locations
  • Look for the following folders in the Trusted Location Dialog:
    • C:\Program Files\Bentley
    • C:\Program Files (x86)\Bentley
    • C:\Program Data\Bentley
    • C:\WorkingDir (This should be the root folder you use for the Work Dirs)

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:

• Select Add New Location
• Browse to: C:\Program Files\Bentley
• Check on the Subfolders of this location are also trusted
• And select OK
• Repeat this for:
  • C:\Program Files (x86)\Bentley
  • C:\Program Data\Bentley
  • C:\WorkingDir (This should be the root folder you use for the Work Dirs)
  • Exit the Trust Center and open a file.

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.

Disabled Com Objects

Manually enabling the com objects.

• Open Word.
• Select File àOptionsà Add-Ins page
  • Select ‘Go’ next to Manage COM Add-ins
  • Select the check box next to “ProjectWise iDesktop Integration” to enable it
  • Exit the trust center.
  • Close and reopen Word

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.

• Use Regedit and find the affected Office product add-in:
  Key: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Resiliency\DisabledItem
  • Your computer may show several office versions. You are looking for the version that corresponds with the Office you are running. 12.0 in the above example.
  • Right click on Disabled items
  • Select Export to back up the key to a safe location.
  • Then delete the keys below disabled items.
  • Exit regedit and Open a file with Word.

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.

Incorrect Version Reg Keys

Deleting legacy registry key

• Use Regedit and find the affected Office product add-in:
  HKEY.CLASSES.ROOT.\Word.Document.PW
  • Right click on Word.Document.PW
  • Select Export to back up the key to a safe location.
  • Then delete the curver keys below Word.Document.PW.
  • Exit regedit and Open a file with Word.
  • Repeat as necessary for additional products:
    • HKEY.CLASSES.ROOT.\Excel.Sheet.PW
    • HKEY.CLASSES.ROOT.\MsProject.Project.PW

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 just hung.  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

Problem

Last Error [50000] error loading Map definition file. Fetching Map Definition file from server failed.

User is getting above error when logging into ProjectWise Explorer. Once logged in the user can only see the top level folder "Documents" and nothing underneath

Solution

User was not part of the group that could read any of the folders\files in ProjectWise. Once his permissions where corrected, he could log in without the error and see the proper folders and files. User has to be able to at least file read in document security in the location where the Maps are defined. (You will need access to the ProjectWise Administrator to determine where Maps are defined)

Problem Description

When I attempt to install Projectwise Explorer on my Windows 10 computer with Microsoft Office 2013 installed, the following error appears: "Microsoft Office 2010 integration feature is selected, but appropriate prerequisites are missing.  Office integration will not install correctly without the following 3rd part packages:  Microsoft .NET Framework 3.5 SP1, Microsoft Office 2010 Primary Interop Assemblies."

Steps to Resolve

1. Microsoft Office 2010 was not installed, however Microsoft Sharepoint Designer 2010 was listed as an installed product in Add/Remove Programs but was not being used.
2. Removing Microsoft Sharepoint Designer 2010 and reinstalling Projectwise Explorer resolved issue.

Problem:

   When launching ProjectWise Explorer, I receive the following error, and the program will not launch

The Application was Unable to Start Correctly (0xc0000005). Click okay to close the application.    

Solution:

   We have seen how some third-party application tracking software will present a case where when ProjectWise Explorer is clicked to startup, it will just present a cursor spin then disappear. We have seen some cases where Windows 7 workstations will work with this tracking software, but Windows 10 presents an error like the below screen capture:

   To get ProjectWise to start, go to the Start button > Control Panel > Administrative Tools > Services > Look for a service with the word “track” in the name. Right click on the application tracking software > properties > Stop the service.   Then try to click on the ProjectWise Explorer to start the application.

Problem

Solution

See Also

XXXXXXX(Add more links as needed for other relevant Be Communities content.)XXXXXXX

Background

Steps to Accomplish

Original Question: Folder descriptions displaying instead of name? by Martin Aitken

I (and others) have folder description being displayed in the tree view instead of the names.

I have been told to untick the "Display Descriptions" box in the Setting tab but I do not have that option available.  This is the view I have had since getting access to PW so I haven't changed anything myself.

Can someone advise please?

Thanks

Verified Answer: RE: Folder descriptions displaying instead of name? by Jeff Burrill

It appears that your account isn't granted the option to "Allow user to change settings" in the User Interface node (where the setting "Display descriptions" resides), which is why it does not appear in the node list. In fact, with the exception of Document List, it looks like your account is not permitted to make changes to any of the other settings nodes.

If you are an administrator you can make the change in ProjectWise Administrator. If not, you'll need to talk to your ProjectWise admin person to get the setting changed.

Question: RE: Folder descriptions displaying instead of name? by Martin AitkenThanks Jeff, I have contacted the administrator to see if they can do this for me
Question: RE: Folder descriptions displaying instead of name? by JRODLook under your User options, settings tab, User Interface then look for "Display Descriptions" if it is checked you will see Descriptions instead of file or Project names.

ProjectWise Edge Wiki

This community will provide capabilities delivered in the ProjectWise Edge Mobile app. It will provide information on new features and allow you to interact with Product Management, Development and the ProjectWise Product Advantage Team. The links above will allow you to post forum questions, that many can answer. We also added a new page called Idea (similar to Reddit) if you have an idea to share, please add it and others can +1 it and the more we see it's a benefit (feature, enhancement, etc...) we will consider it to be added in to a future release. Please take a look around and familiarize yourself with the navigation and links that are available.

Overview of ProjectWise Edge Mobile 

ProjectWise Edge Mobile application provides mobile professionals with access to their project data when they are away from their desk.  Real-time access to project data ensures decisions are made using the most relevant and current information, at the same time, it eliminates the risk of relying on potentially outdated printed materials.  ProjectWise Edge Mobile application provides access to multiple project repositories including Bentley’s ProjectWise Design Integration and  ProjectWise Connection Services   This allows users to directly access secure electronic records for confident decision-making while in a meeting, in the field or while traveling.

Usage Scenario

As ProjectWise users who work on projects with workflow and states, the feature will allow each user to search on your CONNECTED Projects and on-premise project.Each search will provide a hierarchy search from all of your workflows in that project or you can click on a specific state that will return the search results for that state.  

Each ProjectWise CONNECTED Project is now accessible via the ProjectWise Edge Mobile app, all interaction such as design review, marking up, etc.. is available and as a feature. 

ProjectWise links are clickable via emails and will allow any user to click a pw:\\ link that will open the file or prompt the user to select a application on your iOS device from ProjectWise Edge Mobile.

Here is a check list of things to make sure you are ready to use ProjectWise Edge Mobile. 

1. Setup your Bentley Web Services Gateway Server 02.05.02.03+ ; make sure it works via the implementation guide for WSG. which can be downloaded here. 

2. Make sure you CONNECT your ProjectWise project to Bentley Cloud services. Download and setup the cloud integration module plugin Services, which will allow you to associate your ProjectWise Project to a CONNECTED Project on your ProjectWise SS4 (08.11.11.590 or 08.11.11.590 ProjectWise Explroer V8i) environment Please review the linked announcement http://communities.bentley.com/products/projectwise/content_management/f/343469/t/111629 and the plugin can be downloaded from here. 

2a. Make sure you have a ProjectWise Project with files that can be tested with and a workflow with states is associated to that Project

2b. Also make sure the user you will be testing with has the rights to change states in a Project.

3. Make sure you are registered as a CONNECTED user;  please see if you can log in to https://connect.bentley.com if you cannot access it please create a support request. 

4. From the operating systems store install ProjectWise CONNECT Edition to your tablet or phone. Once downloaded and installed you can connect to your Bentley Web Services gateway that has been configured.

5. For ProjectWise to send out clickable links download here and review the document for how to use the add-on.

To register a project with Bentley, the Project Registration utility is used to provide information about a project as well as manage previously registered projects. The CONNECTED Project Registration utility can be accessed by:

1. Go to https://connect.bentley.com/
2. Login with your Bentley IMS credentials (the same credentials used to log into BE Communities)
3. On the Recent projects Tile, Select +New button

4. Fill in the required fields and select "save".  

5. After completing the project registration, select the CONNECT Icon in the upper left hand corner to take you back to the personal  portal.  

6. Select the "My Projects" or the project name from the recent project list.

7. On the project page, select the "ProjectWise Project Mobile" application from the list of application tiles.

See the "Associating on-premise content with the CONNECTED Project" technote for the next steps to take before creating a Share

Review/Markup ProjectWise Documents using ProjectWise Edge Mobile

The following steps will show you how to check out a file using ProjectWise Edge Mobile, open the file using a third-party app such as Adobe Acrobat, make modifications, and check the file back into ProjectWise for access from other users.

Open ProjectWise Edge Mobile on the iPAD

Log into the Repository and browse to the file you want to markup. Remember the third-party app you will be using must be able to open the file format. Is this example, the third-party app is Adobe Acrobat for reviewing a PDF file. Press on the document until the context menu appears and choose Check out.

You will see a red check mark next to the filename indicating the document has been checked out.

Press on the file until the context menu appears and choose Open In.

You will be presented with a list of apps on the iPad that can read the specific document format. In this example, choose Copy to Adobe Acrobat.

The document will now open in the third-party app. Make the modifications and Save the file.

The third-party app should have an Open In icon or a similar option for copying the file into another app. Adobe Acrobat has this icon in the lower right (box with arrow).

You will be presented with a list of apps on the iPad, choose Copy to ProjectWise.

You will get prompted to Update the file.

Once the file is updated, press on the file until the context menu appears and choose Check In.

You will not see the markups in the ProjectWise Edge preview but you can open in the original app you made the modifications in and you will see the markups. Once the document is updated and checked in, the changes can be viewed in ProjectWise Explorer or ProjectWise Edge Desktop.