Quantcast
Channel: ProjectWise Design Integration Wiki
Viewing all 1890 articles
Browse latest View live

Using the CHKLCLEANUP Utility in ProjectWise [TN]

$
0
0
Current Revision posted to Content Management - Wiki by JackiS on 11/21/2013 3:04:04 PM

Using the CHKLCLEANUP Utility in ProjectWise [TN]

TechNotes,ProjectWiseSELECTsupport

  
 Applies To 
  
 Product(s):ProjectWise Administration
 Version(s):V8i (08.11.07.xx)08.11.07.xx+)
 Environment: N/A
 Area: N/A
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Overview

ProjectWise keeps track of all the files that have been checked out, copied out or exported via the dms_chkl table in the ProjectWise database.  This table can accumulate orphan records that generally do not cause any problems.  The table can be cleaned up should one of the following issues occur:
·         A user has many files checked\copied out and their system crashes beyond repair.
·         Users using the same machine have the same ProjectWise working directory.  When one user tries to checkout a file that the other user has copied out, he may get an error.  "working directory is in use"...
 
The dms_chkl tracks what files have been checked out, copied out, or exported, by username and node name.
 
The 08.11.07.107 version of ProjectWise delivers a utility to help users cleanup the dms_chkl table.  The utility, chklcleanup.exe, gets installed as part of the ProjectWise Administrator and must be run from the C:\Program Files\Bentley\ProjectWise\bin directory as it needs required libraries from this folder.
 
Currently the utility only works with 08.11.07.xx + datasources and will not find 08.11.05.xx datasources.
 
*** Note:
·         There is no audit trail option to record these actions.
·         This utility only cleans up the database and does not delete the files from the physical machines they were original copied out too.
 
Preliminary steps
1.       Have the users whose entries you will be deleting check all files in.
2.       Purge their working directories via the local document organizer.
3.       Log out of the system.
4.       Have the users delete their working directories.
 
Steps to run the CHKLCLEANUP.EXE
1.       On a system that has the ProjectWise Administrator installed, Open Windows Explorer and navigate to C:\Program Files\Bentley\ProjectWise\bin
2.       Double click the CHKLCLEANUP.EXE
3.       Click next on the welcome screen
4.       You are then prompted to choose and log into a datasource.
5.       The next screen gives you the choice to “remove copy out locations” by username or by machine name
6.       If you check user name the next screen lists all the users in the datasource.  Check the names you wish to remove the copy out entries for.
a.       There is an option to export the list to a cvs file.  This option gives the User Name, User Description, and Document Count, in a comma delimited file.
b.      Another option on this page is explained as follows:  Some DMS_CHKL location records may be left over after removing users, use this option to remove these orphan rows.
7.       If you checked Machine name, the next screen lists all the machines listed in the dms_chkl table in the datasource that have files copied out.  Check the machine names you wish to remove the copy out entries for.
a.       There is an option to export the list to a cvs file.  This option gives the Machine Name and Document Count in a comma delimited file.
8.       On the next screen you are given a summary of your choices and asked to confirm that you want to delete the copy out location entries.
9.       The final screen will give a message that the wizard has succeeded and a report of how many entries were deleted.
10.   Bentley Recommends to have unique working directories for each user.  Create a new unique working directory for the user via the PW administrator.
11.   Allow the user to log back into the system and make sure the new working directory was created correctly.

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 submit any comments you have on this Wiki article in the "Comments" area below. THANK YOU!


50002 Cannot start application for the specified document

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 11/21/2013 3:47:34 PM

50002 Cannot start application for the specified document

SELECTsupport,ProjectWiseExplorerClient,ErrorMessage,Open/Close/SaveAs,SELECTsuppoErrorMessage,Integration-AutoCAD

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: Integration - AutoCAD
 Subarea: Open / Close / Save As
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

Last Error [50002]  Cannot start application for the specified document.  Check your program associations.  Invalid parameter passed to the API function.

Explanation

When the user tries to open a dwg file from Projectwise, AutoCAD opens with a blank document and then throws  error 50002

