BlueCielo Meridian Enterprise 2013 Release Notes (LTR)

BlueCielo Meridian Enterprise 2013

Release Notes Reference

BlueCielo ECM Solutionswww.bluecieloecm.comThursday, June 27, 2013

BlueCielo Meridian Enterprise 2013 Release Notes | BlueCielo ECMSolutions

i

Legal Not ice

©2013 BlueCielo ECM Solutions B. V.Handelskade 492288 BA RijswijkThe Netherlands

All rights reserved. The names BlueCielo® and InnoCielo® are registered in the U.S. Patent and TrademarkOffice and inmany countries around the world by BlueCielo ECM Solutions Holding B.V. All other brand namesand product names mentioned in this document are trademarks or registered trademarks of their respectiveowners.

The information contained in this document is subject to change without notice. This publication or partsthereof may only be reproduced if its source is explicitly mentioned. BlueCielo ECM Solutions makes no war-ranty of any kind with regard to this material, including, but not limited to, the implied warranties of mer-chantability and fitness for a particular purpose. BlueCielo ECM Solutions, or any of its subsidiaries, shall not beliable for errors contained herein or for incidental or consequential damages in connection with the furnishing,performance, or use of this material.


ii

Contents

Legal Notice i

Contents ii

1 Introducing Meridian Enterprise 2013 1

1.1 What's in this guide 1

1.2 Who should read this guide 2

1.3 Understanding the typographic conventions 2

1.4 Getting technical support 3

2 What's New in Meridian 2013 5

2.1 Deeper Asset Management Module integration 5

2.2 License changes 5

2.3 Shared workspaces 6

2.4 Administration improvements 7

2.5 Application link improvements 7

2.6 Client improvements 9

2.7 Configuration improvements 10

2.8 Customization improvements 11

2.9 Setup improvements 13

2.10 Viewer improvements 13

2.11 Web Access improvements 14

3 What's New in Meridian Enterprise 2012 SP3 15






4.2 CAD application support improvements 17



iii



4.6 Documentation improvements 19









5.7 Documentation improvements 24

5.8 Managed Change improvements 24

5.9 Setup improvements 24


5.11 Web Access improvements 25

6 What's new in Meridian Enterprise 2012 27

6.1 Document renditions 27

6.2 HyperCache 28

6.3 Notifications and subscriptions 28

6.4 Certified for Windows Server 2008 R2 29

6.5 Changes and improvements 29

6.5.1 Administration improvements 29

6.5.2 Application link improvements 30

6.5.3 CAD application support improvements 31

6.5.4 Client application improvements 32

6.5.5 Configuration improvements 33

6.5.6 Customization improvements 34


iv

6.5.7 Documentation improvements 35

6.5.8 Document Import Tool improvements 37

6.5.9 Setup improvements 37

6.5.10 Viewer improvements 38

6.5.11 Web Access Improvements 39

6.5.12 Web Parts improvements 40




7.3 Choosing which client version to install, 32-bit or 64-bit 41



7.6 Managed Change improvements 45


8 What's New in Meridian Enterprise 2011 46

8.1 64-bit support 46




8.2.3 Client improvements 47



8.2.6 Operating system support improvements 49

8.2.7 Web Access improvements 50

9 What's New in Meridian Enterprise 2010 51

9.1 Emphasis on usability 51

9.2 Data Library 51

9.3 Scopes 51


v

9.4 Search enhancements 52


9.5.1 Administration improvements 52



9.5.4 Client improvements 54



9.5.7 Operating system support improvements 57

9.5.8 Transmittal Management Module improvements 58

9.5.9 Viewing improvements 58

10 Known Problems 59

10.1 Application Links 59

10.1.1 Cannot save MSWord 2010 documents 59

10.1.2 AutoCAD P&ID limitations 59

10.1.3 SolidWorks references not created after drag-rand-drop 59

10.1.4 Meridian Enterprise Replace in Inventor 59

10.1.5 Synchronizing Sheet Set Properties and References 59

10.1.6 Viewing AutoCAD drawings in Application Integration 60

10.1.7 Autodesk Inventor remains inmemory after titleblock update 60

10.1.8 File error when synchronizing Inventor references 60

10.2 Client Functionality 60

10.2.1 Jagged icons 60

10.2.2 Opening the shortcut menu on a folder 60

10.2.3 Opening MSOffice 2007 templates on Vista 60

10.2.4 Building reports with MSWord templates on Vista 61

10.2.5 Opening HTML files on Vista 61

10.2.6 Unsupported features of 64-bit clients 61


vi

10.2.7 Semicolon in folder names 61

10.2.8 Windows XP Service Pack 2 and unsigned extensions 61

10.2.9 Opening AutoCAD assemblies after import 62

10.3 Customization 62

10.3.1 Recompiled extensions are not backward compatible 62

10.3.2 Empty drop-down lists for properties in the Field-Path definition 62

10.4 Server Functionality 63

10.4.1 Meridian Administrator empty and unresponsive 63

10.4.2 Vault incompatibility betweenWindows operating system versions 63

10.4.3 Content indexing vaults with non-Western character names 64

10.4.4 Revision number cut off 64

10.4.5 Some privileges do not work in workflow definition states 64

10.5 Setup 65

10.5.1 AMFS not certified by Microsoft 65

10.5.2 File informationmissing 65

10.5.3 Unsigned executables 66

10.5.4 AutoVue setup 72

10.5.5 AMFS andWindows Search incompatible on 64-bit servers 72

10.5.6 Cannot register Asset Management Module 2010 extensions in 64-bit Configurator 72

10.5.7 Vaults unavailable after installing Meridian Enterprise 64-bit edition 72

10.5.8 Meridian Enterprise 64-bit setup workarounds 73

10.5.9 Windows Installer Package setup incompatible with executable setup 73

10.5.10 Windows Vista setup 73

10.5.10.1 Vault incompatibility 74

10.5.10.2 Visual C++ runtime files required 74

10.5.10.3 Modify option of 32-bit setups 74

10.5.10.4 Web Access extension installation with IIS 7 74

10.5.10.5 Content indexing 75


vii

10.5.10.6 64-bit support 75

10.5.11 Windows Server 2008 setup 75

10.5.11.1 Vault incompatibility 75

10.5.11.2 Visual C++ runtime files required 75

10.5.11.3 Web Access extension installation with IIS 7 76

10.5.11.4 Content indexing 76

10.5.11.5 64-bit support 76

10.5.11.6 "Failed to get list of vaults on computer 'ServerName'. A security package specificerror occurred." 76

10.6 Viewers 77

10.6.1 AutoVue 2D Professional 77

10.6.2 Draft Print doesn't work in NavisWorks Freedom viewer 78

10.6.3 Watermarks not supported by Adobe Reader X 78

10.7 Web Access 78

10.7.1 64-bit support 78

10.7.2 Title block field update upon check-in 79

10.7.3 SharePoint 2003 andWebAccess on one server 79


1

1 Int roducing Meridian Enterpr ise 2013

BlueCielo Meridian Enterprise is the departmental to enterprise-wide engineering content management systemfrom BlueCielo ECM Solutions. It can be installed with the following database engines: BlueCielo Hypertrieve,Microsoft® SQL Server®, or Oracle® (see the Supported Applications list for your Meridian version availablefrom your BlueCielo ECM Solutions Certified Partner or the BlueCielo ECM Solutions extranet). The number ofvaults, documents, and concurrent users is limited only by available hardware resources on the host servercomputer.

Be fo re you beg inComplete the following tasks before you attempt to install Meridian Enterprise 2013:

(Optional) Run the Vault Consistency Toolkit tools as described in the BlueCielo Meridian EnterpriseAdministrator's Guide. This will report the current condition of the vaults before they are upgraded.Youmight want to perform some repair or cleanup in advance.

We highly recommend that before installing Meridian Enterprise 2013 on a production server that youperform a trial upgrade in an isolated test environment with copies of your vaults and your cus-tomization. This will allow you to identify potential problems and solve them in conjunction withBlueCielo ECM Solutions before they pose a real problem in your production environment. Proceed toinstall on a production server only when you are sure that the upgrade process has the required result.

Run the Prepare for Backup wizard followed by a complete backup of your system.

Also make daily backups of all critical data. Store the backup in a safe location before making sig-nificant changes to the system. Whether you are upgrading the Meridian Enterprise software, updatingsome other system components, changing the vault configuration, or something seemingly insig-nificant like adding a navigation view, always make sure that you can revert back to the previous work-ing configuration with as little effort and loss of productivity as possible.

1.1 Wha t ' s in th i s gu ide

This document contains important information about BlueCielo Meridian Enterprise 2013:

Release history of supported Meridian Enterprise versions, including brief descriptions of the new fea-tures as well as the minor changes and improvements.

Known problems that could not be resolved before this release and that remain in the product. Theseare typically minor issues that could potentially affect a very small number of customers and for whichpractical workarounds exist. These issues are often resolved in the next release.

For detailed information about Meridian Enterprise, review the following additional documents:

BlueCielo Meridian Enterprise Administrator's Guide included with this release

BlueCielo Meridian Enterprise Configuration Guide included with this release


2

BlueCielo Meridian Enterprise User's Guide included with this release

Meridian Enterprise Supported Software for version 2013 available on the BlueCielo ECM Solutionswebsite.

1.2 Who shou ld read th i s gu ide

This guide is intended for:

BlueCielo Meridian Enterprise system administrators preparing to install or upgrade to this release orconfigure new features.

BlueCielo Meridian Enterprise users who want to learn about the new features in this release.

BlueCielo ECM Solutions Solution Partners who want to learn about the new features in this release.

1.3 Unders tand ing the typog raph ic conven t ions

The table below describes the other typographic conventions used throughout this manual.

Convention Example Description

bold File Named user interface elements: menu items, buttonnames, dialog box titles, dialog box options, icons, andso on.

italic BlueCielo Meridian Enter-prise Administrator’sGuide

Names of other documents.

monospace Document.DisplayName Programming code, configuration file settings, and filesystem paths and folder names. Also user-definedcode elements appearing in the narrative text.

light bluebackground

Call WinMsgBox(“Hello, world!”)

Programming examples that include sample data andare not intended to be used without modification.

bold Document.Log(Line) Named code elements: events, procedures, functions,objects, classes, methods, object properties, con-stants, and so on appearing in the narrative text exceptuser-defined code elements. Variables and parametersappear in italic type.

italic local workspace Introduction of a new term and its definition. Manyterms can also be found in the Glossary if one isincluded in the guide.

T ypog raph ic conven t io ns

http://www.bluecieloecm.com/en/resource-center/product-data/


3

Convention Example Description

bold monospace regsvr32 /u Command-line commands and parameters.

default font F5, Ctrl+O Key names, combinations, and sequences.

italic <DocumentName> Placeholders

bold DisplayName Meridian Enterprise property names

bold+blue Note Note Related information that is not directly applic-able to the adjacent text or might be useful underuncommon circumstances, supplemental, an aside.

Tip Information for intermediate to advanced userson how to use the adjacent text in a more efficient orproductive way.

Warning Information that, if not heeded, could res-ult in lost data or accidents.

T ypog raph ic conven t io ns (con t inued )

1.4 Get t ing techn ica l support

Technical support for BlueCielo products is available from a variety of sources if you have an active supportcontract. Your first source of support is the authorized contacts designated by your company to participate inthe support contract. They are the persons that are responsible for resolving problems with BlueCielo softwarebefore contacting outside sources of support. If your company works with a BlueCielo Partner, that partner isyour second source of support. BlueCielo Partners are responsible for providing technical support to their cus-tomers in order to maintain their status as BlueCielo Partners. BlueCielo will assist the partner company, ifnecessary, to help resolve your problem. If your company is a direct BlueCielo customer, your authorized con-tacts may communicate directly with BlueCielo to resolve your problem.

BlueCielo Partners and direct customers have access to all of these BlueCielo technical support resources:

Online Issue Registration System – Around the clock support issue entry, update, and status.

Knowledge bases – Continuously updated product-related problem solutions, hotfixes, and how-to art-icles about advanced techniques.

FTP server – Downloadable versions of all BlueCielo products and an upload area for files to assistwith problem resolution.

Email notifications – Immediate alerts to support issue status changes and new or changed knowledgebase articles.

Telephone support – Direct access to highly qualified software support engineers with extensive exper-


4

ience in BlueCielo products.

BlueCielo customer forum – Online user-led discussions about BlueCielo products.

The available support contract options, terms, and other details are described in these documents that areavailable from your BlueCielo Partner or on the BlueCielo extranet:

BlueCielo Customer Guide to Support Services (1 MB A4 size PDF)

BlueCielo Customer Guide to Support Services (1 MB LTR size PDF)

http://extranet.bluecieloecm.com/BC_SupportWelcomeCD/literature/BC_guide_SupportServices_A4.pdf

http://extranet.bluecieloecm.com/BC_SupportWelcomeCD/literature/BC_guide_SupportServices_LTR.pdf


5

2 What 's New in Meridian 2013

The following topics describe the new functionality and the changes and improvements to existing functionalityin this release.

Note Youmight see references in the software in this release to the forthcoming Meridian Masters Man-agement Module. Those are preliminary and are not usable in this release. The module will be completelyrevealed, documented, and announced in a future release.

Related informationDeeper Asset Management Module integration 5License changes 5Shared workspaces 6Administration improvements 7Application link improvements 7Client improvements 9Configuration improvements 10Customization improvements 11Setup improvements 13Viewer improvements 13Web Access improvements 14

2.1 Deeper Asset Management Modu le in teg ra t ion

Significant development has been completed that further integrates the Meridian Asset Management Moduleinto Meridian Enterprise:

Similar pages to theObjects andWhere Used pages in PowerUser can now be shown in theMeridianWeb Client. The pages are configured as custom external pages that can be shown only inthe Web Client. The URLs of these pages are two new web applications that are installed on theMeridian web server during setup. The pages show the existing document to object links and can beused to find documents or objects and create new links. For information about configuring and usingthese pages, see the BlueCielo Meridian Enterprise Configuration Guide and BlueCielo MeridianEnterprise User's Guide , respectively.

A new link for AutoCAD P&ID is available that works specifically with the drawing tags created byAutoCAD P&ID. The relationships between the tags and Meridian documents can by synchronized ineither direction from within AutoCAD P&ID and the synchronization status of the tags within the cur-rent drawingmanaged.

2.2 L icense changes

Beginning with release 2013, the Meridian Enterprise license model has been simplified. All Meridian clients arenow authorized by PowerUser Client licenses. One PowerUser Client license and one Database Connectionlicense that is necessary to use it can be purchased as a single license named the Meridian Classic User license.However, the Meridian Classic User licenses do not appear as such on the Licenses tab in Meridian Enterprise


6

Administrator. Instead, the corresponding PowerUser Client licenses and Database Connection licenses will beshown. Each PowerUser Client license entitles the user to use any Meridian client application. This same licenseis claimed and released by the PowerUser, Office Client, Web Access, AutoVue 2D, Application Integration, theapplication links, and the BlueCielo Web Part for SharePoint. Beside Meridian Classic User licenses, no addi-tional client licenses must be purchased except for the optional module licenses and AutoVue 3D licenses,which have not changed. As before, any combination of client software components can be deployed to anynumber of users as the organization requires. The licenses are still floating and are claimed on a first-come,first-served basis unless licenses are reserved for specific user groups.

Existing TeamWork customers will receive an equivalent number of Meridian Classic User licenses with fullaccess to all Meridian functionality such as: multiple vaults, 64-bit server, add-onmodules, and other majorfunctional enhancements. Customers may upgrade the software at their convenience. The TeamWork brand isbeing discontinued and TeamWork licenses will no longer be sold. Existing TeamWork installations will be sup-ported under the normal support and life cycle conditions as described in "Product Life Cycle Support" inBlueCieloTeamWork Supported Software and in the following documents that are available from yourBlueCielo Partner or on the BlueCielo extranet:

BlueCielo Customer Guide to Support Services (1 MB A4 size PDF)

BlueCielo Customer Guide to Support Services (1 MB LTR size PDF)

For more information about these changes, contact a BlueCielo ECM Solutions sales representative or yourBlueCielo Partner.

2.3 Sha red workspaces

Custom folder types may now be associated with a network location outside the vault to act as a sharedworkspace. Shared workspaces are more compatible with authoring applications that create shared, multi-user project and other data files such as AutoCAD Civil 3D, AutoCAD P&ID, and so on. Shared workspaces canbe configured to:

Synchronize with the vault automatically

Assign a default document type to new documents

Show a wizard upon creation of new documents

Delete the shared workspace copies of documents after they have been released from workflow

A new privilege Edit shared workspace settings controls access to configure shared workspace folders.A new privilegeDelete workspace files in shared folders controls permission to delete shared work-space files.

The Shared Workspace Support server license is required for any Meridian application server that hostsvaults that have folder types defined with the Can be used as a shared workspace option enabled. Thelicense is claimed regardless of whether the folder type is actually used or shared workspaces are defined. Ifthe license is absent, the vault cannot be opened by the client applications and documents cannot be opened orsaved in the vault from other applications.

http://extranet.bluecieloecm.com/BC_SupportWelcomeCD/literature/BC_guide_SupportServices_A4.pdf

http://extranet.bluecieloecm.com/BC_SupportWelcomeCD/literature/BC_guide_SupportServices_LTR.pdf


7

