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.

If you come across an undefined error when trying to generate a PDF of the Workflow Designer, the issue could be due to the TempFolderURL in Admin->Configuration->Core not being configured correctly. Navigate to the field and verify that it is set up correctly. 

To be able to retrieve the Job Processor Log files, each Job Processor must first have logging enabled.  To enable JobProcessor logging, follow the directions listed in the KB below

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=62322277&objAction=ArticleView

To obtain the JobProcessor logs, search for RIE_NIE_logfile.xml under %appdata% for the JobProcessor user's profile. Additional logs should be located inside that folder. Please send the IGCMonitorServiceLog.txt (if the JobProcessor does not work at all) and any files in this folder. Typically, the folder that has the RIE_NIE_logfile.xml is:

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

The filesize of the log does 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). You can safely set this up to 32MB.

NOTE: When saving at any time after the first save, each of the originally included files must be populated with at least one markup. Saving with any of the drawings empty of markups disables future saves.

Lately we have been seeing some “Invalid server license errors” when trying to view files in non-Internet Explorer browsers. Below is a list of recommendations in order to fix these problems.

•          Applicable to ProjectDox 8.3 and greater - Make sure there are no spaces in your license keys for both Brava Server and Brava Enterprise Client License, located in IGCKey.lic file on the web server. Move your cursor to the end of the key, click the right arrow button and if it does not go to the next line, then it means you have an extra space and it must be deleted (can be done by simply hitting backspace). The new Salesforce license system adds the extra space when copying so it is important to check this every time you copy a new license.
•          Applicable to ProjectDox 8.3 and greater - After modifying, editing, or replacing the license you must reboot the web server in order for the changes to take effect. First, stop the Job Processor services, then stop Brava service(s), delete DLCache, reboot the web server. Once the web server is up, start the Job Processor service and test viewing files in non-IE browsers again.

This behavior can sometimes be created by latency across the network and causes the Job Processors to never actually release the .LOCKFILE located in the QUEUE Shared Folder.  The purpose of the .LOCKFILE is for each of the Job Processors to open and lock the file when they are working with tickets from the QUEUE folder.  This prevents any of the other JPs in the environment from grabbing files as the same time.  Once the Job Processor releases the .LOCKFILE then the next one available will grab the .LOCKFILE and process publishing requests.  In networks where the latency is high, the delay can cause the Job Processor to appear like it is never releasing the .LOCKFILE so therefore the 2^nd Job Processor appears to be disconnected and not processing. 

To remedy this, follow the steps below on each of the Job Processor servers:

1.)   Login to the Job Processor server.

2.)   Open the JobProcessor.config file from the following path:  D:\Program Files (x86)\IGC\Brava! Enterprise .NET\JobProcessor.

3.)   Look for the dir.watcher.sleep.time.0=250 and update the value to 2000 so the line should read as follows:

                        dir.watcher.sleep.time.0=2000

4.)   Save your changes.

5.)   Restart the Brava Job Processor Service on the Job Processor server.

Example of Updated JobGetter

dir.watcher.sleep.time.0=2000

Problem:  When copying changemarks to a Word file the changemark image does not appear.

Solution:  If a changemark image does not appear when copied to a Word file, follow the steps below: 

1.   Navigate to where this file can be found: Igc.Cdl.GdiPlusGate.dll. This is typically in the Job Processor folder.
2.   Make a COPY and PASTE the copy into the same folder.
3.   Rename the COPY of the file to the following: GdiPlusGate.dll
4.   Now you have GdiPlusGate.dll AND Igc.Cdl.GdiPlusGate.dll in the SAME directory.
5.   Restart the Job Processor server.

Problem: Certain files take a long time to publish, slow performance when viewing files on the Brava Viewer.

• Once the updated PDF driver has been applied, open .\Program Files (x86)\IGC\Brava! Enterprise\JobProcessor\Igc.Loaders\pdf2dl-config.xml file for edit.

• Update the 3 parameters for DisablePaletteCheck to true.

• The update takes affect with a full reboot of the Job Processor.

If Apache does not start on the web server, it may be that Java was updated automatically, and changed the path.

1)     It is important to disable the Java Updates when you install. 

Please see attached image.

After running your monthly Windows updates (including updates for Microsoft Office), there may be a need for the Microsoft Office application to be activated again (See attached image).  Since the NetItSvc account is used for publishing of Office type files, logging into the Job Processor server using the NetItSvc account and starting up one of the Microsoft Office applications, such as Word or Excel, will prompt you for the user's name, initials and company if the application needs to be activated again. However, if the application starts right up without any pop-up windows, then that is all that is needed and you can close out of the application and log off from the machine.   Microsoft Office applications need to be activated and any pop-up messages taken care of in order to successfully publish Office files by the Job Processor.  The initial pop-up message for the user's information will prevent the Job Processor from publishing Office files if the pop-up message is not acknowledged initially under the NetItSvc accounts on any Job Processors in the environment.

When encountering this problem, we have found that the issue could be a setting on your Firewall, which limits large uploads into your network. To correct this, check the Firewall settings and ensure that there is not a limitation on the size of files being transmitted across the Firewall into your network? Some of the settings that you may want to look for would be "tcp-mss-sender" for outbound traffic and "tcp-mss-receiver" for inbound traffic. The values for those settings controls the maximum amount of data that can be sent in a single packet, and can sometimes be troublesome when transmitting large files.

Issue:

When users with the Print permission for files print certain PDFs the printed PDF is missing some details.

Solution:

When printing the PDF file, on the Print Options page place a checkmark in the 'Optimize for PDF/Postscript Printing' option.  This setting will allow the PDF to be printed in the same manner in which the file is viewed.