What can we help you with?

Sorry, you do not have permission to carry out this action.
Avolve Software - Powered by Kayako Help Desk Software
What can we help you with?

knowledgebase : Troubleshooting > Other

There was a problem when uploading large documents, approximate size of 90MB or larger, after editing in BlueBeam. For new installation the changes will be in place, but for existing installation (if they want to use Bluebeam) the web.config will have to be updated manually with the following:

<system.web>
....
  <httpRuntime maxRequestLength="104857600" executionTimeout="7200"
requestValidationMode="2.0" maxQueryStringLength="2000000"  />
  ....
  </system.web>
  <system.webServer>
....
  <security>
   <requestFiltering allowDoubleEscaping="true">
    <requestLimits maxAllowedContentLength="2097151000" />
   </requestFiltering>
  </security>
....
</system.webServer>

 

Also, if there was Bluebeam middleware (ProjectDox Bluebeam Integration) already installed, it has to be uninstalled and installed again using the newer version.


Contributed by: Veronika Zhemoytyakv

Contributed on: 5/19/17

If you receive a failed upload error message when uploading large files, add another zero to the web.config file for the web server.

 <add key="maxFileSizeLimit" value="1000000000" />

 

Written by: John Mitilier

Contributed by: Lora Benedict

ProjectDox Utility Service Troubleshooting Tips

 

The ProjectDox Utility Service is responsible for running ProjectDox processes in the background such as scheduled tasks, group maintenance functions, clean-up files from temporary folders, clean-up workflow instances, republishing files, applying global permissions to new users, synching LDAP users to ProjectDox database, archiving data from ProjectDox logs and tables and deleting old data from the application and database tables.

The ProjectDox Utility Service accomplishes these tasks by making web service calls to ProjectDox.  All of the functions listed are performed each time the Utility Service runs.  The frequency that the Utility Service runs is set to every 5 minutes by default but can be modified within the config file for the service to occur at whatever frequency the user desires.

If the service is having trouble running, you can troubleshoot by disabling the functions one by one to determine the specific call that is failing if there is no discernable information being logged in the debug.txt file located in the installation folder of the Utility Service.

The ProjectDox Utility service allows for disabling each feature that the Utility manages. By default the values are set to “false”. Set each one to true, one at a time, to determine if the Utility service is causing performance issues, or you can eliminate the Utility as the cause.

 

  1. Set DisableProcessTaskScheduler=true
  2. Restart service
  3. Does ProjectDox continue to experience performance issues.
    1. If no, then you have determined which feature is producing the problem and it can remain stopped. Collect logs, review the Event Viewer and enter a ticket for development along with the ProjectDox Utility config file.  
    2. If yes, go to step 4.
  4. Repeat steps 1-3 for each setting.

 

        <addkey="DisableProcessTaskScheduler"value="false"/>

        <addkey="DisableProcessGroupMaint"value="false"/>

        <addkey="DisableProcessCleanupTemp"value="false"/>

        <addkey="DisableProcessCleanupWorkflow"value="false"/>

        <addkey="DisableProcessRepublish"value="false"/>

        <addkey="DisableProcessApplyGlobalPerms"value="false"/>

        <addkey="DisableProcessSyncLDAP"value="false"/>

        <addkey="DisableProcessArchiveOldData"value="false"/>

        <addkey="DisableProcessDeleteOldData"value="false"/>

 

Support Portal Overview for Customers

General Notes:

  • Users can access the portal at https://support.avolvesoftware.com
  • Support Portal can be configured to allow all of the organizations' tickets to be seen by all user accounts or siloed so each user can only see their own tickets
  • Users designated as “Manager” and have permission to update the “account properties” for jurisdiction under the “My Organization” tab

 

Getting Set Up:

  • Users should receive email notification with temp Password to log into the site
  • Once you login, you can enter / update your profile information
  • The Preferences tab > set your timezone, enable DST, etc
  • Change Password > self explanatory

 NOTE:  New user accounts for the Support Portal have to be requested via a Support Ticket entered by someone who already has access to the Support Portal for purposes of security.

