Problem Description

When I attempt to create an iCS scheduled job via iCS Administrator, the following error occured: “Projectwise Login Failed.  No database connection is active at the moment.” If I try to create an adhoc iCS job from Projectwise Explorer, the following error appeared: “The following error occurred on 'servername' inside BeginProcessor.ProcessMessage: System.MissingMethodException:  Method not found: 'Boolean PwApiWrapper.dmscli.aaApi_LoginWithSecurityToken”XXXX

Steps to Resolve

1. 1. An older version of C:\Windows\assembly\pwapiwrapper.dllstill existed from a previous version of iCS for PDF when attempting to remove the product manually.
   2. Manually removed .dll (right-click>Properties>Version; right-click Uninstall). Then removed and reinstalled current version of iCS for PDF to install correct version of pwapiwrapper.dll

In the ProjectWise Administrator datasource properties, statistics tab, there is a date and time for when the data was last updated.  Other than the manual refresh button, how to configure how often the data is refreshed.

When are datasource statistics updated?

On the ProjectWise Integration server, in the dmskrnl.cfg file (c:\program files\Bentley\projectwise\bin), there is a setting called StatisticsFrequency.  By default, this is set to 12 hours (value in seconds.) It is not recommended to run the statistics too often because it can take time depending on the size of your database.  The value can be set to 0 to not have the stats run automattically.

StatisticsFrequency=43200

After the Integration server service is started, PW will wait the amount of time set for this value before first updating the statistics.  It will then run again 12 hours (or whatever the value is set to) after that. 

Note that this timer is restarted back to zero any time the server or service is restarted, and will not update for another 12 hours.

This can happen when running a version of the PW Integration server earlier than Update 2 (in other words 10.00.00.xx or 10.00.01.xx) But using a client machine with either PW Admin or PW Explorer 10.00.02.xx version installed.

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

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

   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"

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

After adding an additional server to PW network configuration, the previous datasources do not show

Reason

There is a duplicate datasource name on the new server.  For example, server1:ProjectWise.Companya.com , server2:ProjectWise.Companyb.com  Only one server will populate because of the duplicate name (regardless of domain name) 

Steps to Resolve

•  In the [Gateway] section of the dmskrnl.cfg file on one of the gateway servers, enter the following (using the name of the server you are on)

on the server named ProjectWise.companyA.com enter the following, which tells the client to send the traffic directly to that server. 

ProjectWise.companyA.com=ProjectWise.companyA.com

OR

•  Manually add/remove servers to PW network configuration as needed

Title

Service 'Bentley Logging Server' (BentleyLogging) failed to start. Verify you have sufficient privileges to start system services error.

Symptoms

When running deployment via Wizard, it stops logging service as last step before completion of deployment and then it waits 120 seconds to start again and doesn't.

Cause

Please make sure you do not have connect edition orchestration framework deployed on the server that you are trying to deploy BTS on. This causes BTS wizard to fail when trying to register BTS logging.

Resolution

Deploy BTS on separate server

Overview

The ProjectWise User Synchronization Service (USS) is used to synchronize ProjectWise user and group accounts with Windows user and group accounts. This allows users to log into ProjectWise using the same username and password that they use to log in to Windows. 

We will look at a few areas in configuring the ProjectWise Synchronization Service, including Trust, Permission, and ProjectWise Administration.

Troubleshooting

Trust

 ProjectWise requires there to be a two way trust when the ProjectWise Integration and USS servers are in one domain and the users ‘live’ in another domain in Active Directory.  Make sure there is a two way trust between domains.

Permission

On the Integration Server, go to services:  the synchronization service 'logon user' must be a domain user and be able to enumerate users on each domain.

• Make sure this user has 'log on as a service' rights on the computer running the USS. (We usually use a domain admin.)
• If you had to change the user name or password, you need to uninstall the service, then reinstall and input the user name and changed password.  (This information gets set in the registry during the install.)

Administration

If your ProjectWise USS stops working, first check the services on the Server (typically the Integration Server) and ensure that the ProjectWise USS is running.

If the service appears to be running, open ProjectWise Administrator.

• In your data source, go to the Windows Security System node and right click User Synchronization Service, and select Properties. When the dialog opens you should see the name of the Computer that the User Synchronization Service is on. 

