When using ProjectWise Deliverables Management integrated with your ProjectWise Design Integration environment, you likely want to take advantage of your ProjectWise attribute information. This document will go over how you can utilize that data in your Transmittals and Submittals, including:

• Setup: Configure which attributes will be included
• Sending Transmittals: How can I automatically include ProjectWise attribute information into an outgoing transmittal package?
• Receiving Submittals: How can I automatically import incoming submittal document attributes into my ProjectWise datasource?
• Modifying attributes: What do to if you need to add/remove attributes from being included in PWDM.

Configure attribute settings in ProjectWise Explorer

This is a one-time setup to make the attributes visible to ProjectWise Deliverables Management

1. Create a global view in ProjectWise, containing all the attributes you wish to make available to Deliverables Management

2. In the PWDM settings for the project (Right click on Deliverables Management node in PW Explorer-settings) set the view in the Document’s attributes tab, and click Apply

3. Click the link at the bottom of the settings window to bring you to the Deliverables Management Portal settings for this project

4. Select Attributes, and you will see the ProjectWise Design Integration attributes synchronized

Including attribute data with the Transmittal

When creating a transmittal from ProjectWise Explorer, the attributes that are configured as part of the view are automatically included in the transmittal

 Attribute values in the Cover Letter

Now that they are made available to PWDM by configuring the view, any of those attributes configured can be used in the cover letter template.

Using the syntax {$DocumentAttribute.GetValue(AttributeName)$} in the configured template will populate with the corresponding value for the PW document.

The Attribute Name should be exactly as it appears in the PWDM settings, which is the display name of the attribute, if there is one configured. 

How to make the attributes available to external organizations working with you on this project

When the external organization accepts the invitation to work with you on the project, your settings (Attributes, classifications, and purposes) will automatically be configured in their project.

Note: see section below “Changing the attributes” if the settings change after the invitation is accepted.

Receiving submittal with attribute data

Now that the attributes are configured, the external organization starts a new transmittal, and when adding documents, the attributes will be available (via one-by-one or through the zip upload options in the excel template)

When you receive the package into ProjectWise Explorer, clicking acknowledge will import the documents, along with the attribute values (be sure that the configured storage location is set to the appropriate environment)

Changing the attributes

If you need to add or remove configured attributes

1. Modify the View in ProjectWise

2. Open the ProjectWise Explorer Deliverables Management settings for the project and click apply

Then for the external organization to pick up these changes, they will need to do the following:

1. Have the external organization open their CONNECT project (that was created during the invitation process)

2. In the Deliverables Management settings, select participants-External

3. Select your Company name (the one with the attributes already configured)

4. Click the blue drop down menu, and select “copy settings”

5. Select Attributes, and the attributes will be the same as yours. (note since they might not be integrated with ProjectWise Design Integration, that column will show n/a)

Requirements for using PWDM in PW Explorer:

• Make sure the PWDM Connector for ProjectWise Explorer is installed.  
• Verify the project is associated with a CONNECTED project, that has Deliverables Management turned on
• CONNECTION Client is running and logged in with Bentley account that has access in the PWDM internal participant settings

Problem

Error 1722 when installing Projectwise Integration server.

User has Microstation, Orchestration Framework, and all pre-requisites installed.

If he runs the PW integration server install without the document processor options, the server installs, but when he tries to install the doc processors, he gets "Error 1720. There is a problem with this Windows Installer package. A
script required for this install to complete could not be run.  Contact your support personnel or package vendor. Custom action  ConfigFTR script error -2146828212, Microsoft JScript runtime error: Path not found Line 41, Column 13"

Product: ProjectWise Server V8i
Version: 08.11.11.111
Area: Application Svr - Integration Svr, Problem ID#: 90272,
ERRORMESSAGE

Solution

1. Make sure the user attaching to the OF database via dbsetup has the proper permissions. If possible try connecting with the SA account, then run the install.. if it works then you know your database user does not have the correct permissions