How to Avoid

Option 1 Remove run as administrator switch

  1. On ths users system, in Windows explorer, Go to the autocad.exe file, right mouse click properties, Compatibility tab, uncheck "run this program as an administrator."

Note:evenifthisswitchisturnedoff,therecouldbethirdpartyapplicationsinstalledthatelevateprivledgesthatleadtothesameproblem.  Totestforthis,openProjectWisewithelevatedpermissions(browsetopwc.exeandrightclick-runasadministrator)toseeiftheerrorstilloccurs.  (PWneedstobeatthesameprivledgelevelastheapplicationyouareopening)

Option 2 Check program associations.

  1. Check the windows program associations to make sure AutoCAD is associated to DWG
  2. On the client machine, in Projectwise, logged in as the user, go to tools \ associations, programs, change to 'user associations', scroll to AutoCAD and expand the open command, remove any associations, click save and close

Option 3 Make sure Projectwise integration is properly installed.

  1. Open AutoCAD from the desktop, then file open, you should be prompted to login to Projectwise, browse to a file and open it.  Check that the Projectwise ribbon is available and all items are functional
  2. Go to add remove program, remove Projectwise explorer, run a repair\reinstall on AutoCAD, then reinstall Projectwise explorer.

See Also

Cannot Start application... Blog

Word or Excel opens as a blank document or error 50002 or 112173

 

Distribution Services does not work with the set file enabled

$
0
0
Current Revision posted to Content Management - Wiki by mantas.nauseda on 11/28/2013 6:14:43 AM

  
 Applies To 
  
 Product(s):ProjectWise Dynamic Composition Server (Distribution Services)
 Version(s):08.11.11.559
 Environment: N/A
 Area: PDF
 Subarea: 
 Original Author:Mantas Nauseda, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Problem Description

When trying to run the Distribution Service job that has the set (InterPlot Settings file) enabled it gives the error (when using Bentley Navigator as a print engine):
Failed -- IPARMENG, The MicroStation IPARM engine did not complete successfully.
- Milepost code: 0

And error (when using MicroStation as a print engine):
Failed -- CMDERR, executed ipmstnsrvm, which failed

When trying to use the same ProjectWise document and the same settings file in the InterPlot Organizer it worked fine without any errors.

Reason

When the set file is used in the Distribution Job the Print Engine process is started with the Current Directory that is the Distribution service working directory (a shared folder on the network, for example: \\ server_name.domain.com\ds_working\1\282_35)

User had the system Path added that syntax was not correct. One of the paths was added like: \c:\windows. This way when the print engine (MicroStation or Navigator) was locating the required dll files it was trying to load the dll from the path: \\ server_name.domain.com\ds_working\1\282_35c:\windows
The syntax of the path is not correct and it failed to load the dll. The whole process stopped at this stage.

Steps to Resolve

To resolve the issue the System Path was fixed (backslash was removed from: \c:\windows to: c:\windows)

 

This file 'C3D 2012.CivilDSProj' format is unsupported

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 12/4/2013 7:47:49 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: Integration - Civil 3D
 Subarea: Data Shortcuts
 Original Author:molly watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

This file 'C3D 2012.CivilDSProj' format is unsupported

Explanation

User was trying to open the CivilDSProj file directly via Civil3D

How to Avoid

 

    1. The recommended workflow is to open the master file from ProjectWise, which will copy out the Data Shortcuts files automattically.

 

 

See Also

http://communities.bentley.com/products/projectwise/content_management/m/mediagallery/228167.aspx

Managed Workspace config file changes are not sticking

$
0
0
Current Revision posted to Content Management - Wiki by Dana Guthrie on 12/5/2013 5:29:47 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: MISC
 Subarea: 
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Background

Changes to files in ProjectWise managed workspace are not updating the workspace on the local machine

User had changed a configuration file on his local system, then renamed the original in ProjectWise to .old and then dropped the newly edited one in. 

When he opens a dgn file that is in a folder with the workspace assigned the changes he made in the workspace are not there.  It seems to be reading the old file

Explanation