2.4 Admin i s t ra t ion improvements

The following improvements have beenmade to the administration of Meridian Enterprise:

All Local Workspace documents for a single user in a single vault can now be unlocked in one oper-ation.

A Check Name button has been added to the Meridian user account dialog box so thatWindows useraccounts can be validated.

The columns that are shown in Meridian Enterprise Administrator for user accounts now include theMail, Title, Unit, and Initials properties.

A new registry setting EnableFQDNS has been added that removes the dependency on NetBIOS forcomputer name resolution. The setting is disabled by default.

New registry values DisableTitleBlockUpdate have been added to the Excel, PowerPoint, andWord application links to control when property synchronization occurs automatically.

If the Use HyperCache option of a vault is enabled , theMaximum log size andMinimumsnapshot interval options are no longer disabled.

On 64-bit computers, HyperCache was not enabled by default.

BlueCielo Publisher support can now be enabled in a vault similar to the Advanced ProjectWorkflowModule and Asset Management Module. The PowerUser client extension no longer needs to be down-loaded from the server. BlueCielo Publisher licenses are still required.

AMRepU.exe now produces a separate report for 32-bit and 64-bit components. On 64-bit platforms,both reports are generated since 32-bit components are also installed.

The Link to Master Document, Unlink from Master Document, Require Merge, ConfirmSuperseded by Master, Confirm Merged with Master, andUndo Make Obsolete com-mands are now included in the Meridian FDA Module audit log.

Web Access users who execute the Release as Master Revision command require Full Controlpermissions to the local workspace folder on the IIS server. They also require the Edit inApplication privilege for the folder in which the master document resides.

For more information, see BlueCielo Meridian Enterprise Administrator's Guide.

2.5 App l ica t ion l ink improvements

The following application link improvements have beenmade:

Microsoft Office 2013 is supported.

Autodesk Inventor 2014 is supported.

AutoCAD P&ID 2014 is supported.


8

SolidWorks 2012 SP SP5 is supported. Also supported by Meridian Enterprise 2012 SP3.

The AutoCAD link now uses Autodesk RealDWG 2014.

A new AutoCAD P&ID link is installed with the Asset Management Module on the client PCs. This linkincludes the functionality of the standard AutoCAD P&ID link plus commands for:

Synchronizing drawings tags to and from asset object in the vault

Syncyhronizing (local or shared) workspace folder structures from the vault.

Showing the Tags dialog box in AutoCAD P&ID for easy tag status review.

A new optionUpdate DWF rendition has been added to the Autodesk Inventor link. The optionqueues rendition updates by BlueCielo Publisher when an open component is saved.

A new property Alias has been added to vault contexts in the Outlook link. A different name can be setin this property for contexts to appear in the Outlook folder tree.

Three new registry values namedDisablePropertiesUpdate have been added to the Office link tocontrol the update of document properties in Excel, PowerPoint, andWord:

HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\AMOfficeAddIn\ExcelHKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\AMOfficeAddIn\PowerPointHKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\AMOfficeAddIn\Word

A new settingRedrawFieldsOnUpdate has been added to the Office link. The setting works similarto the RedrawTitleBlocksOnUpdate setting of the AutoCAD link and controls document contentupdate after property synchronization.

A new settings AutoUpdate has been added to the AutoCAD P&ID link that controls when automaticproject property updates occur.

A new registry values named TempFolder have been added to the Office link to specify the locationof temporary files that are created by the Office link. This setting is intended for use when the path tothe Windows temporary folder is too long and results in odd behavior of the link:

HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\AMOfficeAddIn

The following new registry values were added so that system administrator's can centrally deployapplication integration inclusion and exclusion lists to users. These values are duplicates of the existingvalues in HKEY_CURRENT_USER that are set by users in the Edit Exclusion List and ShowBlueCielo Dialog For dialog boxes of Application Integration. The new values are not set by those dia-log boxes, are typically not editable by the users, and take precedence over the HKEY_CURRENT_USER settings.

For more information, see BlueCielo Meridian Enterprise Administrator's Guide and BlueCielo MeridianEnterprise Configuration Guide.


9

2.6 Cl ien t improvements

The following improvements have beenmade to the Meridian Enterprise client applications:

Adobe Reader 11 is supported.

Windows Search support for memo properties is improved.

A new commandUnlink from Master Document has been added. The command removes the ref-erence between the master document and a project copy and unlocks the master document if it waslocked by the project copy that is unlinked.

Copying a master document to a project folder no longer blanks the properties of Field-Path Definitionsubfolders below the project folder. Instead, the property values are copied from the master doc-ument

The Link to Master Document command now checks for active project copies before executing.

A new commandRequire Merge has been added to the Advanced ProjectWorkflow Module. Thecommand reverses the effects of the Confirm Merge command.

A new commandUndo Make Obsoletehas been added to the Advanced ProjectWorkflow Module.The command reverses the effects of the Confirm Superseded command.

TheOpen in application command has been added to the reference browser dialog toolbar andcontext menu.

A filter icon now appears in the context bar to indicate that a filter is applied to a column in a collectionview that might not be visible without scrolling the collection view horizontally.

Redline layers configured in Meridian Enterprise Configurator can now be selected and used in theAutoVue viewers.

The Find toolbar is now enabled by default after installation.

A new optionAlways on top has been added to the viewer window shortcut menu. When doc-uments are viewed from theWhere Used page of the Asset Management Module, this option pre-vents the viewer window from getting hidden behind the PowerUser window.

Custom navigation views now work similar to the Explorer view when creating new documents orimporting documents using drag-and-drop. The default values of custom properties are the names ofthe corresponding folders in the path where the documents are created.

If only one scope is defined for a vault, it is now selected automatically and the user does not need toselect one when opening the vault.

A new option Include dependent support files has been added to the Add to Briefcase dialogbox. When enabled, this includes AutoCAD support files to which the drawings are dependent upon.The supported file types are: *.dst,*.ttf,*.fmp,*.ctb,*.stb,*.pc3,*.shx,*.shp. Thisoption is only supported by briefcases in the open standard (ZIP, RAR) formats, not in the BRC format.


10

It is now possible to import documents to any read-only workflow state of a workflow definition. Thedocuments can be imported from a briefcase or using drag-and-drop. The workflow states are thosewith theDocument access setting ofDecision or Review. The vault settingAfter importingdocuments must be set to Set state to Under Change. Previously, either the documents couldnot be imported into these states and anAccess denied error would occur or the documents wouldimport but to the initial state of the document type workflow even if a workflow definition was assignedto the document type.

The last selected document is now remembered for each vault.

When the right mouse button is configured as the primary button, the primary button cannot be used tomove windows panes to rearrange the layout without first making the panes floating. This remainstrue for the Shortcuts pane.

TheModified By property of a project copy is now the same value as for the master document. Pre-viously, it was the person who created the project copy.

A new commandReplace Content has been added toWeb Access that works similar to PowerUser.


2.7 Con figu ra t ion improvements

A new option Flexible depth view has been added to navigation views. If enabled, the branches ofthe view can be different lengths, depending on the presence or absence of the property values of doc-uments. This makes the views appear more like the Explorer view and documents can appear at anylevel of the view. If disabled (default), the view appears as in previous versions. All branches of theview are the same length and all of the documents that are included in the view appear at the last levelof each branch.

The Release Quick Change For Others privilege is no longer required to unlock documents in abriefcase created by others. The Unlock from Briefcase privilege is still required.

A new optionDisable all notifications has been added to document types to prevent the sendingof workflow notifications.

A new privilege Can Execute has been added to custom commands and can be assigned to securityroles in the vault.

A new privilege View Rendition Properties has been added to control the visibility of theRendition property page.

The same property may now be used inmore than one location in the Field-Path definition.

The default folder type of a level may now be set by the Change Field-Path Definition command.

If the Advanced ProjectWorkflow Module is enabled, a vault can now be configured to automaticallycreate project folders and subfolders by setting the following options:


11

Configure the Field-Path Definition with one or more subfolders below a project folder level.

Assign a default folder type to the project folder level in the Field-Path Definition.

Configure the default folder type to only be used for project folders.

Assign only one project definition to the default folder type.

Groups can now be granted read-write, read-only, or no access to the branches of the configurationtree in Configurator .

New options Select this group of privileges for this role,Deselect this group ofprivileges for this role, Select all roles for this privilege andDeselect all roles for thisprivilege have been added to the Roles and Privileges dialog box in Configurator.

The behavior of workflow transition equivalence has changed. In prior versions, when releasing abatch of documents in different workflows or different states of the same workflow, any documents inthe batch would be released if there was any eligible transition to an end state. They would bereleased even if a transition had the transition equivalence optionNo other transition set. Thiswas by design to make releasing batches of documents more forgiving. However, this could beundesirable in some configurations. This is no longer possible and all transition equivalence optionsare now respected when releasing documents.

A new parameter -S has been added to BCReminder.exe. It may be used to specify the name of aMeridian group to send reminders to for the documents in a saved search. This allows them to receivenotifications without subscribing to the documents. Also, the -Q parameter now works with privatesaved searches so that the collection that is used with reminders can be hidden from users.

A new security privilege Create Document from Script has been added. This privilege can begranted to users who do not have the Create Document privilege to create documents manually.The privilege is available for custom folder types only.

For more information about these improvements, see the BlueCielo Meridian Enterprise Configuration Guide.

2.8 Customiza t ion improvements

The following improvements have beenmade to the Meridian Enterprise customization (VBScript) features:

The property Vault.HasFeature property has been added to detect which optional features, such asemail notifications or modules, are enabled for the current vault.

The methodDocument.GetNavigationViewLevelPath has been added. It returns an array thatcontains the level names where the current document is located in a specified view.

The global property CurrentPropertyName has been added. This property contains the name ofthe property being affected by the current configuration expression and can be used in custom func-tions to performmore advanced actions than are possible in a single expression statement.


12

The Folder object has a new Roles property. This property is a new Roles object withAssignments and InheritedFromParent properties andAddAssignment, Clear, andDeleteAssignment methods.

The VBScript editor toolbar has a new buttonGo to Line (Ctrl + G) for quickly finding a specific lineof code by number, such as the line numbers shownwhen debugging script.

The keyboard shortcuts Ctrl + S and F12 have been added to the VBScript editor to save the currentcode block.

The VBScript property Client.ClientID did not return the correct value in the Office Client.

A new methodDocument.ProjectCopy.UnlinkFromMaster has been added. It removes the ref-erence between the master document and a project copy and unlocks the master document if it waslocked by the project copy that is unlinked.

New events DocProjectCopyEvent.BeforeUnlinkFromMaster andDocProjectCopyEvent.BeforeUnlinkFromMaster have been added. These events occur whenthe Unlink from Master Document command orDocument.ProjectCopy.UnlinkFromMaster method executes.

New events DocGenericEvent.BeforeCreateReference,DocGenericEvent.AfterCreateReference,DocGenericEvent.BeforeDeleteReference,andDocGenericEvent.AfterDeleteReference have been added.

Creating custom properties with the same names as system properties is now prevented in Con-figurator.

A new methodBCRepository.GetDeletedObjects has been added to the .NET interop assembly.The method returns a table view of the folders, documents, and tag objects that have been deleted inthe vault between two specified dates.

A new constantAS_CONFIRM_ROOT_SELECTION has been added that, when set to False pre-vents selection of the root of the vault in the project folder selection dialog box that is shownwhen pro-ject copies are made. TheNew Folder button is also now enabled in this dialog depending on theuser's privileges.

Eight new VBScript functions are available from the Meridian Asset Management Module link withAutoCAD P&ID. For more information, see the BlueCielo Meridian Asset Management ModuleAdministrator's Guide.

New functions AMMWhereUsedManageLinksIsAllowed andAMMTagsManageLinksIsAllowed have been added to the Meridian Asset Management ModuleVBScript API. The functions control the availability of theManage Links button in theManageDocument Links andManage Object Links dialog boxes.

TheDocCopyMoveEvent_PrepareCopy event now occurs for most actions that create new doc-uments without using a template or that create copies of documents. This was done to support drag-and-drop and Clipboard document creation. The event also provides a place in which to pro-grammatically set the destination folder and to suppress the destination folder selection dialog using


13

the AS_CONFIRM_NO_SELECTPROJECTWIZARD andAS_CONFIRM_IMPORT_FOLDERconstants. If a vault already implements this event for other use cases, it should be evaluated for com-patibility with the new actions in which it occurs andmodified to distinguish between the different usecases using the Client.ImportType or Client.ImportDetails properties, if necessary.

For more information, see the BlueCielo Meridian Enterprise VBScript API Reference Guide or theBlueCieloMeridian Enterprise .NET API Reference Guide.

2.9 Setup improvements

The following improvements have beenmade to Meridian Enterprise setup:

Microsoft Windows Server 2012 is supported with and without the GUI.

A 64-bit version of the BlueCielo IFilter is now installed on 64-bit computers. The IFilter is compatiblewithWindows Search.

Some help files were missing from the 64-bit server setup.

Korean language support (excluding documentation) has been added.

The default local workspace database for 32-bit clients is now SQL Server Compact Edition instead ofMS Access. This was done to improve interoperability between the 32-bit and 64-bit client applicationson the same PC. This is controlled by theWorkSpaceDB value in the following registry key:

HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridi-an\CurrentVersion\Client

The unsupported versions of the AutoCAD link (pre 2007) are no longer included in the setup pro-grams. The links are available upon request.

When AutoVue Client/Server is installed, the Jetty server, AutoVue Server, and BCConnectorServiceservice are started automatically as services as startup by default. Manual starting is no longerrequired.

The vault extensibility extension (BlueCieloECM.Extensible.UI.dll) no longer needs to bedownloaded to the client computers before users can view their subscriptions in the web application orview the audit log. The feature is now a behavior that is installed with the BlueCielo Publisherextension when that component when is selected during installation of Meridian Enterprise on thecomputer.

For more information, see the BlueCielo Meridian Enterprise Administrator's Guide.

2.10 Viewer improvements

The following improvements have beenmade to the Meridian Enterprise viewer:


14

The AutoVue viewer is now the default for all file types.

Setting EnableOfficeMarkups=1 in avx.ini did not work correctly. Redlining Office documentsis now enabled by default and cannot be disabled.

A page number toolbutton has been added to the AutoVue viewer to jump to a specific page in AdobePDF documents.

If installed, the Microsoft Excel Viewer may be selected for viewing .xlsm documents.

2.11 Web Access improvements

The following improvements have beenmade to Meridian Enterprise Web Access:

Web Access can now be configured to show document property pages in a second pane beside the act-ive navigation view instead of replacing the navigation view in the browser window. The browser issplit into two panes and the divider can be dragged horizontally to resize the panes. The viewer thenappears as a property page tab. To enable this configuration for all Web Access users, a new serverregistry settingUseFrames has been added that must be set to 1.

Routed (inherited) folder properties now appear in views other than the Explorer view inWeb Accessif the Size column is shown.

Collections may now be created, edited, viewed, and deleted inWeb Access.

Uploading documents withWeb Access that had references to unchanged documents or tag objectscould fail with the error Access denied. The referenced documents are no longer included in theupload.

The Enable Web Access Client components option inWeb Access preferences is now enabledby default during installation.

Creating project copies of a master assembly document no longer removes the references to otherdocuments. Now, if only the master assembly document is copied, the project copy will reference theoriginal reference documents. If the reference documents are copied together with the master doc-ument, the master document will references the project copies of the reference documents (and cop-ies of themmade in the same project).

Hybrid parts are no longer saved in collections as main documents. This was done to make the beha-vior of PowerUser andWeb Access consistent.


15

3 What 's New in Meridian Enterpr ise 2012 SP3


Related informationApplication link improvements 15Client improvements 15Customization improvements 15



A new value 2 has been added to the application links CheckBlankPropertiesAssigned clientregistry settings to force mapped document properties to empty if the file properties are either Emptyor Null.

The AutoCAD link now supports title block synchronization using dynamic blocks.

The AutoCAD link now supports title block synchronization of multiple title blocks in the same drawingwith different values.



Inactive project copies now appear crosshatched in the Show References dialog box if theDisplayinactive project copies option is enabled.

Added support for Microsoft Access 2007/2010 (.accdb file extension) as an import data source tothe Document Import Tool.

Under certain circumstances in Release 2012 SP1, a user could be denied access to view a documenteven though they had been granted the correct privileges.

An icon is now shown in the info bar of the viewer window when either the native file or the renditionor both files have redlines. The icon shows a tooltip that states which of the files has redlines.


The following improvements have beenmade to the Meridian Enterprise customization (VBScript and.NET API) features:

In the Meridian Connection API, the GetFolderElements andGetReferences methods eachreturned and array of strings instead of an array of objects. This made the methods unusable from


16

VBScript. The methods now return arrays of objects that appear as arrays of variants in VBScript.

A new property BCFolderSearchQuery.OnlyIncludeObjectsChangedSince has been added tothe .NET interop. The property gets or sets the date that defines the changed folders that are includedin the search result.

A new constantAS_CONFIRM_NO_SELECTPROJECTWIZARD has been added that can be usedto show the project folder selection dialog for new non-project copy documents and to force them tobe created in a project folder. A new eventDocGenericEvent_DocumentFolderSelected hasbeen added with which the selected folder can be retrieved for use in setting other properties.

