Error or Warning Message

Not enough space on drive C:\ to extract this package

Explanation

A user has downloaded the Projectwise Client Setups and when launching the executable gets an error that there is not enough disk space to extract the package.  The user has plenty of disk space so this should not be a problem.

How to Avoid

Option 1: Confirm there is enough disk space on the system

1. For Projectwise Client setups you will need at least 1.5 gigs of disk space

2. Check that your system's temp directory is located on a disk with enough free space.  You can view and change where your temp directory is pointing to by going to Control Panel, System, Advanced System Settings,  Environment Variables, then under User Variables and System Variables look for TEMP and TMP.

Option 2: Reboot the system

•  Rebooting will clear up the available address space available on the machine, which is usually what causes this error

Option 3:  Unzip the package using a different extraction program (7-zip)

1. Use 7-Zip to extract the pacakge which is a free extraction program you can download from the internet.

2. Once 7-Zip is installed, right click on the Projectwise Client setups exe and choose  7-Zip, extract files...

Option 4:  Re- Download the Projectwise Client setups

• It may be possible that the Projectwise Client Setups package was not full downloaded and is corrupt.  Try downloading the package again.

See Also

Problem

When viewing the properties of a document in the Document Properties windows in ProjectWise Explorer, the File Size was displayed as GB rather than MB

Solution

This is typically caused when a previous version of ProjectWise Explorer has been removed but there are old resource files left behind. These can cause a conflict with the new version resulting in this issue.  

Performing an uninstall of ProjectWise Explorer, removing the installation folder
(C:\Program Files (x86)\Bentley\ProjectWise\), rebooting and then reinstalling ProjectWise Explorer addressed the issue.

See Also

Error or Warning Message

Last Error 56049 Cannot log in to the data source. Database communication Error.

Explanation

This error message can appear logging in to ProjectWise datasource.

If you check ProjectWise services you might see that they are up and running. Trying to restart ProjectWise Integration Server service and ProejctWise Orchestration Framework service it will not start. This means that the account under which the ProjectWise processes are running, may be locked out, or that the password for this account (which by requirements should have a fixed password) has been changed.

Another possible issue is that the communication between the datasbase server and the integration server has stopped. 

How to Avoid

1. Unlock the account or change the password back under which ProjectWise services are running.

2. or change the account password in Services for the ProjectWise Integration Server service and ProjectWise Orchestration Framework service.

3. On the integration server, check the ODBC connection to make sure the system is able to communicate to the database server. If that fails, then on the database server, check to make sure the database services are running.

See Also

https://communities.bentley.com/products/projectwise/content_management/w/wiki/orchestration-framework-service-will-not-start.aspx

https://communities.bentley.com/products/projectwise/content_management/w/wiki/5504.aspx

Error or Warning Message

When trying to deploy Bentley Transmittal Server, the following error is encountered;
An error occurred, Exception thrown while adding mex endpoint http://servername:8086/DeliveryRepositoryService.svc/mex

Explanation

When the website for Bentley Transmittal Server was setup, the bindings were incorrectly set.

How to Avoid

Open IIS and ensure that the net.tcp and net.pipe bindings for the Bentley Transmittal Server are set correctly.

1. For the net.tcp binding, enter the number of an open port, followed by a colon (:), followed by an asterisk (*).
For example, 8086:*
2. For the net.pipe binding, enter just an asterix (*)
3. Click OK and close the Site Bindings dialog.
4. From an administrative command prompt, type IISRESET and press enter.
5. Once IISRESET is done, re-run the Server Deployment

enter the number of an open port, followed by a colon (:), followed by an asterisk

(*). For example, 8086:*

Error or Warning Message

Error 58040
 Access denied. You have insufficient privileges to finish this operation.

Explanation

One of the following is true for the user logged into ProjectWise, and the user would need to be given the appropriate access

• The ProjectWise user logged in does not have the user setting to create documents (under Settings-Document-Create)
• The ProjectWise user does not have create document permissions in the specific folder (or in the current workflow state of the folder, if workflows are used)
• The ProjectWise user does not have write access to the documents, if the folder is configured with an environment that either has default attribute values, or the setting to "create attribute records upon document creation"
  

ProjectWise Encryption and Certificates

Question: 

