For versions prior to promis.e V8i SELECTseries 5 (08.11.10.xx), please see [[5724|Creating and Updating the promis.e Project Database thru V8i SS3]]

Background

promis.e has used a database to store project related information for the last several versions. Starting with promis.e 2007 and continuing with promis.e V8i and Bentley Substation V8i, the project database is a SQL database instead of an Access database, and a project database file is no longer created in each project folder. Instead, one project database now stores information for several projects.

The term the software will be used in this article to mean the promis.e and Bentley Substation software.

SQL Server Express can be installed from the main promis.e installation dialog (see Figure 1) or from a download from Microsoft (see [[Installing SQL Server]]).  When a local BENTLEYECAD instance of SQL Server is detected when promis.e is first run after installation, the software will attempt to create a project database.  This article describes alternate ways of creating and updating the project database.

Note: Each version of the software has its own corresponding database schema and "version" number property.  When creating or updating the project database with any of the methods in this article, be sure the source material will create or update the database with the correct version number. For example, using a script from the program folder of the software version x will not necessarily create/update the database to a version compatible with the software version y. If the database is created/updated from different media than the version of the software being used, a "Database version does not match the application" message will display when trying to connect to the database in the software. If the media is older, the database schema will then have to be updated. If the media is newer, the software will need to be updated.

If you were last using a version of promis.e 2007 older than v3.0.x, the project database cannot be updated to be compatible with promis.e V8i. Backup files of the projects must be made in the older software using [[Backup Project]]. The resulting .PRJ backup files can then be restored into promis.e V8i connected to a new promis.e V8i-compatible project database.

The "Executing a Script" methods are recommended when the project database is hosted by SQL Server running on a different machine than the workstation.

Create the Database Method 1: Project Database Utility

Create the Database Method 2:  Executing a Script

Update the Database Method 1: Project Database Utility

Update the Database Method 2: Executing a Script

SQL Server must already be installed

The methods described in this article assume that a compatible SQL Server is already installed and running.

A version of SQL Server is included with the promis.e installation and recent versions of Bentley Substation.  Beginning with promis.e V8i SELECTseries 5, it will not be installed during promis.e installation but must be installed separately from the main installation screen:

Figure 1

Installing SQL Server from the promis.e installation file or CD will install SQL Server Express with an instance name of "BENTLEYECAD".  The installation wizard must be run on the machine on which SQL Server is to be installed.  If it is run on the workstation, it will be installed on the workstation and not a different machine such as a network server.

SQL Server can also be downloaded from Microsoft and installed independently of the software.  See [[Installing SQL Server]] for more information.

Creating a Project Database

The methods below will not install SQL Server or create or rename an instance  Instances are created by (re)installing SQL Server Express and specifying a new instance name.  So if creating the database on an existing SQL Server Express that was not installed via the promis.e installation files, the instance name may be different, such as the default instance of "SQLEXPRESS".   Non-Express versions of SQL Server may not use instances.

After a new project database is created with any of the methods below, the Project Database area of the software's [[Setup]] dialog must match the server name and database name in order to connect to the new database. When using Method 1, this is done automatically.  Multiple setup configurations can be created for easily switching between different project databases and other settings.

Create the Database Method 1: Project Database Utility

To create databases on a machine other than the workstation, the Execute a Script method typically works better.

Included with the software is a Project Database Utility that can be used to create the project database.  The utility runs the SqlServerProject.sql script and allows various settings to be adjusted without requiring the script be manually modified as in Method 2.

Note:  This method only creates a project database.  SQL Server must already be installed and running.

On the workstation, open the software's [[Setup]] dialog and click the Create New Database button.

Click Yes to the "Are you sure you want to create a new blank project database?" prompt.

The Project Database Utility dialog will appear. Select the Create Project Database tab.

Server Name 

The server name format is MACHINENAME\INSTANCENAME. If creating a database on the local workstation, "(local)" can be substituted for the machine name.  For non-Express versions of SQL Server there will be no backslash and no instance name.

If the server name or instance name entered for "Server Name" is incorrect (does not exist) an error message like the following will be displayed:

Please check SQL Server connection setting.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

The SQL Server Configuration Manager can be used to determine the names of existing SQL Server instances. On the machine where the SQL Server that is to host the database is installed, run this program by selecting Start > All Programs > Microsoft SQL Server 2008 R2* > Configuration Tools > SQL Server Configuration Manager. Then click on Services in the left pane of the SQL Server Configuration Manager and note the instance name(s) listed in the right pane. For example a service called "SQL Server (BENTLEYECAD)" indicates that there is an instance named BENTLEYECAD installed.

* name depends on SQL version

Authentication

A login with administrator privileges must be used when attempting to create a database, whether Windows or SQL Server authentication is selected.

Windows Authentication - When this option is enabled the utility will try to connect to the SQL Server using the credentials of the Windows user account in which the utiltiy is currently running.  If the current Windows account was used to install SQL Server, then Windows Authentication is likely to work.  Otherwise, the current Windows account would have had to have been added as a SQL Server Administrator on the Database Engine Configuration step of [[Installing SQL Server|SQL Server installation]] or afterwards with SQL Server management software.

Server Authentication - To use this option the SA password must be known.  With this option, a more general SQL login can be created for the users with the Username and Password fields on the Project Database Utility dialog.

SA password

This password is specified during [[Installing SQL Server|SQL Server installation]] and is not required when using Windows Authentication.

Database Name

As configured in the screen shot of the Project Database Utility dialog above, the utility would create a database named "promise" attached to the BENTLEYECAD instance of the local SQL Express Server.  If a "promise" database already exists on the server, use a different name such as "promise1".  The standard name for a project database for Bentley Substation is "Substation".  See [[Rules for Regular Identifiers]] regarding acceptable database names.

SQL Server Management Studio (including Express) can be used to verify the names of existing databases. The figure below shows a database named "promise" in the Object Explorer window of SQL Server Management Studio Express.

Datafile Path

On the Project Database Utility dialog, the Datafile Path is where the database file and transaction log will be created. Once a valid server name is entered into the Server Name field, click the Query button to populate the Datafile Path field with the correct path. Alternatively, the [...] button can be used to browse for the desired folder.

A typical path for SQL Server 2014 with a BENTLEYECAD instance is

C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA

A typical path for SQL Server 2008 R2 with a BENTLEYECAD instance is

C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.BENTLEYECAD\MSSQL\DATA

Specifying the path to the promis.e [[5365|program folder]] or the [[5367|promis-e Data folder]] or the corresponding Substation folders for the Datafile Path field is not recommended since it would result in the loss of the database should the folder be deleted as part of a reinstallation process.