Effective with this release, the DCOM information in the BlueCielo Meridian Enterprise Developer'sGuide will not be updated or improved andmight be removed from a future revision of that document.The Meridian Enterprise DCOM API itself will continue to exist but all changes and additions to it will beundocumented and unsupported. The Meridian Enterprise .NET API and the VBScript API are now theonly supported development interfaces for Meridian Enterprise and TeamWork (VBScript only). The".NET SDK Reference" section of the BlueCielo Meridian Enterprise Developer's Guide, the BlueCieloMeridian Enterprise VBScript API Reference , and the BlueCielo TeamWork VBScript API Referencewill continue to be updated and improved until further notice.

For more information, see the BlueCielo Meridian Enterprise VBScript API Reference Guide and the BlueCieloMeridian Enterprise .NET API Reference.


17



Related informationAdministration improvements 17Application link improvements 7Client improvements 18Customization improvements 18Documentation improvements 19Viewer improvements 19



A new registry value named Language has been added in the following registry key to allow switch-ing the user interface language of Meridian Enterprise. This can be valuable to accommodate remoteaccess users in different locales. You can set the value by any method that is compatible with yourremote access system, such as with a batch file that executes when a user logs on to a new session.The new value overrides the default language that is set during installation in the HKEY_LOCAL_MACHINE hive in the value with the same name.

HKEY_CURRENT_USER\Software\Cyco\Meridian Enterprise\CurrentVersion


4.2 CAD app l ica t ion support improvements

The support provided by Meridian Enterprise for a particular CAD application comprises three elements:

Link components that load inside the CAD application to synchronize properties and external ref-erences and provide application-specific functionality, for example, BlueCielo ARX modules.

File access components used by the Meridian client applications to synchronize properties and externalreferences outside the CAD application, for example, Autodesk RealDWG.

File viewing components used by the Meridian client applications to display files outside the CAD applic-ation, for example, Oracle AutoVue.

Some of these components are dependent on products provided by third party developers. BlueCielo makescommercially reasonable efforts to support new versions of CAD applications within 60 days of the release ofthe version to market. However, if dependent products are not yet available from the third-party developers,BlueCielo may either delay supporting a new version of a CAD application or it may release limited support forthe version.

The following additions to our support for popular CAD applications have beenmade with the limitations noted:


18

Autodesk Inventor 2013 SP1

SolidWorks 2013

For more information, see BlueCielo Meridian Enterprise User's Guide.

For the application versions that are supported by the Oracle AutoVue version that is included in this release,refer to the Oracle AutoVue website.

For a full list of the supported CAD software, see the Supported Software document for this release of MeridianEnterprise, consult your BlueCielo ECM Solutions Partner, or contact BlueCielo ECM Solutions Sales.



All hotfixes that have been created for the 2012 release are included in this release.

The Edit Redlines button in the AutoVue toolbar can be enabled for Microsoft Word, Excel, Outlook,and RTF file types by setting the ENABLEOFFICEMARKUPS option to 1 in the file AVX.ini asdescribed in the Oracle AutoVue Desktop Deployment Viewing Configuration Guide. For informationabout deploying this and other standard settings to all client computers, see the BlueCielo MeridianEnterprise Administrator's Guide.

The default of the KeepSearchSettings value in the following registry key has been changed to 1.This causes the search settings in the Find dialog box to be retained between searches by default. Setthe value to 0 to discard the settings between searches.

HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\AMFind\Settings

Microsoft Internet Explorer 10 is supported as a web browser.


A new settingRtmRenditionAction has been added to the Vault section of Application Integrationconfiguration. This setting controls the disposition of the master document rendition when a projectcopy is released as a new revision of the master document.

The registry values DiscardProjectRefs andDoNotRerouteRefs2Master have beenmoved tothe Vault section of Application Integration configuration.

For more information about these improvements, see theBlueCielo Meridian Enterprise Configuration Guide.



http://www.oracle.com/us/products/applications/autoVue/index.html


19

The Task Server in Meridian Enterprise 2012 SP1 would create tasks in the Pickup folder but not pro-cess them. After restarting the server, the existing tasks would be processed but new tasks would notbe processed.

For more information, see the BlueCielo Meridian Enterprise VBScript API Reference Guide.

4.6 Documenta t ion improvements

All BlueCielo products are supplied with documentation that consists of an Administrator's Guide, aConfiguration Guide, a User's Guide, a Release Notes, or a combination, depending on the complexity of theproduct. Additional documents are available for some products, such as System Requirements, API Reference,and Quick Start Guide.

All manuals are available in either Microsoft HTML Help (.chm format for on-screen viewing) or AdobePDF format (for on-screen viewing or printing). Most manuals are available in both formats. Manuals that areavailable in Adobe PDF format are provided in both LTR and A4 page sizes for optimal printing and are not copyprotected.

All manuals provide on-screen cross-reference hyperlinks for convenient navigation to related topics. The

Microsoft HTML Help files can be opened with context-sensitive links (press F1 or click Help or click thebutton on the toolbar) from appropriate locations in the programs and from shortcuts in the Windows Startmenu.

Note For technical reasons, context-sensitive help is not possible from within the Meridian Administrator pro-gram. However, the help can be viewed by pressing F1 and browsing to the appropriate topic.

Besides being updated with the new features and improvements in Meridian Enterprise and overall qualityimprovements, the following improvements have beenmade to the Meridian Enterprise documentation in thisrelease:

The order of API events for each object type has been added to the BlueCielo Meridian EnterpriseVBScript API Reference. For the sequence of events for particular objects, see the "About the <ObjectType> events" topics in the chapter "Understanding the Meridian event procedures."


The following improvements have beenmade to the Meridian Enterprise viewers:

Version 20.0.4 of Oracle AutoVue desktop deployment and version 20.2.1 of Oracle AutoVue Cli-ent/Server deployment are now included in Meridian.


20



Related informationAdministration improvements 20Application link improvements 20CAD application support improvements 21Client improvements 22Configuration improvements 22Customization improvements 23Documentation improvements 24Managed Change improvements 24Setup improvements 24Viewer improvements 25Web Access improvements 25



Restoring a 32-bit Hypertrieve vault on a 64-bit server no longer requires manual editing of theDataStore.ini file to specify the correct database engine DLL file.

Restoring a vault backup from SQL Server or Oracle onto a server operating system that is incom-patible with the sort order of the operating system where the backup was created will now show aprompt to upgrade the database with the icosnlsver.exe tool.

A registry settingNotReservedTmmLic has been added to disable the requirement for reservedlicenses by the Meridian Transmittal Management Module.

A registry settingDiscardProjectRefs has been added to control the disposition of referencesbetween project copies made in the same project folder when one of the project copies is discarded.




When opening a Revit model read-only and reference paths need to be updated, a warning will beshown to the user.

If a Revit model is opened read-write, absolute reference paths are converted to relative paths inorder to allow the model to be opened for review.


21

Finite element analysis (FEA) files created by Autodesk Inventor Professional and referenced by anassembly are now managed similar to other files.

A settingNotShowXrefDialog has been added to the AutoCAD link to suppress the dialog that isshownwhen Xrefs that reside outside a vault cannot be resolved.

The reliability of data exchange with AutoCAD 2004 and earlier drawings has been improved.

The Revit link can now be configured to automatically import sheet sets and build references betweenthem.

For more information, see BlueCielo Meridian Enterprise User's Guide and BlueCielo Meridian EnterpriseConfiguration Guide.


The support provided by Meridian Enterprise for a particular CAD application comprises three elements:

Link components that load inside the CAD application to synchronize properties and external ref-erences and provide application-specific functionality, for example, BlueCielo ARX modules.

File access components used by the Meridian client applications to synchronize properties and externalreferences outside the CAD application, for example, Autodesk RealDWG.

File viewing components used by the Meridian client applications to display files outside the CAD applic-ation, for example, Oracle AutoVue.

Some of these components are dependent on products provided by third party developers. BlueCielo makescommercially reasonable efforts to support new versions of CAD applications within 60 days of the release ofthe version to market. However, if dependent products are not yet available from the third-party developers,BlueCielo may either delay supporting a new version of a CAD application or it may release limited support forthe version.

The following additions to our support for popular CAD applications have beenmade with the limitations noted:

AutoCAD 2013

Autodesk Inventor 2013

SolidWorks 2012 SP3

MicroStation V8i, SELECTseries 2 and 3


For the application versions that are supported by the Oracle AutoVue version that is included in this release,refer to the Oracle AutoVue website.

For a full list of the supported CAD software, see the Supported Software document for this release of MeridianEnterprise, consult your BlueCielo ECM Solutions Partner, or contact BlueCielo ECM Solutions Sales.



22



All hotfixes that have been created for the 2012 release are included in this release.

Unlocking a selection of documents that were locked in a briefcase created by a different user nowworks correctly.

A wizard page shown for a canceled transition executed in a project folder will now appear correctly ifthe transition is repeated.

Searches performed while a scope is active are now restricted to documents within the scope.

Files may now be imported up to 4 GB in size. The previous limitation was 2 GB.

A commandOpen Rendition has been added that opens a rendition in its Windows registered applic-ation.

A button has been added to the left end of the title bar in the viewer pane to toggle display of the cur-rent document's source or rendition content.

Properties that are assigned a lookup list of values now show that list in theQuick Find dialog box.

The Replace Content command now updates the extension of the document if it is different fromthe new content.

The Set Property Value dialog box now correctly shows a lookup list of existing values for a prop-erty that has been assigned a VBScript function.

The Meridian Enterprise desktop applications now support creating new empty static collections fromwithin the Collections dialog box.

Options have been added to the Add to Briefcase and Import from Briefcase dialog boxes toinclude the native, rendition, and thumbnail files in those commands.

A web application is now provided for viewing document subscriptions and for viewing the audit logdatabase of the Meridian FDA Module in a web browser.



The message text for email notifications can now be configured with variables for the current user, pro-ject, and vault.

Email notifications may now include text calculated by a VBScript expression.

Custom icons may be configured for folder types and documents.


23

Property assignments are now supported by the workflow definition commands Reroute andMigrate.

New optionsNoExportContent andNoImportContent have been added to briefcase con-figuration.

A new optionBefore starting a new revision in projects has been added to the revision num-ber options for document types. When enabled, it increments the major part of the revision numberwhen the document is released from a project folder and the minor part of the revision number at thestart of the document's workflow.

The scope of execution of custom commands has been reduced to the selected object and in somecases, its immediate contents. Custom commands no longer execute recursively on subfolders andtheir contents.

A new optionCalculate file name upon project copy creation has been added to documenttype definitions.

For more information about these improvements, see theBlueCielo Meridian Enterprise Configuration Guide.



The property Batch.ApplyToAll has been added for use in applying property value changes in wiz-ard pages to all documents in a batch.

The property Client.BuildNr has been added that returns the file version number of theAmEdmUI.dll client library file.

The eventBrcEvent_MatchDocument has been added to programmatically match incoming filesin a briefcase with vault documents.

Events that occur during the Link to Master, Confirm Superseded by Master, andConfirmMerged with Master commands of the Meridian Advanced ProjectWorkflow Module have beenadded.

Methods Document.Subscribe andDocument.Unsubscribe have been added to manage eventnotifications in script.

The property IsUniqueValue has been added to the Folder object.

Backward compatibility of UI extension commands created with the BlueCielo .NET interop librarieshas been improved. The commands will now register and execute on computers with interop versions1.4.30 and prior installed.

For more information, see the BlueCielo Meridian Enterprise VBScript API Reference Guide.


24

5.7 Documenta t ion improvements

All BlueCielo products are supplied with documentation that consists of an Administrator's Guide, aConfiguration Guide, a User's Guide, a Release Notes, or a combination, depending on the complexity of theproduct. Additional documents are available for some products, such as System Requirements, API Reference,and Quick Start Guide.

All manuals are available in either Microsoft HTML Help (.chm format for on-screen viewing) or AdobePDF format (for on-screen viewing or printing). Most manuals are available in both formats. Manuals that areavailable in Adobe PDF format are provided in both LTR and A4 page sizes for optimal printing and are not copyprotected.



Note For technical reasons, context-sensitive help is not possible from within the Meridian Administrator pro-gram. However, the help can be viewed by pressing F1 and browsing to the appropriate topic.

Besides being updated with the new features and improvements in Meridian Enterprise and overall qualityimprovements, the following improvements have beenmade to the Meridian Enterprise documentation in thisrelease:

The availability of context-sensitive help has been expanded throughout the Meridian client applic-ations and added to the Meridian Advanced ProjectWorkflow Module and Meridian FDA Module fea-tures.

5.8 Managed Change improvements

The following improvements have beenmade to the Meridian Enterprise Managed Change features:

If an assembly had parts under change inmultiple projects, it was possible to release the assembly.This has been corrected. Assemblies that have parts in other projects cannot be released.

For more information, see the BlueCielo Meridian Enterprise User's Guide.

5.9 Setup improvements

The following improvements have beenmade to Meridian Enterprise setup:

The 32-bit BlueCielo IFilter files are now installed with the 64-bit client components. Installation of theIFilter can be completed as described in the BlueCielo Meridian Enterprise Administrator's Guide.

Meridian Enterprise now supports Microsoft SQL Server 2012.

Removing and replacing the Revit link with a Windows Installer package and UAC enabled now workscorrectly.


25

The Microsoft Visual C++ 2008 Redistributable Package is no longer required for installing BlueCieloMeridian Enterprise.

The Meridian Enterprise client setup programs now include options to install and register the clientextensions of the BlueCielo Publisher, the Meridian Global Collaboration Framework, and the MeridianConnection API library. Licenses must be installed for each before they can be used. The WindowsInstaller packages also support custom installations be specifying the components in the ADDLOCALargument: PublisherExt,GCFExt, andNETAPI, respectively.

The MeridianWeb Client setup package is now available as a single executable file for both 32-bit and64-bit computers. On 64-bit computers, it will install both the 32-bit and 64-bit components so that thesetup does not need to be run twice. The file can be unpacked by running it with the /a command lineparameter to perform an administrative installation that results in an installable .msi file with the spe-cified language transform applied. The .msi file can then be deployed with Active Directory Services.Alternatively, the package can be deployed as described in the following bullet.

The MeridianWeb Client may now be installed from a local server. During Meridian Enterprise install-ation, the setup wizard now prompts for the location of the MeridianWeb Client setup file to copy to theWeb Access server. The setup program copies the MeridianWeb Client setup file to a subfolder of theWeb Access application. Web Access users who do not have the viewer installed can click a link in theWeb Access viewer pane to download the setup program.



The following improvements have beenmade to the Meridian Enterprise viewers:

AutoVue 2D Professional version 20.2 is now included in Meridian. For a list of the supported fileformats, see the Oracle website.

Note If AutoVue Client/Server is already installed, the AutoVue server must be upgraded to thesame version that is supplied with Meridian.

AutoVue Client/Server is supported by the desktop applications by setting several registry values.

The supplied registry file for the Navisworks viewer has been updated to support Navisworks 2013.


5.11 Web Access improvements

The following improvements have beenmade to Meridian Enterprise Web Access:

Custom property values may be applied to all documents in a batch during file upload.

Custom property pages that are configured to show onworkflow transitions now show for only the firstdocument in a batch instead of for all documents in the batch.

http://www.oracle.com/us/products/applications/autoVue/autovue-supported-file-formats-065285.pdf


26

The menu bar (with limited commands) is now available and property editing is possible in undockedproperty page windows.

Using selections and the Selection menu have been improved.

Cross-site scripting (XSS) vulnerability has been further reduced.

Batch support for Managed Change and Meridian Advanced ProjectWorkflow Module commands hasbeen added. However, commands that prompt for a project folder once in PowerUser do so for eachdocument in the batch inWeb Access.



27

6 What 's new in Meridian Enterpr ise 2012


Related informationAdministration improvements 29CAD application support improvements 31Certified for Windows Server 2008 R2 29Changes and improvements 29Client application improvements 32Configuration improvements 33Customization improvements 34Document renditions 27Documentation improvements 35HyperCache 28Setup improvements 37Viewer improvements 38Web Access Improvements 39Web Parts improvements 40Application link improvements 30

6.1 Document rend i t ions

Meridian Enterprise is able to store andmanage multiple files for each document in a vault. The primary file isthe editable content of the document. Other files include hybrid document parts, a thumbnail image, and elec-tronic redlines. BlueCielo Meridian Enterprise 2012 adds another file type for renditions.

A document rendition is a copy of a document in a format other than the original. Renditions can be auto-matically generated by BlueCielo Publisher.

Document renditions:

Can be seen in the viewer pane by enabling the Show Renditions option in the PowerUser client.Youmay also switch between viewing the native document and viewing the rendition. When the rendi-tion is shown, Rendition of <DocumentName.ext> appears in the title bar of the viewer.

Can be updated on demand for either a folder or a selection of documents.

Can be accessed and verifed using VBScript. See the BlueCielo Meridian EnterpriseVBScriptAPI Reference for more information.

Can be sent as attachments in emails generated from a Meridian Enterprise desktop application.

Include properties to handle rendition settings such as page layout, rendition color, etc.

Are secured by new privileges that control viewing of renditions, manually updating renditions, view-ing rendition redlines, and editing rendition redlines inside and outside of a workflow.


28

Can be included in briefcases.

Can be dragged and dropped to attach them to the current document.

Can be included when importing documents. This is done by specifying a data source field for the Data-base ImportWizard that contains the path to the renditions.