Does ProjectWise Integration Server support 2048 Bit key length for
end entity certificates, and 4096 Bit key length for CA certificates?

Answer: Yes

See Also

http://communities.bentley.com/products/projectwise/content_management/w/wiki/5630.aspx

http://communities.bentley.com/products/projectwise/content_management/w/wiki/5465.aspx

How to keep users from creating folders

Background

I have users who are creating folders all over the datasource.  We are trying to keep a standard folder structure for each project.  What permissions or settings can we use to keep users from creating folders?

Steps to Accomplish

Option 1:  Remove the project/folder security permission "create Subfolder".

1. In ProjectWise Explorer, right click on a project folder or parent folder, choose properties, folder security.
2. For any group or user us have assigned to this folder, uncheck the option for "Create Subfolder" and allow the permissions to inherit down.
3. This would be per folder or project, so if you set it at the top level and allowed it to inherit down, it would apply for that folder structure.
4. Additionally you could set this at the datasource level which obviously would apply for the entire datasource. In Projectwise Administrator, right click the datasource, Properties, Folder Security, assign the everyone group, and uncheck the "Create" permission.
5. Just as a side note, any folder the user has already created and owns, he will be able to create folders and files under what he owns.  To  keep the user from creating more sub folders under the folder he owns you would have to go in and take or change ownership.
   ***There is another datasource setting under Miscellaneous called "grant implicit \ change permissions rights to owners of project folders and documents.  This is on by Default.  IF you turn this off then users will not have implicit change permissions to the objects they create in the future.

Option 2: Under the user setting uncheck the 'Create' setting under the Folder node

1. In ProjectWise Administrator, right click the user name, choose properties, settings, then expand the Folder node.  Uncheck the setting 'Create'.

2. Even if the user has permissions to create a subfolder they will not be able to because of this user setting.  So this is for the entire datasource.

See Also

Error or Warning Message

DEBUG dmsconv - resetting '<failed>' MIME type entries to NULL
INFO  dmsconv - 0 '<failed>' MIME entries were reset

Explanation

User has a datasource that was upgraded / converted some time ago from a previous version of Projectwise.  The user is unsure if the mime type switch to update the mime types in the datasource was run.

The user now wants to run the dmsconv –mime to update the mime types but when the command is executed, they get the above messages.

How to Avoid

What the messages are really saying is: 'I searched the datasource for MIME entries that were in the "FAILED" state and found there were none (0) that needed to be reset so there is nothing for me to do here'

There is nothing wrong hence why this is logged as an INFO line.

So the mime types are already set for the files in the datasource and you do not need to run the dmsconv -mime.

Other the running the dmsconv tool, how would I know if the mime types are set in my datasource?

In ProjectWise Explorer, Right click a file, choose properties, on the general tab, click on the Advanced button, and choose mime type.  If configured the mime type will show for that file type.  If you have access to the database, The mime types are
stored in the dms_doc table.

See Also

Problem Description

I need to change the Datasource name, and the Database name for our Projectwise implementation.  What problems might this change cause?

Steps to Resolve

Changing the Database Name:

1. Changing the database name in the database will likely cause the ODBC connection to fail. So you would need to reset the ODBC connection on the integration server.

Changing the Datasource name in the ODBC connection

1. If you also change the name in the ODBC connection you will need to reconnect the Datasource via Projectwise Administrator.

Changing the Datasource name in the Projectwise Administrator.

1. If you used the $datasource$ variable in the path for the User Template working directory, Any new users will have the new datasource name in the path, but any old users will still have the old datasource name in their working directory path.  Not really a problem just something to be aware of.
2. If you used the $datasource$ variable in any attribute; any new file created with in the environment that had this variable set in an attribute will have the new datasource name.  Old files would continue to have the old datasource name and less they were updated.  Again not really a problem, just something to be aware of.
3. If you use links in documents.  For instance yesterday you sent an email to another user with a link to a file in projectwise.  Today you change the datasource name.  The link in the email you sent yesterday will no longer work.
4. Instead of changing the name, change the description and then turn on "show descriptions" in the user settings under Interface.  Note this setting will also show the descriptions for folders as well.

Problem

 user c:\windows\installer\ProjectWise Explorer V8i (SELECTseries 3) (x86).msi when tyring to uninstall PWE