Username

To create a general SQL login to be used on the the software's [[Setup]] dialog, enter the desired name in this field.  For example, SQL Server installed via older versions of promis.e have historically used "ecaduser" for the SQL Login name.

This field is only available when the Server Authentication option is enabled.

Password

Specify a password to be used with the login/username that will be created if using Server Authentication.

Confirm Password

Enter the same password as entered into the Password field.

Test Connection button

After configuring the parameters on the Create Project Database tab, click the Test Connection button.  If the utility determines the parameters on the dialog are acceptable, a confirmation message is displayed in the message window and the Execute Script button will become available.  Otherwise, see the message display area for reasons why the test failed.

Execute Script button

Click the Execute Script button to create the database.  A separate command window will open as the database is created. When this window closes itself, click the Close button on the Project Database Utility to return to the software's Setup dialog, which will be populated with the newly created database name and other associated settings.

Create the Database Method 2:  Executing a Script

The project database can also be created by modifying and executing the SqlServerProject.sql script using SQL Server Management Studio, sqlcmd, or the osql utility. For an Oracle database the script is OracleProject.sql. When the database is to be created on a machine other than the workstation, the script can be can be copied to the server machine from the workstation that has promis.e/Bentley Substation installed, then executed by the database administrator.

For this example, the script will be executed using SQL Server Management Studio, which is normally installed when SQL Server 2008 R2 is installed via the promis.e or Bentley Substation package, unless the Management Tools feature was declined during installation. [[Install SQL Server Management Studio|SQL Server Management Studio will need to be downloaded from Microsoft and installed separately]] when SQL Server 2014 is provided with the promis.e/Bentley Substation package.

Note: This method only creates a project database. SQL Server must already be installed and running.  

The script can be found in the [[5365|promis.e program folder]] and in the [[7613|Substation program folder]] on the workstation that has promis.e/Bentley Substation installed.  If the file cannot be found, perform a search.  Make a backup copy of the script before modifying it.

1. Navigate to the script file in Windows Explorer and double click it.  On machines where SQL Server Management Studio is installed, double clicking on a .sql file will open it in SQL Server Management Studio. 

2. When the Connect To Database window appears, enter the name of the server machine and instance where the database to be updated resides in the format MACHINENAME\INSTANCENAME.  Consulting the Project Database tab of the software's [[Setup]] dialog may help determine what should be entered here.  Select the appropriate Authentication method, then click Connect.
   
   Refer to the script excerpt shown in the Script Excerpt section below.  The excerpt shows how the script would look for creating a database named "promise1" with paths typical of a SQL Server 2008 R2 Express installation with a BENTLEYECAD instance.

3. Remove the following line, which is highlighted in red in the script excerpt below.  This is related to preventing [[Disable Auto Shrink to avoid performance degradation|performance degradation]].

   ALTER DATABASE $ShortProductName$ SET AUTO_SHRINK ON
   
   Alternatively, change ON to OFF for that line. The line will already be set to OFF in recent versions.

4. Replace the instances of "$ShortProductName$" with the name of the database to be created.  See [[Rules for Regular Identifiers]] regarding acceptable database names. The text highlighted yellow shows where the database name must be inserted.  DO NOT USE FIND AND REPLACE to replace all instances of this text throughout the script or you will introduce an error by replacing too many instances of this text.  Only replace the ones indicated.

5. The "$ShortProductName$" value in the last line of the excerpt must be changed to promise for the promis.e software and Substation for the Bentley Substation software, regardless of the name of database, and it is case-sensitive.  The correct value for promis.e is shown highlighted in magenta in the excerpt below.

6. Modify the paths for the database and transaction log files to reflect the true path to be used.

   A typical path for SQL Server 2014 is

   C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.BENTLEYECAD\MSSQL\DATA

   A typical path for SQL Server 2008 R2 is

   C:\Program Files (x86)\Microsoft SQL Server\MSSQL10_50.BENTLEYECAD\MSSQL\DATA

   A typical path for SQL Server 2005 is

   C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

   The paths are highlighted in cyan in the script excerpt below but the correct paths may be different than shown.  The [[6619|Finding the SQL Data folder]] solution may be helpful.

   Note: Executing the script will not create any folders in the specified path.  All folders in the path must exist at the time the script is executed.

7. After making the necessary changes, click the Execute button.

After successfully executing the script in SQL Server Management Studio, the Messages pane should display many lines of "(1 row(s) affected)" with no errors.

Script Excerpt

use master
GO