Are included in vault archives.

Can be printed.

Can be redlined.

Can be automatically updated upon execution of a workflow transition.

Can be attached to email messages sent from the PowerUser.

Can be restored during vault restoration.

Are supported by BC Meridian Explorer.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide and the BlueCielo MeridianEnterprise User's Guide.

6.2 HyperCache

Because the 64-bit platform provides a vastly larger memory address space and server computers with largeamounts (16 GB or more) of physical memory are readily available and affordable, Meridian Enterprise per-formance and scalability can be improved with an optimal new configuration called HyperCache.

In the HyperCache configuration, a vault is stored in a Hypertrieve database that is loaded entirely intomemory. This maximizes the performance of the vault, which typically serve larger numbers of users andhigher document quantities. The Hypertrieve database gives the cache persistence between service shut-downs and startups. The vault contents are replicated to repositories hosted by SQL Server or Oracle wherethey can be accessed read-only with the Meridian Explorer client or standard reporting tools such as SQLReporting Server and Crystal Reports.

For more information about HyperCache, see the BlueCielo Meridian Enterprise Administrator's Guide.

6.3 Not i f ica t ions and subscr ip t ions

Notifications can be configured by a system administrator to automatically sendmessages to workflow par-ticipants whenworkflow, project copy, redline, and configurable events occur.

Subscriptions allow non-participating users to select items (documents or object tags) and choose from a list ofevents (for example, when a document is changed, deleted, or released from change) on which they want tobe notified by email. The messages are automatically sent from an SMTP server. Authorized users canmodifythe subscriptions of other users (Web Access not supported).


29

Reminders can be configured by system administrator's to send scheduledmessages based on navigation viewqueries.

The SendNotification method has been added to VBScript to allow custom notifications.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide and the BlueCielo MeridianEnterprise User's Guide.

6.4 Cert i f ied for Windows Server 2008 R2

After its release, Meridian Enterprise 2011 was certified for Windows Server 2008 R2 by Microsoft.

This certification identifies hardware and software solutions that meet Microsoft standards for compatibility andrecommended practices with the Windows Server 2008 R2 operating system. Solutions that have earned thecertification take advantage of top-performing technologies, such as 64-bit and virtualization. Meridian Enter-prise 2011 has been tested by a third party test vendor. Microsoft periodically reviews the certified solutions forcompliance with these standards.

For more information about this certification, see the Windows Server catalog web site.

Related conceptsWhat's new in Meridian Enterprise 2012 27

6.5 Changes and improvements

The following topics describe the changes and improvements to the existing functionality in this release.

6.5 .1 Admin i s t ra t ion improvementsThe following improvements have beenmade to the administration of Meridian Enterprise:

A registry key has been added to control incoming references after a project copy is released.

It is now possible to automate the collection of performance data for the AutoManager EDM Server ser-vice. The Process ID uponwhich the performance counters rely no longer changes.

http://www.windowsservercatalog.com/content.aspx?ctf=logo.htm


30

Performance improvements have beenmade to the Meridian server to improve start-up times withlarge vaults.

The Database ImportWizard now supports the ability to select the comparison operator for each data-base field.

A tool is now included that reads the membership of an Active Directory group and adds or updatesthose members and their properties in a Meridian group.

A check has been added to disable automatic client updates if the computer running Meridian is theMeridian server.

The 64-bit Windows Installer package now contains both the 32- and 64-bit versions of PowerUser.

Licenses have been added for use in test environments. TheseNot for Production (part numbercontainsNFP) licenses do not need to be authorized and will not expire.

The recovery log will now always complete even if errors occur. All errors encountered will be loggedin the Windows Application Log.

During the creation of a vault, an option is now available to enable or disable work areas for the vault.The default setting is disabled. For existing vaults that have work areas enabled, a conversion tool isavailable to upgrade to folders.

Vaults using Microsoft SQL can now be backed up to a configurable location.

A SplitImportPath setting can be added to a vault's import filter file. When set to 1, the path and filename of source documents will be split into separate path and a filename values and stored in theAMFSObjectPropertySet._IMPORTEDFROMPATH andAMFSObjectPropertySet._IMPORTEDFROM properties, respectively.


6.5 .2 App l ica t ion l ink improvementsThe following have been improved in the various application links:

Manually updatingmultiple fields in Microsoft Word did not function correctly. Some fields were notupdated with the new value.

It is now possible to import Microsoft Outlook and Lotus Notes message attachments as a batch. Prop-erties can be set for the first attachment and the same values are used for all following attachments.This is not supported for vaults that use a Field-Path definition.

User interaction in Microsoft Outlook during drag-and-drop import operations can be minimized by sup-pressing dialogs.

Microsoft Outlook emails and their attachments can now be saved as a single file in the .msg fileformat.


31

When exporting Lotus Notes or Microsoft Outlook emails, it is now possible to see the email attach-ments in the export dialog.

The functionality available for Lotus Notes has beenmade more consistent with the Microsoft Outlooklink functionality.

When routing an Autodesk Inventor IDW document through document workflow via AutodeskInventor, the title block properties are now synchronized to the document and the viewer correctly.

The Microsoft Outlook settings have now been centralized for all users on the Email Settings page inthe Meridian Enterprise Configurator.

6.5 .3 CAD app l ica t ion support improvementsThe following improvements have beenmade to the CAD application support:

Support has been added for the following CAD application versions:

Solidworks 2011 and 2012 (not yet supported by AutoVue)

AutoCAD 2012 family

AutoCAD Civil 3D versions 2011 and 2012 both 32-bit and 64-bit

Autodesk Revit 2012

In some cases, the menus in AutoCAD 2010 would disappear when loading.

When opening an AutoCAD drawing, some title block properties were not updated correctly.

Support has been added to manage Autodesk Revit model hierarchies andmanagement of referencescreated in the Autodesk Revit model. This excludes references to point clouds.

Support has been added for Revit worksharing.

Support for AutoCAD P&ID project files and their parts has been improved.

The BlueCielo panel of the ribbon in AutoCAD has been improved.

Attempting to synchronize references for Autodesk Inventor drawing files would fail in Teamwork.

Commands in the AutoCAD, Inventor, Microstation, and Solidworks links are now shown in a BlueCielopanel in the ribbon.

Using a registry key, it is now possible to control checking of mapped property values that have beenset to empty or set to null. If set to empty, the corresponding document property is also emptied.

A registry key has been added to control when titleblock properties are updated. The possibilities forupdating titleblock properties can be set to:

Auto update

Disable update on open


32

Disable update on save

Disable update on open and save

The Save Release command has been added to AutoCAD. Using this command will save the currentdocument and if the document's next workflow step is a released state, it will automatically be routedto that state.

Buttons have been added to the BlueCielo panel in Revit to handle referenced documents.

Activation of the AutoCAD link on a 64-bit French system has been improved.


6.5 .4 Cl ien t app l ica t ion improvementsThe following improvements have beenmade to the Meridian Enterprise client applications:

Commands for Managed Change and the Meridian Advanced ProjectWorkflow Module have beenmoved to a sub-menu of the document shortcut menu.

In some cases it was not possible to edit dynamic collections.

Using a registry key, the Microsoft Access database format is supported for Local Workspace.

The generation of thumbnails for certain Microsoft Excel files would sometimes crash PowerUser. Thishas been resolved with the inclusion of AutoVue 20.1.1.

Thumbnails are now shown for folders in navigation views.

New icons that are more consistent, clear, and intuitive.

When using the Set Property Value command for a property that uses a lookup list, the existing val-ues will be shown in a list for selection.

In some cases, printing using AutoVue would hang PowerUser.

In some cases it was possible to create a new folder even though the user did not have the necessaryprivilege.

When creating project copies, the current project copy sometimes did not display references in theReference Explorer.

If the main toolbar in PowerUser was undocked and PowerUser was closed, the menu could not easilybe recovered.

The Find command can now be used to find folders based on the folder name or properties, includingcustom properties. Folder searching is not supported by the Quick Find or Key Find features.

The Find dialog now supports routed properties.

An option has been added to clear the search history for Quick Find.


33

ClickingOK after editing property pages in PowerUser with the Properties page set to Auto Hidesometimes caused display artifacts to show in underlying open window panes.

Changes made to a navigation view filter can now be saved between sessions.

PowerUser, Office Client, andWeb Access will now remember the last selected folder for certain oper-ations such as importing documents, copying with references and creating project copies, This folderwill be the default for the next operation.

It is now not possible to see reference types that are not assigned to the current scope. This also pre-vents deletion of reference types that are not assigned to the current scope.

When cutting and pasting documents from one folder to another folder in PowerUser, the navigationview is refreshed correctly.

PowerUser can be launched from the command line with the /scope parameter allowing you to openPowerUser immediately in the desired scope.

Meridian Enterprise now includes a stand-alone tool, BC Sequence Manager, for managing sequencenumbers used in a Meridian vault.

Attachments of Lotus Notes emails can now be batch imported whereby different document types canbe assigned to each attachment.

Column filters can now be saved for collections and search results in PowerUser and Office client.

A new Clipboard command, Paste Multiple, is available to create multiple copies of documents onthe Clipboard.

Folders created based on folder type definitions are automatically assigned the corresponding foldericon. Even in the case where a Field-Path definition is being used, the icon defined for the folder typewill be shown in the navigation views.


6.5 .5 Con figu ra t ion improvementsThe following improvements have beenmade to the configuration of Meridian:

A Sort Priority option has been added to custom commands to specify the order of custom com-mands in the shortcut menu of a document.

Support for Microsoft Excel and Microsoft Access files on 64-bit computers is now available.

It is now possible to map a single document property to multiple project folder type properties. Thevalue of the document property will depend on the document's parent folder.

An option has been added to the Database ImportWizard to include a time stamp in the import log.

When a table is created or imported, all of its privileges are now added to all roles.


34

Improvements have beenmade for importing documents that were originally exported using the VaultArchive Wizard. The system looks for a mapping file and if found will automatically create the appro-priate field mappings for the import.

It is now possible to add keywords to document types that allow you to check for classes of documenttypes using VBScript instead of just by their names.

A registry key has been added to control how embedded images are handled in Lotus Notes emails.

The VBScript methodVault.ExecSQL can use the connection string associated with a external tablequery that is defined in the vault by prefixing the query name with "$$".

The user name and password entered in theData Link Properties dialog are not shown in theConnection string text box for increased security.

Table values included in a configuration file (MET) were not imported by the 64-bit version of theMeridian Configurator.

A branch Column Collections has been added to the Environment branch in the Meridian Con-figurator and the column configuration in the Vault Settings branch have beenmoved to the newbranch. This provides a centralized area for configuring the columns for views.

The conditions of custom properties have been expanded to include a setting for batch operations.With the settingApply to entire batch, properties can be filled in for all documents in the batchbased on an expression or always.

A second instance of Meridian Enterprise Configurator can be opened in read-only mode to view thevault configuration while changes are made in a different instance.

When using theMigratemethod in the AfterNewDocument event, the Document Import Toolwould fail to import hybrid documents.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide and the BlueCielo MeridianEnterprise VBScript API Reference.

6.5 .6 Customiza t ion improvementsThe following improvements have beenmade to the customization of Meridian Enterprise:

A Sort Priority option has been added to custom commands in .NET extensions to specify the orderof custom commands in the shortcut menu of a document.

In the BrcEvent_BeforeCreate event, if the current object is a folder, the Folder object refers tothat folder. If the current object is a document, the Folder object refers to the parent folder of the cur-rent document.

A new constantAS_CONFIRM_NO_SELECTPROJECTWIZARD has been added to VBScript tomake it possible to create new documents in non-project folders.

It is now possible to retrieve additional properties of a user using VBscript.


35

Type mismatch errors occurred using the Transmittal_BeforeSelectRecipients andTransmittal_AfterSelectRecipients events when reading the SelectedRecipients parameter.

Whenworking with the VBScript editor it is now possible to save and load code to and from a file.When saving code to a file, the file name is automatically generated which includes the current date.Loading code from a file will completely replace the existing code in the editor.

A VBScript methodDocument.GetLog() has been added. This method can be used to copy the pro-ject copy comment log to the master document log when releasing the copy as a new version to themaster document.

Using VBScript it is now possible to automatically select a document type for a newly created doc-ument when only one document type is available. This can be done using the constantAS_CONFIRM_SINGLEDOCTYPE.

The order of the events that occur for the Change Document Type command have been adjusted:

1. BeforeChangeDocumentType

2. AfterChangeDocumentType

3. BeforeNewDocument

4. If a wizard has been enabled for the action it will appear at this point.

5. AfterNewDocument

For additional information, see the BlueCielo Meridian Enterprise Developer's Guide and the BlueCielo MeridianEnterprise VBScript API Reference Guide.

6.5 .7 Documenta t ion improvementsAll BlueCielo products are supplied with documentation that consists of an Administrator's Guide, aConfiguration Guide, a User's Guide, or a combination, depending on the complexity of the product.

All manuals are available in either Microsoft HTML Help (CHM format for on-screen viewing) or AdobePDF format (for on-screen viewing or printing). Most manuals are available in both formats. Manuals that areavailable in Adobe PDF format are provided in both LTR and A4 page sizes for optimal printing and are not copyprotected.



The following improvements have beenmade to the Meridian Enterprise documentation.

The following documents have been updated, expanded, and corrected:

BlueCielo Meridian Enterprise 2012 Administrator's Guide

BlueCielo Meridian Enterprise 2012 Configuration Guide


36

BlueCielo Meridian Enterprise 2012 User's Guide

BlueCielo Meridian Enterprise 2012 Developer's Guide

BlueCielo .NET SDK Reference Guide

BlueCielo Meridian Enterprise 2012 Release Notes

BlueCielo Meridian Enterprise Supported Software

BlueCielo Meridian Advanced ProjectWorkflow Module Configuration Guide

BlueCielo Meridian Advanced ProjectWorkflow Module User's Guide

BlueCielo Meridian Email Manager Configuration Guide

BlueCielo Meridian Transmittal Management Module Configuration Guide

BlueCielo Meridian Transmittal Management Module User's Guide

BlueCielo Web Parts Administrator's Guide

BlueCielo Web Parts User's Guide

All of the manuals that are available in Adobe PDF format can now be installed on the Meridian Enter-prise server by the setup programs. The documents are automatically detected by PowerUser andadded to theHelp menu for easy access. You can install other supplemental documentation asdescribed in the BlueCielo Meridian Enterprise Administrator's Guide.

The application links section of the BlueCielo Meridian Enterprise User's Guide has been considerablyrevised.

Installation checklists with related topic hyperlinks have been added to the Meridian Enterprise, Pub-lisher, Global Collaboration Framework, and Explorer administrator's guides.

The VBScript Reference appendices of the BlueCielo Meridian Enterprise Configuration Guide havebeenmoved to a new manual, the BlueCielo Meridian Enterprise VBScript API Reference.

This was done to:

Accommodate the growth of the VBScript API.

Acknowledge the VBScript API as the primary method of customizing BlueCielo products,superceding the COM and .NET APIs, which will continue to be supported.

Recognize the typical division of responsibilities and skill sets between users who configureBlueCielo products and users who customize the products using programming languages.

Make the VBScript API Reference more convenient to print alone as a hardcopy desk ref-erence.

Make VBScript information easier to find.


37

The BlueCielo Meridian Enterprise Supported Applications document has been renamed toBlueCieloMeridian Enterprise Supported Software. This was done to better reflect the supported Meridian Enter-prise modules, operating systems, database management systems, web browsers, and languagesthat are listed in the document. The document now also contains the current support life cycle status ofthe products in the BlueCielo Meridian Enterprise product suite. This information was previously foundin the BlueCielo Products Life Cycle Policy document that has been largely replaced by the BlueCieloCustomer Guide to Support Services.

The BlueCielo Meridian Enterprise Release Notes (this document) has been shortened by eliminatinginformation about versions that are no longer supported.

6.5 .8 Document Import Tool improvementsThe following improvements have beenmade to the Document Import Tool:

An option to automatically link a document being imported to a master document in the vault. This canbe used if the document being imported is a new revision of an existing document in the vault.

Support for the Microsoft Excel 2007 file format (XLSX).

Data source field names that match a Meridian property internal name or display name will auto-matically be mapped.

An option to force all imported documents to be of the same type.

Support for scopes.

In some cases, the error description was missing for some errors in the Document Import Tool log.

An option to provide a base path that is common to all relative paths. This feature is useful in caseswhere only a relative path or file names are available in the source data.

Any property that has limited values due to a property validation configuration can be assigned a prop-erty value from a lookup list that contains only valid values (With fixed value option).

Property values can be initialized using VBScript.

Supports events for documents that are imported as revisions of existing documents. These eventsare:DocWorkingCopyEvent_BeforeSubmitWCDocWorkingCopyEvent_AfterSubmitWCDocWorkingCopyEvent_BeforeCreateWCDocWorkingCopyEvent_AfterCreateWC

An option to skip already imported documents.

All settings for an import are no longer lost when selecting a different Microsoft Excel data source.

6.5 .9 Setup improvementsThe following improvements have beenmade to Meridian Enterprise setup:


38

An installation option is now provided to install components for the AutoVue Client/Server on theMeridianWeb Access server.

When running Meridian Enterprise and BlueCielo View on the same computer, uninstalling MeridianEnterprise will no longer break the BlueCielo View installation.