• Highlight and delete all entries (do not highlight and retype). Make sure you have the correct information before deleting the current entries.
• Retype the computer name where USS resides.  In some cases we have seen browsing to the Server may not work and you can’t find the Server name.  If this is the case, type in the name of the computer that has the USS running.  (Example:  \\myserver)
• Retype the ProjectWise username and password. The main ProjectWise Admin account.  (Not the service account and not a user account with “admin rights”).
• Restart the USS services.
• From the ProjectWise Administrator, execute User Synchronization. Go to the Windows Security System node and right click User Synchronization Service, then select Synchronize Accounts

** If none of the above resolves the problem please configure logging by doing the following:

• Go to the drive that USS is installed on.
• On a Windows 2008 Server go to .. \Program Files (x86)\Bentley\ProjectWise\bin and open the usersync.log.xml file in notepad.
• Change all priority values = "warn" to "all".  Save the file, then stop and restart the synchronization service.
• Execute a "synchronize accounts".  Wait a few minutes for the log to generate. The usersync.log file is located under C:\Users\Public\Bentley\Logs directory and is called usersync.log.
• Open the usersync. log with notepad and do a search for “Unique constraint violated” (without the quotes)You will likely find a line that looks similar to this:
  User group issue
  2014-02-19 15:22:03,761 ERROR [0x00000000] pwise.usersync - Failed to create user group 'MyDomain\MyGroup[MyDatasource://MyDomain.com/DC=us/OU=company/OU=MySection/CN=MyGroup] [S-1-2-12-123456-123456789-123456789-12345]' in the datasource 'PROJECTWISE.mydomain.com:PWdatasource'. Unique constraint violated
  
  User issue
  2014-02-19 15:22:04,856 ERROR [0x00000000] pwise.usersync - Failed to create user 'MyDomain\MyUser [MyDatasource://MyDomain.com/DC=us/OU=company/OU=MySection/OU=MyGroup] /CN=MyUser] [AD:S-1-2-12-123456-123456789-123456789-12345]' in the datasource 'PROJECTWISE.mydomain.com:PWdatasource'. Unique constraint violated

 Follow the instructions below to fix the user and groups that are listed in these lines.

What if only one user has a problem or several random users are not being synchronized?

Typically there is a lost SID or the user was created in ProjectWise with a SID that no longer matches the SID in Active Directory.

• In PW Admin, go to the User Account Properties. 
• On the General tab, under Security, switch the account type from window-synchronized to windows 
• Run user synch.
• Go back to the user account and switch back to Windows-synchronized.
• Run the User Synch again.

If you have several users or groups you can highlight them all, go to properties and make the changes as directed above.

 Switching the user to “windows” and then back to “windows synchronized” should flush and recreate the user SID.

Before moving to TLS 1.2 please make sure your SQL server supports TLS 1.2 protocol and perform upgrade if needed:
https://support.microsoft.com/en-us/help/3135244/tls-1.2-support-for-microsoft-sql-server

Please make sure "SQL server Native Client 11.0" driver is available in "ODBC Data Source Administrator".

1. Load certificate on the server that the clients will be connecting to.  This would need to be the server that is in your ProjectWise Network Control Panel.
2. Modify the dmskrnl.cfg to enable encryption and start PW Integration server in secure mode
3. Uncomment SecureConnection=1
4. Enter the cert name here: SecureCertificateCommonName=CNfromCertificate)
5. Download this application: https://www.nartac.com/Products/IISCrypto/Download
6. Once installed Run IIS Crypto GUI version2.0, and select TLS 1.2 and make sure TLS 1.0 and TLS 1.1 are unselected.
7. Hit apply
8. Reboot the server this task was performed on.
9. Re-create your ODBC connection using "SQL server Native Client 11.0" driver if it's an old driver or you will receive database communication error.

Note:  The above information applies to the CONNECT Edition only.  Select Series versions require TLS1.0

Error Message:

“Cannot Initialize permissions files set, the current document will not be managed by ProjectWise”.

Issue Description:

Revit Integration with ProjectWise was giving the following error when trying to save a central model in ProjectWise Explorer. Only “.rvt” file gets created while the associated “.dat” files won’t get created in the folder.

The versions were as follows:

Windows OS: Windows 7

Revit 2018

ProjectWise Explorer: 10.00.02.265