CREATE DATABASE promise1
ON (NAME = N'promise1',FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.BENTLEYECAD\MSSQL\DATA\promise1.mdf',SIZE = 200,FILEGROWTH = 40%)
LOG ON (NAME = N'promise1_log',FILENAME = N'C:\Program Files\Microsoft SQL Server\MSSQL10_50.BENTLEYECAD\MSSQL\DATA\promise1_log.ldf',SIZE = 80,MAXSIZE = 200,FILEGROWTH = 20%)
GO

ALTER DATABASE $ShortProductName$ SET AUTO_SHRINK ON
GO

ALTER DATABASE promise1 SET RECOVERY SIMPLE
GO

use promise1
GO

ALTER DATABASE promise1 SET AUTO_CLOSE OFF
GO

SET QUOTED_IDENTIFIER ON
GO

--********************************************************************--
if exists (select * from master..sysdatabases WHERE name=N'promise1')
begin
CREATE TABLE Project (
    id int IDENTITY (1, 1) NOT NULL,
    name nvarchar(255) NOT NULL,
    anum nvarchar(255) NULL,
    templatename nvarchar(255) NULL,
    username nvarchar(50) NULL,
    date_create datetime NOT NULL,
    version nvarchar(255) NULL,
    prjpath nvarchar(255) NULL,
    guid nvarchar(50) NULL,
    ModifyTime datetime NULL,
    ConnectionBuildTime datetime NULL,
    isLock int NULL DEFAULT 0,
    refid int NULL,
    CONSTRAINT PK_Project PRIMARY KEY (id)
);

EXEC sp_addextendedproperty 'Version', '8.0.69', 'user', dbo, 'table', project;
EXEC sp_addextendedproperty 'ShortProductName', 'promise', 'user', dbo, 'table', project;

Updating a Project Database

Update the Database Method 1: Project Database Utility

To update a database attached to SQL Server running on a machine other than the workstation, the Execute a Script method typically works better.

When the Project Database tab of the software's [[Setup]] dialog is configured to connect to a project database that has a schema for an older version, the software will prompt to update the database.  If accepted, the Project Database Utility will open to the "Upgrade Project Database" tab.  Alternatively, it is possible to click the Create New Database button on the Setup dialog then select the Upgrade Project Database tab.

1. Set the "Server name" and "Database" name fields and the other parameters to the correct values for the project database. The information should usually be made to match what is seen on the [[Setup]] dialog when connected to the database; it may not be automatically configured correctly.

2. When the dialog is configured correctly, click the Upgrade Database button.

3. A prompt will appear to optionally backup the database.  Click Yes or No.  Consider electing to backup the database if current [[Backup Project|backups]] of the projects have not been made.

4. An "Are you sure you want to upgrade the database?" prompt will be displayed.  Click Yes to accept.

5. A separate command window will open as the database is updated. When this window closes itself, click the Close button on the Project Database Utility to return to the Setup dialog.

    

If the server name or instance name entered for "Server Name" in the front-end dialog is incorrect (does not exist) a message such as the following will appear in the message area:

Upgrade Error: A network related or instance-specific error occurred while establishing a connection to SQL Server.  The server was not found or was not accessible.  Verify that the instance name is correct and that SQL Server is configured to allow remote connections.

If the database specified in the Database field does not exist, a message such as the following will appear in the message area:

Upgrade Error: Cannot open database "database" requested by the login.  The login failed.

If the incorrect Login name or Password were entered, a message such as the following will appear in the message area:

Upgrade Error: Login failed for user 'login name specified'.  Please check MS-SQLServer Login info.

Update the Database Method 2: Executing a Script

Execute the SQL_UpdateDB.sql script using SQL Server Management Studio, or sqlcmd or the osql utility. For an Oracle database, the update script is ORA_UpdateDB.sql. When the database to be updated is attached to SQL Server running on a machine other than the workstation, the script can be can be copied to the server machine from the workstation that has promis.e/Bentley Substation installed, then executed by the database administrator.

When using this method to update a project database shared between multiple users, be sure the version of the promis.e or Substation software installed on the workstation being used matches the desired database version.

The script can be found in the [[5365|promis.e program folder]] and in the [[7613|Substation program folder]] on the workstation that has promis.e/Bentley Substation installed.  If the file cannot be found, perform a search.

The script can be can be copied to the server machine and executed by the database administrator.  For this example, the script will be executed using SQL Server Management Studio, which is normally installed when SQL Server 2008 is installed via the promis.e or Bentley Substation package, unless the Management Tools feature was declined during installation. [[Install SQL Server Management Studio|SQL Server Management Studio will need to be downloaded from Microsoft and installed separately]] when SQL Server 2014 is provided with the promis.e/Bentley Substation package.

1. Navigate to the script file in Windows Explorer and double click it.  On machines where SQL Server Management Studio is installed, double clicking on a .sql file will open it in SQL Server Management Studio.

2. When the Connect To Database window appears, enter the name of the server machine and instance where the database to be updated resides in the format MACHINENAME\INSTANCENAME.  Consulting the Project Database tab of the software's [[Setup]]dialog may help determine what should be entered here.  Select the appropriate Authentication method, then click Connect.

3. When the script opens, find the following line:

   use [$ShortProductName$]

   Change $ShortProductName$ to the name of the database to be updated.  For example, to update a database named "promise1", the line should be changed to the following:

   use [promise1]

4. Find the following line:

   EXEC sp_addextendedproperty 'ShortProductName', '$ShortProductName$', 'user', dbo, 'table', project;

   For the promis.e software, change $ShortProductName$ in that line to promiseregardless of the name of the database being updated:

   EXEC sp_addextendedproperty 'ShortProductName', 'promise', 'user', dbo, 'table', project;

   For Bentley Substation, change $ShortProductName$ in that line to Substationregardless of the name of the database being updated:

   EXEC sp_addextendedproperty 'ShortProductName', 'Substation', 'user', dbo, 'table', project;

5. Click the Execute button to execute the script.

After successfully executing the script in SQL Server Management Studio, the Messages pane should display many lines of "(1 row(s) affected)" with no errors.

See Also

[[Disable Auto Shrink to avoid performance degradation]]

[[Installing SQL Server]]

[[Install SQL Server Management Studio]]

[[6619|Finding the SQL Data folder]]

[[Rules for Regular Identifiers]]

[[5824|Creating an SQL Server Login]]

[[6255|Project Database Version - promis.e]]

[[6897|Project Database Version - Bentley Substation]]

Error or Warning Message

"The Ribbon does not have any tabs or panels currently loaded."

Steps To Resolve

1. In promis.e, type OPTIONS at the Command prompt. This will open the Options dialog.
2. In Options, select the Files tab, expand Support File Search Paths, and note the path. It should be something like:
   C:\Documents and Settings\(your login)\Application Data\Autodesk\AutoCAD 2009\R17.2\enu\Support
   or
   C:\Users\admin\AppData\Roaming\Autodesk\AutoCAD 2009\R17.2\enu\Support
3. Close promis.e.
4. Browse to the path noted using Windows Explorer.
5. Copy the acad.CUI file or acad.CUIX file located in that folder to another folder as a backup.
6. Start plain AutoCAD.
7. Type OPTIONS at the command line.
8. Select the Profiles tab, select the <> profile, and click Set Current. Delete the "promise" and "ECAD_CAD" profiles.
9. Close the Options dialog.
10. Type CUI at the command line. This will open the Customize User Interface dialog.
11. In the upper left pane on the Customize tab, right-click on "ACAD" at the very top of the tree and select Reset ACAD.CUI. Click Yes at the prompt. Click OK to exit the Customize User Interface dialog.
12. Start promis.e.

P/S: 42491

Problem Description

When trying to insert or modify a symbol, insert a macro, or assign a title block to a page, the item has a wrong or unexpected appearance. When used, the item may appear differently than the thumbnail preview indicated or the item may only seem to exist in a different catalog than expected. Or perhaps the family definition is different than expected, with different symbols or connection point texts used.

Explanation

This behavior occurs when the item exists in multiple catalogs.  When inserting or modifying a symbol, macro, or title block, the software searches the Catalog Paths list from top to bottom. It uses the first instance that matches the specified name and type (symbol, macro, or title block) that it finds.

Steps to Resolve

Option 1

Use [[Catalog Manager]] to find and delete unwanted duplicate items.

Option 2

Use [[Catalog Manager]] to rename one or more of the items so the same item name does not appear in multiple catalogs.

Option 3

Move the catalog containing the desired symbol definition to the top of the list on [[Setup]] > Catalog Paths.

Option 4

Use [[Catalog Manager]] to move the desired item to a catalog higher in the list according the order shown on [[Setup]] > Catalog Paths list.

For All Above Options

Once the conflict is resolved and the correct appearance occurs in new pages or projects, the item may need to be updated in problem projects or pages by using tools such as [[Update Symbol]], Replace Title Block, etc. to update the project/page with the correct definition of the item.

See Also

[[Symbol modifications not reflected in project]]

Keywords: TFS 4682, wrong, duplicate, appearance, graphics, old, incorrect, Create Symbol, Title Block Designer

P/S: 88673, 500000100089

Problem Description

Why are the changes I made to a symbol not appearing in my project?  An old or otherwise wrong version of the symbol appears when I insert the symbol.

Explanation

Changes to symbols are not automatically updated in projects in order to preserve the appearance of completed projects as they were designed. 

If a symbol is modified in [[Create Symbol]] while a project is open and the symbol has been used in that project, a prompt will appear with an option to update the symbol definition in the project.

Steps to Resolve

To update a project with a new symbol definition:

1. Open a page of the project with [[Project Manager]].

2. Select [[Update Symbol]].

3. Click the Get Symbol List button on the Update Symbol dialog.

4. Click OK to begin updating the symbols in the project.  Click the Help button on the Update Symbol dialog for details.

Note: For a schematic symbol inserted on a page that has a family assigned, the connection point text specified by the family will override the connection point text defined in the symbol.  To change the connection point text on a symbol in this situation, modify or create a new family and adjust the connection point text there.

Another possible cause of the "wrong" appearance when a symbol is inserted is that the symbol exists in more than one catalog listed in the Catalog Paths area of the [[Setup]] dialog or it also exists in a ProjectCatalog subfolder of the project's folder.  Regardless of which catalog the symbol is selected from, the software will insert the definition it finds first, and the search hierarchy is the "ProjectCatalog" folder (if present) followed by the Catalog Paths in the order they are listed.  In this case, remove the symbol from the extra paths, or change the order of Catalog Paths.

See Also

[[Error - Some connection point text is invalid]]

Error or Warning Message

While attempting to install the software from the downloaded file a "Not enough space on drive C:\ to extract this package" message is displayed and installation cannot continue. 

Explanation

In some cases, this message is false.  Try the options below in the order they are listed.

How to Avoid

Option 1

Ensure there is actually enough disk space to install the application.

Option 2

Reboot the computer on which the software is to be installed, then try installing again.

 Option 3

1. Use Windows Explorer to create a new folder in a convenient location.

2. Download and install 7-Zip (http://www.7-zip.org) if not already installed.

3. Open 7-Zip File Manager and browse to the downloaded .EXE installation file that gives the error message.

4. Right-click the .EXE file and select Open Inside.

5. Select all the files and folders and drag them to the new folder created in step 1.

6. In the new folder, find the setup.exe file and double-click it to install the software.

Background

The Mode Manager enables you to edit the text that appears in menus and dialogs for any given drawing mode. This includes menu selections and the labels for buttons and fields in the dialogs. New drawing modes can also be created using Mode Manager.

Background

Some organizations may set up a mechanism by which the setup.xml is distributed to all users in order to distribute a common setup configuration. Because each user’s machine will have a unique certificate installed by default, this mechanism will fail if passwords are stored in the file as is the case with SQL server authentication (as opposed to using Windows Authentication).

In order for SQL server authentication to work, the same certificate must be installed on each user’s machine, and the Setup.xml must be directed to use that certificate. This article describes how to obtain a certificate that can be installed on all machines.

Creating and distributing a security certificate is not necessary if using Windows Authentication on [[Setup]] or if the Setup.xml file is not going to be distributed.

Steps to Accomplish

Create the certificate

Makecert.exe is Microsoft’s tool for creating certificates. It is available through the Windows SDK.

To create a certificate that can be installed on multiple computers, follow this procedure:

1. Run makecert.exe to create the certificate and private key file (at the prompt, enter a password for the private key or click None)
   
   MakeCert -r -n “CN=ExampleCertificate” -a sha256 -sky exchange -sr LocalMachine –sv ExampleCertificate.pvk ExampleCertificate.cer
   
   
2. Run pvk2pfx.exe to create a .pfx file that can be imported into the certificate store. The .pfx file contains the certificate and private key.
   
   pvk2pfx -pvk ExampleCertificate.pvk -spc ExampleCertificate.cer -pfx ExampleCertificate.pfx

Install the Certificate

Install the .pfx file in the certificate store using the Microsoft Management Console plugin.

1. Launch the Microsoft Management Console. Select Start > Run and enter mmc.exe.
2. Select File > Add/Remove Snap-in
3. Select Certificates from the available snap-ins and click the Add button.
4. Select the Computer account option and click Next.
5. Select the Local computer option and click Finish.
6. Click OK on the Add or Remove Snap-ins dialog.
7. On the Console dialog, expand Console Root > Trusted Root Certification Authorities > Certificates.
8. Right-click Certificates and select All Tasks > Import.
9. Click Next on the Certificate Import Wizard.
10. Click Browse and select the .pfx file created in the previous procedure.
11. Continue through the wizard to complete the import. Make sure the check box named “Mark this key as exportable. This will allow you to back up or transport your keys at a later time.” is not set. You don’t want users to be able to export the private key, and you already have the .pfx file.
12. Back on the Console dialog with Console Root > Trusted Root Certification Authorities > Certificates highlighted, find the imported certificate. Right-click it and select Open.
13. Select the Details tabon the resulting Certificate dialog.
14. Select the Thumbprint field in the top pane.
15. Select the contents of the bottom pane and press CTRL+C to copy it to the clipboard.

Set Setup.xml to use the certificate

1. Open Setup.xml in a text editor such as Notepad. Setup.xml is located in the following path:

   [ [[5366|promis.e program data]] ]\Config\Setup.xml

   [ [[Program data folder - Substation|Substation program data]] ]\Config\Setup.xml

2. Paste the Thumbprint value copied in the previous section over the Thumbprint value in the Setup.xml file. This value is highlighted below. The spaces in the pasted value can be removed, but this is not necessary.
   
   <Configuration using="ANSI-IEEE Default">
     <Log Enable="false" Prefix="@" Postfix="@" />
     <OEM Feature="0" />
     <Certificate thumbprint="D07B60E49E688709ED73D21D90A747519DBBBF5A" />
     <Config name="ANSI-IEEE Default">
   
   
3. Save the Setup.xml file.
4. Confirm that the configuration works by starting the software, opening the [[Setup]] dialog, using SQL server authentication, and clicking the Apply button. If the dialog says "Configuration saved" it is working.

Distribute the certificate and Setup.xml

1. Install the certificate on each workstation by copying the .pfx file to the workstation and following steps 1 - 11 of the Install the Certificate procedure above.
2. Rename the Setup.xml file on the workstation to Original_Setup.xml.  Setup.xml is located in the following path:

   [ [[5366|promis.e program data]] ]\Config\Setup.xml

   [ [[Program data folder - Substation|Substation program data]] ]\Config\Setup.xml

3. Copy the Setup.xml file configured in the Set Setup.xml to use the certificate procedure above to the \Config folder of the workstation (where Original_Setup.xml resides).

See Also

[[Distributing the Setup configuration]]

[[Network Installation Guide]]

Background

Once a workstation is configured to use data on the network, it is often desired to configure other workstations the same way. Besides manually configuring the [[Setup]] dialog on each workstation to be set the same, the Setup.xml file can be copied to the other workstations. This will transfer all the settings on the Setup dialog on the configured workstation to the destination workstation(s).

The Setup.xml file is found in the following path:

[ [[5366|promis.e program data]] ]\Config\Setup.xml

[ [[Program data folder - Substation|Substation program data]] ]\Config\Setup.xml

Steps to Accomplish

V8i SELECTseries 8

Starting with the V8i SELECTseries 8 releases of promis.e and Bentley Substation, the password security for the SQL Authentication on the Setup dialog was improved and uses a security certificate for encryption. Upon installation of promis.e / Bentley Substation, a unique certificate is installed on the workstation. While this improves security, it prevents the simple distribution of the Setup.xml file to other workstations from working. This is because the Setup.xml file identifies the security certificate the software should use by its thumbprint, and each workstation will have a unique certificate with a unique thumbprint installed. Below are the options for maintaining the improved security while distributing a common configuration.

Option 1 - Install a common security certificate

1. Create a security certificate and install this same certificate on each workstation.
2. On one workstation:
   1. Configure promis.e / Bentley Subststation to use the security certificate to encrypt the password
   2. Configure the [[Setup]] dialog to use the desired resources.
3. Distribute the Setup.xml file to the other workstations. Rename or backup the original Setup.xml file on the destination workstations before distributing the configured Setup.xml file in case the as-installed configuration needs to be restored.

See the [[Create a Security Certificate for Password Encryption]] article for steps 1 and 2.

Option 2 - Use Windows Authentication

The security certificate is only used when SQL server authentication is used on [[Setup]]. If Windows authentication is used, the Setup.xml file can be distributed to other workstations without needing to create and install a common security certificate. SQL Server tools must be used to configure each user's Windows login in SQL Server or else the user will not be able to connect.

Option 3 - Copy and paste setup.xml contents

To avoid the need to create a common security certificate while using SQL server authentication, the security certificate unique to each workstation could be used. This would entail combining the as-installed Setup.xml file of the destination workstation with the Setup.xml file configured as desired and ready to be distributed. The thumbprint value for the certificate on the destination workstation would need to be preserved with this method.

1. Rename the Setup.xml file of the destination workstation to Original_Setup.xml.
2. Copy the configured Setup.xml file to the \Config folder of the workstation (where Original_Setup.xml resides).
3. Open the Original_Setup.xml file on the destination workstation using a text editor such as Notepad.
4. Copy the "Certificate thumbprint" line to the clipboard. This line is highlighted below.
   
   <Configuration using="ANSI-IEEE Default">
     <Log Enable="false" Prefix="@" Postfix="@" />
     <OEM Feature="0" />
     <Certificate thumbprint="D07B60E49E688709ED73D21D90A747519DBBBF5A" />
     <Config name="ANSI-IEEE Default">
   
   
5. Open the configured Setup.xml file on the destination workstation in a text editor such as Notepad.
6. Paste the copied line over the "Certificate thumbprint" line in the configured Setup.xml.
7. Save the Setup.xml file.

Option 4 - Manually configure each workstation

The setup configuration can be distributed by simply setting the settings on the [[Setup]] dialog on each workstation.

through V8i SELECTseries 7

In versions prior to V8i SELECTseries 8 (08.11.13.xx), the configured Setup.xml can be distributed by copying it to the other workstations.

1. Rename or backup the original Setup.xml file on the destination workstations before distributing the configured Setup.xml file in case the as-installed configuration needs to be restored.
2. Copy the Setup.xml file from a configured workstation to the same folder on the workstations to be configured.

See Also

[[Network Installation Guide]]

[[Create a Security Certificate for Password Encryption]]

For versions of promis.e prior to promis.e V8i SELECTseries 5, please see [[Network Installation Guide ARCHIVE]]

Background

This installation guide contains the information necessary to perform a basic "network" installation of promis.e or Bentley Substation for the purpose of sharing data between users.  For the remainder of this document "the software" will refer to promis.e and Bentley Substation.

A basic network installation typically involves sharing the following on a network:

• The project database
• Project folders containing project drawing files
• Symbol catalogs
• Parts and language databases
• Report and page templates
• Options profiles

Some or all of the above items can be shared. This guide will outline the process for sharing all of the above items. Note that to share projects, not only the project folders but also the project database must be shared.

By nature, sharing data over the network can result in some performance degradation.  promis.e and Bentley Substation require a maintained 35 megabits per second transfer rate.  What is actually achieved by the network is not the same as the equipment ratings of the network components.  Failure to maintain a transfer rate 35 megabits per second will be noticeable by the users and performance will likely be considered unacceptable.

A basic outline of the network installation process would be:

1. Install promis.e/Bentley Substation on at least one workstation.
2. Install SQL Server on a server machine and create the project database.
3. Copy the [[5367|promis-e Data folder]] or [[Substation Data folder]] to a shared location.
4. Setup the workstations to use the shared data.

This document is intended for users/companies that have limited IT resources or do not have Database Administrators (DBAs). As a result, advanced security settings and alternative database servers are not discussed.

Definition of Terms Used

The following definitions are used throughout this document:

project database: The database that contains project related data as well as some system related data. This database is a SQL database and is attached to a SQL Server. A connection to a project database must exist to create or open projects. This connection is managed on the [[Setup]] dialog.

installation file: The file that, when run, has options to view the Installation Guide, install the software, and install SQL Server software. Visit http://selectservices.bentley.com, to download this file or request a CD.

Server: The computer that is used to store shared data. Consult the SQL software documentation for system requirements.  System requirements for SQL Server 2008 R2 Express can be found here: http://msdn.microsoft.com/en-us/library/ms143506.aspx

SSMS: SQL Server Management Studio. This is an optional program that can be used to explore and manage SQL databases.  With SQL Server 2008, this program will be installed during SQL Server installation if the "Management Tools" feature is selected (see also [[Installing SQL Server]]).  With SQL Server 2005 Express, this program is called SQL Server Management Studio Express and is installed separately.

Installing the software

Install promis.e/Bentley Substation on at least one workstation. See the Installation Guide (available on the installation menu) for details. 

SQL Server can also be installed on the workstation from the installation file or CD.

• Choose to install SQL Server on the workstation if that computer is not always connected to the company's network SQL Server.  This will enable you to use a local SQL Server and database while working with the software while away from the network.

• SQL Server does not need to be installed on the workstation if that computer will always be connected to the company's internal network SQL Server.

If using promis.e for AutoCAD, a compatible version of AutoCAD must also be installed on the workstation.  See

Server Setup

promis.e/Bentley Substation is not typically installed on the server.  The server(s) only hosts the shared data.

Installing SQL Server

Since the software is designed to work with a SQL database, a compatible SQL Server must be available. For this purpose, Microsoft SQL Server Express is included in the installation file.

The installation media should be copied to or made available to the machine that will be the SQL Server.  For a network install, this is typically a server machine and not a workstation. SQL Server installation is then run on the server machine.  See [[Installing SQL Server]] and [[Creating and Updating the Project Database]] for more details.

If your company is already running a compatible version of SQL Server, you may opt to use that as your database server.  Alternately, the software can be configured to function on a compatible Oracle database. See [[Compatibility Chart - promis.e]] and [[Compatibility Chart - Bentley Substation]].

Important: Specify and make note of the SA password during SQL Server installation.

Create the project database

This process is discussed in the [[Creating and Updating the Project Database]] article.

To move existing projects created with a local setup configuration to the network, see the [[Moving Projects]] article.

Adding users and changing permissions of the project database

In versions earlier than promis.e V8i SELECTseries 5, an SQL login was automatically created when the database was created. This login had a username of ecaduser and a password of Ecad1pass. In many situations it will be acceptable for all promis.e users to use this default database login. If the user is creating this database on a server that hosted a promis.e 2007 version 2.0 database it is possible that the password may be ecadpassword.

For additional security, this account may be disabled and additional users may be manually assigned to the database. However, we recommend that this be done by qualified personnel familiar with SQL and Windows security to avoid problems.

Beginning with promis.e/Bentley Substation V8i SELECTseries 5, the script used to create the database does not create a SQL Server login.  A SQL Server login can be created when the database is created using the Project Database Utility.  A SQL Server login can also be created and associated with an existing database.  See [[Creating an SQL Server Login]] for details.

A database administrator can also add the Windows accounts of users to the SQL Server in order to allow users to connect using Windows Authentication.

Setting up the directory structure

Besides sharing the project database, many users will wish to share other data across a network. The most commonly shared data are: the project drawing files, the parts and language databases, various configuration files, and the report templates.

For the purposes of this guide, it is assumed that the software has been installed on at least one workstation prior to the next step and that the user wishes to share all possible data.

Copy the "[[5367|promis-e Data folder]]" or "[[Substation Data folder]] from the workstation to the shared location on the server. Refer to the System Paths area of the [[Setup]] dialog to find the location of the Data folder on the workstation.

The resulting folder should have the following structure. Substitute "Substation Data" for "promis-e Data" if using Bentley Substation.

Workstation Setup

Creating Setup Configurations

Multiple setup configurations can be created to facilitate switching between different settings. Setup configurations store all of the settings on the Setup dialog.   A  local setup configuration can be created for use when working while disconnected from the company network, and a "Network" configuration can be used when working while connected.

After starting the software, click the Setup link on the Welcome dialog:

[[Setup|The Setup dialog can also be accessed via menu selections]].

Setup Configuration

Setup configurations can be created and deleted in the top portion of the dialog.

By default, the software creates the "ANSI-IEEE Default" and "IEC Default" setup configurations during installation.  In these setup configurations, the paths are based on the data folder path specified during installation.  The default paths during installation point to folders on the local workstation.

The default configurations can be used as a basis for a new network configuration. Choose the appropriate configuration for the drawing standard used (ANSI-IEEE or IEC) as the basis for the new configuration.

To create a "network" configuration, click the New button, type in a configuration name of "Net" and click OK.

Notice that the settings from the local configuration were transferred to the new configuration. Any changes made will take place only in the active configuration.

Confirm that "Net" is displayed in the Setup Configuration box.

Project Database

The software requires a Microsoft SQL or Oracle database to store various project related information. The Project Database area of the [[Setup]] dialog tells the software where to find this database and how to connect to it.

The format of the Server Name field is:

MACHINENAME\INSTANCE

with a backslash separating the machine name and instance name with no spaces.

For new installations of promis.e and Bentley Substation V8i, the instance name would be "BENTLEYECAD".  If SQL Server was installed via older versions of promis.e, the instance name may be "ECTECAD".

Note: when connecting to full versions of SQL Server (not Express) there may be no instance name, in which case the Server Name field should only contain the machine name of the server.

Change the Server Name field to match the server and instance to be used.

To use Windows authentication, the Windows login for each user must be added to the SQL Server by the database administrator.

An easier method is usually to use SQL Server Authentication and have all users use the same SQL login.

If upgrading from an earlier version of promis.e V8i or promis.e 2007, a SQL login name of ecaduser with a password of either Ecad1pass or ecadpassword may exist.

If the SQL Server is new for promis.e V8i SELECTseries 5 or otherwise not previously used for promis.e, a SQL login may need to be created as discussed in the "Adding users and changing permissions of the project database" section.

System Paths

The software uses various paths to store configuration files. There are two options available for managing System paths: Manage Data Folder Path and Manage Individual Paths. For this basic network setup, the simpler method of Manage Data Folder Path is used. 

It is recommended that all users map a drive to the network Data folder using the same drive letter.   Each user should map the drive to the same exact path.  For the remainder of this article, the

\\<server name>\<subfolder>\promis-e Data

location will be referred to as drive "P".

Note: Mapped drives are preferred over use of UNC paths in the Setup dialog.  In earlier versions of the software, use of UNC paths were known to cause problems.

After mapping the "P" drive to the network "promis-e Data" folder, specify "P:\" for the Data Folder Path field on the System Paths tab of the Setup dialog.

Parts Database

The software can connect to a parts database in two main ways: it can use a connection string to connect to various databases or database servers, or it can use an MS Access database file (.mdb). This example uses an Access database file for the parts database.

Locate the Parts Database Path label on the System Paths tab of the Setup dialog.

The ansi-ieee_parts_database item is a mapping to the local parts database. A new path to the parts database file on the network must be created.

To add a new parts database path, click the New button next to the Parts Database Path field. The following dialog will appear.

In the Parts Database Name field enter: Network

In the Use File field, select the Browse button and navigate to:
P:\Databases\ANSI-IEEE_database.mdb

The Table and SQL Query options should now be available. Select the Table option and then parts_database from the drop down box.

Click Next. The follow dialog should appear:

If the last three columns are blank, click the Default Mapping button.

Once this is completed, click the Finish button.

The main Setup dialog should reappear.

Using the drop down box next to Parts Database Path, select the newly created "Network" path to make it the active path.

Catalog Paths

The final item(s) that must be configured is the symbol catalog(s). Select the Catalog Paths tab of the Setup dialog.

Select existing paths to local catalog folders then click the X button to remove the paths.

Click the + button to [[Add Catalog Path|add a new catalog path]]. Click the [...] to browse to the network catalog. For this example it is P:\Catalogs\ANSI-IEEE. Then click OK.

The network catalog path should now appear in the bottom window. 

Click OK to exit the Setup dialog.

The software should now be configured to work on a network.

To switch between the "Net" and a local setup configuration, simply choose the desired configuration from the Setup Configuration drop down box.

Note: Setting up "network" and "local" configurations does not synchronize the data between the two. To synchronize, modified files must be copied from one Data folder to the other. To transfer projects from one project database to another, use File > Backup in Project Manager to create a backup of the project while connected to the source database, then use File > Restore in Project Manager while connected to the destination database.

Setting Up Additional Workstations

Once a workstation is setup to use data on the network, the [[Setup]] dialog on the other workstations can be configured the same way. This can be done manually or the Setup.xml file can be copied to other workstations.  This will transfer all the settings on the [[Setup]] dialog on the configured workstation to the destination workstation(s).  See the [[Distributing the Setup configuration]] article for details and considerations about this procedure.

See Also

[[Distributing the Setup configuration]]

[[Compatibility Chart - promis.e]]

[[Compatibility Chart - Bentley Substation]]

[[Installing SQL Server]]

[[Creating and Updating the Project Database]] 

[[Moving Projects]]

[[4532|Troubleshooting Project Database Connection Problems]]

Error or Warning Message

when opening promis.e it may hangs up and goes not responding after few minutes and the project manager also not opens up.

Explanation

This type of behaviour may be seen because of the corrupted ECAD.DGN file which is available at C:\ProgramData\Bentley\promis-e V8i(M)\Config

How to Avoid

Option 1

Reboot te computer on which the software is installed and try again.

Option 2

1. Replace the ECAD.DGN file from any other computer in which promis.e works fine.

Make sure that while replacing the file promis.e must be closed.

See Also

Error at Startup - Promis.e Stopped Working

Error or Warning Message

If Following error appears at promis.e Start-up.

"Promis.e stopped working"  A software error has occurred. we apologize for any inconvenience this may have caused. This error has been logged locally.

Explanation:

This error might be occurred because of a sudden shut-down of promis.e or because of some unwanted changes done in the previous session.

How to Avoid

Option 1

Reboot the computer on which the software is installed and try again.

Option 2

Delete the temporary project options(.xml) file which is located in “C:\Users\user\AppData\Roaming\Bentley\promis-e V8i(M)”.  

Also delete the temporary files located in “C:\Users\User\AppData\Local\Temp”. 

Overview

Each version of Bentley Substation has its own corresponding project database schema, identified by a version number. The version number of the database is stored as an extended property of the Project table in SQL Server databases and as a comment on the Project table for Oracle databases.

When connecting to the project database, if the "Version" property/comment of the database does not match what Substation expects or cannot be retrieved for some reason, a [[Error - Database version does not match the application|Database version does not match the application]] message will appear.  Generally this means that either the Substation application or the database schema needs to be updated, whichever is older.

Database version numbers can also be revealed in a prompt when restoring a project from a different version of Substation.  In this case, when the current project database version is newer than the database version for the backup listed in the message, the message is purely informational and no action is necessary.  If the database version of the backup is newer than the application, the backup cannot be restored and the message typically indicates this ([[Error - Unable to restore project, project's database version is newer|Unable to restore project because the project's database version is newer than your current database version]]).

The purpose of this document is to help determine the proper course of action, if any is necessary.

Version Chart

This chart applies to SELECT releases of Bentley Substation.

Determining the application version

The installed version of Bentley Substation (Application Version in the chart) can be found on the About Bentley Substation V8i dialog.

Determining the database version

The current database version can be determined by connecting to the SQL Server using SQL Server Management Studio (SSMS) and checking the extended properties of the Project table in the database used by Substation.  In SSMS, expand Object Explorer > Databases > Substation* > Tables, right click dbo.Project, and select Properties > Extended Properties.

Alternatively, executing the following query will also return the database version.

use Substation
SELECT * FROMfn_listextendedproperty ('Version', 'user', 'dbo', 'table', 'project', default, default)

Replace "Substation" in the above query with the name of the database is not "Substation".

Additional Notes

• "SS" in the above chart stands for SELECTseries.

• The version of the database that will be created by a script file can typically be found as a comment near the beginning of the script.  For example:
  --$DBVersion:8.1.33$-- 
  Similarly, an update script will list the version to which the script will update the database.

• The SQL Server and database used by Bentley Substation can be determined by looking in the Project Database area of the Substation [[Setup]]dialog.

See Also

[[How to download the Bentley Substation software]]

[[Creating and Updating the Project Database]]

[[Error - Database version does not match the application]]

[[Error - Unable to restore project, project's database version is newer]]

Problem Description

While trying to place a symbol by part number following message is displayed "There is no symbol associated with this part number to place" on trying to place a part.

Background

The symbols that are associated with a part number might not be compatible with certain drawing modes , when effort is made to insert such symbols using insert symbol by part number then the above message is displayed to the user.

How to Avoid

Make sure that the "Only parts with symbol for current drawing mode" checkbox is ticked (see below screenshot) , When ticked, it will only show parts that have a symbol specified for the current drawing mode.

How do I bring up the Tutorial if I have closed the Welcome Screen and told promis.e to always start with the Project Manager, so that the Welcome Screen no longer appears?

Steps to Accomplish

Option 1 - Open the Welcome dialog

In promis.e V8i Standalone and Bentley Substation V8i

select Help > Show Welcome Dialog

In promis.e V8i for AutoCAD

select promis-e|Help > Show Welcome Dialog

Option 2 - Open the PDF directly

Browse to and open the PDF file for the desired tutorial using PDF reader software. 

promis.e

The tutorials are found in a "Help" subfolder of the [[Program folder - promis.e|Program folder]].  A typical path is:

C:\Program Files (x86)\Bentley\promise V8i\promise\promise\help

The tutorial files are named

promis-e_ANSI-IEEE_tutorial.pdf

promis-e_IEC_tutorial.pdf

Substation

The tutorials are found in a "Help" subfolder of the [[Program Folder - Substation|Program folder]].  A typical path is:

C:\Program Files (x86)\Bentley\Substation V8i\Substation\Promise\help

The tutorial files are named

Substation_ANSI-IEEE_tutorial.pdf

Substation_IEC_tutorial.pdf

The purpose of this document is to indicate the compatibility of various software with Bentley Substation.  It is not intended to describe compatibility of the various software with each other.  For example, certain versions of SQL Server may not be compatible with certain operating systems.  Always check the documentation of the various software involved.

Beginning with Bentley Substation V8i SELECTseries 3, the MicroStation CAD engine is built into the Substation application.  There is no longer an "add-on" version available.

Consult the Bentley Substation Readme for details.  A link to the Readme document is available by clicking the product name in the search results list in the Fulfillment Center.   Links to the  Readme files for Bentley Substation V8i are also included in the See Also section below.

Important Notes:

• Bentley Substation V8i is a 32-bit application.  It is also compatible with 64-bit operating systems and will install as a 32-bit application in the "C:\Program Files (x86)" folder.

• Microsoft Office, specifically Microsoft Access, is not required to be installed to use Bentley Substation.

• For SQL Server

• Bentley Substation is currently only certified on English SQL Server versions, even for versions of Bentley Substation localized for other languages. The SQL_Latin1_General_CP1_CI_AS collation is recommended.

• For Oracle databases

• Install the 32-bit version of the Oracle client if using even if the operating system is 64-bit since Bentley Substation V8i is a 32-bit application.

• For Oracle 11g with Bentley Substation V8i SS6 and SS7, install the 11.2.0.2.0 Instant Client.  Installing the Oracle Universal Installer ODAC112021.zip is a convenient way to install this client and other the other requirements for Oracle with Bentley Substation V8i.

• For Oracle 11g with Bentley Substation V8i through SS5, install the 11.1.0.7.0 Instant Client.  Installing the Oracle Universal Installer ODAC1110720.zip is a convenient way to install this client and other the other requirements for Oracle with Bentley Substation V8i.

• Later releases of the Oracle 11g client such as 11.2.0.1.0 are not compatible with Bentley Substation SS2 through SS5.  Even though it is not certified for Windows 7, ODAC 11.1.0.7.20 will work in that operating system.

• For Bentley Substation V8i SELECTseries 4 - 7 and Oracle 10g server,  v10.2.0.4 or higher is compatible.

• ProjectWise integration

• Bentley Substation V8i SELECTseries 8 has been certified with ProjectWise CONNECT. Specific versions of ProjectWise CONNECT that are compatible with Bentley Substation are forthcoming.

• For integration with ProjectWise 08.11.07, ProjectWise Explorer 8.11.7.133 or higher is compatible.

• Integration with ProjectWise is not required.

• Bentley Substation V8i SELECTseries 6 is compatible with Bentley Descartes, version 08.11.09.263 and higher

See Also

[[Project Database Version - Substation]]

Readme for Bentley Substation V8i SELECTseries 8 (must be logged into Bentley Communities)

Readme for Bentley Substation V8i SELECTseries 7

Readme for Bentley Substation V8i SELECTseries 6

Readme for Bentley Substation V8i SELECTseries 5

Readme for Bentley Substation V8i SELECTseries 4

Readme for Bentley Substation V8i SELECTseries 3

Readme for Bentley Substation V8i SELECTseries 2

[[Compatibility Chart - promis.e]]

Bentley Raceway and Cable Management (BRCM) has an integrated MicroStation based drafting platform.  It does not run "on top of" separately installed MicroStation or AutoCAD applications.

Consult the BRCM Readme or datasheet for details.

Important Notes:

• BRCM is a 32-bit application. It is also compatible with 64-bit operating systems, where it will install in the "C:\Program Files (x86)" folder.

• Microsoft Excel must be installed to import cable and equipment information from spreadsheets.  Importing from .XLSX files is only possible when Excel 2010 or higher is installed.

• Integration with ProjectWise is not required.

• Bentley Raceway and Cable Management has been certified with ProjectWise CONNECT. Specific versions of ProjectWise CONNECT that are compatible with Bentley Raceway and Cable Management are forthcoming.

• For integration with ProjectWise 08.11.07, ProjectWise Explorer 8.11.7.133 or higher is compatible.

See Also

Readme for BRCM V8i SELECTseries 2

Readme for BRCM V8i SELECTseries 1

Datasheet for BRCM V8i

Problem Description

After selecting 3D Layout Design > Insert Cable/Bus Object, folders appear in the Part Tree pane but no part numbers are found or some are missing, even when the "All Parts" folder is selected in the Part Tree.

Reason

For part numbers to be available on the Insert Cable/Bus dialog, they must meet the filter settings.  Either the part numbers or the filter settings need to be adjusted.

Steps to Resolve

Bentley Substation V8i SELECTseries 8

The Part_Type value must be VAR for a part number to appear on Insert Cable/Bus dialog. [[Parts Database Manager]] can be used to modify the Part_Type value.

Bentley Substation V8i SELECTseries 7

1. The Part_Type value must be VAR for a part number to appear on Insert Cable/Bus dialog. [[Parts Database Manager]] can be used to modify the Part_Type value.
2. Select Manage > Admin Management > 3D Layout Settings to open the 3D Substation Layout dialog

3. Select the User Settings tab.

4. Find the "Cable/Bus Filter" node and note the values for FilterField and FilterWord.
   
   Only part numbers with the value specified in FilterWord contained in the field (column) specified in FilterField will appear on Insert Cable/Bus.  The default FilterField is Discipline and FilterWord is Cable, meaning that part numbers with "Cable", "cable", "Power Cable", etc. in the Discipline column in the parts database will appear on Insert Cable/Bus.

5. Add the appropriate values ("Cable") to the appropriate field ("Discipline") for each cable part number using [[Parts Database Manager]], and/or specify the desired values for FilterField and FilterWord on 3D Substation Layout.

See also

[[Quick Filtering in the Parts Database Manager]]

Select Manage > Admin Management > 3D Layout Settings to open the 3D Substation Layout dialog