The Meridian Asset Management Module extensions were not included in the 64-bit version of theMeridian Enterprise setup packages.

Improvements have beenmade to the setup packages to minimize reboots.

An option has been added to the 64-bit Windows setup package to specify the location of the 32-bit cli-ent files.

Due to the fact that Bentley MicroStation is only available in 32-bit, it was not possible to select theBentley MicroStation application link when installing the 64-bit version of Meridian Enterprise.

By default, only application links for the latest three AutoCAD versions are automatically selected dur-ing the setup.

The Microsoft Visual C++ 2005 Redistributable Package is no longer required for installing BlueCieloMeridian Enterprise.

Manual registration of AutoCAD vertical applications is no longer needed.


6.5 .10 Viewer improvementsThe following improvements have beenmade to the viewer:

Version 20.1.1 of Oracle AutoVue 2D Professional is now included in Meridian.

The Navisworks Freedom viewer is now supported by the BlueCielo viewer and can be configured asthe default viewer for Navisworks files.

When using Navisworks Freedom viewer version 2012, it is necessary to add the supplied registry filemanually to the computer using the viewer for it to function as expected.

Certain Microsoft Excel documents could crash AutoVue.

Some Microsoft Excel documents would not view correctly.

The panes of the Compare window are now synchronized when viewingmulti-page Microsoft Exceldocuments.

Some Microsoft Visio files caused the viewer to crash.

If the BlueCielo Filesystem Service (AMFS) was enabled, the paths to X-refs were not always correctlyset.

Attempting to remove multiple redlines in the viewer inWeb Access could fail.


39

Certain issues with viewing an Autodesk Inventor drawing title block have been resolved.

Viewing of Autodesk Inventor 2011 files is now supported.

Searching for text in the viewer now highlights the words that were found.

URL files stored in the vault will now show the contents of the web page that is referenced by the file.

Viewing a document for which the user does not have the privilege will show the rendition of the doc-ument automatically. If the user does not have privilege to view the rendition, the native document isshown instead.

TheHotspots are visible option for the AutoVue viewer is now enabled by default.

The search feature of the AutoVue viewer now supports the keyboard shortcuts Ctrl + C and Ctrl + Pfor copying and pasting respectively.

The AutoVue Client/Server now supports the following features:

Watermarking

Hotspots

Printing


6.5 .11 Web Access ImprovementsThe following improvements have beenmade to Meridian Enterprise Web Access:

Internet Explorer 9 is supported.

The visual style has been updated and configurable styles can be customized.

The properties and viewer panes can now float on the desktop.

Most of the dialog-looking pages are now actual floating dialogs.

AHybrid Parts page now shows attached hybrid files.

It is now possible to specify a scope when publishing a vault inWeb Access.

Whenmaking a project copy of a document that includes hybrid parts, an extra menu item was some-times visible for the hybrid parts.

In certain situations, an error was shownwhen trying to view a document that had references to afolder for which the user did not have access privileges. This has been resolved by showing the doc-ument that has the missing references.

Canceling the wizard during document creation would sometimes result in an error message.


40

A limit has been set on the number of documents or folders shown on a single page to increase per-formance. This is controlled by a registry key.

Itis now possible to compare documents and document revisions inWeb Access.


6.5 .12 Web Pa rt s improvementsThe following improvements have beenmade to the BlueCielo Web Parts:

An option has been added to the Office Web Part to support Local Workspace.


41





In some cases on 64-bit Windows 7 with a 64-bit version of AutoCAD, it may have seemed as thoughAutoCAD was running in full-screenmode when all menus and toolbars where hidden. This issue hasbeen resolved.


The following additions to our support for popular CAD applications have beenmade:

AutoCAD 2012

AutoCAD Architecture 2012

AutoCAD Electrical 2012

AutoCAD Map 2012

AutoCAD Mechanical 2012.


Note These support improvements are to the corresponding CAD application links developed by BlueCieloECM Solutions. Corresponding viewer support provided by third party software such as Oracle AutoVue is notnecessarily included. For the application versions supported by the Oracle AutoVue version included in thisrelease, refer to the Oracle AutoVue website.

For a full list of the supported CAD software, see the Supported Applications document for this release ofMeridian Enterprise, consult your BlueCielo ECM Solutions Partner, or contact BlueCielo ECM Solutions Sales.

7.3 Choosing wh ich cl ien t vers ion to in s ta l l , 32-b i t or 64-b i t

Meridian Enterprise 2008a introduced 64-bit versions of the Windows desktop client applications and applic-ation links, a major step forward inmigration to full 64-bit support. However, numerous features in the applic-ations rely on components for which 64-bit versions were not yet available. Therefore, choosing which clientversion to install for a particular user depends largely on the user's need for those features. We strongly recom-mend that, unless a user has no need for any of the following features, they use the 32-bit version of the Win-dows desktop client applications until full support is provided in a future release.

Note Both the 32-bit and the 64-bit Windows desktop client applications will be installed when running the64-bit setup of Meridian Enterprise 2011 SP1. The default client will be 32-bit.



42

The 64-bit editions of the Windows desktop client applications are supported on all 64-bit editions of theMicrosoft desktop operating systems. The 32-bit editions will also work on 64-bit operating systems and run as32-bit processes.

When they were originally released, the 64-bit versions of the Windows desktop client applications had limitedsupport for the features listed in the following table. Improved support has been added in subsequent releases.The current solution for each issue is described in the following table.

Feature Solution

AutoVue viewer Until a 64-bit version of AutoVue is available from Oracle, install AutoVue Cli-ent/Server as described in the BlueCielo Meridian Enterprise Administrator'sGuide.

Visual Basic extensions Convert extensions to .NET as described in the BlueCielo Meridian EnterpriseDeveloper's Guide.

Visual Basic support DLLscalled from VBScript

Convert support DLLs to .NET as described in the BlueCielo MeridianEnterprise Developer's Guide.

Visual Basic extension prop-erty pages displayed by theAMMEDIT command inAutoCAD 64-bit versions

Remote sessions and theOffline Client

Install the Microsoft Access Database Engine hotfix described in MeridianEnterprise/TeamWork 2011 hotfixes in the Meridian Enterprise knowledgebase.

Briefcases in open standardformats


Document Import Tool Install the Microsoft Access Database Engine hotfix described in MeridianEnterprise/TeamWork 2011 hotfixes in the Meridian Enterprise knowledgebase.

Database ImportWizard(Configurator)


Global Collaboration Frame-work function calls

Global Collaboration Frame-work functions that use theGlobal Collaboration Frame-work support object in

Move Global Collaboration Framework operations from VBScript to the TaskServer.

So lu t io ns f o r 64-b i t f e a tu re l im i ta t io ns

http://extranet.bluecieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000AA4A





43

Feature Solution

VBScript

Document viewing or down-loading withWeb Access

Supported by version 2011 and higher.

Scanner support

64-bit application links AutoCAD, Autodesk Inventor, SolidWorks, Revit only. Additional support maybe provided depending onmarket demand.

CAD vertical application linkinstallation

Depending on the version, CAD vertical application links may need to beinstalled manually as described in the BlueCielo Meridian EnterpriseConfiguration Guide and Installing AutoCAD vertical application support whenthe Windows Installer Package (MSI) is used in the Meridian Enterprise know-ledge base.

So lu t io ns f o r 64-b i t f e a tu re l im i ta t io ns (con t inued )

Resolving all of these issues completely is a high priority for BlueCielo. Solutions will be made available as hot-fixes, in service packs, or in future releases. Monitor the Release Notes provided with future releases forupdated information on this issue. The information provided in this version of the Release Notes will not neces-sarily contain the latest information.

For additional background information on any of the following, see BlueCielo support for 64-bit Windows oper-ating systems in the Meridian Enterprise knowledge base:

Benefits of 64-bit support

History of 64-bit support in each Meridian Enterprise release

Limitations of the 64-bit server components

Installation notes for 64-bit versions

References to related 64-bit articles by BlueCielo and Microsoft

For instructions on installing 64-bit versions, see the BlueCielo Meridian Enterprise Administrator'sGuide.


The following improvements have beenmade to the Meridian Enterprise desktop client applications:

All hotfixes that have been created for the 2011 release are included in this Service Pack.

There was a certain situation in which it was not possible to edit a dynamic collection. This has beenresolved.

http://extranet.bluecieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A89E

http://extranet.bluecieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT00007D32


44

The document reference type was not remembered when performing a search. This has beenresolved.

Filter settings for email messages and attachments have beenmoved from the client to the Email sec-tion of the vault configuration.

The context menu of the Assembly Structure Browser now includes the appropriate master documentand project copy commands.

In some cases whenmoving a document to another location using workflow, the navigation viewwould not refresh correctly. This has been resolved.

It is now possible to import from an Excel or Access file using a 64-bit client.


The following are new briefcase events:

BrcEvent_BeforeIncludeFile

BrcEvent_BeforeWriteFileProperty

BrcEvent_AfterIncludeFile

A DWORD registry valueDoNotRerouteRefs2Master has been added to control how referencesare handled when releasing a project copy to the master document:

HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client

A String registry value BriefCaseOpenFormat has been added to allow the use of the MDB formatfor briefcases. This option only works for 32-bit versions of Windows. The value can be set to .mdb.

HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings

When using Managed Change, it was not possible to convert a folder to a project. This has been fixed.

The following new properties are available for retrieving user information with VBScript:

User.Description

User.Initials

User.Title

User.OrganizationalUnit

User.Manager

A new VBScript method Folder.GetUsersWithRole(<Role>) is now available to retrieve a list ofusers with a certain role.

For more information about these improvements, see theBlueCielo Meridian Enterprise Administrator's Guideand theBlueCielo Meridian Enterprise Configuration Guide.


45

7.6 Managed Change improvements

If an assembly had parts under change inmultiple projects, it was possible to release the assembly.This has been corrected. Assemblies that have parts in other projects cannot be released.


AutoVue 2D Professional version 20.0.1 is included in this release. More information about this versioncan be found on the AutoVue website.

In some cases, it was not possible to view certain PDF files, resulting in the client application hanging.This has been resolved.

Certain Excel files did not view accurately. Improvements have beenmade to improve accuracy.

There were some issues when viewing specific Visio files using AutoVue. This has been resolved.

When using AMFS, X-Ref paths that contained a comma were not resolved correctly. This has beenresolved.

There were some issues when trying to remove several markups in a single delete action. This hasbeen resolved.

Viewing the title block of an Autodesk Inventor DWG file was not possible. This has been resolved.

Autodesk Inventor 2011 files are now supported by AutoVue.

Certain Excel files caused the PowerUser to crash when viewing or creating thumbnails. This has beenresolved with the inclusion of AutoVue 20.0.1.

In AutoVue Web Version, words that made up search criteria were not highlighted during a search.This has been resolved.

There were some issues when viewing certain DWG files with fills. This has been improved.

While trying to invoke the Pan and Zoom commands for some PowerPoint files, the viewer wouldcrash. This has been resolved.



46

8 What 's New in Meridian Enterpr ise 2011


8.1 64-b i t support

64-bit editions of the following components are provided with this release:

EDM Server service

Hypertrieve database engine

Configurator

Web Access

License Server

Meridian Enterprise is now fully 64-bit compliant with the exception of the BlueCielo viewer, which relies onAutoVue 2D Professional, for which a 64-bit version is not yet available.

Vault external tables and the user accounts database are now also stored in MS SQL Server Compact Edition on64-bit computers similar to Local Workspace as described in "Operating system support improvements."

Note The 64-bit edition of the EDM Server service, although fully tested, is considered an early adopter'srelease in this version of Meridian Enterprise. We highly recommend that if you deploy this edition that you doso in close cooperation with your BlueCielo Solutions Partner or BlueCielo ECM Solutions.

The 32-bit edition of the server components will continue to be supported. A 64-bit server components setupprogram is also provided for those customers who want to upgrade prior installations without deploying the 64-bit EDM Server service.

Related information

Vaults unavailable after installing Meridian Enterprise 64-bit edition

Operating system support improvements

AutoVue known problems

Vault incompatibility betweenWindows operating system versions

Unsupported features of 64-bit clients

Meridian Enterprise 64-bit setup

AMFS andWindows Search incompatible on 64-bit servers

Cannot register Asset Management Module extensions in 64-bit Configurator

Windows Server 2008 setup


47

Windows Vista setup

Web Access 64-bit support


The following topics described the changes and improvements to the existing functionality in this release.

8.2 .1 App l ica t ion l ink improvementsThe following application link improvements have beenmade:

Two new settings SkipDocTypesDialog and SkipSelectionDialog have been added to theMS Outlook link configuration to suppress the display of the attachment document type and attachmentselection dialogs when saving attachments in a vault.

When an email message or attachment is saved in a vault, the MS Outlook link now checks whether adocument with the same name exists. If one exists, the link also checks that the files are identical. Ifthey are identical, the import is aborted. If they are not identical, the user is prompted to replace thecontent of the existing document.

The MS Outlook link now allows document type and destination folder selection for individual emailmessages when storing them in a vault.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide and BlueCielo Meridian Enter-prise User's Guide.

8.2 .2 CAD app l ica t ion support improvementsThe following additions to our support for popular CAD applications have beenmade:

Autodesk Inventor 2011 SP1

Autodesk AutoCAD P&ID 2011 SP1

SolidWorks 2011

For a full list of the supported CAD software, see the Supported Applications document for this release ofMeridian Enterprise, consult your BlueCielo ECM Solutions Solution Partner, or contact BlueCielo ECM SolutionsSales.

8.2 .3 Cl ien t improvementsThe following improvements have beenmade to the Meridian Enterprise desktop client applications:

An Expand All command has been added to the folder shortcut menu of the PowerUser and Office Cli-ent.

A new DWORD value AutoExpandOnDrag has been added to the following registry key. When setto 1, it causes folders to automatically expand when a document is dragged over them so that the doc-ument can be dropped on a sub-folder:

HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings


48

A new option Include drawing and presentation files has been added to the Find dialog to bet-ter support Autodesk Inventor.

A new optionClear credentials after logging off has been added to the Preferences page ofWeb Access to improve security.

A new import optionAs New Revision has been added to the document shortcut menu that is shownwhen a file from outside the vault is dropped onto a vault document.

A new optionCreate an empty document if file to import doesn't exist has been added tothe Document Import Tool to enable importing asset tag records into a vault to support the MeridianAsset Management Module.

A new option Import existing documents to the specified folder has been added to the Docu-ment Import Tool. This option specifies a folder to import documents into that have the same nameand revision as specified by the Property in the vault that identifies document revision andDatabase field that identifies revision options.

Quick Find-like query parameters may now be specified on the command line described in the fol-lowing table:

Argument Description

/AMFS The vault in which to find the objects specified by the other command line arguments. Use thefollowing syntax:

/AMFS=M-<ServerName>,D-<DatastoreName>,S-<VaultName>

For example:

/AMFS=M-EngServer,D-MyCompany,S-BigVault

/O The ID of the object where you want to application to open. To specify the ID of a document,use its Document ID value. To specify the ID of a folder, use the Parent Folder ID valueof a document or sub-folder contained in the folder. If this argument is specified, do not spe-cify the /DT or /PF arguments.

/DT Document type search criteria specified as a list of the internal or display names of the doc-uments types in which to search.

For example:

/DT="GenericDocument,Drawing,EmailDocType"

This argumentmay be specified in combination with the /PF argument. If this argument isspecified, do not specify the /O argument.

/PF Property search criteria specified using the following syntax:

/PF=<PropertyName>,<PropertyValue>,<Operator>


49

Argument Description

For example:

/PF="DrawingNumber,D-09-12345,OP_STARTWITH"

TheOperator argument is specified as a shortened version of one of the IC_OPERATOR constants that can be found in the Constants branch of theObject Browserin the Meridian Enterprise VBScript Editor. The default isOP_EQUALS.

This argumentmay be specified in combination with the /DT argument. If this argument isspecified, do not specify the /O argument.

The results of opening the vault with command line arguments will be shown in a view namedStartup Search.


8.2 .4 Con figu ra t ion improvementsThe following improvements have beenmade to vault configuration:

A new settingRemove has been added to briefcase format configuration to specify a command linefor third-party programs to remove documents from a briefcase file.

Two new settingsOutgoingRefType andRemoveMetadataBeforeSent have been added tobriefcase template configuration. The first specifies the reference type to relate outgoing transmittalsheets to transmittal briefcases. The second removes documentmetadata from the transmittalbriefcase before sending to an email recipient.

A new setting IncludeTransmittalSheet has been added to briefcase template configuration toallow preventing the transmittal sheet from being included in a transmittal briefcase.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide.

8.2 .5 Customiza t ion improvementsThe following improvements have beenmade to the Meridian Enterprise customization features:

A new VBScript methodDelete has been added to theDocument object that deletes the current doc-ument.

The -deployperuser command line argument of the PackageBuilder tool can be used to deploy.NET user interface extension packages to only the current user. This makes deploying the packageseasier in high security environments where users are not administrators of their own computers. Formore information, see the BlueCielo Meridian Enterprise .NET API Reference Guide in BlueCieloMeridian Enterprise Developer's Guide.


8.2 .6 Opera t ing system support improvementsThe following operating system support improvements have beenmade:


50

The BlueCielo IFilter based on Oracle AutoVue has been improved to supportWindows Search as wellas Indexing Service. Windows Search is supported in 32-bit mode on 64-bit computers, however.