Projectwise knows that the file he renamed is part of a configuration block and when he changed the name in PWE, PW also changed the name in the configuration block to reference the .old file

Steps to Resolve

  • Remove the new file
  • Rename the .old file to the original name
  • Go to the properties of that file and using the advance button import the new file.

 

 

"generic error" running Bentley i-model Composition Server Configuration

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 12/6/2013 3:54:28 PM

  
 Applies To 
  
 Product(s):ProjectWise Dynamic Composition Server
 Version(s):
 Environment: N/A
 Area: Administrator
 Subarea: 
 Original Author:Molly Watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

generic error while running the Configuration Wizard

Object reference not set to an instance of an object when trying to uninstall iCS when its in this state

Explanation

The installation of iCS will finish, and then attempt to kick off the configuration wizard.  The first step of the configuration is to create a printer, and in this case the Windows Print Spooler service was disabled

How to Avoid

 

  1. In Windows Services, set Print Spooler to startup "Automatic"

  2. Start the Print Spooler service

  3. Rerun the configuration wizard (Start-Programs -Bentley-ProjectWise V8i (SELECTseries 4)-Bentley i-model Composition Server for PDF-Bentley i-model Composition Server Configuration)

 

Error 58502 deleting document

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 12/6/2013 9:57:43 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: GUI
 Subarea: 
 Original Author:Molly Watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

Error 58502: Error deleting document. user is not an administrator

Explanation

User had full rights on the document, also had document delete user setting turned on.  Datasource settings were configured that only Administrators could delete.

How to Avoid

 

  1. In ProjectWise Administrator, log into the datasource
  2. Right click on datasource name-properties
  3. Settings tab
  4. Change global delete restrictions to "default"

 

 

See Also

 

SSO Clients are not silently re-authenticated to the datasource

$
0
0
Current Revision posted to Content Management - Wiki by john.lee on 12/6/2013 11:33:05 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.423
 Environment: Windows 7 64 bit
 Area: MISC
 Subarea: 
 Original Author:John Lee, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Problem Description

Cached SSO domain login credentials are not expired is failing. SSO Clients are not silently re-authenticated to the datasource.

Findings

In the failed case: 

integrated MicroStation SSO credentials are expiring.  The Default lifetime for Client-side cached  login credential used to silently re-authenticate a client to the Integration  Sever is not working correctly and affecting the cached SSO/domain login. The SSO credentials should not expire.

As referenced to the cfg file, cached SSO/domanin login credentials are not expired:

; Default lifetime (in seconds) for client-side cached login credentials, used to

; silently re-authenticate a client to the Integration Server in the event of a

; network disconnect. When using ProjectWise authentication, after this timeout

; occurs clients will be required to re-input their ProjectWise login credentials.

; A value of 0 (or less) is illegal. Use the "User Credential Expiration Policy"

; General user settings (in the ProjectWise Administrator) to set the policy for

; user expirations.

;

; If this setting is commented out, a default expiration value of 10 hours is used.

; Note that this applies to ProjectWise authenticationonly -- cached SSO/domain login

; credentials are not expired.

;

UserLoginTokenTimeout=36000

 

The failure has been confirmed using  MicroStation SS3 version 08.11.09.357 integrated with PWExplorer  version
08.11.11.567 (see fig 1)

Steps to Resolve

Manually reconnect the MicroStation session to ProjectWise by clicking the <OK> button in fig 1 above.


"generic error" running Bentley i-model Composition Server Configuration

$
0
0
Revision 1 posted to Content Management - Wiki by Molly Watts on 12/6/2013 3:54:28 PM

  
 Applies To 
  
 Product(s):ProjectWise Dynamic Composition Server
 Version(s):
 Environment: N/A
 Area: Administrator
 Subarea: 
 Original Author:Molly Watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

generic error while running the Configuration Wizard

Object reference not set to an instance of an object when trying to uninstall iCS when its in this state

Explanation

The installation of iCS will finish, and then attempt to kick off the configuration wizard.  The first step of the configuration is to create a printer, and in this case the Windows Print Spooler service was disabled