Solution

1. Had user copy the ProjectWise Explorer V8i (SELECTseries 3) (x86).msi for PWSS3 version 08.11.09.122 to the c:\windows\installer folder then run the add remove again.  This time it worked.  User thinks that originally these machines where installed using and sms push and that the ProjectWise Explorer V8i (SELECTseries 3) (x86) must have been temporarily placed on the machine and then removed after the install.

2. Another possible solution would be to go to windows Control Panel, programs and features, find ProjectWise SS3 and do a modify\ repair, then try the uninstall.

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!

Firewall is blocking ProjectWise

What port does ProjectWise use?

ProjectWise uses Port 5800.  It needs to be open on the firewall bidirectionally

See Also

http://communities.bentley.com/products/projectwise/content_management/w/wiki/default.aspx

Error or Warning Message

When Revit 2015 integrated with Projectwise explorer, the error "Autodesk Revit has stopped working" after launch the Revit 2015.

Explanation

In user's PC Windows 7 SP1 (64-bit), install ProjectWise Explorer V8i (SELECTseries 4) 08.11.11.574，Revit2015 and projectwiseintegrationforrevit081111789en.exe. After launching the revit 2015, the error shows. The reason is every user installs the esafeNet software that is encrpytion software from third party. esafeNet causes the revit crashes.

How to Avoid

1.Uninstall the esafeNet software.

2.In EsafeNet,to see if there would be a way to add any exceptions for the EsafeNet software that it would not scan Revit process.

No solutions have been added yet, please check back soon!

No solutions have been added yet, please check back soon!

Problem Description

Unable to synch recreated user from Active Directory, Projectwise account is disabled

A user was corrupted in Active Directory (AD) and his account was deleted and then recreated in AD.

When Projectwise User synchronization ran it disabled the users old account but did not create the new account because it is the same name.

Reason

Projectwise uses the SID to track the user.  When you create a new user in AD a new SID will get created even if you use the same name.  So when User Synch ran the SIDs did not match and it disabled the user of the same name in Projectwise.

Steps to Resolve

In ProjectWise Administrator go to the user account and change it to a logical account

Then run user synch and the newly recreated user should then synch with Projectwise.

When you delete an account in projectwise you are prompted with a message that says “if the user has documents you will become the owner of the documents owned by this user. Are you sure you want to delete the user?” 
If you do not want to be the owner of his documents, and you want the newly created user to be the owner of his documents then you will need to do the following:

In Projectwise Administrator, add the new user (temporarily) to the Adminstrators group.

Log into Projectwise administrator as that user

Delete the old account and take ownership of the documents, then Log out.

Log back in as the administrator and remove the user from the administrator group.

See Also

Problem Description

User has manually created  Windows user accounts in Projectwise.
After some time these users keep getting disabled.

In checking the user accounts that he created that are getting disabled, the accounts where set to “Windows Synchronized”.  This means the account is handled by the User synchronization service.

Explanation

When Projectwise User synchronization ran it disabled the users account because the user was not part of a group in Active Directory that was being synchronized with Projectwise nor was he listed in the users that were being synchronized by Projectwise..

There are three security settings or user account types that can be created in Projectwise.

• Logical users are users who are created directly in Projectwise and the user name and password are stored directly in the Projectwise database.
• Windows accounts are accounts created by the administrator that are exactly the same as the users Windows Active Directory account.  Projectwise does not store the password for these user accounts, and uses Active Directory to authenticate the user at login.
• Windows Synchronized Accounts are user accounts brought in from Windows Active directory using the Projectwise Synchronization service. User accounts and groups are created automatically from Windows Active directory.  The Admin can choose what groups or users to synch with this service.  Passwords are not stored in ProjectWise and users are authenticated via active directory.

Steps to Resolve

1. In Projectwise Administrator, Set the user account back to Windows to keep the account from being disabled by the User Synchronization service.
2. If the account is supposed to be synchronized then make sure the account is part of one of the Acitve Directory groups that is being synched via Projectwise Synchronization Serive.

In Projectwise adminstrator go to Windows security system \ User Synchronization Service \ Synchronized accounts \ User groups.  Compare the groups listed here to the groups the user is assinged to in Active Directory.  The user must be in one of the groups being synchronized

