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 Sync 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 sync and the newly recreated user should then sync 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 Administrators 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.

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

User has a couple of Datasources that are not syncing on a manual
synchronize.

Product: ProjectWise Administrator V8i
Version: 08.11.11.111
Area: User Sync Settings, Problem ID#: 91151, Select Category

Solution

Try going to PW Admin module and > Datasource > User Sync > right
click Properties >Re-enter the credentials for datasource Server Tab >
"Use this ProjectWise Account" for username and password as we have
seen how this remedial action fixes the credentials somehow.

Problem Description

When publishing a file from ProjectWise Web Explorer, an error message is displayed that ends in "ProjectWise requests are not supported."  That error means that the ProjectWise Publishing Gateway isn't installed on the ProjectWise Publisher Server.

Solution

Install ProjectWise Publishing Gateway on the ProjectWise Publisher server

See Also

Troubleshooting ProjectWise Publishing Server [TN]

Problem Description

ProjectWise Publisher not displaying  jpg or tiff files.

Solution

Ensure the following verification:

In the vpriiprasterview.asp page, please make sure to replace the VPR parameter name "RasterName" by "RenditionName".

...PARAM NAME="RenditionName" VALUE=...

User was able to publish .itiff and .jpg from msexamples through publisher, however, we realized that he is trying to publish through digital interplot.  He is getting an error that it cannot read the configuration file.  User is on Windows 2008 server. We found that ProjectWise 08.11.07.xx Publisher will not publish .tiff or .jpeg files using technology  (ie. Old DIP folder ) that was delivered in Bentley Publisher XM Edition.  The JPEG and .tiff output format is blank

Also note that Arbie Parker (Professional Services) is putting together a GreenBook on how to use the 32 bit PubExtension.dll.

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

In the application event log the following message appears

Faulting application PubServer.exe, version 8.9.4.19, faulting module PubServer.exe, version 8.9.4.19, fault address 0x00043580.

Explanation

One reason this could happen is that Publisher user an xml file (pubconfig.xml ) for configuration. On occasion this file gets corrupted.

How to Avoid

Option 1: Replace the pubconfig.xml with a known good file

1. Make sure the publisher executable (pubserver.exe) is not running via task manager. If it is, end the process.

2. Publisher delivers an original file (pubconfig.xml.ori ) along with the one it uses for configuration.

3. In the C:\Bentley\PublishingServer\Config folder on the server, Rename the pubconfig.xml file to pubconfig.old

4. Make a copy of the pubconfig.xml.ori

5. Rename the copy to pubconfig.xml.

6. Start the Projectwise Publisher service

For this use case, the Publisher service started but when a user went to view a file he got an error “cannot load…”

Option 2:  Publisher now starts but I can't view a file

1. Make sure the Projectwise Publisher Administrator service and Projectwise Publisher image engine service is running