How to Avoid

 

  1. In Windows Services, set Print Spooler to startup "Automatic"

  2. Start the Print Spooler service

  3. Rerun the configuration wizard (Start-Programs -Bentley-ProjectWise V8i (SELECTseries 4)-Bentley i-model Composition Server for PDF-Bentley i-model Composition Server Configuration)

 

"generic failure" running Bentley i-model Composition Server Configuration

$
0
0
Revision 2 posted to Content Management - Wiki by Molly Watts on 12/9/2013 2:41:30 PM

"generic errorfailure" running Bentley i-model Composition Server Configuration

Administrator, SELECTsupport, ProjectWise Dynamic Composition Server, Error Message, iCS for PDF

  
 Applies To 
  
 Product(s):ProjectWise Dynamic Composition Server
 Version(s):
 Environment: N/A
 Area: Administrator
 Subarea: 
 Original Author:Molly Watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

generic errorfailurewhile running the Configuration Wizard

Object reference not set to an instance of an object when trying to uninstall iCS when its in this state

Explanation

The installation of iCS will finish, and then attempt to kick off the configuration wizard.  The first step of the configuration is to create a printer, and in this case the Windows Print Spooler service was disabled

How to Avoid

 

  1. In Windows Services, set Print Spooler to startup "Automatic"

  2. Start the Print Spooler service

  3. Rerun the configuration wizard (Start-Programs -Bentley-ProjectWise V8i (SELECTseries 4)-Bentley i-model Composition Server for PDF-Bentley i-model Composition Server Configuration)

 

ProjectWise Web scroll bar too low to view attributes

$
0
0
Current Revision posted to Content Management - Wiki by Bill on 12/10/2013 10:07:45 PM

Is the ProjectWise Explorer web client scroll bar too low to view environment attributes ?  There is a workaround for this that involves editing an xml document on the Web Server to bring the scroll bar up and close, in the view, to see which attributes are in what columns.   The solution for the scroll bar is to edit the default.aspx page, and change the two lines that have “ExpandWithContent" = “true”” to “false”. 

This file is often found in the C:\Inetpub\wwwroot\Default directory

 

"Network Path Not Found" when running i-model Composition Server job

$
0
0
Current Revision posted to Content Management - Wiki by sboniwell on 12/11/2013 1:11:38 AM

  
 Applies To 
  
 Product(s):ProjectWise Dynamic Composition Server
 Version(s):
 Environment: Window Server 2008 64 bit, Windows 7 64 bit, Windows Server 2008 R2
 Area: PDF
 Subarea: 
 Original Author:Steve Boniwell, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

When running an i-model Composition job from either ProjectWise Explorer or i-model Composition Server Administrator, an error message "Network Path Not Found" is displayed and the job is not processed.

Explanation

The working directory that is set for i-model Composition Server is not accessible.

How to Avoid

Ensure that the Working Directory specified is accessible.

ProjectWise V8i (SELECTseries 4) Refresh

$
0
0
Revision 13 posted to Content Management - Wiki by Shauger on 11/12/2013 4:16:28 PM

Click here for current readme and requirements

Current version 08.11.11.574, released October 14, 2013
Original version 08.11.11.559, released April 2, 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
Tags: ProjectWise V8i (SELECTseries 4) Refresh

How to export and import Projectwise applications

$
0
0
Current Revision posted to Content Management - Wiki by Dana Guthrie on 11/18/2013 3:04:22 PM

  
 Applies To 
  
 Product(s):ProjectWise Integration Server
 Version(s):08.11.11.559
 Environment: N/A
 Area: ProjectWise Administrator
 Subarea: Application Configurations
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

I have two datasources. The first datasource is my original that I have configured with all the applications.  The second datasource is a new datasource and I want to copy\export the applications I created in the original datasource to my new datasource

Background

To perform this task you will need to be the administrator of both datasources, know the odbc connection user name and password, and be able to run a dos command

Steps to Accomplish

Step 1 Export the applications

  1. In ProjectWise Administrator, right click the applications node and choose, export application
    configurations.

  2. Savethe file as an *.xml