2. Check to make sure the drive that the Microsoft Indexing server's data is on is not full, or is on line (for instance it may be on a NAS)

3. Instead of using the Setup.exe to install, go to the ...Server\integr_srv folder in the install set and run the ProjectWise Integration Server (x64).msi

Problem Description

In ProjectWise Administrator, when performing “Start Processing Now” on Document Processing, the following error displays:

Cannot open database “<database name>” requested by the login. The login failed.

Bentley.Orchestration External module has reported an error.

Solution 

When using Windows authentication with dbsetup.exe, use the same Windows account for the PW Integration and Orchestration Framework services, and the ODBC connection used by the datasource.

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!

Problem Description

When I attempt to submit an ad-hoc rendition to our iCS server, the following error appears: "No rendition service endpoints are defined on the server." The dmskrnl.cfg file has been edited correctly. Also when typing in http://server-name/RenditionService/RenditionService.svc in an IE browser to test the Rendition Service, the following error also appears: "Server Error in '/' Application. The resource cannot be found. Description: HTTP 404.  The resource you are looking for (or one of its dependencies) could have been removed, had it's name changed, or is temporarily unavailable."

Steps to Resolve

1. Open IIS and look under "Application Pool" to verify the "Rendition Service" application pool is present.  In this case it was not.
2. From Add/Remove Programs, run the 'Repair' option on the iCS for PDF product to restore the 'Rendition Service" application pool.

Problem Description

Steps to Resolve

The steps to resolve are below:

1. This is actually a Revit Issue
2. Revit crashes when it hits a bad link and opens a second time
3. To fix – go to a reference file of that master file and re-path/re-attach
4. Note you will need to kill revit.exe via task manager
5. Under the Manage Links option, choose the "Reload From" option to re-path and fix the links
6. Save and check in

See Also

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

About User Synchronization Service

ProjectWise User Synchronization Service (USS) will create datasource users for you automatically, using one of the following sources:

• User accounts configured on the local computer (local accounts).
• Active Directory user accounts on the domain to which the computer is joined (domain account).
• Active Directory accounts on an external domain with which a forest or domain two-way trust has been established (trusted domain account). 

Synchronizing Users from Multiple Domains

In scenarios where the ProjectWise Integration Server and other backend services are in one domain, and user accounts that need to use ProjectWise belong to another, a trust relationship between the two domains must be in place.  This trust should be configured as ‘two-way’, meaning that users from one domain can log into resources belonging to the other domain, and vice versa. 

Additional details on this topic can be found by searching for ‘Active Directory Domains and Trusts’ on Microsoft TechNet.

Example Scenario

Set up sync for primary domain

1)      Identify a domain account for use as your service account.  Ensure that this account has a secure password, and set the ‘Password never expires’ flag, if permitted by your organization’s security policy.  

2)      Verify that this account on the domain.  You can test the service account by using a desktop shortcut. 

3)      Install the ProjectWise User Synchronization Service on a system is joined to the same domain as your ProjectWise Integration Server.  Administrators commonly install the component on their Integration Server, but it is not a requirement to do so.

4)      When prompted, provide the domain user account credentials you identified in previous steps.

5)      During installation of the service, you will be prompted to provide a ProjectWise logical user account.  This account should be configured as a delegate user.  It will be used to access the datasource and add the users to the ProjectWise database, so permissions for this account should be set appropriately.

6)      Create a security group for your ProjectWise users in Active Directory, then add users to this group.

Set up for the trusted external domain

1)      Verify that the service account can log into resources in the trusted domain. 

• You can log onto a workstation that is a member of the trusted domain using the service account, or
• Repeat step 2 of the last section on a workstation that is joined to the external domain. 
• Contact your organization’s IT department for assistance with using the service account in the trusted external domain.

2)      Create a security group for your ProjectWise users in Active Directory for the trusted external domain. 

