Avolve has investigated the .DWX file format and have found this format type to be produced exclusively by a 3^rd party company called CADLock, Inc. (www.cadlock.com). To create a .DWX file, AutoCAD users are required to purchase CADLock’s CADVault Digital Rights Management (only available for the Microsoft Windows operating system) add-on to AutoCAD. The .DWX format that is created “…utilize a proprietary system of adding internal security capabilities…” to the file or group of files. This process is much like putting a password on a .PDF file. If the receiver of these .DWX files do not have a CADVault Runtime license, they are not allowed/unable to open the .DWX file. Because the .DWX is a proprietary file format and the CADVault Runtime application is required to open it, Avolve’s ProjectDox Electronic Plan Review system cannot support this .DWX file format. Avolve also reviewed this with our Brava viewing engine vendor, and they have no future plans to support the .DWX file format.

Description

Job Processor logging may be turned on to diagnose any publishing problems that may be occurring with the Job Processor. Avolve may ask you to turn on logging for the Job Processor (temporarily) and to reproduce the problem.

It is advised to turn the logging off when the data has been collected (problem reproduced) as it can cause a minor decrease of performance with the Job Processor.

Solution

To enable logging you must go into the Job Processor directory, which is typically E:\Program Files (x86)\IGC\Brava!\Brava! Enterprise JobProcessor.
From within this directory, open the JobProcessor.config file in a text editor (Microsoft Word is not advised as it may add formatting to the text file that will cause issues with the Job Processor).

You will notice near the top of the file that by default:

     log=off

Please simply change "off" to "on," save the file, and then restart the JobProcessor Service. The "log.size=200" is the default maximum amount of jobs that will be reported in the file. Remember you need to restart the service again when you turn logging off (and save the file) after reproducing the problem.

Further down in the file you will notice this section:

     # Log file
     ProcessMonitorLogFile=%temp%\Informative Graphics Corp\IGCMonitorServiceLog.txt
     ProcessMonitorLogFileMaxSizeInMB=1

The ProcessMonitorLogFile= is the location of one of the log files.

**Please note that this is the location of the %temp% folder for the user that the JobProcessor is running as (should be an Administrator account). This means if you are remotely connected to the machine as a user that is not the JobProcessor service user then you will not see the logs in this location and instead need to navigate to the folder for the JobProcessor User.

Usually it is easiest to find this by going to C:\Users\[Job Processor USER]\AppData\Local\Temp\ and then performing a search for "IGCMonitorServiceLog.txt" without quotes. This is because there could be several folders under \Temp\ that the file could be located under.

Search for RIE_NIE under %appdata% for the Job Processor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt and any files in this RIE_NIE folder to Avolve.

The filesize of the log will not exceed 1MB by default unless you modify ProcessMonitorLogFileMaxSizeInMB= to a higher setting which is usually not necessary unless you change log.size= to more than 200 (jobs).

Revised 02-26-2015

Description

This will explain how to resolve the issue where the Job Processor service will not start, but other Brava services will.

This occurs with the following:

     Brava Type: Brava Enterprise .NET 7.1 and earlier

If all Brava services are able to start except the Brava Job Processor, this is usually related to the service account that is being used to logon the service, typically named NetItSvc. This means that the user that installed Brava Enterprise .NET is different from the user being used as the service account.

Solution

In order to resolve this, you will need to either change the service account to the user that installed Brava Job Processor or reinstall Brava Enterprise .NET Job Processor application as the user that will be running as the service account, in a typical installation, the NetItSvc account. 

The NetItSvc and the PD_USR accounts should be created on the machine as a Local Administrators prior to the installation of the Job Processor application.

Revised 02-26-2015

Description

Brava scalability touches many parts of the system, including the integration in which Brava runs.   This section covers scalability and fault tolerance of the Brava system itself. Integration scalability is covered in a separate section.

Solution

The attached white paper that was released by the makers of ProjectDox Publishing Engine, Informative Graphics, provides a very good understanding of the architecture used for the publishing paradigm in ProjectDox.

Revised 02-18-2015

Description

Certain configurations of Windows 2008 R2 may experience a memory leak in the "WinHTTP Web Proxy Auto-Discovery Service" (WinHttpAutoProxySvc) when the Job Processor is running. Microsoft is aware of this issue and Informative Graphics is working closely with Microsoft to provide a fix. However, at the time of release this fix is not yet available.

Solution

If you are experiencing memory growth in the WinHTTP Web Proxy Auto-Discovery Service on a 2008 R2 machine running a Job Processor, you can work around this issue in one of two ways:

1. Configure the WinHTTPAutoProxySvc to run in its own process. Open a command prompt and enter the following commands:

     sc stop "WinHTTPAutoProxySvc"
     sc config "WinHTTPAutoProxySvc" type= own
     sc start "WinHTTPAutoProxySvc"

2. Disable the WinHTTPAutoProxySvc. This will not affect the operation of the Job Processor, but may affect other components on the machine. To do this, open a command prompt and enter the following commands:

     sc stop "WinHTTPAutoProxySvc"
     sc config "WinHTTPAutoProxySvc" start= disabled

This will stop and disable the service.

In either case, If you've experienced memory growth, you'll have to reboot the machine to clear up the memory.

Revised 02-18-2015

Issue: 