2. Launch the ProjectWise Publisher Administrator, (Start / Programs / Bentley / ProjectWise Publishing Server / ProjectWise Publishing Server Administrator

3. Turn off run as a webserver extension under the general tab, clicked submit, then restart the server control

4. Go back and check on ‘run as a webserver extension’ and hit submit and restart the service control again.

5. You should now be able to view a file.

See Also

Troubleshooting ProjectWise Publishing Server

What does the delegate user do?

This delegate user\setting is for use with ProjectWise Web Server, to simulate single sign on for users using ProjectWise Web Parts. When this setting is on, it authorizes this user to request passwords for other users who are connecting to a datasource from ProjectWise Web Parts, when those other users are attempting to log in with their Windows-based ProjectWise user account. For this setting to work, you must also go to the computer on which ProjectWise Web Server is installed and specify that this user is the delegate user.

Will the permissions for this user carry through and give all users the same access to files?

No, the permissions of the delegate user are not carried through.

Will the delegate user be the owner of the objects created by users using the web interface?

No, the owner of the objects created will remain with the user who created them.

See Also

The ProjectWise Administrator Help.

This article describes where to find integration compatibility for Revit and any software that can be integrated with ProjectWise

What versions of Revit are supported with PW 08.11.11.559

The ProjectWise readme delivered with all ProjectWise modules provides a list of integration compatibility for all software that can be integrated

This infornation was taken from the PW 08.11.11.559
C:\Program Files (x86)\Bentley\ProjectWise\ readme_projectwise.chm

Here are the supported version of Revit with PW 08.11.11.559
Revit (32-bit and 64-bit) 2013 (Update 2)
Revit Architecture (32-bit and 64-bit) 2013 (Update 2), 2012 (Update 2), 2011 (Update 2), 2010 (Update 2)
Revit MEP (32-bit and 64-bit) 2013 (Update 2), 2012 (Update 2), 2011 (Update 2), 2010 (Update 2)
Revit Structure (32-bit and 64-bit) 2013 (Update 2), 2012 (Update 2), 2011 (Update 2), 2010 (Update 2)

It doesn’t list it in the readme but Revit 2012 is also supported in this version.

Problem

If I go to attach an Xref, even if I use the ProjectWise menu or the DMSXREF command, it opens a local dialog and not ProjectWise.

We're using ProjectWise 8.9.4.50 with iDesktop Installed for Autocad 2006. It seems that some portions of the integration are not fully functional? For instance, the File>New, Open, and Save As... options all correctly bring up a ProjectWise dialog. However, if I go to attach an Xref, even if I use the ProjectWise menu or the DMSXREF command, it opens a local dialog and not ProjectWise.

customer is using the class path of The class path AutoCAD.Drawing.16  in his associations

Solution

Customer had user associations set on his workstation we removed the user associations so that the global association would be the one chosen.
However the customer has different version of AutoCAD on the system and needs a way to set associations for the different versions.

The command line required to correctly launch AutoCAD with Projectwise integration is:
"C:\program files\AutoCAD 2006\acad.exe" /t

HKEY_CLASSES_ROOT\AutoCAD.Drawing.pw\shell\open\command
The class path AutoCAD.Drawing.PW finds the most current version of AutoCAD and uses "C:\program files\AutoCAD 2006\acad.exe" /t to open AutoCAD with PW integration. (if you search the registry for AutoCAD.Drawing.PW you will find this path)

HKEY_CLASSES_ROOT\AutoCAD.Drawing.16\shell\open\command
The class path AutoCAD.Drawing.16 shows a path of "C:\Program Files\AutoCAD 2006\acad.exe" "%1"
This will launch AutoCAD but only parts of the integration will work, as described.

However I found another class path
HKEY_CLASSES_ROOT\AutoCAD.Drawing.pw.16.2\shell\open\command
Which shows the path as "C:\program files\AutoCAD 2006\acad.exe" /t I set up another program association using AutoCAD.Drawing.16.2 as my class path, and All the integration worked within AutoCAD.

Additional information:  when you setup a user program association and browse to the acad.exe rather then use the class path, you will get a warning that "the application might not work correctly if associated using full path."

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 installing Web Server Client Components in the IE , error 2738 pops up:

The installer has encountered and unexpected error installing this package. this may indicate a problem with this package. the error code is 2738.

Steps to Resolve

Register vbscript.dll and javascript.dll in cmd. User is using the Windows 7 64-bit but it is still an operation system issue not a ProjectWise issue.

Problem

 When will ProjectWise Reports for V8i be released?

Solution

 A V8i version of Reports is not being produced.  Bentley  is working on a replacement that provides a more scalable approach.
For now, V8i users will have to create reports with a standard reporting tool by going directly to the db.
We apologize for any inconvenience this may cause.
If you need assistance with setting up reports with a standard reporting tool, Please contact Bentley Professional Services.

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

While using Text Editor box the paste options and enable popup are grayed out.

Solution

The problem was the program association settings. There was a %1 at the end of the command line argument line in the Program Association for MicroStation. Once this was removed all worked well.

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

User is running thru a test upgrade and after dmsconv and connecting the datasource, the datasoruce icon shows a red X.  However he is able to login and do things.  Same red X appears in ProjectWise explorer.

other users have reported the red X and were not able to login, and or do certain functions.

Solution

The red X usually indicates that there is something wrong with a table or index in the database.  When Projectwise Admin starts it checks all the tables and indexes against the \bentley\projectwise\bin\schema_dms.xml, as long as everything matches no red X should appear.

To solve the problem, turn up the logging for the dmskrnl and PWadmin, then launch PWadmin. send the logs to Bentley technical support for review.

Another reason the red X appears may be permissions in Oracle
for Oracle make sure permissions are correct as indicated in the implementation guide

When Oracle is your database, the Oracle database user must have
(at a minimum) the following privileges and permissions in order
to run ProjectWise Integration Server:
— CONNECT role
— CREATE PROCEDURE privilege
— CREATE SEQUENCE privilege
— CREATE TABLE privilege
— CREATE VIEW privilege
— UNLIMITED TABLESPACE privilege
— EXECUTE permission on the DBMS_LOB package

The EXECUTE permission on the DBMS_LOB package is the one that is usually missed.
You can run the following script to grant the permissions.

grant execute on <schema>.DBMS_LOB to user;
Or we can try : grant execute on <schema>.DBMS_LOB to public

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

Window 7 Users not getting check-in prompt when checking in a MicroStation drawing

Solution

Documents and settings not accessible - related to Part of the integration piece. Solution is the following:
1. Change everyone’s path
2. Run chklcleanup tool and clean working directory
3. Purge all work directories
4. Update Database statistics and rebuild indexes.

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

ProjectWise i-model Composition Server was printing .doc files to pdf correctly. After installing Microsoft Excel it stopped working and following error appeared. 

ERROR: Failed to add plot on 'datasource name' for document 'document path on ProjectWise' WORDPROV, Cannot open document 'document path on ProjectWise'

--file may be password protected,
--or incorrect password specified,
--or there was another problem opening the file.

Steps to Resolve

Restart ProejctWise Orchestration Framework service and check in ProjectWise Orchestration Framework administrator if all processes are running.

Error or Warning Message

503 Service Unavailable

Explanation

In a new setup of PW Web Parts with Single Sign On configured, the user logs in and gets "503 Service Unavailable" The IIS application pool that is used for the PW Web Site actually crashes and the following is in the Event Viewer

Log Name:      Application
Source:        ASP.NET 2.0.50727.0
Date:          9/30/2013 12:50:31 PM
Event ID:      1334
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      servername
Description:
An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/3/ROOT

Process ID: 4440

Exception: System.Security.Cryptography.CryptographicException

Message: Keyset does not exist

StackTrace:    at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
   at System.Security.Cryptography.SafeKeyHandle._FreeHKey(IntPtr pKeyCtx)
   at System.Security.Cryptography.SafeKeyHandle.ReleaseHandle()
   at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
   at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
   at System.Runtime.InteropServices.SafeHandle.Finalize()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ASP.NET 2.0.50727.0" />
    <EventID Qualifiers="49152">1334</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-09-30T19:50:31.000000000Z" />
    <EventRecordID>93314</EventRecordID>
    <Channel>Application</Channel>
    <Computer>servername</Computer>
    <Security />
  </System>
  <EventData>
    <Data>An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/3/ROOT

Process ID: 4440

Exception: System.Security.Cryptography.CryptographicException

Message: Keyset does not exist

StackTrace:    at System.Security.Cryptography.CryptographicException.ThrowCryptogaphicException(Int32 hr)
   at System.Security.Cryptography.SafeKeyHandle._FreeHKey(IntPtr pKeyCtx)
   at System.Security.Cryptography.SafeKeyHandle.ReleaseHandle()
   at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
   at System.Runtime.InteropServices.SafeHandle.Dispose(Boolean disposing)
   at System.Runtime.InteropServices.SafeHandle.Finalize()</Data>
  </EventData>
</Event>

How to Avoid

The issue only occurs when the Physical Path Credentials in the Web Site settings were set with a specific user.  In this case, this setting was not necessary, so we changed to the default (option 1)  another option to use a specific user is still to be determined.

Warning: these changes are within Microsoft IIS, please check with your IT department on any requirements before modifying

Option 1 :

1. Open IIS on the PW Web Server

2. Highlight the Web Site that has PW Web Parts deployed

3. Advanced Settings

4. Physical Path Credentials

5. Change to "Application user (pass-through authentication)

6. Open a command prompt and type iisreset (this will temporarily shutdown access to any/all applications on any website on this machine)

Problem Description

 User was installing ProjectWise SS4 Integration Server and got "error- Non-HTTP activation features required.

Solution

User found that the "Non Http activation error" was caused by not having a submodule of .net loaded.  Once that was installed - everything worked fine.

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!

Here you will find more Information about ProjectWise Web Server Client:

Installation:

• • 503 Error With Single Sign On
  • Error Non-HTTP Activation Features Required

MISC:

• Authenication Failed. Unspecified Project...(Solution 500000101386)
• Checkout Option is Missing in Webparts Web Client
• Components Not Visible in Web Parts For Some Users
• ProjectWise Web Server Evaluation License has Expired
• Properties Do No Display in SharePoint ProjectWise Web Parts

For more information on ProjectWise, please see the Table of Contents to the left

Problem

Authentication Failed. Unspecified Projectwise Error occurred (-1) Contact website administrator.  User is trying to log into the ProjectWise web parts (aspx) page. He Gets to the login page, picks the datasource, enters his credentials
Clicks log in and gets the error message.

Product: ProjectWise Web Server V8i
Version: 08.11.11.559
Area: ASPX Webparts, Problem ID#: 90600, ERRORMESSAGE

Solution

The web server had two nics on the machine.
There seemed to be an issue with the webserver properly connecting to
the integration server. (we found this by looking at the ProjectWise webserver
logs)
in the webservers host file, we add an entry for the integration server,
restarted IIS and that solve the problem.

Problem Description

When I right click a file in Projectwise WebParts web client, the checkout option is not listed.  It is also not available under the documents pull down.

Steps to Resolve

1. Make sure you are connecting to a site that has read write access.  If you are connecting to the Projectwise Web View site, then the checkout option will not be available.
2. Check to make sure you are using a supported Browser. You can find this information in the Projectwise Readme file under requirments for the Webserver section.  If you don't have a copy of the readme then Click HERE.  Choose your version then click the readme link. (As of this posting Internet Explorer 11 is not supported)
3. Make sure you are using the 32 bit version of the browser you are using and that the lastest updates are installed
4. The Checkout option requires that the PWWebFileTransfer Active X control be installed.
   1. As of this posting, ActiveX is only available in IE 8, IE 9, and IE 10 desktop, therefore all other supported browsers will have limited Web Parts functionality
   2. Check that the popup blocker is not blocking the active X control from being installed