Related information

AMFS andWindows Search incompatible on 64-bit servers

64-bit support

Vault incompatibility betweenWindows operating system versions

8.2 .7 Web Access improvementsThe following improvements have beenmade to the Meridian Enterprise Web Access:

A new optionClear credentials after logging off has been added to the Preferences page toimprove security.

Scopes can now be selected inWeb Access.

A new Find in this folder command has been added to allow searching within a folder and option-ally, its sub-folders.

Quick Search now searches document content as well as metadata.



51

9 What 's New in Meridian Enterpr ise 2010


9.1 Emphasi s on usab i l i ty

The major emphasis of Meridian Enterprise 2010 is improved usability. Over 150 improvements requested bycustomers have beenmade. The major enhancements to usability in this release include:

Independent windows. Each of the Shortcuts, Properties, andViewer windows may be draggedinto position anywhere on the Windows desktop, docked to any side within the main Meridian windowor each other's window, and automatically hidden or pinned open. The windows also now work fullyindependent of each other. For example, in prior releases a user could not manipulate the viewer win-dow while editing properties in the Properties window. The windows are no longer dependent onone another.

Application looks. Many different visual styles can now be selected that alter the user interface style tomatch the most common standards regardless of the version of the computer's operating system.

Modern icons. The toolbar andmenu icons have been replaced withmodern artwork to complete theuser interface update.

Configurable toolbar. One toolbar is available that can be configured by a system administrator toshow different toolbuttons for each scope.

For more information, see the BlueCielo Meridian Enterprise Configuration Guide. Many additional enhance-ments to usability have beenmade that are listed in the other topics in this section.

9.2 Da ta L ib ra ry

The Meridian Enterprise Data Library is an optional component that can be installed on the Meridian Enterpriseserver. It provides a read-only, synchronized replica of the documentmetadata of one vault. The metadatacan be store in a SQL Server or Oracle database. You can use the Data Library as a data source for your favor-ite reporting application or for more complex reports than can be configured in Meridian Enterprise. You canconfigure reports against the Data Library using any application that supports SQL Server or Oracle as a datasource, for example, MS SQL Server Reporting Services or SAP Crystal Reports.


9.3 Scopes

The concept of client application scopes has been added. A scope is a configurable, named set of vault objectsand functions that limit what a user may see and do in a vault. Scopes are defined by a system administratorandmay be selected by users based on the users' needs. For example, a vault used for managing facilitiesmight define scopes for as-built documents, design projects, archived documents, or maintenance man-agement. A vault used for managing AEC documents might define a different scope for each customer. And a


52

vault used for manufacturing documents might define different scopes for standard parts, active projects, andinactive projects. A configurable toolbar is available for each scope.

For more information about scopes, see the BlueCielo Meridian Enterprise Configuration Guide and BlueCieloMeridian Enterprise User's Guide.

9.4 Sea rch enhancements

Many improvements in search functionality have beenmade, including:

The Find command has been added to the folder shortcut menu to allow searching within a selectedfolder.

New options have been added to the Find command to add search results to theMy SearchResults collection.

The Find commandmay now be restricted to search within a selected folder and its sub-folders.

When searching with the Find command on a property that is associated with a lookup list, the Finddialog now shows the lookup list values for selection so that you do not need to know the precise valueto enter.

Property searching has been improved to support percent symbols in search values.

Full text searching has been improved to work for sub-strings and non-alphanumeric characters.



The following topics described the changes and improvements to the existing functionality in this release.

9.5 .1 Admin i s t ra t ion improvementsThe following improvements have beenmade to Meridian Enterprise administration:

The MS Access database format (.mdb) has been replaced by the XML format in the Vault Archive Wiz-ard. For more information, see "Operating system support improvements."

BlueCielo user groups may be assigned to security roles in vaults to improve performance in envir-onments where domain security authentication negatively effects performance.

BlueCielo users may now be assigned another user as their manager in the Administrator utility.

The BlueCielo iFilter based on AutoVue 2D Professional is now installed along with the server com-ponents.

Individual licenses may be deleted in the Administrator utility.


53

This Meridian license file format has changed and is not downward-compatible. The License Serverwill require the creation of a new license file after installation of this release.

Registry information for reserved licenses andWeb Access Find form customization are not removedif the product is uninstalled. This makes it more convenient to reinstall Meridian on the computer.

The Meridian Asset Management Module client extensions can now be installed with the Meridiansetup program to ease the deployment of the module. In this release, these extensions are providedfor evaluation and testing purposes only and are not recommended for production use.


9.5 .2 App l ica t ion l ink improvementsThe following application link improvements have beenmade:

Support for MS Office 2010 has been added.

The sizes of Outlook Link dialogs are now preserved between sessions.

A new Inventor Migration Tool is provided for upgrading Autodesk Inventor files.

The SolidWorks link may now be configured to hide specified Navigation views in the SolidWorksbrowser.

A new value for the RedrawTitleBlocksOnUpdate setting has been added to the AutodeskInventor link. When set to 2, the link will only redraw title blocks (by launching Autodesk Inventor)when the document is transitioned to the Released state.

The AutoCAD Link now supports underlay X-Refs.

The AutoCAD Link now uses RealDWG 2011, which is installed by the setup programs.

A new client DWORD registry value has been added to configure the compatibility of the AutoCAD Linkwith drawings created by RealDWG, which is used by Autodesk Inventor. For more information, seetheBlueCielo Meridian Enterprise Administrator's Guide.

A new configuration option has been added to the SolidWorks link to hide specified Navigation views inthe SolidWorks browser.


9.5 .3 CAD app l ica t ion support improvementsThe following additions to our support for popular CAD applicationshave beenmade:

Autodesk AutoCAD 2011

Autodesk AutoCAD Electrical 2011


SolidWorks 2009 SP 5.1 and 2010 SP 1 to SP 2.1


54

Autodesk Revit 2010 64-bit versions (Architecture, Structural, and MEP)

MicroStation V8i SELECTseries 1

For a full list of the supported CAD software by all recent releases of Meridian Enterprise, consult yourBlueCielo ECM Solutions Solution Partner or contact BlueCielo ECM Solutions Sales.

9.5 .4 Cl ien t improvementsThe following improvements have beenmade to the Meridian Enterprise client applications:

The property values of two documents may now be compared in addition to graphical comparison.Users with the Set Property Value privilege may also update the properties of one document fromthe values of the other document.

The Document Import Tool has been changed such that when a file is not found in the location spe-cified in the import database, an error is added to the import log instead of creating an empty doc-ument as was done previously. To create an empty document, leave the path field empty.

When copying a document inWeb Access, if wizard pages are shown, the selected document becomesthe new document instead of the original document.

Hybrid documents may now be created in Offline Mode with the application links. However, hybrid rela-tionships cannot be created with documents that exist only in Local Workspace and do not yet exist inthe vault. Such documents must be synchronized with the vault first so that they are assigned doc-ument types that define the hybrid part relationships.

Prior revisions of hybrid document parts may now be seen in the Show Revisions dialog. The revi-sions of the hybrid document parts that are shown are the revisions that were effective when the maindocument part was released. Prior to this release, hybrid document parts were always associated onlywith the current revision of the main document. This new feature enables more effective product con-figurationmanagement.

The positions of columns in the Show Revisions dialog is now saved between sessions. The pos-itions are saved per vault.

A new commandAdd to My Search Results has been added to the document shortcut menu tomake it easier to add documents to personal static collections.

Due to the lack of 64-bit OLE DB drivers fromMicrosoft, the MS Access format option for reports andopen standard briefcase metadata has been removed from the 64-bit client applications. Documentmetadata created in open standard formats using a Meridian 64-bit version is now stored inXML format by default.

The URL of documents is now shown at the bottom of the General page inWeb Access. The URL canbe copied to the Windows Clipboard and pasted into other applications (for example, email) in order toprovide a hyperlink to the latest released revision of the document.


55

The dialog that displays the workflow diagram of a document or folder when the user clicks theStatus hyperlink on theDocument or Folder property page now lists the interlock status of out-going workflow transitions.

Property value filters may now be defined for theMy Search Results, static collection, and dynamiccollection views similar to defining filters in MS Excel.

The Unlock Master Document command has been added to the Managed Change feature set ofMeridian. The command can be used to unlock master documents for which the project copy doc-uments have been deleted, for example.

A Go to command has been added to a shortcut menu that is available for documents in the ShowReferences dialog.

The references of a master document being copied to a project folder may now be individually selec-ted for copying to the project.


9.5 .5 Con figu ra t ion improvementsThe following improvements have beenmade to vault configuration:

Multivalue string properties are now supported. A configurable separator character may be defined,which causes the property to display a drop-down combobox control on property pages from whichusers can select multiple values read from a lookup list, table, or other source.

Options have been added to the Validation page of custom properties to specify a VBScript expres-sion that can be used to validate a user's input that is selected from a lookup list generated by anotherVBScript expression.

VBScript expressions for a property are now validated when exiting edit mode in the Configuratoreven if the validation options are disabled.

Searching in the VBScript editor has been improved to use highlighted text as the default text for newsearches.

A new optionUse shared transaction has been added for external property pages to allow them tobe used as wizard pages.

New privileges have been add to the vault configuration to control access to table data: Get entries,Update entries, Add entries, Delete entries.

Note The new privileges are not available for existing tables immediately after upgrading to thisrelease. To add the new privileges, click the Privileges button on the table's General page in Con-figurator. The new privileges are available for new tables that are created with this release or higher.

If multiple Configurator sessions are active, only the first session is allowed to save changes. All othersessions are read-only and a warning is shown.


56

The layout of property page panel elements may now be in a dynamic array with the visibility andbehavior of each element controlled by the value of a specified property. This makes defining one prop-erty page useful for multiple different document types. The controlling property can be used to dis-tinguish between document types, workflow states, user security roles, and other conditions that yourequire. Convenient controls are also provided to set a fixed field width and VBScript expressions tocontrol the visibility and read-only behavior of multiple panel elements at one time.

Registry keys that control the icon shown for and the command line that is executed by documentshortcuts returned by the Vault.ComposeURL method are now installed by the setup programs.

Table entries may now be sorted on one or more columns.

Table column names may now be edited directly in Configurator.

The initial state of documents that use workflow definitions may now be selected in Configurator andthe workflow diagram is shown.

Options have been added to briefcase configuration to export and import thumbnail images inbriefcases.


9.5 .6 Customiza t ion improvementsThe following improvements have beenmade to the Meridian Enterprise customization features:

Custom VB extensions compiled with the 2009 libraries were compatible with Meridian Enterprise 2009and higher but were not compatible with 2008a and lower. This has been fixed and extensions com-piled with the 2010 libraries are compatible with all lower versions.

The Meridian Enterprise .NET libraries are installed on client computers by default to simplify deploy-ment of custom .NET extensions.

New VBScript methods: CreateHybridPart,DeleteHybridPart,GetHybridPart,ImportHybridPart, SaveToFile, LoadFromFile, LoadFromTemplate and propertyHybridParts were added to theDocument object to support conversion of documents to hybridparts.

TheDocument.LockLWS andDocument.UnLockLWSmethods now return string values.

A new VBScript method namedGetPropertyNames was added to the Vault object to retrieve thenames of all properties in a given property set.

New VBScript events, properties, and constants for customizing the Meridian Transmittal ManagementModule.

The VBScriptBatch.IsFirstInBatch property now ignores folders that are selected along with abatch of documents and the property is set for the first valid document in the batch.


57

A new VBScript eventDocGenericEvent_PrepareCommand, propertyBatch.ProcessAsBatch, andmethodBatch.AddDocuments were added to support pro-grammatic building of batches of documents and processing batches by custom commands.

A new VBScript function FindDocuments has been added for searching for documents from withinVBScript.

The functionality of the Client.ImportDetails property has been extended to wizard page propertyvalidation expressions.

A new VBScript methodVault.RunShellCommand has been added to simplify executing commandline programs.

A new VBScript eventAfterReplaceReleased has been added to allow for updating a documentafter a document that replaced it has been released from a workflow.

A new VBScript methodDocument.SetModified has been added to change the internalModifiedproperty.

The VBScript property Document.MasterDocument.LockingProjectCopy was added inrelease 2009a.

The VBScript eventDocGenericEvent_PrepareCommand event now occurs after a title block isread during batch import by the Document Import Tool.

The DocCADLink event procedures now occur in Remote mode.


9.5 .7 Opera t ing system support improvementsThe following operating system support improvements have beenmade:

The Windows Installer packages for Meridian now support User Account Control (UAC) except whenupgrading from release 2009a or earlier as described in "Windows Server 2008 setup" and "WindowsVista setup."

By default, Meridian Enterprise client applications store Local Workspace tracking data in anMS Access-compatible database using the MS Jet database engine. To better support the 64-bit Win-dows operating systems, which do not include a 64-bit version of MS Jet, Meridian Enterprise nowincludes an option to install Microsoft SQL Server Compact Edition as a replacement, which is sup-ported on 64-bit Windows operating systems. SQL Server Compact Edition is installed and used bydefault for all new Meridian Enterprise 64-bit installations. Upgrading to release 2010 on a 64-bit com-puter will retain existing MS Jet databases used for Local Workspace. By default, 32-bit installationswill continue to use MS Jet databases but SQL Server Compact Edition is available as an option duringinstallation. To enable the use of SQL Server Compact Edition requires a registry setting that isdescribed in the BlueCielo Meridian Enterprise Administrator's Guide.

Note Errors will result from using SQL Server Compact Edition for a Local Workspace on a UNC ormapped drive location. Use local drives only.

See also "Vault incompatibility betweenWindows operating system versions."


58

For more information, see the BlueCielo BlueCielo Meridian Enterprise Administrator's Guide.

9.5 .8 T ransmi t ta l Management Modu le improvementsSignificant improvements have beenmade to Meridian Transmittal Management Module:

Submittal management features for importing and linking to transmittals.

Submission document features for importing and linking to transmissions.

Transmittal and submittal properties.

For more information, see the Meridian Transmittal Management Module User's Guide.

9.5 .9 Viewing improvementsThe following improvements have beenmade to the BlueCielo viewer:

The BlueCielo viewer has been improved to display external references even if they are moved to a dif-ferent folder in the vault.

The BlueCielo viewer now supports the AutoVue viewer's Search (with result highlighting, for contentindexed vaults only) andConvert commands. Converted documents may be saved in the vault. Fordetails and supported file formats, see the documentation for AutoVue products available on theOracle web site.

The BlueCielo viewer now uses the AutoVue viewer's hyperlink technology for creating hotspots thatcan link to vault documents or tag objects (Meridian Asset Management Module only). Creating hot-spots is not supported by Web Access. For more information, see theBlueCielo Meridian EnterpriseUser's Guide and theBlueCielo Meridian Asset Management Module Configuration Guide.

The BlueCielo viewer now supports the AutoVue viewer Explode, Section, Perspective, and other3D commands when viewing 3D formats.

The BlueCielo viewer now supports the AutoVue Client/Server (Java applet), which can be deployedfor zero footprint web clients and Meridian 64-bit users. For more information about Meridian supportfor the AutoVue Web Version, see theBlueCielo Meridian Enterprise Administrator's Guide.

For more information about the BlueCielo viewer, see the BlueCielo Meridian Enterprise User's Guide.

http://www.oracle.com/technology/products/autovue/index.html


59

10 Known Problems

10.1 App l ica t ion L inks

10.1 .1 Cannot save MS Word 2010 documentsMS Word 2010 documents might randomly fail to save to folders in vaults that do not use Local Workspace.This issue appears to be limited to Windows 7 client computers and Meridian 2009 and higher. Other versionsof MS Office andWindows do not appear to be affected.

There is no practical workaround yet.

A solution will be provided as soon as possible.

10.1 .2 Au toCAD P&ID l imi ta t ionsFollowing are known problems related to AutoCAD P&ID:

Opening or saving files to anMeridian Enterprise vault with AMFS enabled can generate the error"Drawing file is write protected" if the Meridian Enterprise client, EDM Server, and AMFS service are allon the same computer. The error does not occur when Local Workspace is enabled.

The AutoManager File System (AMFS) does not work (vault drive mappings are inaccessible and foldercontents invisible) after saving a drawing from AutoCAD P&ID, while AutoCAD P&ID is still open, and ifthe Meridian Enterprise client and server are running on the same computer.

An unhandled exception can occur after viewing a project's properties from anMeridian Enterprisevault with AMFS enabled. Restart AutoCAD P&ID to reopen the project.

10.1 .3 Sol idWorks references not crea ted a fter d rag-rand- d ropAfter importing a SolidWorks assembly through drag-and-drop, the way to create the references is with theSynchronize References From File command in the PowerUser. Before doing that it is necessary to tem-porarily rename the directory where the source assembly is located.

10.1 .4 Mer id ian En terp r i se Rep lace in Inven torIn Inventor there are two commands available in the context menu of a part or sub-assembly: Meridian Enter-prise Derive, and Meridian Enterprise Replace. Normally the Meridian Enterprise Replace command is disabled.It will only be enabled if there is a replacement for the selected document, and that replacement was notloaded when the assembly was opened.