The user received the error message below when attempting to use the File Browse button to select files on their local machine for upload to a particular project. The user is able to drag and drop files into the Upload Window and is successful.  All other Projects are able to use the File Browse button in the uploader control as well.  The issue is only affecting a single project. 

Solution:

The issue is caused by improper syntax of the Print Ready File Extensions list or the Pass Thru File Extensions list.  If the list in incorrectly formatted or the syntax is bad then the users will be displayed with the error message when they click the File Browse button on the Uploader Control.  See screenshot below of incorrectly formatted string of file extensions.  To fix the issue, correct the syntax of the field.

Description

Customers with anti-virus installed on the ProjectDox Servers must enable the following exclusion rules in any scanning utilities installed to prevent issues with the function of the software.  Avolve recommends that only the PdoxTemp folder be scanned in real-time.  All other ProjectDox application folders and supporting folders, including all sub-folders, should be excluded from anti-virus applications real-time scanning.  A nightly scan of the directories is acceptable.  It is not recommended to have anti-virus installed on the Job Processors.  Avolve cannot guarantee the operation of the Job Processors with anti-virus installed on the servers and, in the event issues occur with publishing, the first recommendation will be to remove the anti-virus application from the Job Processors and perform a full reboot.  Perform testing after the Job Processor has been rebooted to see if the issue is resolved.  

Solution

Avolve recommends setting up exclusion rules for the folders specified below on the ProjectDox servers indicated.  Assuming the Operating System is installed on the C:\ drive and the ProjectDox, related services and Brava applications are installed on the E:\ drive, you would want to exclude the following folders, including any sub-folders, on the ProjectDox servers.  A list of common Share Folder Names used by ProjectDox is provided below.

• UserFilesSource or UFS - Stores original files uploaded by users
• UserFilesPublish or UFP - Stores published ActiveX version of files uploaded by users
• DLCache - Stores published HTML version of files uploaded by users
• Queue - Stores Job Tickets created for publishing requests for the Job Processors
• PdoxLogs or Logs - Stores Archive PDFs if using ProjectDox Archive Feature
• PdoxExport or Export - Stores Exported Projects until retrieved by EDMS solution
• WFlowDLLCache - Stores ProjectFlow workflow instance DLLs for active workflows

• PdoxTemp - All uploaded files are stored in this folder first before being moved to the UserFilesSource folder.  This folder should not be excluded as it is the single point of entry for any new files uploaded to ProjectDox and should be scanned in real-time.

NOTE:  Some anti-virus applications may need an additional exclusion rule enabled for .rtf file types.  If you experience trouble with missing Markups or Changemarks within the workflow, then please try adding the exclusion rule for file types of .rtf and see if that resolves your issue.  Markups and Changemarks are saved to the PdoxTemp folder temporarily and some anti-virus applications will false alert and remove the .rtf file causing saved Markups and Changemarks to not show up in the workflow.

Job Processors

     C:\Windows\system32\spool\PRINTERS\  

     C:\Windows\Temp\  **  (see additional info below)

     C:\Users\NetItSvc\AppData\Local\Informative Graphics Corp\

     C:\Users\NetItSvc\AppData\Local\Temp\

     C:\Users\NetItSvc\AppData\Roaming\Informative Graphics Corp\

     C:\ProgramData\IGC\  (Brava 16.2 and 16.4)

     C:\ProgramData\OpenText\  (Brava 16.6 and up)

     E:\Program Files (x86)\IGC\   

     E:\Program Files (x86)\Avolve\    

     E:\Program Files\IGC\   

     E:\JPTemp\  **  (see additional info below)

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)


Web Server

     w3wp.exe Process

     E:\ProjectDox\     (Superion customers may see E:\EPR instead of E:\ProjectDox)

     E:\ProjectDox.Web.API

     E:\ProjectDox.Web.UI

     E:\Program Files (x86)\Avolve\   

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)


Application Server

     E:\Program Files (x86)\Avolve\

     E:\ProjectDoxSupportFiles\  or  E:\PDSF  * (see note below)



NOTE *

ProjectDox file share folders may exist on any ProjectDox server, Network Storage Device or stand-alone File Server. 
The PdoxTemp folder is the single entry point of new files to the server and therefore it is recommended to scan this folder only in real-time.  A nightly scan can be performed of the folders if desired.
Exclude all share folders with the exception of PdoxTemp from real-time scanning. 

ADDITIONAL INFO **

     If you are unable to exclude C:\Windows\Temp on the Job Processors, you can update the system output path of the IGC Writer Print driver and use a different directory for example E:\JPTemp.

To do this:

1. Create a folder on the E:\ drive named JPTemp
2. Grant Full Control under the Security Options for the folder, to the PD_USR and NetISvc accounts
3. In the Control Panel Printers and Faxes panel, right-click on the CSF Writer printer and select Properties
4. Select the Advanced tab
5. Click the Printing Defaults... button
6. Select the Filename Generation tab
7. Change the Output Directory path to the following:  E:\JPTemp
8. Click OK to save your settings.

Then add an exclusion rule for the E:\JPTemp folder on the Job Processors in place of the C:\Windows\Temp folder

SQL Server

Antivirus exclusion on SQL files:

When you configure antivirus software settings, make sure that you exclude the following files or directories on SQL Server machine from virus scanning. Doing this improves the performance of the files and helps make sure that the files are not locked when the SQL Server service must use them. However, if these files become infected, your antivirus software cannot detect the infection.