The user had 3 different datasources, but this issue was specific to a datasource. Furthermore, a few users had 10.00.02.320 version of ProjectWise Explorer installed on their machines. They did not face any issue with any of the datasources.

Cause and Resolution:

This was found as a defect. The user faces this issue only when the datasource setting “Display Descriptions” is enabled for the user through ProjectWise Explorer.

(Tools -> Options -> Settings and enable the option "Display Descriptions")

This was also tested against Revit 2015, and found to be valid.

This defect has been identified, filed and resolved in ProjectWise Explorer version 10.00.02.320.

Problem Description

User has a client in a remote office who has installed Projectwise Explorer, but when they launch it, no datasources appear in the window.

Explanation

In order to connect to a datasource the Projectwise Network Control DNS and Datasource tabs need to be populated, Port 5800 needs to be open bi-directionally, and if the network is being restricted, the FQDN for the ProjectWise server you are connecting to needs to be allowed through any proxy \ firewall filters.

Steps to Resolve

Option 1:  Checking the ProjectWise V8i Network Control

1. Go to Control Panel, then double click the ProjectWise V8i Network icon

2. On the General Tab, solid check the “Prevent UDP”

3. On the DNS Services tab, enter in a name for the connection, under Host Name enter in the FQDN name of the server you are trying to reach, and under port put 5800, then click add

4. On the Datasource Listing tab, enter in a name for the connection, under Host Name enter in the FQDN name of the server you are trying to reach, and under port put 5800, then click add

5. Click apply and okay.  Launch Projectwise Explorer to see if this process solved the problem

6. If it fails, then double check with the Projectwise Administrator that the information you are entering is correct.

7. Note you can also get to the ProjectWise V8i Network Control by launching Projectwise explorer, then choosing Tools \ Network Configuration Settings.

Option 2:  Check to see if port 5800 is blocked on your network using Telnet

1. If Telnet is not installed on the client machine, go to control panel, programs and features, click the link that says “ turn windows features on or off”, a new window will pop up, turn on Telnet Client. Click okay.

2. Telnet should be run from the command prompt on the client machine. Go to start, run, then type cmd. (you may need to run as administrator depending on how locked down the system is)

3. Example command line:  Telnet Projectwise.Bentley.Com 5800

4. Where Projectwise.Bentley.Com is the information that the you enter into the ProjectWise network control for the connection to your server.

5. If it does not connect, then port 5800 is blocked somewhere on the network.

6. Or it could be that the address (in this example:Projectwise.Bentley.Com) needs to be allowed through the firewall.

7. Unblocking the port and or address is a Network administrators job.  Allowing access to the FQDN is also a network firewall issue. It is not a client side problem unless the client has their client firewall locked down.

8. Running Telnet will prove to the network admin that the port and or address is blocked.

Option 3: Check the connection to Projectwise using the Windows Socket Analyzer

1. Go to Start \ Programs \ Bentley \ Projectwise \ Tools \ User Tools \ Windows Socket Analyzer

   1. Protocol name: TCP  (Click Next)

   2. Service Name: dms (Click Next)

   3. Port number: 5800 (Click Next)

   4. Remote host: <FQDN of server you are trying to reach> 

2. Click next and it should resolve the Ip address of the server you entered

3. Click next again and the clients name and IP address are resolved.

4. Click next again, and the tool sends a bit of data to the Projectwise server.

5. If it is successful, then at the bottom of the tool you will see a message that says " Connection to remote host established and closed successfully"

6. If it fails you will be presented with an error message with the possible cause of the problem.

Option 4:  Turn up the Projectwise Logging on the client to see where the problem might be

1. Go to C:\Program Files (x86)\Bentley\ProjectWise\Bin and open pwc.log.xml with notepad

2. Choose Edit \ Replace

3. Under Find What type =”warn”

4. Under Replace With type =”all”

5. Click replace all

6. Now choose Edit \ Find

7. Look for the work Hook

8. If found change the priority value from "all" back to "warn"

   1. <category name="pwise.hook">               <priority value="all"/></category>

   2. <category name="pwise.hook">               <priority value="warn"/></category>

9. Save and exit the file

10. Go to C:\Users\<user name>\AppData\Local\Bentley\Logs and delete the pwc.log

11. Launch Projectwise Explorer. Then open the pwc.log file in notepad

