Error reproduction:

In a clustered environment, a ProjectWise user opens properties of a document and imports a new file from his computer to replace already existing file that is currently linked to said document.

In some cases user will receive a file not found error and the document will be left locked in "coming in" state.

Solution:

Three  DWORD values need to be created in registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters\Directory

CacheLifetime

FileInfoCacheLifetime

FileNotFoundCacheLifetime

All values should be set to 0.

Further notes:
https://blogs.msdn.microsoft.com/winsdk/2009/07/10/file-exists-_access-getfileattributes-findfirstfilefindnextfile-_stat-behavior-over-smb-2-0/

To view files stored in a ProjectWise repository you need to setup a connection to the repository.

Administrators can create repositories so each ProjectWise Project has the connection automatically configured. 

Please follow the steps bere to pre configure Work Area Connections:

https://communities.bentley.com/products/betas/projectwise-share-work-area/w/projectwise-share-work-area---wiki/36678/2---managing-connections

The next steps will help create repositories manually.

1. From the Repositories screen, select the Connect to Repository icon.  The Connect to Repository dialog box opens.
2. In the Server URL field, type in the server URL provided by Bentley Web Services Gateway. Check with your IT administrator for this URL. ProjectWise Edge attempts to connect to the server and get a list of available repositories.
3. From the Repository dropdown, select the desired repository.
4. Enter your Username, Password, and Name in the appropriate fields. If you wish, you may provide a Description as well.
5. Select Continue. ProjectWise Edge connects to the repository. The name and description of the repository display in the repository list. You can now open the repository by double clicking it and navigate through the folders to find the files you want. ProjectWise Edge remembers your connection information so you do not need to login to the repository again unless your password changes.

Editing and Deleting Repositories

You can edit or delete a connection to a repository by selecting the edit icon  or the delete icon  from the Repositories list. Selecting the edit icon opens the Edit Repository dialog where you can change the Server URL, Repository, Username, Password, Name, and Description. When you select the delete icon, you are asked to confirm that you wish to remove the repository. Removing the repository deletes the repository connection, and all favorites, folder shortcuts, and connection credentials for that repository.

Problem Description: The location of Central Model in Revit sometimes changes from the mapped drive to the local directory of the user as seen in the snapshots below.

Cause: When Revit is unable to find a linked file, it opens a “Resolve Links” window for the user. If while opening a file, the “Create New Local” option is ticked and the “Resolve Links” window pops up next, it creates a new Central File instead of new local file, hence the path of the central file changes. This is a defect identified in ProjectWise Explorer version 10.00.02.320 and has been rectified in 10.00.03.49 version.

Steps to recreate the issue: This happens when “Create New Local” is turned on while resolving links for the Central Model. This issue can be recreated using the following steps.

1. Launch Revit and create new central file. Save it in ProjectWise Explorer
2. Insert Revit Link to this file from ProjectWise. Save the file, close it and then check In.
3. Open the ProjectWise Explorer and delete Revit link file which was linked in Step 2.
4. Open central file from ProjectWise Explorer.
5. In the 'Open File' dialog, select 'Create New Local' to create a local copy, click OK 
6. Select new link file location in "Resolve Links" dialog and press OK button
7. New central file will be created in the local machine instead of local copy

Solution to correct the path of the files:

1. Open the files directly from ProjectWise without the create local option.
2. Once the file is open, resolve the links, if any, then save and close file, it will get checked in.
3. Open the file with the options you want to use.

Solution to avoid this issue: We have 2 solutions in this scenario:

1. Upgrade to 10.00.03.49
2. Uncheck the option “Create New Local” every time the user opens a Revit File.

Error message and log information

User is able to log in to connection client. User can log in to ProjectWise using logical users. When he attempts login with IMS authentication (while connection client is already connected), error 58274 is thrown

Log reads something like below:

