Articles in this Section

Add a Custom Logo

Adding Tables to Email Notifications

Assign Future Tasks with the Form Assigner

Can HTML forms be hosted outside the Integrify portal?

Can I change the name of a milestone task on a process in production?

Can I migrate a group of requests from one version of a process to an updated version?

Can Integrify Pass Files into SharePoint?

Can we authenticate with SAML when hosting HTML forms outside the Integrify Portal?

Can we prevent a new request ID from being created until a task completed?

Coalescing Data: An Advanced Integrify Technique

Creating Ad-Hoc Related Requests

Creating a Table Maintenance Process

Does the user_recent_activity store data when a user resets or re-assign a task?

Does Integrify support two factor authentication?

Does Integrify support leap year dates?

Do notifications get sent out to users that have been disabled?

Embedding Calendars in Dashboards

How do I limit the allowed max file attachment size?

How do I force local communication within the application?

How do I enable AUTH for Integrify to redis communication?

How is user concurrency determined for my installation?

How do I force a user to change their password on the next login?

How can I extract grid data to add it to custom tables?

How do I import Active Directory users into Integrify using ADSync?

How Do I Make The Lines In A Process Straight?

How can I paste spreadsheet rows into a grid?

How do I schedule a process?

How do you edit Request Description and other fields after the workflow has started?

How to Clear Your Browser Cache

How to Configure Dynamic Task and Request Names?

I forgot my password.

Is there a way to edit the name of a request after it has been submitted?

Is there any negative impact if we change the time_out configuration on a task in a process in status production?

I would like to set a report to run from a set date say (1/1/15) through the current day (Today). How can I set my report to do that automatically?

Is there any way to configure account lockout rules?

The Difference Between a Requester and a Recipient

Upgrading Your Select List Fields (Step-By-Step Guide)

Using Assigner Tasks

What Does "Create a Copy of this Request" Do?

What is "Submit on Behalf of:" when starting a new request?

What are Best Practices for Testing in Integrify?

What do I need to change when I load balance Integrify?

What browsers does Integrify support?

What is the PDF Generator Task?

What Is Advanced Technical Support (ATS)?

When an Integrify Administrator performs a task resets or redo-completion, is there a logging table where this information is stored?

What is the best practice for archiving request data (e.g. attachments)?

When to Version a Production Workflow

Where are the logs for my OnPremise installation, what do they contain, and what should I look out for?

Using The Excel Import Task to Enhance Your Automation

Does Integrify integrate with Microsoft products?

Frequently Asked Questions about the PSPDFKit Acquisition

Where are the logs for my OnPremise installation, what do they contain, and what should I look out for?

Below is a list of the most common log files produced by the application and its services. These files contain general logging of Integrify events as well as critical and informational messages helpful in troubleshooting if problems occur. If these files become large on your system, you can delete them at any time. Some of these logs will only show up if you have debug turned on in the integrify\app\settings\settings.config file.
 

We are asked often what to look for in these files when implementing a monitoring tool. The answer is that you probably shouldn't. The Integrify application has numerous self-checks embedded in the code. So, even though a message may appear in a log, there is a very good chance that the application already either worked around the issue or retried the same activity successfully before you are even alerted of an error. A good rule of thumb is that the Integrify logs files should only be used to assist in troubleshooting user-facing issues. Almost every critical error will have a corresponding negative user interface impact.
 

integrify\app\scheduler\logs (v6 only):

  • <YYYY-MM-DD>_scheduler.log - contains information regarding scheduled reports and processes depending on your logger-config.json configuration. 
     

integrify\app\service:

  • <instancename>_exceptions.xml - contains mostly critical and some noncritical errors relating to the function of Integrify. Typically errors that cannot get logged to the database because of a database connectivity issue or any other system issues are logged here. If for some reason Integrify does not function after an upgrade or a server reboot / IIS restart, you will want to take a look at this file. 
     
  • _<descriptor>_exceptions.xml - contains error messages relating to the descriptor. As an example, _connections_exceptions.xml will show errors relating to database connections.
     
  • SystemSettings.log - contains a log of the number of Integrify instances and the number of settings per instance. For most installed customers this should be 1 and 47 respectively. It writes to this file anytime the first user hits the site after an application pool recycle or service restart. This is a verbose log and contains information as well as errors.
     

integrify\app\webserver\iisnode:

  • <servername>-<#>-stderr-<##>.txt - contains both critical and non-critical messages relating to the function of Integrify. If for some reason Integrify does not function after an upgrade or a server reboot / IIS restart, you will want to take a look at this file. Most real errors will appear in this file along with verbose messages. 
     
  • <servername>-<#>-stout-<##>.txt - contains both critical and non-critical messages relating to the function of Integrify. If for some reason Integrify does not function after an upgrade or a server reboot / IIS restart, you will want to take a look at this file. Most real errors will appear in this file along with verbose messages


integrify\app\webserver\logs:

  • <YYYY-MM-DD>_session_stats_<license>.log - contains license usage stats.
     
  • <YYYY-MM-DD>_error_<application area>.log - contains errors of all kinds depending on what area of the application was affected (process, route, etc). This should be one of the first logs to look at when a user reports an error or an issue.
     
  • <YYYY-MM-DD>_info_<application area>.log - contains informational messages of all kinds depending on what area of the application was affected (process, route, etc). 
     
  • <YYYY-MM-DD>_warning_<application area>.log - contains warnings of all kinds on what area of the application was affected (process, route, etc). 


integrify\app\windowsservices:

  • <instancename>_exceptions.xml - contains mostly critical and some non-critical errors relating to the function of Integrify. Typically errors that cannot get logged to the database because of a database connectivity issue or any other system issues are logged here. If for some reason Integrify does not function after an upgrade or a server reboot / IIS restart, you will want to take a look at this file. 
     
  • SystemSettings.log - contains a log of the number of Integrify instances and the number of settings per instance. For most installed customers this should be 1 and 47 respectively. It writes to this file anytime the first user hits the site after an application pool recycle or service restart. This is a verbose log and contains information as well as errors.
     
  • <instancename>_sync_log.xml is updated every time the ADSync application is run. It contains success and error logging.
     

integrify\app\windowsservices\tp_logs:

This directory contains logs and errors from the Integrify Task Processor. Error files are named yyyymmdd_tp.error. These files will list each instance the processor was able to hit, and the count of the notifications sent for reminders as well as the number of task timeouts for that instance. This is logged every time the Task Processor runs, which is every 5 minutes by default.
 

integrify\app\windowsservices\em_logs:

This directory contains logs and errors from the Integrify Email Monitor. Error files are named yyyymmdd_em.error.
 

ERROR_LOGGER

This is a table that resides in your Integrify database. You can run a select statement directly against the table with the tool of your choice to view its contents

 

Aside from the files, folders, and tables listed above, the windows event logs will also hold valuable information in case of a problem. Normally the event logs are most useful for analysis if the files above are not being updated or recreated after deletion.

 

The main locations for logged events for the application are in the \intergrify\app\webserver\logs directory as well as the \integrify\app\webserver\iisnode directory.