3)      Add users from the trusted external domain to this group. 

Configure the Datasource for User Synchronization

The User Synchronization Service Administration tool is installed on a system with ProjectWise Administrator as an add-in extension.  Open ProjectWise Administrator after installing the component and log into your datasource.  A new option ‘Windows Security Service’ has been added to the navigation tree on the left.

1)      Expand the menus ‘Windows Security Service’ and ‘Synchronized Accounts’.  Select ‘User groups’.

 

2)      Right click on ‘User Groups’.  Select ‘New > Synchronized User Group’.

3)      Click ‘Next’.

4)      If the User Synchronization Service is running on the local computer, select ‘Use Local Computer’, otherwise, type the name of the computer that is hosting the service.  (Typically the Integration Server).  Click ‘Next’.

5)      In the pull-down, select your Primary domain, then locate the group you created for users in the primary domain in the list.  Click the ‘Add >>’ button to add to the list.  Click ‘Next’, then ‘Finish’.

 

6)      Repeat steps 2 – 5, selecting the Trusted External domain and add the group which contains your external trusted domain users.

7)      Select ‘User Synchronization Service’ in the navigation tree on the left.  Right click on this item, then select ‘Synchronize Accounts’.  Confirm when prompted.

The system will start the synchronization process, which can take a few minutes, depending on how many users you added to the groups.  You can see the accounts that have been synchronized by selecting the ‘Users’ icon in ProjectWise Administrator.  

By default there is a form definition name added as a display name in Forms Register. This will also reflect in PDF export when you do this. So the Table Of Content (ToC) won't look too meaningful:

To change that you can define a "Display Name Property" per form definition in Forms Designer (when editing the form definition) and opening the Form Settings menu:

Typically you would have an attribute which uniquely identifies the form, i.e. "Meeting Number" for Meeting Minutes form, and you would select this attribute as Display Name Property. Then, Forms Register and subsequently PDF would have a great looking, referable grid list / Table Of Content:

If you are collecting forms using mobile device, make sure you have Location Services turned on:

If Location Services setting is on, then longitude and latitude coordinates will be stored for your form.

We are working on the Map feature to be available in Project Portal > Field Data management, that will show forms as a pinpoints on the map:

So if you start collecting forms today, you'll see them on the map in the near future retrospectively.

Problem Description

      When I highlight some jpegs in my ProjectWise Explorer, I immediatley get an entry in the Photo previewer tab,

but when I highlight others - there is no jpeg previewed !   Why would this happen ?

Steps to Resolve

    You might want to check it's mime type. Right click > Properties  > Advanced button offers a drop down menu > Select Mime type and give it a value of "Raster" for the mime type.  It will now display in the photo preview tab. The other jpegs already display as they have mime type already assigned.

     The photo preview has a config file in the ...ProjectWise\bin directory   pwviewer.cfg   for setting to display of not display file type extensions.

Before the moving to TLS 1.2 make sure your SQL server supports this protocol and 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 namehere: 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 on old driver or you will receive database communication error.

Problem

User is unable to synchronize active directory accounts.

the log files show the following messages

DEBUG [0x00001b40] pwise.usersync.schedule - Supervisor is exiting 'sustain schedule' state for schedule check up
INFO  [0x00001b40] pwise.usersync.jobs - Enqueue [Datasource list refresh;*; 07:38:27] priority:normal
INFO  [0x00001b40] pwise.usersync.jobs - Duplicate job is rejected [Datasource list refresh]. Datasource: *; found the same that was scheduled at:13:38:24

When user tries to stop the USS service it fails to stop and gives error 1053

Solution

The 1053 error usually indicates a problem with the software needing some resource.  Something could have been recently installed on the server like an update or maybe a virus scan that removed a resource.

User uninstalled then reinstalled the ProjectWise User Synchronization service and that solved the problem.

Problem

