Tips and Tricks from BlueCielo Technical Support

AutoVue Viewer

How to alter line thickness when printing via AutoVue Viewer

1. This is a printing problem associated with AutoVue Viewer where the line thickness in a drawing is not implemented in the printout.
2. This problem is known to occur on BlueCielo Meridian 2011. This problem can occur with all versions of AutoVue Viewer.
3. The following workaround will tell you how to alter the line weight by changing the settings in the configuration file.
   • Open the AVX.INI file
   • Look for [AVPrintOptions] section and insert the following values:
     • [AvPrintOptions]
     • PenThicknessFname=aa123.c2t
     • PenThicknessUnits=0
     • Adjust the PenThicknessUnits value where PenThicknessUnits 0/1 = inch/mm
     • Place the c2t file in C:\Program Files\Common Files\Cyco Shared\AutoVue

How to alter pen thickness when printing via AutoVue Viewer

To edit the line thickness, users must change the Color values under section [Plotter/Device/WidthTable] to the desired number.

e.g.

Color0 = 0.010000000 or
Color0 = 0.030000000

This line weight is then controlled by PenThicknessUnits=0 option in the AVX.INI file. PenThicknessUnits can have two values, 0 or 1 where 0 = inch and 1 = mm

Upgrading licenses gives license access errors

1. After upgrading Advanced Project Workflow License, clients keep getting license errors. This issue occurs if the users do not have the Advanced Project Workflow module installed on their BlueCielo Meridian Enterprise system. This is because, after the upgrade, the HTV license is not released if the current DB license is an MP-DBL license.
2. This problem can occur on BC Meridian versions that use Advanced Project Workflow.
3. The Advanced Project Workflow module must be installed on the client’s computer in order to fix this error.

Menubar disappears after undocking

1. The menubar of the BC Meridian PowerUser will disappear if a user moves the menubar and re-opens the application
2. This issue occurs on all versions of the BC Meridian PowerUser up to BC Meridian 2011.
3. These are the 3 workarounds for this issue:
   1. Delete the Layout registry key:
      • Close PowerUser
      • Locate the following registry key and delete it HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\PowerUser\Layout
      • Restart PowerUser
   2. Use the shortcut keys :
      • Select a folder or file in PowerUser
      • Click the Alt key on the keyboard (the folder or file will now be highlighted in grey)
      • On the keyboard arrow keys, press right 2 times and then down 2 times
      • Press enter on Reset layout
      • Restart the PowerUser
   3. Rename the workspace registry key :
      • Close the PowerUser
      • Locate this RegKey on the user’s computer
      • HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\PowerUser\Workspace
      • Rename the Regkey “Workspace” (e.g. oldWorkspace)
      • Restart the PowerUser

AutoVue Error during installation of BlueCielo Meridian 2011 SP1

1. Users have had trouble installing and setting up the viewer for BC Meridian 2011.
2. This issue comes up when setting up a 32-bit BC Meridian installation for BC meridian 2011 SP1 on Windows 7.
3. To solve this problem, BC Meridian 2011SP1 has to be installed in the following order:
   1. Install the 32-bit BC Meridian using the BCME 2010STD. This will install the 32-bit PowerUser and AutoVue Viewer.
   2. Perform a custom installation 64-bit BCME 2010 and make sure you install only the application integration.
   3. Go to Files\Cyco Shared\AutoVue\avwinreg.ini and manually replace avwinreg.ini with the new .ini file. Please note that this new .ini file will be provided by BlueCielo Support.
   4. Install the SMB regkey on the user’s computer. To install:
      • Open regedit and locate this sub tree HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters
      • Add a new registry key (DWORD) with the name “Smb2”
      • Set the value to 0 to disable SMB2.0
   5. Test the 32-bit PowerUser and ensure that it has a working viewer. It can create confusion to have shortcuts to 2 PowerUsers on the desktop. Therefore, we recommend removing the desktop shortcut to the 64-bit PowerUser.

AMFS Registry Key is missing after MSI Installation

1. When BC Meridian Application Integration loads, users see a pop-up box in the Windows Taskbar.
2. Users have requested for a way to disable this pop-up notification.
3. This workaround applies to all supported versions of BC Meridian and Windows operating systems.
4. The pop-notification for BC Meridian Application Integration can be disabled in the following manner:
   • Open regedit and locate this sub tree HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer \Advanced
   • Find the registry key EnableBalloonTips and set its value to 0