12. Choose Edit \ Find, the look for the work ERROR and match case.

The most common problems are:

• Reverse DNS lookup is not configured for the server you are configured to connect to, or that a server listed in the Gateway section of the dmsknrl.cfg on the server you are connecting through is not configured correctly

• The Gateway section of the dmsknrl.cfg on the server you are connecting through is not configured correctly, either has an incorrect address, miss spelling, etc.. or your ipaddress has been denied access.

Error or Warning Message

"Encountered an improper argument"

Explanation

When opening the Transmittal settings on certain projects, the error appears, but once clicking ok everything works fine.  This is because there has been a ProjectWise user configured as an internal participant, that was removed from the datasource, but was not cleared out of Transmittals.

How to Resolve

This is resolved in the latest version of the BTS connector

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

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

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

Problem

Error 55049: Error copying document to client. Cannot create storage area. The storage area is not within the allowed storage locations defined for this server. Please contact your administrator

Background

There is a new feature in PWCE Update 3, see below from the “what’s new” section of the readme:

Allowable Locations for Storage Areas

Before you can create a storage area, you must now first define at least one allowable storage location, which is a local and/or network location where storage areas hosted by a ProjectWise Design Integration Server or ProjectWise Caching Server can be created.

Allowable storage locations are defined in the DMSKRNL.CFG file. If no locations are defined, you will not be able to create any storage areas on the server.

For convenience, the ProjectWise Design Integration Server and ProjectWise Caching Server installers have been modified to let you define the default allowable storage location during installation. You can also manually add, modify, or remove allowable storage locations from the DMSKRNL.CFG file.

Solution

1. On the PW integration server, open the dmskrnl.cfg file (found in c:\program files\bentley\projectwise\bin)
2. Find the section labeled: [FileStorageService]  
3. Add a line pointing to the path of the storage area
   1. Example:  StorageLocation0=E:\storage

The following describes how to configure a new temporary caching server, in its simplest form. This will be applicable to most users that have their Integration Server hosted by Bentley.

If you don’t already know the PW Integration Server and Datasource name, open ProjectWise Explorer and log in. Look in the address bar for pw:\\servername.bentley.com:datasource

1. Install ProjectWise Gateway Server
2. Open the dmskrnl.cfg file in notepad (default location C:\program files\bentley\projectwise\bin)
3. Update the file with the following information, in the appropriate location

FileTransferSrv=1                                                          {this line is already in the file, remove ; if there is one}

ConnectionSrv=1                                                            {this line is already in the file, remove ; if there is one}

[Gateway]                             {this line is already in the file, find it and enter the appropriate entry below}

Servername.bentley.com=yourservername.com

[Routing]                                {this line is already in the file, find it and enter the appropriate entry below}

Servername.bentley.com=5800

[cache]                              {this line is already in the file, find it and enter the appropriate entries below}

enabled=true

storagepath=c:\cache                                     {set this to the path on your server to store the cached files}

limit=200              {set this to the max size (in megabytes) of the cache before oldest files start purging}

4. On the machines running ProjectWise Explorer, open the PW Network Configuration Tool (found in the control panel or in the tools menu within ProjectWise Explorer)

5. In the DNS Services tab add an entry for your local caching server. Leave Datasource tab as is (directly to the Integration Server)

Caching 101:
communities.bentley.com/.../5614.how-to-configure-projectwise-caching-server-tn

Gateway Configuration:
communities.bentley.com/.../5616

Additional advanced setup information:

https://communities.bentley.com/other/old_site_member_blogs/bentley_employees/b/timpoths_blog/posts/the-many-ways-of-configuring-the-projectwise-network-control-panel-how-to-deal-with-roaming-users

Problem

User getting error message in pwc.log file every two minutes.
2009-03-17 08:28:36,355 ERROR [1460] pwise.dms - Error -11025 reported at func: dmsExecServerCommandBySocket line: 1468
2009-03-17 08:30:36,357 ERROR [1460] pwise.dms - Error -11025 reported at func: dmsExecServerCommandBySocket line: 1468

Solution

 This error is the message polling notification.  by default it is set to check for new messages every two minutes.