Step 2 Import the applications using the dmsconv tool

  1. On the integration server, Open a command prompt and navigate to C:\Program Files\Bentley\ProjectWise\Bin
  2. Type dmsconv –d ODBCdatasourceName –u databaseUsername
    –p databasePassword –nomime –appfile (path and file name to xml you created)

  3. Example:  C:\Program Files\Bentley\ProjectWise\Bin>dmsconv -d
    test -u sa -p password -nomime -appfile c:\apps.xml

  4. Note: This command will overwrite the applications that are currently configured in the
    datasource.  This command can be used to add applications as well. 

  5. Important:  This command does not set the Icons.  Icons will need to be set manually

See Also

The Projectwise Administrator Help (search for dmsconv)

Tags: Application Configurations, ProjectWise Administrator, how to, ProjectWise Integration Server, SELECTsupport

Last Error [-1] The view contains invalid column '{name}.

$
0
0
Current Revision posted to Content Management - Wiki by Dana Guthrie on 11/18/2013 3:45:26 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: Search
 Subarea: 
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

Last Error [-1] The view contains invalid column '{name}.

Explanation

User has exported a project from a test environment that included saved searches, and has imported it into a new datasource. When he clicks on his saved searches or the view he gets the error

How to Avoid

We compared the global views between the two datasources, and they were not the same.
Once we made them the same and assigned the correct environment to the view, the searches and views started working correctly

Tags: search, error message, ProjectWise Explorer Client, SELECTsupport

Microsoft Excel cannot access the file ':: ODMA\.....filename.xlsx.

$
0
0
Current Revision posted to Content Management - Wiki by Dana Guthrie on 11/18/2013 4:25:56 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: Integration - Office
 Subarea: Word / Excel / PowerPoint
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

Microsoft Excel cannot access the file ':: ODMA\.....filename.xlsx.  There are serval possible reasons:
The file name or path does not exist
The file is being used by another program
The workbook you are trying to save has the same name as a currently open workbook.

Explanation

User has a datasource that he has had through many migrations.  The datasource is currently on PW SS3.  He has other datasources on the same version that are not experiencing the problem.  He is connecting to the datasource with a PW SS4 client.

The problem is:  When he double clicks an excel document he gets the above error, but it only happens in this one datasource. The file will open after clicking okay to the error. All other datasources work fine.

How to Avoid

Option 1 Check user program associations on the client machine

  1. In Projectwise Explore, log in as the user, go to tools, associations, programs
  2. Change the pull down to User associations, then scroll down to Microsoft Excel
  3. Expand Microsoft Exel, open, and remove any associations

Option 2 Check program applications via the ProjectWise Administrator client

  1. Open Projectwise administrator and log in to the datsource
  2. Double click applications, then find Microsoft Excel
  3. Right click properites on Microsoft Excel, highlight 'open Microsoft Excel' click modify
  4. Uncheck the box that says 'replace default arguments'
  5. Click okay and okay
  6. If this does not solve the problem compare these application settings to a datasource that is working.
Tags: Integration - Office, Word / Excel / PowerPoint, error message, ProjectWise Explorer Client, SELECTsupport

Setup Windows 2008 R2 Server to let ProjectWise full text search .msg files [TN]

$
0
0
Revision 5 posted to Content Management - Wiki by Ranveer.Basra on 11/18/2013 6:21:36 PM

  
 Applies To 
  
 Product(s):ProjectWise Integration Server, Orchestration Framework
 Version(s):08.11.07.xxx
 Environment: N/A
 Area: N/A
 Subarea: N/A
 Original Author:Ranveer Basra, Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Overview

Please Note: 

As of ProjectWise V8i (SELECTseries 2), the MSG iFilter is no longer required to extract file
properties from MSG documents.

This document will show the steps on how to configure the server for .msg file full text retrieval in Windows Server 2008 and Select Series 1 (08.11.07.xx). In ProjectWise V8XM the option was to install Windows Desktop Search or Office Outlook on the server; however In the Windows Server 2008 you will need to install the Windows Search Services. 