5. Users can also disable all pop-up notifications for Windows through the following steps:
   • Open regedit and locate this sub tree HKEY_CURRENT_USER\Software\Cyco\{ActiveProduct}\CurrentVersion\AMHookTray \Settings
   • Find the registry key ShowBalloonOnStart and set its value to 0

AMFS Registry Key is missing after MSI Installation

1. After an MSI installation of BC Meridian 2009a SP1, users find that they have vault access via LWS instead of BlueCielo File System (AMFS). This is because an MSI installation does not add the registry key for using AMFS. This key must be added manually.
2. This applies to MSI installations of BC Meridian 2009a SP1 on Windows XP operating systems.
3. The workaround can be implemented through the following steps:
   • Open regedit and locate this sub tree HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Client
   • Add a new registry key (DWORD) with the name “UseAMFS”
   • Set the value to 1

iFilter does not work for x64 Explorer version

1. The iFilter does work after an x64 MSI installation of BlueCielo Meridian Explorer. This is because this package will install the x64 Application Manager which cannot use the iFilter.
2. This issue is seen in BC Meridian Explorer’s x64 MSI installations.
3. This problem can be fixed by uninstalling the x64 Application Manager and installing the x32 Application Manager using the x86 MSI installation for BlueCielo Meridian Explorer.

Content Indexing is not available for all editions of SQL Server 2008 R2 Express

1. Some editions of SQL Server 2008 R2 Express do not support full-text search. If the administrator uses one of these editions, he will not be able to set up content indexing for his database.
2. This feature is not available in SQL Server 2008 R2 Express and SQL Server 2008 R2 Express with Tools.
3. In order to avoid this issue, the administrator must install SQL Server 2008 R2 Express with Advanced Services which supports full-text searches. For more information, please refer to the Programmability section of the Features Supported by SQL Server 2008 R2 document.

Changing upload limit for web access on Windows 2008 R2 Server

1. After upgrading to Windows 2008 R2 Server, users find that they cannot upload documents larger than 20MB via web access.
2. This problem is known to occur on Windows 2008 R2 x64 Server.
3. The upload limit can be changed through the following steps:
   • Locate and open web.config for the web application (AMM)
   • Add the following code under the system.webServer node:

The value is set in bytes. Please change it to a value which best suits your users’ needs. This example sets it to 2GB. If users get an error saying maxAllowedContentLength cannot be overwritten, this can be altered using the following steps:

• Locate and open %windir%\System32\inetsrv\config\applicationHost.config
• Find
• Change “Deny” to “Allow”
• Check all options for "requestFiltering"

Disabling Server Busy messages in PowerUser

1. When there is a communication delay between the AutoManager EDM Server service and the BC Meridian PowerUser, users might get a ‘Server busy’ message. If this occurs on multiple client computers and these users click ‘Retry’, this can affect performance.
2. This problem is known to occur on all supported versions of BC Meridian.
3. The ‘Server busy’ message can be disabled through the PowerUser or by changing the registry keys.
   1. Sing the PowerUser:
      • In the PowerUser, click View in the menubar and select Options.
      • Under the Advanced tab under DCOM Warnings, make sure Server Busy and Server Not Responding are ticked. Please note that the PowerUser will hide the error messages only if these options are ticked. If the checkboxes are cleared, the error messages will be displayed.
   2. Using registry keys:
      • Open regedit and find the following subtree HKEY_CURRENT_USER\Software\Cyco\AutoManager Meridian\CurrentVersion\Client\Settings
      • Look for these (DWORD) registry keys and change to 1: dbgDisableOleBusyDialog dbgDisableOleNotRespondingDialog

Task arguments are case sensitive

• Users can get a KeyNotFound error when they use VBscript to set the task argument for Vault.Task.Set(ArgumentName, Value).
• This problem is known to occur on versions up to and older than Meridian .NET SDK 1.4.27.zip.
• Users can avoid this issue by ensuring that the argument name being passed is the same case as the argument name in VBscript.

Configuring the order/visibility of columns in PowerUser

• In the Navigation View in the BC Meridian PowerUser, users find that they cannot
use right-click on a column to configure the order/visibility of the column. In versions older than BC Meridian 2010, right-clicking on a column would bring up these options.
• This change in functionality applies to BC Meridian 2010 and BC Meridian 2011.
• In BC Meridian versions from 2010 and onwards, users must press CNTRL and right-click on a column. This will bring up the options controlling the order and visibility for all the columns.