10.1 .5 Synch ron izing Sheet Set Propert ies and ReferencesWhen synchronizing properties or references of an AutoCAD sheet set file (.dst), the error One or morelibraries that are needed to access document data are not found can occur if the viewer pane isactive in the PowerUser. This can happen if in the viewer options for the AutoCAD viewer the Use ObjectDBXoption is enabled. As a workaround, clear the Use ObjectDBX option.


60

10.1 .6 Viewing Au toCAD drawings in App l ica t ion In teg ra t ionWhen opened from within AutoCAD, the Application Integration dialogmay hang when trying to view anAutoCAD drawing. There is no knownwork around.

10.1 .7 Au todesk Inven tor rema ins in memory a fter t i t leb lockupda teWhen the registry value RedrawTitleBlockOnUpdate is enabled to force Autodesk Inventor to redraw thetitleblock of an IDW after a property update, Autodesk Inventor can remain inmemory after the update hascompleted.

There are two knownworkarounds:

Start Autodesk Inventor before performing the property update.

Set the TerminateInventor11 value to 1 in the following registry key to automatically terminateAutodesk Inventor after the update has completed:

HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManagerMeridian\CurrentVersion\InventorLink

10.1 .8 F i le error when synch ron izing Inven tor referencesWhen using the Synchronize References From File command in PowerUser, a Specified file cannotbe opened message can appear. This can happen if Inventor View is used for viewing the files and the reasonis a conflict between two Inventor components. The solution is to retry the operation, if necessary with theviewer pane in the PowerUser disabled.

10.2 Cl ien t Funct iona l i ty

10.2 .1 Jagged iconsSome icons may appear jagged or missing when the Windows text size is configured to more than 100% of nor-mal.

10.2 .2 Open ing the shortcu t menu on a folderWhen the focus in PowerUser is set to a folder or document and you directly right-click (open the shortcutmenu) on a folder, there may be a slight delay before the menu is shown completely. This is due to the eval-uation of access rights for the current user.

10.2 .3 Open ing MS Office 2007 temp la tes on Vis taThe error Access is denied can occur when opening MS Office 2007 templates (*.xlt, *.xltx, *.dot, *.dotx)from PowerUser when User Account Control (UAC) is enabled. The error occurs when opening the files bydouble-clicking or with theOpen in Application toolbutton, but not with the document shortcut menu.


61

10.2 .4 Bu i ld ing report s w i th MS Word temp la tes on Vis taThe error Access is denied can occur when building reports that use MS Word 2007 templates (*.dotx) fromwithin PowerUser when User Account Control (UAC) is enabled. The error does not occur with templates savedwith the extension .dot.

10.2 .5 Open ing HTML fi les on Vis taThe error Access is denied can occur when opening HTML files (*.htm) from PowerUser when User AccountControl (UAC) is enabled and Internet Explorer is the default browser. The error occurs when opening the filesby double-clicking or with theOpen in Application toolbutton, but not with the document shortcut menu.

10.2 .6 Unsupported fea tu res of 64-b i t cl ien t sThe unsupported features of the 64-bit Windows clients (PowerUser, Office Client, and Application Integration)in this release are:

AutoVue viewer (not available)

Visual Basic extensions

Visual Basic support DLLs called from VBScript

Visual Basic extension property pages displayed by the AMMEDIT command in AutoCAD 64-bit ver-sions

Remote sessions and Offline mode

Briefcases in open standard formats

Document viewing or downloading withWeb Access

Scanner support

Document Import Tool

Database ImportWizard (Configurator)

Global Collaboration Framework function calls

Global Collaboration Framework functions that use the Global Collaboration Framework support objectin VBScript. This issue can be worked around by moving Global Collaboration Framework operationsfrom VBScript to the Task Server.

10.2 .7 Semicolon in folder namesThe viewer is unable to find external references of documents that reside in a folder that contains a semicolon(;) in the folder name.

10.2 .8 Windows XP Serv ice Pack 2 and uns igned extens ionsMicrosoft has changed the default security settings for Internet Explorer inWindows XP Service Pack 2 so thatunsigned executable files can no longer be downloaded from the Internet. Because Meridian Enterprise usesthe Internet Explorer mechanism to download extensions from the server, this change also impacts Meridianinstallations. There are a number of ways to resolve this issue:


62

Relax theDownload unsigned ActiveX controls setting in the Internet security zone. Thismethod is not preferred.

Add the Meridian server to the Trusted sites security zone.

Obtain a Code Signing Digital ID from Verisign to digitally sign your own extensions.

10.2 .9 Open ing Au toCAD assemb l ies a fter importAfter importing an AutoCAD assembly in Meridian Enterprise, opening the assembly for the first time inAutoCAD, AutoCAD Mechanical, or Mechanical Desktopmay not resolve the external references correctly. Toprevent this, manually launch AutoCAD before opening the assembly. After saving the assembly, subsequentopening of the assembly will work as expected.

The reason is that in this situation the Meridian Enterprise AutoCAD link is not yet loaded by AutoCAD when thedrawing is being opened. Once the assembly is saved by AutoCAD while the Meridian Enterprise Link is loaded,information is written in the drawing which instructs AutoCAD to load the Meridian Enterprise Link as soon as itopens the drawing.

10.3 Customiza t ion

10.3 .1 Recomp i led extens ions a re not backward compat ib leA Visual Basic user interface extension compiled with Meridian 2009 components cannot be registered in vaultsrunning earlier versions of Meridian software. If necessary, recompile the extension using the same Meridianversion as the destination vault.

For more information, see Customization improvements.

10.3 .2 Empty d rop- down l i s t s for p ropert ies in the F ield - Pa thdefin i t ionDrop-down lists for properties that appear on property pages or wizard pages can be unexpectedly empty if allof the following conditions apply:

The property is specified as a level of the vault's Field-Path definition.

The property is bound to another property in a different property set (not Custom), such as defined ina user interface extension.

The List of existing values for this property option is enabled on the Validation page of theproperty definition in Configurator.

Possible workarounds include:

Using properties that are only defined in the Custom property set.

Validating input using a lookup list of acceptable values instead.

http://www.verisign.com/products-services/security-services/code-signing/digital-ids-code-signing/index.html


63

10.4 Server Funct iona l i ty

10.4 .1 Mer id ian Admin i s t ra tor empty and un respons iveBy default, Meridian Enterprise Administrator relies on SQL Server Compact Edition being installed on 64-bitcomputers to store the user accounts database. If it is not installed or the ConnectionString registry settingis not set correctly, the Meridian Administrator window will be empty and unresponsive when it is launched. Toresolve this, either install SQL Server Compact Edition or set the ConnectionString registry setting. Formore information about installing SQL Server Compact Edition or the ConnectionString registry setting, seeBlueCielo Meridian Enterprise Administrator's Guide.

10.4 .2 Vau l t incompat ib i l i t y between Windows opera t ing sys-tem vers ionsVaults created by older versions of Meridian (up to version 2008a) are not compatible with upgrades of the Win-dows operating system running on the Meridian server. This issue affects server operating system upgrades aswell as vaults moved or restored to a new server with a different operating system version. The reverse is alsotrue; vaults are not compatible with downgrades of the Windows operating system running on the Meridianserver. The reason is Windows API sorting functions that support National Language Support (NLS) changebetween eachWindows version (includingWindows XP, Windows Server 2000, Windows Server 2003, Win-dows Server 2008, Windows Vista, andWindows 7 at a minimum). Technical information about this issue canbe found in this MSDN article: http://msdn.microsoft.com/en-us/library/dd464640%28VS.85%29.aspx.

Vaults created by newer versions of Meridian (version 2008a SP1 and later) are also affected by this issue butthe operating system version and NLS version information are stored in the vault and a check of this inform-ation is performed in the software that will prevent the vault from opening on a different operating systemunless the vault is properly upgraded as described below. A vault restored from a backup that was created onone Windows version to a server running a differentWindows version will be invisible and an error added tothe Application event log.

Warning The only way to safely transfer an existing vault from a computer running one Windows version toanother version is to import the vault from the computer running the first operating system into a new vault ona computer running the second operating system. After import, no further action is necessary. For informationon "Access denied" errors that can occur when importing vaults between servers running different versions ofWindows, see http://www.cyco.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A8CE. For inform-ation on the vault corruption that can occur if a vault is not upgraded properly, see http://www.blue-cieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A91E

Note Windows Vista andWindows 7 are not supported by BlueCielo as a production quality server platformsand should be used for evaluation and demonstration purposes only.

The following table lists the most common scenarios involvingWindows Vista andWindows Server 2008 wherecompatibility problems can occur and the corresponding solutions.

http://msdn.microsoft.com/en-us/library/dd464640(VS.85).aspx

http://www.cyco.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A8CE

http://www.bluecieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A91E


64

ScenarioInnoCieloVersion

Solution

Upgrade server oper-ating system

Any Import existing vaults into new vaults.

Upgrade InnoCielo To 2008aSP1 or later

Existing vaults must be modified with a tool available from BlueCieloin the Meridian knowledge base article "Vault incompatibility betweenWindows operating system versions."

Upgrade server oper-ating system andMeridian at the sametime

To 2008aSP1 or later

Import existing vaults into new vaults.

Create a new vault On 2008aSP1 or later

None required, but vaults will not be downward compatible to pre-vious Windows versions. Downgrade the vaults by importing existingvaults into new vaults after installing the software downgrade.

Warning When importing vaults in these scenarios, the source vault must be hosted on the Windows ver-sion under which it was created and the target vault must be hosted on the targetWindows version. Therefore,it is not possible to upgrade a server operating system in-place (on the same computer) and two computersmust be used.

10.4 .3 Con ten t indexing vau l t s w i th non-Western cha racternamesCreating a content indexing catalog for a vault with a name containing non-western characters, for exampleRussian, causes the Indexing Service to stop responding with 100% CPU usage. The only knownworkaroundat this time is to use only western characters for the vault name.

10.4 .4 Revi s ion number cu t offWhen using a VBScript expression to calculate the revision numbers on a transition in a workflow definition, therevision number can be lost on the next revision of the document. This can happen when the revision numbercontains the same separator character as the version numbering scheme of the document type. To workaround this problem, make sure that the separator character in the expression is different from the separatorused in the document type's version numbering scheme.

10.4 .5 Some priv i leges do not work in workflow defin i t ion sta tesThe following privileges do not work when a document is in a workflow definition state:

Document

Attach Hybrid Parts

Draft Print

Add to briefcase

http://www.bluecieloecm.com/extranet/Meridianknowledgebase.nsf/DBUI/NT0000A8A6


65

Workflow

Change Manager

10.5 Setup

10.5 .1 AMFS not cert i f ied by MicrosoftAs one requirement for its Microsoft Gold Partner certification, BlueCielo ECM Solutions submits each release ofMeridian Enterprise for rigorous testing by an independent third party to ensure that it conforms to industry-standard best practices. One of the requirements for that testing is that hardware device drivers must be testedby the Microsoft Windows Hardware Quality Labs or be documented as untested. The BlueCielo File SystemServer (AMFS)service is one such device driver.

The AMFS service is thoroughly tested by BlueCielo ECM Solutions prior to each release and it has been provenin production usage by thousands of customers for many years. However, as of this release, the AMFS servicehas not yet been submitted for testing by the Microsoft Windows Hardware Quality Labs and is therefore notcertified by Microsoft.

10.5 .2 F i le in format ion miss ingFollowing is a list of executable files that are included with Meridian Enterprise for which the software man-ufacturer did not provide Publisher, Product, or Version file property values. All Meridian Enterpriseexecutable files developed by BlueCielo ECM Solutions contain this information. The file paths may differdepending on the location of these files on your computer.

Autode sk

C:\Program Files (x86)\Common Files\Autodesk Shared\acgixclipper16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixhiddenline16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixviewdefinition16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixwhipview16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\axdb16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\dboleutl16.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AdImaging.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AdImagingRes.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\dboleutl18.dll

Conte x

C:\Program Files (x86)\Common Files\Cyco Shared\CTX_AS32.DLLC:\Program Files (x86)\Common Files\Cyco Shared\HLSI.DLL

Orac le

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\libpng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\UninstAv.dll

Mic ro so f t

C:\Windows\REGTLIB.EXE


66

10.5 .3 Uns igned execu tab lesFollowing is a list of executable files that are included with Meridian Enterprise that are either unsigned by thesoftware manufacturer or the files have been signed with a test certificate. All Meridian Enterprise executablefiles developed by BlueCielo ECM Solutions have been signed by BlueCielo ECM Solutions. The file paths maydiffer depending on the location of these files on your computer.

AccuSo f t

C:\Program Files (x86)\Common Files\Cyco Shared\GEAR32SD.DLL

Autode sk

C:\Program Files (x86)\Common Files\Autodesk Shared\acgiclipengine16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgix16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixclipper16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixhiddenline16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixviewdefinition16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\acgixwhipview16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\axdb16.dllC:\Program Files (x86)\Common Files\Autodesk Shared\dboleutl16.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AdImaging.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AdImagingRes.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Common.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Common.Localization.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Common.Platform.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Common.SolverAPI.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Common.XmlBasedParser.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.Compressors.CompressorTest.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.Compressors.TileCompressor3D.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.Compressors.Wavelet.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.GISCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.Sde.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.SdeBridge.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.Igmap.Core.SpatialAPI.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ExportAsciiDelimitedCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ExportESRIAscii.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ExportLAS.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ExportTIFF.dllC:\Program Files (x86)\Common Files\Cyco


67

Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportESRI.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportLAStoPointCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportLiDARCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportSDTS.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportTiffCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.ImportExport.ImportUSGS.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.ArcConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.BaseTiffConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.EPSGConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.ExternalTiffInformationPrjConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.GeoTiffConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.PluginGeneral.PrjConvertors.MapInfoConvertor.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.GapFillerBase.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.LasPointConversion.Base.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.LidarGridGeneratorBaseCore.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.MergeLayers.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.MergeLayersDefinitions.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IgmapPlus.PlugIns.Solvers.SGridSplicer.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IsdCodecAPI.Common.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.IsdCodecAPI.Core.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\AmberCore.LidarAccessAPI.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\dboleutl18.dllC:\Program Files (x86)\Common Files\Cyco Shared\RealDWG\libtiff.dll

Conte x

C:\Program Files (x86)\Common Files\Cyco Shared\CTX_AS32.DLLC:\Program Files (x86)\Common Files\Cyco Shared\CTX_SN32.DLLC:\Program Files (x86)\Common Files\Cyco Shared\HLSI.DLL

I n s ta l l Sh ie ld

C:\Program Files (x86)\Common Files\InstallShield\engine\6\Intel 32\ctor.dllC:\Program Files (x86)\Common Files\InstallShield\engine\6\Intel 32\iuser.dllC:\Program Files (x86)\Common Files\InstallShield\engine\6\Intel 32\objectps.dllC:\Program Files (x86)\Common Files\InstallShield\IScript\iscript.dll

Mic roQu i l l

C:\Program Files (x86) folder\BC-Meridian\Program\SHW32.DLL


68

Mic ro so f t

C:\Windows\SysWOW64\atl70.dllC:\Windows\SysWOW64\mfc70.dllC:\Windows\SysWOW64\mfc70u.dllC:\Windows\SysWOW64\MSBIND.DLLC:\Windows\SysWOW64\msstdfmt.dllC:\Windows\SysWOW64\msvci70.dllC:\Windows\SysWOW64\msvcp70.dllC:\Windows\SysWOW64\msvcr70.dllC:\Windows\REGTLIB.EXEC:\Program Files (x86)\Common Files\Cyco Shared\GdiPlus.dll

Orac le

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\InstallPdfPrintDriver.exe (the execution level tag of this file is also not set)C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\2dentity.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\acfpdf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\acfpdfu.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\acfpdfui.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\apputils.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\attdll.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\at_gpstest.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\at_info.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\at_outtext.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\at_pfc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\AutoVueX.ocxC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\AvCompareX.ocxC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\avlink.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\avmapi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\AVMrkpX.ocxC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\AvPrintX.ocxC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\AvTree.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBPRO955.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResDE.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResFR.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResJA.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResKO.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResTW.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\BCGCBProResZH.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\bcgext.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\bmpfill.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\comm_png.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csichart2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csicore.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csifonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csigdi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csigdiplus.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csipdf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csireg.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csitbar.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csitree.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csiwin.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\csiwingdi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\cvtcore.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\dibapi.dll


69

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\doctbl.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_acis.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dc2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dcf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dcf2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dcic.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dcic2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dct.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_dcw.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_fbmp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_fbmp2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_fwmf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_fwmf2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_rsm.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_ss2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\drv_ssdb.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ecadsymb.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\edat.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\eschers.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\eschersxml.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\fonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\fontserver.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\freetype.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ftfonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ftype.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\gpscadex.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\graphics.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\graphics3d.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\h3d.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\iges3d.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\image.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\imageop.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\infodll.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\int_pngo.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\jpeg2000.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\libpng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\listdll.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\markup.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\mrkcvt.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\mtfmngr.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\m_note.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ole2wmf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\oleclnt.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\outtext.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\packagefile.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\packngo.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pafsutil.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panbrep.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pancore.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pandib.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panexp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pangl.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panio.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panlib.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panmesh.dll