Before we start please make sure you have installed all windows updates on the server along with .net Framework 3.5.1 Features are enabled from Server Manager, Features.

1.       Navigate to Server Manager and click Add Roles, Install File Services(Fig1)
 Fig 1.
 

                

2.       Under Role Services make sure Windows Search Services is installed(Fig2)

 Fig2

   

3.       Install the Add-in for Outlook saved mail (.msg file) indexing from  Microsoft site below:

 http://www.microsoft.com/downloads/details.aspx?FamilyID=134ecbb0-c162-4d07-bef3-0b602c4a79dd&displaylang=en

a.       Validate the install with navigating to control panel, and selecting Programs and Features;  there     should be a  Windows Desktop Search: Add-in for Outlook is installed (Fig3)

Fig3
 

  

 

4.       Now Remove Windows Search Services (from step 2) role (reboot of the server is mandatory)(Fig4)

Fig4

5.       Now add the indexing Service from Role Services.(Fig5)

Fig5
 

 

6.       After adding the Indexing Service Add MSMQ which is mandatory for Orchestration Framework function   properly.(Fig6)

Fig6
 

Once the entire configuration on the server is done, you may move forward with installing ProjectWise Components:


1.       Install MicroStation Pre-Requisite pack
2.       Install MicroStation
3.       Install Orchestration Framework - setup OFW database
4.       Install Integration Server
5.       Install ProjectWise Administrator

a.       Login to the datasource
b.      Configure document processors; right click Full Text Indexing, select the check box for Indexing    enabled. Under User context and select a ProjectWise User: (that does not have expiring password    credentials) Password: (Fig7)

Fig7

 


c.       Right click Full Text Indexing and select ‘Mark Folder Documents for Reprocessing…’, select a folder or the   ROOT folder(Fig8)

Fig8

d.      Right click Full Text Indexing and select ‘Start Processing Now’ Once the process has begun
 You will see a dialog box as shown in (fig9). Depending on the size of your database you may be able to run a   full text search instantaneously or after the process has gone through its full document pass.

Fig9
 

Tags: ProjectWise SELECTsupport

Datasource statistics

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 11/19/2013 4:45:19 PM

  
 Applies To 
  
 Product(s):ProjectWise Integration Server
 Version(s):08.11.11.123
 Environment: N/A
 Area: Integration / Caching /Gateway
 Subarea: MISC
 Original Author:Molly Watts, Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

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

 

 

Tags: Integration / Caching /Gateway, MISC, Generic, ProjectWise Integration Server, SELECTsupport

Using the CHKLCLEANUP Utility in ProjectWise [TN]

$
0
0
Current Revision posted to Content Management - Wiki by JackiS on 11/21/2013 3:04:04 PM

  
 Applies To 
  
 Product(s):ProjectWise Administration
 Version(s):V8i (08.11.07.xx+)
 Environment: N/A
 Area: N/A
 Subarea: N/A
 Original Author:Bentley Technical Support Group
  

 

 

 

 

 

 

 

 

Overview

ProjectWise keeps track of all the files that have been checked out, copied out or exported via the dms_chkl table in the ProjectWise database.  This table can accumulate orphan records that generally do not cause any problems.  The table can be cleaned up should one of the following issues occur:
·         A user has many files checked\copied out and their system crashes beyond repair.
·         Users using the same machine have the same ProjectWise working directory.  When one user tries to checkout a file that the other user has copied out, he may get an error.  "working directory is in use"...
 
The dms_chkl tracks what files have been checked out, copied out, or exported, by username and node name.
 
The 08.11.07.107 version of ProjectWise delivers a utility to help users cleanup the dms_chkl table.  The utility, chklcleanup.exe, gets installed as part of the ProjectWise Administrator and must be run from the C:\Program Files\Bentley\ProjectWise\bin directory as it needs required libraries from this folder.
 
Currently the utility only works with 08.11.07.xx + datasources and will not find 08.11.05.xx datasources.
 