2018-03-22 11:39:38,691 WARN  [0x000049b4] pwise.security.sts - GeneralClaimsIdentityProvider::ValidateSecurityToken: SecurityTokenException occurred: System.IdentityModel.Tokens.SecurityTokenException: ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer.

   at System.IdentityModel.Tokens.SamlSecurityTokenHandler.ValidateToken(SecurityToken token)

   at System.IdentityModel.Tokens.SecurityTokenHandlerCollection.ValidateToken(SecurityToken token)

   at Bentley.GeneralClaimsIdentityProvider.ValidateSecurityTokenInternal(GeneralClaimsIdentityProvider* , Char* token, IClaimsIdentity* nativeClaimsIdentity, List`1& updatableTrustedIssuers, String& configFilePath)

   at Bentley.GeneralClaimsIdentityProvider.ValidateSecurityToken(GeneralClaimsIdentityProvider* , Char* securityToken, IClaimsIdentity* claimsIdentity)

2018-03-22 11:39:39,723 ERROR [0x000049b4] pwise.security.sts - FederationMetadataRetriever::GetSigningCertificates: exception occurred: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 104.209.211.13:443

   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

   --- End of inner exception stack trace ---

   at System.Net.HttpWebRequest.GetResponse()

   at Bentley.FederationMetadataRetriever.GetSigningCertificates()

Cause

In this particular case, certificates were changed at IMS so thumbprint provided to the client requesting federation data is not getting validated and connection is termed non-secure. A certificate thumbprint is a hexadecimal string that uniquely identifies a certificate. IMS does not provide any data to such connection and refuses connection.

Usually in such events, client (PWDI server in this case) should be able to re-request and get a new thumbprint. In this case something is stopping it from doing that.

Resolution

Thumbprint for IMS connection is available on ProjectWise Design Integration Server machine in C:\Program Files\Bentley\ProjectWise\bin (for default installation location secection) directory. Find and open Bentley.projectWise.IdentityproviderRP.Core.dll.cfg file (Bentley.projectWise.IdentityproviderRP.dll.cfg in case of old versions).  Contact ProjectWise Technical Support group and get a new thumbprint. Manually replace the value in above configuration file and attempt connection.

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.

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 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

Load Behavior

   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"

There is no “Silver Bullet” when it comes to improving performance with integrated Civil 3d. The list of suggestions below come from many sources Colleagues, Service Requests and Civil 3d user groups. When combined you will be surprised at the difference.

PLEASE TEST in your environment before applying this to Production data.

• NO WORKING ON PROJECT FILES OUTSIDE OF PROJECTWISE EXPLORER – EVER
  Do NOT export them and then import them after editing. Do NOT edit them directly in your working directory. This is the number 1 cause for slow performance.

• ProjectWise version needs to be 10.00.03.49 for all users – Performance improvements and a fix to the nested Ref issue.
  
  
• ALL Project Participants (that work in Civil 3d) need to use ProjectWise version 10.00.02.320 or higher.
  
  
• Run scanref to correct the Xref file links for all ProjectWise drawings – Do not include the Data Shortcut folders
  DSFolderRepair can be used on the Data shortcut folder to find and repair data shortcuts.
  
  
• Lower User Access on shortcuts – Only the users that create, edit and control data shortcuts should have write rights. Everyone else should be read-only.
  
  
• Installation of ProjectWise Data Shortcut editor – Only for the users that create, edit and control the data shortcuts. The data shortcut file should be maintained so that it is as error free as possible. Remember that when you have the DSProj file open it is checked out to you and nobody else can change it.
  
  
• Add DMSSET commands to the Civil3d startup LISP or to the profile
  • If using Sheet Set Manager set SharedSheetSets = 1 & SheetSetUnlockTime = 10 (sec) to 3 or 5.
  • Use #HOOKLESSREPATH = 1 to automatically repair broken data shortcuts
  • Set SHEETCHECKUPDATETIME = 120 (Sec) to 4 (240) or 5 min (300) to lengthen the time between checking for reference file changes.
  • INDEXCTL = 3 To organize files by layer and spatial data for faster file open and recalculation. (See the Autodesk help and website for more info on this.)
    
    
• The workstation should have as much memory as possible. Set virtual memory to 2x physical memory. (From the Autodesk discussion group)
  
  
• Each user’s ProjectWise network settings need to be adjusted so that only the needed datasources display. – Improves the connection and reconnection time.
  
  
• Create specific program names and Open actions in for every version. i.e. Civil3D 2016, Civil 3d 2017, … Using less specific program groups (such as ACLauncher) can cause integration to fail or open more slowly. Program groups should be like “AutoCAD.acadCivil3d.Drawing.PW.22.0.”

This is a first draft being posted because I have gotten many requests for the information. It will be under construction for some time.

Please feel free to add comments and additional information that you may have found.

Problem

58060 Error Creating new document. Cannot Access storage directory. Storage area directory has been removed or Projectwise caching server is not on the specified server.

Scenario

User took a backup of his 08.11.11.590 database, restored it to a test server 10.00.03.49, created ODBC connection, ran dmsconv and then created the datasource connection via PW admin.  Changed storage areas to point to an allowable location for storage areas (dmskrnl.cfg [FileStorageService] StorageLocation0=C:\PWSTORAGE) so he was not using production files. Did not move original folders to new storage.
In ProjectWise Explorer drag and drops a file into an existing folder.
User gets error 58060 Error Creating new document. Cannot Access storage directory.  Storage area directory has been removed or Projectwise caching server is not on the specified server.

Steps to reproduce

This can reproduce In ProjectWise 10.00.03.49 by simply changing the storage area location.
Change a storage area to point to a new location that is included as an allowable location for storage areas (dmskrnl.cfg [FileStorageService] StorageLocation0=C:\PWSTORAGE), do not copy over folders and files
Drag and drop a file into an existing folder in PW.
The folder\file does not get created and User gets error 58060 Error Creating new document. Cannot Access storage directory.  Storage area directory has been removed or Projectwise caching server is not on the specified server.

Solution

This is a known issue and has to do with new security settings in PW.

User will need to either create new folders for testing or copy the original storage area to the test server’s storage area.

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Error or Warning Message

Last Error 112233 CONNECTION Client could not be accessed- unknown error occurred.

Failed to retrieve a login token from CONNECTION Client.

Explanation

Might happen when logging into ProjectWise Explorer with Bentley IMS credentials.

How to Avoid

1. Have user verify if they are registered to the organization by going here: https://ims.bentley.com/IMS/Profile
2. If the organization field is empty in the profile, an admin will need to add them to the organization via user management tool
3. Have user log out and log back into CONNECTION Client
4. If the issue still occurs do the following:
5. Close the CONNECTION Client

1. 1. Close the CONNECTION Client
   2. Delete the MySELECT.db file found in %localappdata%\Bentley\
   3. Relaunch the CONNECTION Client

Error or Warning Message

Error 58273 Cannot login to the datasource

Identity mismatch. Please contact your ProjectWise Administrator

Explanation

When logging into ProjectWise Explorer using Bentley IMS login, there is a mismatch between the PW account settings and the email account logged into the CONNECTION Client

How to Avoid

1. In PW administrator, users section, browse to the user having the issue
2. Open the users properties, Federated Identity tab
3. Click disassociate
4. Enter the users email address in the Identity name field and click apply (note this should match the email logged into the CONNECTION Client)

Possible issues when using Bentley IMS Login Credentials

Navigate to https://connect.bentley.com - Select the Connected Project & click Field Data Management:

Click Settings

The DESIGN FORMS will be greyed out if the user is not an\a:

• Administrator
• Co-Administrator
• Project Manager

------------------------------------------------------------------------------------------------------------------------------

How to check a User Role's? 

NOTE: Only a CONNECT Services Admin will be able to see\modify the following information

Navigate to the Connected Project using your Browser: click Settings or click Manage Members

This will bring up the Project Team Management page:

Some User(s) may have one or more Role's - To Assign a New or Remove a Role from a User - Select the User: Add from the Available Roles or removed from the Role(s) to be Assigned by highlighting.

Permissions for a User on a Project can be check & Edited from Manage Roles:

A Connect Administrator will likely have all the permissions, whereas a User(s) depending on his\her Role(s) may have different permissions

TIP: A Custom Role can be created if required by clicking "New Role"

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Scenario:

1st scenario: Need Access to Design Forms in Field Data Management - Provide access to the User

2nd scenario: User is a CONNECT Services or Co-Admin& is set up as a Project Manager for the specific Project but Design Forms is still greyed out. 

- Verify the information on the Connect Portal

- Launch ProjectWise Explorer

- Navigate to the Connected Project & expand the node

- Right click Deliverables Management (ProjectWise Deliverables Management connector for ProjectWise Explorer needs to be pre-install)

- Click Settings

This will bring up the Deliverables Management Settings page:

From the above - Two User's are Project Manager however one has just View package enable.

Reason: A User can be part of one or more group which was getting his rights overwritten

Solution: Removed the User & add him back 

Important: How to manage permissions for ProjectWise user groups/lists or individual users?
When you set permissions for a ProjectWise group or user list, all members of the group or user list inherit those permissions. If a ProjectWise user is added to the internal participants list twice (once as an individual user, then again as a member of a group or user list), the permissions set for the individual user will override the permissions the user inherited from the group or user list they are a member of

For more information on Field Data Management refer to the link below:

https://communities.bentley.com/products/projectwise/content_management/w/wiki/32432/field-data-management-welcome 

Background

After installing ProjectWise Language pack (localization) the language of the application did not change.

Steps to Accomplish

After installing the ProjectWise localization (language pack) the language needs to be changed in the User Tools. To do that:
1. Using Windows 7 open: Start -> All Programs -> Bentley -> Projectwise V8i (SelectSeries X) -> Tools -> User Tools
    or using Windows 10 open: Start (->All apps) -> Bentley -> User Tools

2. Open the Set Locale and select the required language.

3. Restart the ProjectWise Explorer and the language will be changed.

ProjectWise Edge Mobile is a client for your iOS tablet or phone. This application provides the following functionalities. 

Version 05.05.21.30

• Import multi folders: Quickly  drag and drop folders with documents from your desktop to upload folder and files
• Added missing icons: Enhanced user experience added missing icons for Visio, MSG and TXT
• Display document attribute sheets: Review file with attribute sheets attached to documents
• Keyboard Enter support in Advanced Search: Simply hit enter on keyboard to run advanced search
• Removal of Personal Share
• New Form features: Forms dependent dropdown control, Time tracking support and Attachment caption
• Performance & Refresh update: Make sure files are always up to do with auto refresh running in the background
• Work Rules Engine (Technology Preview): Edge apps now support WRE commands from ProjectWise Design Integration 10.00.03.49. Please NOTE version of ProjectWise Design Integration and WSG (PWplugin) version 02.06.05.07
• Bug fixes

Version 05.05.20.26

• Advanced Search:Find files in your repository connection in your common data environment of ProjectWise faster using new criteria to narrow your search results
  
• Multi file upload: Drag and drop  multiple files from desktop
• Lock name field and document field:Identify  and organize content easily by synchronizing name field and file name
• Auto Refresh on file and folder:Ensure you are always looking at the latest content
• Auto logging configuration: Save time when troubleshooting issues with enabling detailed logging and accessing logs location
• Proxy Configuration: Configure local proxy to access content outside your company securely
• New UX interface: New and improved update on interface
• Quick Start Guide: Guide now walks you through important settings and explains in details each feature
• ProjectWise Share: Update to accessing ProjectWise Share

File upload

Folder creation

File folder rename

File folder delete

• Bugs Fixes

Version 05.05.12.14

• Access ProjectWise Work Area Connections: ProjectWise Projects can now be configured on connect.bentley.com to automatically bring on-premise ProjectWise Work Area connection to the app automatically when a ProjectWise Project is selected.
• Form Attachment with location: Adding an attachment to a form can now set a location from where that attachment was taken from.
• Ability to clear locally stored data: Data that is cached can now be cleared via a button in the settings area. This will clear cache for shortcuts, manually created connections and favorited items.
• Bug fixes

Version 05.05.06.35

• Form Capability:
• Single Sign On (SSO) Support for Bentley managed services:
• ProjectWise Share Access
• Multiple Language Support
  • Chinese
  • Traditional Chinese
  • Korean
  • Japanese
  • Spanish
• Check out/In capabilities
• Updates server copy
• Free documents/files
• Copy file
• New folder creation
• Deleting documents and folder
• Importing documents

Version  05.05.04.50: Commercial Release 

• Quick Access to CONNECTED Project Features
• Access Workflows
• Access Issue Resolution Punch List forms
• Click on a CONNECTED Project link for direct access to CONNECT.BENTLEY.COM browser access
• View Mapped view of Project location
• Changes ProjectWise document States
• Review documents in specific Workflow and States
• Set Final Status on document
• New UX Icon to show read-only and final status documents

Error 55501 - Failed to Connect to the Remote Server Application by jcallicott

Greetings,

I happened upon a bit of info that I hadn't seen documented, so I wanted to pass it along. 

I had several users getting Error 55501, and were unable to open or otherwise download files. I couldnt figure out why initially, and saw the post

communities.bentley.com/.../12240.last-error-55501

I realized he project in question was in a new storage area. Even stranger, only external users were affected - it worked in the local office (the same office where the Integration Server is located). 

The fix in PW Administrator, when looking at the properties on the storage areas, the "Computer Name or IP address:" field, the Integration server name was entered as: "servername".  It did not have the fully qualified domain name (FQDN). I thus opted to re-name it using the FQDN thus: "servername.company.com" and not just "servername".  That turned the trick and eliminated Error 55501 for external users. 

If you have Windows 10, and cannot Drag and Drop documents from your Windows Explorer to your ProjectWise Explorer (get circle with line through it). You can fix this by going to your lower menu bar, right click on it, and select “Task Manager”

In Task Manager, Select “PWC for Windows” > right click > Properties > Compatibility tab > Uncheck “Run this Program as Administrator” (see next two screen shots).  You would now need to close ProjectWise Explorer, and then Re-Open it. You should now be able to drag and drop documents from Windows Explorer to ProjectWise Explorer.

ProjectWise Design Integration Flow Connector is a new way to get more work done in Design Integration. It is a self-service automation tool for individuals or teams. It can be used to automate repetitive tasks, interact with Office 365, connect to a growing number of other cloud services, and more. 

Flow users do not have to have any administrator rights. A regular ProjectWise account is sufficient. Microsoft Flow designer provides an intuitive graphical interface for designing Flow logic. No prior coding experience is required.

(tbd)

(tbd)

(tbd)

There is no “Silver Bullet” when it comes to improving performance with integrated Civil 3d. The list of suggestions below come from many sources Colleagues, Service Requests and Civil 3d user groups. When combined you will be surprised at the difference.

PLEASE TEST in your environment before applying this to Production data.

• NO WORKING ON PROJECT FILES OUTSIDE OF PROJECTWISE EXPLORER – EVER
  Do NOT export them and then import them after editing. Do NOT edit them directly in your working directory. This is the number 1 cause for slow performance.

• ProjectWise version needs to be 10.00.03.49 for all users – Performance improvements and a fix to the nested Ref issue.
  
  
• ALL Project Participants (that work in Civil 3d) need to use ProjectWise version 10.00.02.320 or higher.
  
  
• Run scanref to correct the Xref file links for all ProjectWise drawings – Do not include the Data Shortcut folders
  DSFolderRepair can be used on the Data shortcut folder to find and repair data shortcuts.
  
  
• Lower User Access on shortcuts – Only the users that create, edit and control data shortcuts should have write rights. Everyone else should be read-only.
  
  
• Installation of ProjectWise Data Shortcut editor – Only for the users that create, edit and control the data shortcuts. The data shortcut file should be maintained so that it is as error free as possible. Remember that when you have the DSProj file open it is checked out to you and nobody else can change it.
  
  
• Add DMSSET commands to the Civil3d startup LISP or to the profile
  • If using Sheet Set Manager set SharedSheetSets = 1 & SheetSetUnlockTime = 10 (sec) to 3 or 5.
  • Use #HOOKLESSREPATH = 1 to automatically repair broken data shortcuts
  • Set SHEETCHECKUPDATETIME = 120 (Sec) to 4 (240) or 5 min (300) to lengthen the time between checking for reference file changes.
  • INDEXCTL = 3 To organize files by layer and spatial data for faster file open and recalculation. (See the Autodesk help and website for more info on this.)
    
    
• The workstation should have as much memory as possible. Set virtual memory to 2x physical memory. (From the Autodesk discussion group)
  
  
• Each user’s ProjectWise network settings need to be adjusted so that only the needed datasources display. – Improves the connection and reconnection time.
  
  
• Create specific program names and Open actions in for every version. i.e. Civil3D 2016, Civil 3d 2017, … Using less specific program groups (such as ACLauncher) can cause integration to fail or open more slowly. Program groups should be like “AutoCAD.acadCivil3d.Drawing.PW.22.0.”

This is a first draft being posted because I have gotten many requests for the information. It will be under construction for some time.

Please feel free to add comments and additional information that you may have found.