70

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panose.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panpmi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pantext.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\panver.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_bmp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_eps.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_gp4.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_pcl.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_pcx.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_rlc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcrs_tif.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctlbase.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctlp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_3d.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_ar.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_db.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_dc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_rs.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pctl_ss.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pcvc_pdf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfar_ar.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfar_gzip.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfar_lzh.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfar_tar.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_asc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_exe.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_hex.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_msg.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_rtf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_txt.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_word.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_wordxml.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_ww.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_ww6.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfdc_xls.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_a11.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_bmp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_gif.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_hprs.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_hrf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_ico.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_itg.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_j2k.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_jpg.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_mod.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_nrf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_pcx.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_pic.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_png.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_ppm.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_pr.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_rif.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_rlc.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_rle.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_tga.dll


71

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_tif.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfrs_xwd.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfss_xls.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfss_xlsxml.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_cgm.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dg8.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dgn.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dst.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dwf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dwg.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dwg13.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_dxb.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_fmt.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_fmt2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_igr.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_igs.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_mi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_msp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_p95.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_p97.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_pdf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_pptxml.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_pr3.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_prn.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_prt.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_ps.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_se.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_shp.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_slb.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_sld.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_sw2.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_vis.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pfvc_wmf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\pmi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\privilege.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\qviewav.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\regdll.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\regex.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\rtf.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\shxfonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\sldworks.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\smodeler.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\sm_buildbody.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\sysfonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\thread.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\thumb.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\translay.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_angd.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_arcd.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_area.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_cdis.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_clud.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_dist.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_dm.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_grop.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_lder.dll


72

C:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_ole.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_signoff.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ude_sym.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\ufffonteng.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\UninstAv.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\vbcsi.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\vcetutils.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\vueLicense.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\xerces-c_2_8.dllC:\Program Files (x86)\Common Files\Cyco Shared\AutoVue\xmlsax.dll

10.5 .4 Au toVue setupIf AutoVue has already been installed on a computer by a setup program other thanMeridian Enterprise, theMeridian Enterprise setup program cannot detect it and errors might occur during Meridian installation. Werecommend that you uninstall the previous installation of AutoVue before installing Meridian Enterprise.

10.5 .5 AMFS and Windows Sea rch incompat ib le on 64-b i t serv-ersThe BlueCielo File System 2010 service andWindows Search are incompatible on 64-bit Windows operatingsystems.

Workarounds are to use Windows Indexing Service instead or to enable Local Workspace for the vaults forwhichWindows Search content indexing is configured.


10.5 .6 Cannot reg is ter Asset Management Modu le 2010 exten-s ions in 64-b i t Con figu ra torAttempting to register an Asset Management Module user interface extension (included with Meridian Enter-prise 2010) in the 64-bit edition of the Meridian Enterprise Configurator can result in a "Cannot createobject..." error.

A workaround is to register the extensions with the 32-bit edition of the Meridian Enterprise Configuratorinstalled on a different computer.


10.5 .7 Vau l t s unava i lab le a fter in s ta l l ing Merid ian En terp r i se64-b i t ed i t ionUpgrading an existing Meridian Enterprise server from 32-bit components to 64-bit components on a 64-bitcomputer requires extra attention. The 64-bit Meridian Enterprise setup programs do not detect a previousinstallation of 32-bit components or upgrade them. The process must be performedmanually. For more inform-ation, see the Meridian Enterprise knowledge base.

Related information

Meridian Enterprise 64-bit setup


73

10.5 .8 Mer id ian En terp r i se 64-b i t setup worka roundsTo install 64-bit support, launch the 64-bit .msi package included on the distribution package. Following are lim-itations, prerequisites, and workarounds that apply to various scenarios:

This setup does not install the AutoVue 2D Professional viewer since a 64-bit version is not available.The Meridian 32-bit version, which does include AutoVue 2D Professional 32-bit, may be installed andrun on 64-bit computers if the viewer is required. However, installing both versions can lead to occa-sional errors if installed onWindows 7 and should be avoided. In such configurations, we recommendinstalling the AutoVue Client/Server viewer instead as described in theBlueCielo Meridian EnterpriseAdministrator's Guide.

Installing 32-bit Meridian components on 64-bit client computers does not install 64-bit applicationlinks to support 64-bit authoring applications. To install the 64-bit application links, install them fromthe 64-bit Windows Installer Package and install the remaining client components from the 32-bit Win-dows Installer Package or Setup program.

Before running the Meridian 32-bit setup program (Setup.exe) on 64-bit computers runningWin-dows XP or Windows Server 2003 or prior Windows versions, download and install Microsoft Core XMLServices 6 64-bit (msxml6_x64.msi) fromMicrosoft if it is not installed already. This component isnecessary for proper Meridian operation or else errors will occur. Installing this component is notnecessary onWindows Vista or Windows Server 2008 or higher because it is included withWindows.

Attempting to install or upgrade a Meridian application or optional modules on any 64-bit Windowsoperating system can fail if a 32-bit version of Application Integration (AMHookTrayU.exe) isalready running. The problem occurs when the Select Components page of the Setup program isshown and produces the error "Remote procedure call failed." This can occur when performing a cus-tom installation of an additional product on an existing installation or whenmodifying an existing install-ation. This issue does not occur with the initial installation of BlueCielo products, when setup typesother thanCustom are selected, or with the Windows Installer Packages. To work around the prob-lem, close Application Integration before running any BlueCielo setup programs (setup.exe) on 64-bit Windows computers.

Attempting to upgrade Meridian Enterprise 2010 64-bit server components (with 32-bit EDM Server) tothe release 2011 server components can result in a corrupt installation. To prevent this issue, first unin-stall the existing 64-bit server components before installing the 2011 release.

10.5 .9 Windows Insta l ler Package setup incompat ib le wi thexecu tab le setupRunning a Windows Installer Package (.msi) setup on a computer where Meridian has already been installedwith an executable (.exe) setup will not work. Remove the existing installation with the executable setup first.This limitation only applies to Windows Installer Packages. Executable setups may be run after anWindowsInstaller Package setup without issue.

10.5 .10 Windows Vis ta setupMeridian Enterprise can be installed onWindows Vista with the following limitations.


74

10. 5. 10. 1 Vau l t incompa t ib i l i t yWarning Due to fundamental changes made inWindows Vista andWindows Server 2008, vaults are notcompatible betweenWindows XP or Windows Server 2003 andWindows Vista or Windows Server 2008 andvice versa without serious side effects. For more information see "Vault incompatibility withWindows Vista andWindows Server 2008."

10. 5. 10. 2 Visua l C++ run t ime f i le s requ i re dThe followingmust be installed (either manually or by a different application) onWindows Vista beforeinstalling Meridian Enterprise with the Windows Installer Package (MSI) setup programs. Otherwise, DLL filesmay fail to register.

Microsoft Visual C++ 2005 SP1 Redistributable Package (Meridian Enterprise 2011 SP1 andprior only)

32-bit download:

http://www.microsoft.com/downloads/details.aspx?familyid=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en

64-bit download:

http://www.microsoft.com/downloads/details.aspx?familyid=EB4EBE2D-33C0-4A47-9DD4-B9A6D7BD44DA&displaylang=en

Note On 64-bit systems, both downloads must be installed.

Microsoft Visual C++ 2008 SP1 Redistributable package (Meridian Enterprise 2012 and prioronly)

32-bit download:

http://www.microsoft.com/downloads/details.aspx?familyid=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2&displaylang=en

64-bit download:

http://www.microsoft.com/downloads/details.aspx?familyid=BA9257CA-337F-4B40-8C14-157CFDFFEE4E&displaylang=en

10. 5. 10. 3 Mod i f y op t io n o f 32-b i t se tup sTheModify option the 32-bit executable setup packages may not work under certain circumstances onWin-dows Vista 64-bit versions.

10. 5. 10. 4 Web Acce s s e xte ns io n ins ta l la t io n w i th I I S 7Prior to this release, if the IIS 6 Management Compatibility feature of IIS 7 was not installed, the install-ation of the MeridianWeb Access extension would fail. The feature had to be installed before installingWebAccess. This has been fixed and IIS 6 Management Compatibility is not required.






75

10. 5. 10. 5 Con te n t inde xingWhen activating content indexing in Meridian Enterprise Administrator, the content index may not be created orthe indexing process may not be properly scheduled. This is due to the change by Microsoft inWindows Server2008 from the Indexing Service to Windows Search Service which is supported.

10. 5. 10. 6 64- b i t s uppo r tFor information on installing 64-bit support, see Meridian Enterprise 64-bit setup, andWeb Access 64-bit sup-port.

10.5 .11 Windows Server 2008 setupMeridian Enterprisecan be installed onWindows Server 2008 with the following limitations.

10. 5. 11. 1 Vau l t incompa t ib i l i t yWarning Due to fundamental changes made inWindows Vista andWindows Server 2008, vaults are notcompatible betweenWindows XP or Windows Server 2003 andWindows Vista or Windows Server 2008 andvice versa without serious side effects. For more information see Vault incompatibility withWindows Vista andWindows Server 2008.

10. 5. 11. 2 Visua l C++ run t ime f i le s requ i re dThe followingmust be installed (either manually or by a different application) onWindows Server 2008 beforeinstalling Meridian Enterprise with the Windows Installer Package (MSI) setup programs. Otherwise, DLL filesmay fail to register.

Microsoft Visual C++ 2005 SP1 Redistributable Package (Meridian Enterprise 2011 SP1 andprior only)

32-bit download:


64-bit download:


Note On 64-bit systems, both downloads must be installed.

Microsoft Visual C++ 2008 SP1 Redistributable package (Meridian Enterprise 2012 and prioronly)

32-bit download:


64-bit download:







76

10. 5. 11. 3 Web Acce s s e xte ns io n ins ta l la t io n w i th I I S 7Prior to this release, if the IIS 6 Management Compatibility feature of IIS 7 was not installed, the install-ation of the InnoCielo Web Access extension would fail. The feature had to be installed before installingWebAccess. This has been fixed and IIS 6 Management Compatibility is not required.

10. 5. 11. 4 Con te n t inde xingWhen activating content indexing in Meridian Enterprise Administrator, the content index may not be created orthe indexing process may not be properly scheduled. This is due to the change by Microsoft inWindows Server2008 from the Indexing Service to Windows Search Service which is supported.

10. 5. 11. 5 64- b i t s uppo r tFor information on installing 64-bit support, see "Meridian Enterprise 64-bit setup," and "Web Access 64-bit sup-port."

10. 5. 11. 6 " Fa i le d to ge t l i s t o f vau l t s o n compute r ' Se rve rName ' . A secu r i t ypackage spec i f ic e r ro r occu r red . "This error can occur when attempting to open a vault that is hosted on a Windows 2008 R2 server from a Win-dows XP client computer. This error does not occur from a Window 7 client computer.

This error occurs because the user is not properly authenticated by the server as described in Error 80070721Occurs When Instantiating a COM Component on a Remote Windows 2008 Server in MSDN.

To resolve this issue, we recommend that you implement one of the following solutions:

Solution 1

Configure a Service Principal Name (SPN) for the user as described in the previous linked article and in the set-spn command description in the Windows Server 2008 Command-line Reference.

Run the following command on the Windows 2008 R2 server:

setspn -A http/<DomainName> <AccountName>

Solution 2

Allow the computer to be trusted for delegation as described in Allow a computer to be trusted for delegation inMicrosoft TechNet. This solutionmay not be permitted by your organization's security policy. Consult a systemadministrator before implementing this solution.

Solution 3

Disable the default Server Message Block (SMB) 2.0 protocol used by Windows Server 2008 R2. BlueCielo soft-ware is compatible with SMB 1.0 and if you disable SMB 2.0, the software will not be affected.

To disable SMB 2.0:

1. Open the Registry Editor on the Windows Server 2008 computer.

2. Expand the registry tree to the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

http://blogs.msdn.com/b/distributedservices/archive/2009/07/20/activation-of-a-com-component-fails-on-windows-server-2008-with-the-error-80070721.aspx

http://technet.microsoft.com/en-us/library/cc731241(WS.10).aspx

http://technet.microsoft.com/en-us/library/cc738491(WS.10).aspx


77

3. Add a new DWORD value with the name Smb2.

4. Set the value of Smb2 to 0 to disable SMB 2.0 or set it to 1 to renable SMB 2.0.

5. Reboot the server.

10.6 Viewers

10.6 .1 Au toVue 2D Profess iona lFollowing are known problems with the AutoVue viewers in some Meridian Enterprise versions. These prob-lems are actively being resolved wherever possible. Some of these issues are limited to the BlueCielo imple-mentation of the viewers and are the responsibility of BlueCielo ECM Solutions. Other issues are native to theviewers themselves and are the responsibility of Oracle, Inc. Solutions will be provided as hotfixes or in futureMeridian releases.

Thumbnail images are not created in Meridian if the user's Windows environment variables TMP andTEMP are not set to the default value %USERPROFILE%\AppData\Local\Temp.

The AutoVue Desktop versions are not supported by the 64-bit Meridian clients. Consider installing theAutoVue Client/Server in such cases. For more information, see the BlueCielo Meridian EnterpriseAdministrator's Guide.

No support for object enablers in .dwg files created by the AutoCAD vertical applications and AutodeskInventor. The objects are not shown in the viewer.

Right-clicking to display the shortcut menumay execute the Zoom All command.

Drawings may not display correctly after using the Show Product Structure command.

Thumbnail images are not created if Windows Vista User Account Control (UAC) is enabled.

Thumbnail images are built from the model view, not from layouts. If the model view is empty but anon-empty layout exists, the thumbnail image will be empty.

The BlueCielo client applicationmay fail after successive uses of Print Preview.

The Print Preview commandCurrent page option does not work. All pages are shown. Theoption does work for the Print command.

License file informationmay be requested when switching between:

AutoVue Desktop and AutoVue Client/Server viewers

BlueCielo viewer and AutoVue viewers

When viewing documents inWeb Access with the Enable Meridian Web Client option dis-abled

Restarting the client application resolves the error.


78

If AutoVue 3D Professional Advanced is installed on a computer where AutoVue 2D Professional wasoriginally installed by a BlueCielo setup program and the BlueCielo setup program’s Repair option isexecuted, the original BlueCielo installation will be restored and the computer will revert to theAutoVue 2D Professional viewer. To restore AutoVue 3D Professional Advanced, uninstall AutoVue 3DProfessional Advanced before executing the BlueCielo setup program's repair option and reinstallAutoVue 3D Professional Advanced afterward.

If the Meridian Asset Management Module is installed and the AMFS service has stopped, clicking theShow Viewer or View Full Screen buttons on theWhere Used page in PowerUser will show Nodocument available in the viewer.

The AutoVue Document Converter will fail to install if User Account Control (UAC) is enabled on 64-bitcomputers.

The borders drawn around hotspots can appear inaccurate depending on the computer's operating sys-tem. The region that the borders surround can be several pixels too large or too small in height orwidth. The location of the borders has no effect on the functionality of the hotspots.

The borders are drawn using the Autodesk RealDWG library that does so with a virtual graphic deviceso that the borders can be shown on any hardware graphics device. The screen coordinates of the vir-tual device are slightly different on different operating systems and in different versions of RealDWG.

The borders drawn by AutoCAD are accurate because AutoCAD does so with the hardware graphicsdevice.

Even after configuring one or more of the settings described in the BlueCielo Meridian EnterpriseAdministrator's Guide, users may still be prompted for their credentials by some versions of Javawhen AutoVue Client/Server is used. This can be prevented by installing a Java upgrade.

10.6 .2 Dra ft P r in t doesn ' t work in NavisWorks F reedom viewerUsing theDraft Print command from the viewer toolbar will result in an error messageNo vieweravailable for this document. The NavisWorks viewer does not support the command.

10.6 .3 Watermarks not supported by Adobe Reader XPrinting watermarks is not supported by Adobe Reader X .

10.7 Web Access

10.7 .1 64-b i t supportThe following features are not supported by Web Access on 64-bit platforms:

Document viewing with AutoVue Desktop versions. AutoVue Client/Server may be used instead.

Document download, batch, and hybrid document support

Offline mode


79

Briefcase metadata stored in Microsoft formats unless the Microsoft Access Database Engine 2010Redistributables package is installed.

Remote session support

To install 64-bit support, launch the 64-bit .msi package included in the distribution package in the BCME-MSI64folder.

10.7 .2 T i t le b lock field upda te upon check- inWhen checking in a document withWeb Access or in Offline mode that contains synchronized title block prop-erties, the local copy of the documentmay be different from the version in the vault after the check-in is com-pleted. This happens only when on the Title Blocks tab of the document type, the Read title block fieldswhen a document is checked in through Web Access option is set and one or more of the optionsunderWrite title block fields.

The reason this happens is that during the check-in, the title block properties are read from the title block andcopied into the vault. After that, the working copy is submitted, which causes the title block fields in thechecked-in document to be updated according to the new values. The result is that the document in the vault isnewer than the document on the local computer. To resolve this, use theDownload Document command inWeb Access to download the updated document.

10.7 .3 Sha rePoin t 2003 and WebAccess on one serverTo allow SharePoint 2003 and MeridianWeb Access to coexist on one server, youmust add the Meridian virtualfolder as the Excluded Paths option in SharePoint Central administration. To do so, follow these steps:

1. Open the Central Administration web page.

2. SelectConfigure Virtual server settings.

3. Select the site to configure, usually this is Default Web Site.

4. Under Virtual Server Management, chooseDefine managed paths.

5. IfMeridian is not yet in the list of Excluded Paths, enter it in the Path entry field at the bottom,select Excluded path and click OK.