*** Note:
·         There is no audit trail option to record these actions.
·         This utility only cleans up the database and does not delete the files from the physical machines they were original copied out too.
 
Preliminary steps
1.       Have the users whose entries you will be deleting check all files in.
2.       Purge their working directories via the local document organizer.
3.       Log out of the system.
4.       Have the users delete their working directories.
 
Steps to run the CHKLCLEANUP.EXE
1.       On a system that has the ProjectWise Administrator installed, Open Windows Explorer and navigate to C:\Program Files\Bentley\ProjectWise\bin
2.       Double click the CHKLCLEANUP.EXE
3.       Click next on the welcome screen
4.       You are then prompted to choose and log into a datasource.
5.       The next screen gives you the choice to “remove copy out locations” by username or by machine name
6.       If you check user name the next screen lists all the users in the datasource.  Check the names you wish to remove the copy out entries for.
a.       There is an option to export the list to a cvs file.  This option gives the User Name, User Description, and Document Count, in a comma delimited file.
b.      Another option on this page is explained as follows:  Some DMS_CHKL location records may be left over after removing users, use this option to remove these orphan rows.
7.       If you checked Machine name, the next screen lists all the machines listed in the dms_chkl table in the datasource that have files copied out.  Check the machine names you wish to remove the copy out entries for.
a.       There is an option to export the list to a cvs file.  This option gives the Machine Name and Document Count in a comma delimited file.
8.       On the next screen you are given a summary of your choices and asked to confirm that you want to delete the copy out location entries.
9.       The final screen will give a message that the wizard has succeeded and a report of how many entries were deleted.
10.   Bentley Recommends to have unique working directories for each user.  Create a new unique working directory for the user via the PW administrator.
11.   Allow the user to log back into the system and make sure the new working directory was created correctly.

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 submit any comments you have on this Wiki article in the "Comments" area below. THANK YOU!

Tags: ProjectWise SELECTsupport, TechNotes

50002 Cannot start application for the specified document

$
0
0
Current Revision posted to Content Management - Wiki by Molly Watts on 11/21/2013 3:47:34 PM

  
 Applies To 
  
 Product(s):ProjectWise Explorer Client
 Version(s):08.11.11.559
 Environment: N/A
 Area: Integration - AutoCAD
 Subarea: Open / Close / Save As
 Original Author:Dana Guthrie, Bentley Technical Support Group
  

 

 

 

 

 

 

 

Error or Warning Message

Last Error [50002]  Cannot start application for the specified document.  Check your program associations.  Invalid parameter passed to the API function.

Explanation

When the user tries to open a dwg file from Projectwise, AutoCAD opens with a blank document and then throws  error 50002

How to Avoid

Option 1 Remove run as administrator switch

  1. On ths users system, in Windows explorer, Go to the autocad.exe file, right mouse click properties, Compatibility tab, uncheck "run this program as an administrator."

Note: even if this switch is turned off, there could be third party applications installed that elevate privledges that lead to the same problem.  To test for this, open ProjectWise with elevated permissions (browse to pwc.exe and right click-run as administrator) to see if the error still occurs.  (PW needs to be at the same privledge level as the application you are opening)

Option 2 Check program associations.

  1. Check the windows program associations to make sure AutoCAD is associated to DWG
  2. On the client machine, in Projectwise, logged in as the user, go to tools \ associations, programs, change to 'user associations', scroll to AutoCAD and expand the open command, remove any associations, click save and close

Option 3 Make sure Projectwise integration is properly installed.

  1. Open AutoCAD from the desktop, then file open, you should be prompted to login to Projectwise, browse to a file and open it.  Check that the Projectwise ribbon is available and all items are functional
  2. Go to add remove program, remove Projectwise explorer, run a repair\reinstall on AutoCAD, then reinstall Projectwise explorer.

See Also

Cannot Start application... Blog

Word or Excel opens as a blank document or error 50002 or 112173

 

Tags: Open / Close / Save As, Integration - AutoCAD, error message, ProjectWise Explorer Client, SELECTsupport, SELECTsuppoError Message
Viewing all 1890 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>