The integration server is stopped daily and doesn't restart. Looking at the Windows error logs there are warnings and errors generated by MsiInstaller each evening stating first that ProjectWise.WCF.PWTransp
ort.dll.config' does not exist then a RestartManager and then another MsiInstaller saying No valid source could be found for product ProjectWise Integration Server V8i.

Solution

The issue turned out to be related to a Windows feature that tries to re-install an application when it determines a missing or corrupted file.

User ran a repair on the PW integration service and that seemed to solve the problem. 

Problem

Drive C:\ on the server is running out of space. We found a very large file Windows.edb that continues to grow located at C:\ProgramData\Microsoft\Search\Data\Applications\Windows.  It appears to be part of the windows search.  Can it be deleted or moved?

Solution

This issue is a Microsoft windows issue.  According to Microsoft's website (link below) "To resolve this issue, install update rollup 2836988 for Windows 8 and Windows Server 2012.  This update is preventative, but not corrective. To reduce the size of a Windows.edb file that is already affected by this issue, you must rebuild the search index after you install this update."  Information on where to obtain the update, and how to rebuild the index are also included in this link. 

https://support.microsoft.com/en-us/help/2838018

Problem Description

Creating new document and generating Serial number in Document Code it doesn’t increase the number and always generates serial number 0001 even if the document with this sequence number was created just now.

Of cause trying to proceed and create document with ‘0001’ sequence number it gives an error message Last Error [58132] Can not create document. Code is already in use.

The cause of this issue can be that one of the attributes length, that are in a document code, is too short. E.g. we have attribute ‘ASSET_CODE’ that length is only two symbols. That means in a database it will save only two symbols.

However, I can have a pick list ‘CAR | CNS | DEV | MAR’ with the values that have more symbols and in that case it will save only two symbols to the database for this attribute even though we might think it’s saved the value that we see.

When document code is generated we see that it have all three symbols CAR - ‘123-B-CAR-2DM-F-0001’. However next time when we will try to create new document and generate sequence number it will compare ASSET_CODE attribute ‘CAR’ with the one that is saved in a database ‘CA’. As it won’t match it will generate ‘0001’ as for a new doc code.

Solution:

Option 1. Change your pick list values or values in a look up tables so it had not more symbols that is defined in the database. (You can find what is the length of your attribute by exporting environment from ProjectWise Administrator to .aam file format and open that file with the Notepad application)

Option 2. Increase the length of the attribute in a database.

Problem

User is getting the following errors when trying to add a synchronized group

The local computer type information could not be obtained.

The Specified computer is not running Windows NT

Steps to reproduce:
In ProjectWise Administrator

• Log into the datasource go to Windows Security Systems,
• Expand User Synchronization Service,
• Expand Synchronized Accounts,
• Rright click user groups and choose,
• New, Synchronized User Group.
  When the wizard appears click next, and choose Use local computer, hit next and the error appears
  "The local computer type information could not be obtained." click okay
• Change to "use this computer, enter the computer name and hit next and the error appears
  "The Specified computer is not running Windows NT", click okay
• Browse to another computer and it works fine.

Solution

The "Server" service on the computer was set to manual and was not started

Set the "Server" Service to automatic and start the service.
You should now be able to get past the above error messages.

Error or Warning Message

It is impossible to map drive R: since its already mapped or used by a physical device

Explanation

Revit integration with ProjectWise requires a drive to be temporarily mapped on the users machine (R: by default), and in this case, the users machine already had a drive mapped using the R drive

How to Avoid

Option 1 Remove the existing R: drive on the users machine

Work with your IT group if you need help on this one, but to unmap the drive do the following

1. Open Windows Explorer, right click on the R: drive and select Disconnect

2. Open the rvt file like normal from ProjectWise

Option 2 Change the drive PW uses for Revit (this will change for ALL users)

1. Log into ProjectWise Administrator
2. Right click on the datasource name and choose Properties
3. Select the Revit Integration tab
4. Change the drive letter to one that all users should have available