General Use:

  • You can find information in the following ways:
    • Search using the search bar under the main menu which will return results from the Knowledge Base articles as well as Tickets and News articles that match the criteria
    • Navigate the Knowledge Base articles (Main categories are accessible on the left-hand side)
  • Click on “My Tickets” to view and navigate existing tickets

NOTE:  To see Tickets that have been closed previously, click on the "View Resolved Tickets" button on the upper right of the page

 

To Submit a Ticket:

  • Click on “Submit Ticket"
  • Select “Support”, then complete all the info as completely as possible
    • When choosing a type for your ticket, there is a Training Request type.
      • If you pick this type, it will put it in their training queue
      • This type is useful if you have new users who may need training.
    • As you type in the "Subject" box, the "Knowledge Base" suggestions will update with articles that match what you are typing at the bottom of the page for review
    • Detail the exact steps that were taken to create the issue > support will need to try to recreate, so these details will be key.
    • When describing the problem, ensure to give the folder name, file name, etc.
    • Please be as descriptive as possible. If you can add screenshots, please do so. You can go to the bottom of the screen and click “Add file” to upload screenshots.
    • Attaching a file/screenshot:
      • 20 MB is the file limit
      • No restrictions on file types uploaded
  • Once complete, click “Submit”
    • You will get a confirmation screen with your ticket number, as well as an email with the ticket details

 

Ticket Priorities:

  • Priorities determine response time > the more severe the priority, the faster the support response.
    • System Down > no one can login or do anything > quickest response time
    • High > many users affected, but others can get in
    • Medium > some users affected, etc
    • Low > low impact item
  • SLA defines these items. SLA came with the initial order and is also available on our website

 

Responding to Tickets:

As the Avolve team responds to your ticket according to the priority in the Support Queue, customers can respond in two ways:

  1. Login to the portal and update the ticket directly, or
  2. "Reply All" to the email sent to you, which will capture your email comments as notes on the ticket.

NOTE:  It is important to note that replying to an email for an old / closed ticket will re-open the ticket for further follow up / investigation.

NOTE:  You can change the ticket status and priority yourself. However, if you do so, please include a note as to why you have changed either.

Other Resources:

The Knowledge Base contains articles with common issues and can be a good resource in troubleshooting problems. A couple of helpful areas in the knowledge base are:

  1. Documentation - here you can find training guides, release notes, best practices, install guides, etc
  2. Tutorial videos - you can find helpful videos showing how to do specific tasks within ProjectDox

User Forums can be another good resource for users to discuss issues with other users of ProjectDox and OAS.

  1. Click on the User Forums menu option
  2. Register for account
  3. Login and search for the appropriate Group to post your question in and review responses from other users on your posting

Avolve Support offers additional services for customers which are outside of the terms of the Standard Support Agreement.  The additional services of "System Tuning" and "Health Check" may be purchased separately by a customer at any time and scheduled to be performed for their installation of ProjectDox.  These services may also be incorporated into Avolve's "Premium Support" and "Named Enhanced Support" options as part of a customized Support Solution for Avolve's Products.  The tasks that are performed for each of the services are listed below.

 

System Tuning

  • Involves evaluating the ProjectDox software configuration settings and comparing them to Avolve's installation guide for best performance
  • Evaluating site content for unused / redundant records which maybe cleaned up for Projects / Users / Templates etc. 
  • Review of Project Templates for configuration issues
  • Review of Site Groups usage
  • Review of Unpublished Files Report to determine Publishing issues

Health Check

  • Evaluating the customer's current server environment and determining if server resources are appropriate for the utilization and adjusting when necessary
  • Evaluation of the System Event Logs, ProjectDox System Logs and Brava System Logs looking for issues being reported that may need corrected
  • Evaluating IIS web site performance and review of configuration
  • Evaluating Database performance and review of SQL Server configuration including scheduled jobs and maintenance plans being performed