You can turn it off two ways
In pw explorer go to tools, messenger, in the messenger dialog box go to tools, polling, change the time to 0
The following only works for ProjectWise version 08.09.04.89 or higher in XM.
edit this key in the registry
HKCU\Software\Bentley\ProjectWise\08.09\NoticePolling
DWORD Disabled=1

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Problem

Trying to attach a DWG file as a reference file to a DGN file and getting error, "is not a recognized format".

Using MicroStation SS4 version 08.11.09.829.

The DWG file was created with AutoCAD 2018.

Solution

This issue can be reproduced inside and outside of ProjectWise.

MicroStation SS4 V8i version 08.11.09.829 does not support AutoCAD 2018.

MicroStation Connection Edition will need to be used to attach AutoCAD 2018 files as reference files to a DGN file.

Rebuilding the Windows Search index using Indexing Options has resolved this failure. However, on rare occasions, a new Orchestration Framework database will need to be created and used prior to rebuilding the index. A new OF database resolves the 58186 error, but Full Text searches do not return results until the index is rebuild.

ProjectWise Connect Edition Update3 Unattended Installation from a Command Prompt

You can do an unattended install in ProjectWise Explorer silently (without using the install wizard) from a command prompt.

To find out which features you can include or exclude from your install, open a command prompt with elevated privileges (run as administrator) and then enter the following command:

"path_to_PWEinstaller\Setup_ProjectWisex64_10.00.03.xx.exe" ExportCliArgs=path_to_output\FeatureIDTree.txt

For example:

"C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe" ExportCliArgs=C:\PWinstalls\FeatureIDTree.txt

This creates a file called FeatureIDTree.txt which contains a list of all the features that can potentially be installed through the ProjectWise Explorer installer. Open this file in a text editor and review which features you want to include in your installation command. Items with an asterisk * next to them (for example, ProjectWiseExplorerPackage*) are required features that will always be installed and therefore do not need to be specified in the command.

Features that are normally turned on by default in the wizard do not need to be specified in the installation command unless you want them not to be installed. Likewise, features that are normally turned off by default in the wizard do not need to be specified unless you want them to be installed. If the installer delivers integration for an application you have installed, integration will be turned on for that application by default unless you specify to not install it. Use the ADDLOCAL property in your command to install a feature that is not normally installed by default, or if modifying the installation, to install a feature that was previously not installed. Use the REMOVE property in your command to turn off a feature that is normally installed by default, or if modifying the installation, to uninstall a feature. If you need to install more than one feature, or turn off more than one feature, separate those features in the command with a comma. The feature names are case sensitive and should be typed exactly as they appear in the FeatureIDTree.txt and without the leading dashes (for example, type Office2016 instead of ---Office2016).

Example: Install ProjectWise Explorer silently, with all default features and integration for installed applications:

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” -silent

Example: Install ProjectWise Explorer silently, and do not install the Document Creation Wizard (which is normally installed by default):

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” REMOVE=ProjectWiseExplorerPackage_DocumentCreationWizard -silent

Example: Install ProjectWise Explorer silently and do not install Office 2016 integration (assuming Office 2016 is installed), or modify the installation and turn off Office 2016 integration (if it was installed and now you want to turn it off):

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” REMOVE=Office2016 -silent

Example: Modify the ProjectWise Explorer installation, and turn on Office 2016 integration (if it was not installed and now you want it installed):

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” ADDLOCAL=Office2016 -silent

Example: Install ProjectWise Explorer silently, with the Bentley DGN Navigator Control and the ProjectWise Deliverables Management connector for ProjectWise Explorer (which are both normally turned off by default):

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” ADDLOCAL=DgnNavigatorControlAx,PWDeliverablesMGTClient -silent

By default, the installation log file is saved to C:\Users\<user.name>\AppData\Local\Temp\ProjectWise_Explorer_CONNECT_Edition_<datetime>.log. You can change where the log file gets saved adding the -log argument to your command.

Example: Install ProjectWise Explorer silently, and send the log file to a different folder:

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” -log="C:\PW_installs" -silent

Example: Uninstall ProjectWise Explorer silently:

“C:\PW_installs\Setup_ProjectWisex64_10.00.03.24.exe” -uninstall -silent

Tip: Always test your installation configuration by running your command without the -silent argument. This will open the installation wizard and show which features your command has turned on or off, on the Select feature to install page. If this page shows what you are expecting, then you can assume that running the same command silently will install everything you instructed it to install.