See Also

For more information see the Projectwise Administrator help.

Problem Description

When switching DGN files an Alert dialog appears stating:

MicroStation must be restarted to load the new workspace configuration. Do you want to restart now?

And you are presented with two options, YES or NO

Reason

Most likely due to a difference in the workspace associated to the DGN file being opened.

Steps to Resolve

Option 1 - Workflow

1. If you are launching MicroStation first, then logging      into ProjectWise and accessing a file with a workspace associated, this is      the reason for the Alert
2. Try opening the file from within ProjectWise and the      dialog should not appear

Option 2 – Managed Workspace

1. Check the Properties dialog of the two files
2. See if there are different CSB’s associated with each      of the files
3. If there are determine which workspace attributes you      would like to use and choose the option accordingly. YES will restart      MicroStation and use the new workspace, NO will keep MicroStation open and      retain the old workspace settings

Option 3 –Workspace Profiles

1. Check the Properties dialog of the two files
2. See if there are different Workspace Profiles      associated with each of the files
3. If there are determine which workspace attributes you      would like to use and choose the option accordingly. YES will restart MicroStation      and use the new workspace, NO will keep MicroStation open and retain the      old workspace settings

Option 4 –Debug the Workspace

1. If neither of these options work for you, obtain a      debug report of the workspaces to determine what is different between the      two files.
2. Adjust the workspace settings/ variables as needed to      prevent the workspaces from being different.

Click here for current readme and requirements

Current version 08.11.11.590, released July 06, 2014
Update version 08.11.11.574, released October 14, 2013
Original version 08.11.11.559, released April 02, 2013

The following is a list of the major new features delivered with this release:

• ProjectWise Explorer Enhancements
  • Bentley DGN Navigator Control, for viewing DGNs and i-models in ProjectWise Explorer
  • Support for ProjectWise Explorer on Citrix XenApp 6.5
  • 'Send To > Mail Recipient As Link' now always creates URN links
  • New 'Include Engineering Component Access Rights' option on the Project Properties dialog > Participants tab, to either set or hide/ignore component security settings
  • Workflow Rules Engine extension (option on the ProjectWise Explorer installer)
  • ProjectWise Export/Import Tool Now Delivered with Client Setups
• Integration Enhancements
  • Support added for:
    • AutoCAD 2013 applications
    • Revit 2013 applications
    • 64-bit Microsoft Office 2010 (Word, Excel, Outlook, PowerPoint)
    • Microsoft Project 2010 and Visio 2010 (32-bit and 64 bit)
  • Advanced integration for AutoCAD Civil 3D 2012 and 2013
  • AutoCAD integration enhancements:
    • New Disable / Enable Integration button
    • Full integration of DGNIMPORTMODE variable (now supports all modes (=0, =1, =2) (AutoCAD 2012 and later)
  • Revit integration enhancement
    • New Resolve Links dialog, to fix broken links before the document opens in Revit
  • Office integration enhancement
    • New Disable / Enable Integration button in Office 2007 and 2010 (Word, Excel, PowerPoint, Project, and Visio)
• ProjectWise Administrator Enhancements
  • New 'Rules Engine' datasource node, for importing custom workflow rules
  • Delivered workflow rules
    • Generic workflow rules delivered with the Rules Engine Template (part of the Example Dataset delivered with ProjectWise Admin Setups)
    • BS1192 workflow rules delivered with the ProjectWise Business Process Template for BS1192 (delivered with ProjectWise Admin Setups)
  • Updated Attribute Exchange example files for Microsoft Office 2003
• Infrastructure Enhancements
  • Support for Windows 8 and Windows Server 2012
  • Full Text Indexing supports Windows Search Service on Windows Server 2012, and Microsoft Indexing Service on Windows Server 2008
  • New option in dmskrnl.cfg (LogLicenseToWindowsEventLog) that lets you control whether or not an informative message is sent to the Windows event log every time the server license is renewed
• Rebranding
  • ProjectWise Dynamic Composition Server for PDF is now Bentley i-model Composition Server for PDF
  • ProjectWise Dynamic Composition Server for i-model (extension to ProjectWise Automation Service) is now Bentley i-model Composition Server for i-model