Adobe eSign Installation Error

The typical cause is that the end user does not have appropriate permissions to work with the object in the solution. CAUSE
Adobe eSign does not appear to be installed or your security settings don't allow access to it. This error usually occurs for an end user after the administrator has completed and tested the solution.

The typical cause is that the end user does not have appropriate permissions to work with the object in the solution. WHAT TO DO
Look at the profile for the end user and ensure that they have appropriate permissions to work with the associated object(s).

A problem occurred in the merge process. Please try once more before contacting Support. (Error: 0122) (Release 7)

  • ERROR MESSAGE: This error usually occurs as a result of a corrupted template file.
  • Cause: This error usually occurs as a result of a corrupted template file.
  • What to do:
    • Review the template you are working with.
    • Ensure that the template you are using has a valid file extension (.doc, .pdf .xls etc.) Verify that the template file can be opened and edited on your local computer.
    • Ensure that the template follows Conga best practices.



Cannot remove because there is no parent (Release 8)

ERROR MESSAGE. A carriage return in the TableEnd text-based field will cause the error message. CAUSE
A carriage return in the TableEnd text-based field will cause the error message. WHAT TO DO
To prevent this error, ensure that there are no carriage returns in the text-based fields in your template. To check for carriage returns in your Word template turn on the "Show/Hide Paragraph Marks":

Composer Authorization Error | 404 Page Cannot Be Found

ERROR MESSAGE: This error message is generated when the browser cannot resolve a URL. In Conga, this is generally caused by a malformed url in your Conga Composer button.
Cause
The error message is generated when the browser cannot resolve a URL. In Conga, this is generally caused by a malformed URL in your button. Typical causes can include:

  • Spaces within the URL
  • Spaces at the end of the URL
  • Missing an ampersand (&) between parameters
  • Using a URL pointing to an invalid server (such as beta vs. www) What to do

Remove all spaces from the button's URL. Use plus signs instead of spaces in a parameter. Plus signs render as spaces in the Composer merge operation, but do not lead to 404 authorization errors.
Also see There was an Issue Getting the Conga Authorization Response.

Conga Composer Cannot Communicate with Salesforce (Release 7)

ERROR MESSAGE: Conga Composer Cannot Communicate with Salesforce (Release 7). CAUSE
Conga Composer is unable to connect to your organization's instance of Salesforce. This may be due to a server issue with Salesforce - click here to check status of Salesforce instance.
WHAT TO DO

  • Ensure "Lock Sessions to IP Address from which they originated" is disabled (Setup > Administration Setup > Security Controls > Session Settings)
  • Verify that the Session Timeout value is at least 30 minutes
  • Ensure the Conga Composer URL contains an "&Id=" parameter and that it is set to a valid ID
  • Don't try to "Preview" a Conga Composer button. You must click it from a Salesforce record


Conga Composer cannot connect with Salesforce because master ID is invalid. (Release 7)

ERROR MESSAGE. This error results when the ID designated as master object in the Conga Composer button URL is incorrect.
CAUSE
This error results when the ID designated as master object in the Conga Composer button URL is incorrect.
This could result from the ID number (e.g. RU-0001) being selected as the master object ID by mistake when Conga needs the record ID (e.g. a00G0000007MAXg) in order to function correctly.
WHAT TO DO
Ensure that the field you have selected in the button URL is the record ID for the record you've put your button on. If you're using a Salesforce standard object as your master object ID, the record ID field will be listed as Account ID, Opportunity ID, Contact ID, etc. If you've put your button on a custom object, the record ID field will be listed as Record ID.
This will be listed as Record ID if you're placing your button on a custom object. The &id=parameter designates which object will be your master object.

Conga Composer Expiration Warning

When launching Conga Composer, you receive an expiration warning. When launching Conga Composer, you receive an expiration warning.

Cause

Your Conga Composer licenses are expiring within the number of days listed.

What to Do


Trials:

  • If you did not purchase Conga Composer yet, but have a trial, engage with your salesperson.


Paid Customers:

  • If this is a Sandbox, Dev, or UAT org, submit a case to extend your licenses to co-term with your subscription end date if the expiration is in 10 days or less.
  • If this is your Production Org, and you purchased or renewed Conga Composer already, then submit a case.
  • If you recently purchased and installed Conga Composer for the first time, submit a case.

Note: All new Composer installs in Production or Sandbox Orgs for Composer default to a 14 day trial. Production Orgs default to 10 licenses, and Sandboxes default to an Unlimited Site License. ActionGrid, Conga Sign, and Conga Contracts default to a 15 day trial in Production Orgs.

Conga Composer Settings Error

The following error occurs when navigating to Composer Setup. Issue
The following error occurs when navigating to Composer Setup:Conga Composer Settings Error. There was an issue getting the Composer settings. There was an issue contacting the Salesforce servers. Check to ensure that 'Lock IPs' is not enabled and that the instance has available API calls.
What to Do

  1. Click Ok.
  2. Click Create Salesforce Token.
  3. Refresh the page.

It may take a few minutes to resolve the issue.

Conga Email Staging Record Error

ERROR MESSAGE: Conga Email Staging record could not be created, most likely because you don't have access to the object or Create/Read/Edit/Delete for this object on your profile.
MISSING SOLUTION TO THE ERROR. CAUSE
Conga Email Staging record could not be created, most likely because you don't have access to the object or Create/ Read/Edit/Delete for this object on your profile. (Release 7)
There are two causes for this issue:

  • User does not have full access to the object.
  • If it is not a permission issue, it may be a character limit issue. The HTML Body field on the Conga Email Staging object is a SFDC rich text field that has a character limit of 32,000 characters. Take a look at the size of the email template body.

WHAT TO DO
Verify that the user has access to the Conga Email Templates object as well as all fields on this object.

Error "id parameter is missing" with Composer 8 buttons in Lightning

Cause
Composer 8 buttons in Salesforce Lightning will produce an id parameter is missing error message when an additional question mark is included in the button URL. This most commonly happens when you use ?pv0= to pass a non-standard field value into the filter of your data source. For example, the following would cause an error in Lightning:
&QueryId=a0441000002PxvVAAS?pv0={!Opportunity.AccountId}
Tip: The example above only contains one question mark. Isn't the problem when you have more than one question mark? Yes! Composer buttons also have a question mark in the base URL (which is the first few lines), making the question mark in the above example the second.
What to Do
Encode the question mark using the URLENCODE function in the Salesforce button, as shown below: &Queryid=a0441000002PxvVAAS{!URLENCODE("?")}pv0{!URLENCODE("=")}{!Opportunity.AccountId} For more information on encoding characters, see {_}http://meyerweb.com/eric/tools/dencoder/_.

Error 0754 The document appears to be corrupted & cannot be loaded (Release 7)

ERROR MESSAGE: This error indicates there is something corrupt within your template. Cause
This error indicates there is something corrupt within your template. What to do
The easiest way to solve this error is to simply save a new version of your template in .doc format instead of .docx.
Find more information on different troubleshooting methods see Error: Something's wrong with your template (bad mojo). The merge template has serious problems.

Error 500 - "Internal Server Error" (Release 7)

ERROR MESSAGE. This error results when Conga Composer cannot access the report and/or the data within the report.
CAUSE
This error results when Conga Composer cannot access the report and/or the data within the report. WHAT TO DO
Please check the following items to correct the problem:

  • If using a Custom Report Type, ensure it is set to "Deployed" and not "In Development".
  • Ensure the user's profile has the following permissions: "API Enabled", "Run Reports" and "Export Reports".
  • Ensure the user has at least Read access to the folder that contains the Report.
  • Ensure that the High Assurance Session Required setting is disabled, allowing Conga Composer to access exported report data. If this setting is enabled, the session security level required to export reports is increased, preventing Conga Composer to access the report data.



Error appears when clicking security token in Sandboxes

On the Composer Set up tab, you see an error when you click Update Salesforce Token button in your Sandbox orgs. The error can be ignored because the security token is used for scheduled Conductor only.
Problem or Issue
On the Composer Setup page, you see an error when you click Update Salesforce Token button in your Sandbox orgs. The error can be ignored because the security token is used for scheduled Conductor only.



















































Possible Causes
There might be code path configuration differences. Workarounds
On the Conga Conductor Setup page, click the Update Salesforce Token button.

OpportunitiesCasesReportsComposer Test.s Composer Test Compariso






conga ConductorConductor Setup
Welcome to Conga Conductor




Scheduled Conductor Master SWitch

IJsethis!Salesforce RefresOneOrive Refresh TokenAPI Fl oo r




Google Refresh Token Bo:x Refresh Token

ERROR at Row:1:Column:40 value of filter criterion for field 'CloseDate' must be of type date and should not be enclosed in quotes (Release 7)

ERROR MESSAGE. This error message occurs because The Conga Query Builder leaves quotation ' marks ' around date fields.
CAUSE
The Conga Query Builder is a tool that helps you build SOQL queries. This error message occurs because The Conga Query Builder leaves quotation ' marks ' around date fields.
WHAT TO DO
Remove single or double quotation marks around dates from the generated query as shown below. Change this:

SELECT Amount, Account.Name FROM Opportunity WHERE CloseDate > '2012-12-31'

To this:
SELECT Amount, Account.Name FROM Opportunity WHERE CloseDate > 2012-12-31

"Error: CreateEnvelope in DocuSignAPI. One or both of Username and Password are invalid. You may need to set &DocuSignEndpoint="AlternateEndpoint, e.g., Demo)."

Composer DocuSign API error.
Cause
The most common reason for this error message is that an incorrect &DocuSignEndpoint parameter has been applied.
This issue can also be caused by DocuSign credential setup issues as incorrect credentials can cause problems sending an agreement in background mode.
What to Do

  1. Ensure the &DocuSignEndpoint parameter is configured correctly.
  2. Verify that the DSProSFUsername and DSProSFPassword on your Docusign Account Configuration object and your running user's User record are valid.

This error can come up because an incorrect endpoint was included, so the first step is to reference this page and make sure the right endpoint is used. However, this error message can also indicate a credentials issue. Basically, situations can arise where the DSProSFUsername values on the user's record and the Docusign Account Configuration record are the same, but the DSProSFPassword values are different. If you wipe out the
DSProSFPassword value on the user and wait about 20 minutes (seemed to take awhile to sync), the issue should go away. Looks like it might be caused by an incorrect password included on the user record.

A problem occurred in the rendering process. Please verify your template is valid (Release 7)

ERROR MESSAGE: This message indicates that a problem prevented Conga Composer from rendering from the template.
Needs solutions under What To DO. Cause:
This message indicates that a problem prevented Conga Composer from rendering from the template. There are a number of issues that can produce this problem:
What to do:

  • Start simple - try clearing the browser cache.
  • The template type might be unsupported. For example Conga Composer v7 does not support templates created in Office 2013.
  • The user does not have permissions for the object being used in this solution. This could be the cause if a solution works for the Admin but not an end user, or it works in Sandbox but not Production.
  • The user does not have field-level security for the field(s) being used in the solution
  • Merge fields in a Word Text Box. Text boxes are not supported for merging
  • The template may be corrupted template. Try recreating the template.
  • This can occur if QVars are not populating fields correctly.


Found end of mail merge region 'ReportData1 0' without matching start (Release 7)

ERROR MESSAGE: Missing Table Start merge field. CAUSE
This error occurs when a template table has a TableEnd merge field but is missing the corresponding Table Start. What To Do
Review your template to make sure you have all of your Table Start and Table End merge fields.

Input string was not in the correct format

ERROR MESSAGE: One or more of the merge fields in your template are formatted to display the data as either number/currency or date/time formats while the corresponding data in Salesforce that is being merged to that field is a text value.
Cause
This error occurs when one or more of the merge fields in your template are formatted to display the data as either number/currency or date/time formats while the corresponding data in Salesforce that is being merged to that field is a text value. The template attempts to format a string of text as a number/currency or date/time format, which will not work, so the error occurs.
WHAT TO DO
To correct the problem, locate the offending fields and update them to properly reflect their formatting as dictated in Salesforce which can be done by either a) deleting the merge field and recreating it from scratch, or b) in Word
templates, remove the merge field's appearance parameter and right-click to either Toggle Field Codes back to normal or Update Field.
Tip: Tip: In Word templates, toggle field codes open on all merge fields by selecting the entire document (Ctrl + A) and right-clicking on any merge field and selecting Toggle Field Codes; these two steps can also be accomplished via keyboard shortcut Alt + F9 (on a PC) or Alt + Function + F9 (on a Mac). Once all field codes are toggled open, you can more easily look through the merge fields to locate those that have
appearance parameters that are attempting to format them in a way that does not match the format of the field in Salesforce.
For example, the merge field { MERGEFIELD Name # Currency } in a Word template would need to be updated because likely a name field in Salesforce is formatted as text while the template is attempting to format it for currency using the # Currency appearance parameter.

Insufficient Access: Current IP Address is not allowed or invalid_grant: IP restricted

Conga Error Message. If you limit Profiles to specific IP Ranges, you will need to add the Composer IP Addresses to each Profile using Conga Composer.

Issue

If you limit Profiles to specific IP Ranges, you must add the Composer IP Addresses to each Profile that needs to use Conga Composer.

Workaround

Add the Conga IP addresses for the Profile. In Salesforce Classic:

  1. Navigate to Setup.
  2. Click Security Controls.
  3. Click Network Access.
  4. Click New.
  5. Enter the Start IP Address and End IP Address.
  6. Click Save.
  7. Repeat for all Composer IP Addresses.
  8. Navigate to the Profile(s) in question and add the same IP Addresses to the Login IP Ranges.



In Salesforce Lightning:

  1. Navigate to Setup Home.
  2. Click Security.
  3. Click Network Access.
  4. Click New.
  5. Enter the Start IP Address and End IP Address.
  6. Click Save.
  7. Repeat for all Composer IP Addresses.
  8. Navigate to the Profile(s) in question and add the same IP Addresses to the Login IP Ranges. Contact Conga Support to get the list of Composer IP Addresses.

Warning: In addition to adding the Composer IP Addresses to User Profiles in Salesforce, ensure the IP Addresses are accessible and not blocked by your IT team, as this disallows users from accessing Conga Composer.
Composer IP Addresses

Region

Start IP Address

End IP Address

N. Cali

54.219.139.180

54.219.139.180

N. Cali

54.219.145.149

54.219.145.149

Virginia

54.85.136.135

54.85.136.135

Virginia

54.236.206.9

54.236.206.9

Ireland

52.30.25.119

52.30.25.119

Ireland

52.17.12.74

52.17.12.74

Ireland

54.77.185.212

54.77.185.212

Frankfurt

52.29.3.21

52.29.3.21

Frankfurt

52.29.110.43

52.29.110.43

Singapore

13.114.67.52

13.114.67.52

Singapore

52.196.157.45

52.196.157.45

Sydney

52.64.238.135

52.64.238.135

Sydney

52.64.246.142

52.64.246.142

Sydney

52.64.246.142

52.64.246.142

Sydney

54.206.92.149

54.206.92.149


Insufficient Access to Custom Settings Error

The error stems from incompatibility with the aforementioned Salesforce Critical Update and the running Composer user's permission to access the Composer Settings custom settings.

Issue


Non-admin users that launch Conga Composer in a Salesforce orgs without My Domain and that have accepted the Require Customize Application permission for direct read access to custom settings Salesforce Critical Update will incur the error message below. Error message: Have your system administrator access Composer in this org to enable the custom settings to be read and migrated to a location which can be accessed going forward.
The error stems from incompatibility with the aforementioned Salesforce Critical Update and the running Composer user's permission to access the Composer Settings custom settings.
This error only occurs if there has not been a Composer merge since accepting the Require Customize Application permission for direct read access to custom settings Salesforce Critical Update.

Workaround

To resolve this error, contact the Salesforce's org system administrator and have them launch Conga Composer. Launching Conga Composer as a system administrator enables access to the Composer Settings custom setting for all non-admin Composer users.

Invalid Grant: authentication failure

ERROR MESSAGE. This error message occurs because the user record attempting to launch Composer is frozen. Cause
This Invalid Grant: authentication failure error messages appears in the Composer UI when a user launches their Composer button. The error occurs if a Salesforce user is frozen and attempts to launch Composer.
What to Do
Unfreeze the Salesforce user to resolve the error message. For more information on freezing or unfreezing User Accounts, see Freeze or Unfreeze User Accounts.

Invalid master object ID(must be a Salesforce id) (Release 7)

ERROR MESSAGE: Invalid master object ID. Cause
There are two potential causes for this error:

  • You have not entered a valid Salesforce ID for the &Id parameter in your Composer button URL. This can occur if you hard-code an incorrect ID or an invalidly constructed ID (perhaps using a QVar query)
  • You have created a custom field on the Master Object that is also named ID. Even though the Web API name will have a suffix identifying it as a custom field ( c), this can still cause the error listed above as Conga Composer is "confused" by the presence of two ID fields.

WHAT TO DO
Rename your custom ID field (e.g. "Custom ID"), updating both the field label and API field name, and re-run your Composer solution.
You may need to restart your internet browser in order to clear the cache and have Composer recognize the new name of your custom ID field.

Invalid PPTX TableGroupStart Field

ERROR MESSAGE: PPTX templates that use TableGroupStart but which has no data. Cause
This error occurs in PPTX templates that use TableGroupStart which has no data. WHAT TO DO
Use a SlideHide for the same dataset at the bottom of the page.

Invalid Query Filter Operator

ERROR MESSAGE: Invalid Query Filter Operator. Cause
This message can occur if you enter a pv1 without a pv0. WHAT TO DO

  • You must specify pv0 as well as pv1. For example:

should read

Invalid Session ID found in SessionHeader (Release 7)

ERROR MESSAGE: Problem related to button URL. Cause
This error typically occurs when there is a problem related to the button URL. Issues that can cause this error include:

  • The object name of the Master Object is too long.
  • There are spaces in the button URL. Check the button URL, especially at the end of each line where spaces tend to "hide" to ensure that there are no spaces within the URL.
  • The button URL is too long. Too many characters in a button URL can prevent Composer from running properly.
  • The "Lock sessions to the IP address from which they originated" setting is enabled in your Salesforce instance. With this setting enabled, Conga Composer cannot operate. To check this whether this setting is enabled, navigate to Salesforce Setup > Administration Setup > Session Settings.
  • Salesforce.com has timed out. Try refreshing your webpage, logging out of Salesforce and logging back in, and restarting your internet browser.

What To Do

  • Clear your cache and try again

Upgrade to Conga Composer Release 8

  • If you are using Conga Composer Release 7, ensure you are not running it in Lightning or Salesforce1, or using an OAuth button


Merge and Box errors

Error messages might appear when you select Merge and Box in Composer: There was an issue processing the Composer request or the remote server returned an error: (409) Conflict.
Known Errors and Workarounds
Error messages might appear when you select Merge and Box in Composer:
Error:
There was an issue processing the Composer request The remote server returned an error: (409) Conflict. Cause
A common reason for these errors is that there is more than 1,000 folders included at any given level of the Composer document output file path. For more information on the OFP parameter, see: https://support.getconga.com/ Conga_C...eter_Guide/OFP Composer uses Box's Get Folder Items API call to identify folders where the document
is saved. The Get Folder Items API call has a limit of 1,000 folders. Composer is unable to query for folders beyond the limit. For more information on Box, see: {_}https://developer.box.com/reference#...-folders-items_
Solution:
Add folder levels to your OFP parameter that do not exceed 1,000 folders at any given level in your Box account.

No DocuSign Recipients Defined (Release 7)

ERROR MESSAGE: No DocuSign recipients defined. Cause
This can occur for a few reasons:

  • The master object is an Opportunity and the Opportunity Contact roles do not align (aren't synced) with the DocuSign roles. To resolve edit either the Salesforce or DocuSign roles so they match. Then any contact roles from the Opportunity will be assigned as Recipients on the DocuSign Envelope
  • The &DocuSignR1Id is not set to a valid ID (for example setting it to a Contact's text value rather than the ID)
  • The user doesn't have access to the field used for the Docusign Recipients parameter.

What To Do

  • Ensure a Recipient is defined
  • Ensure the Recipient ID is a valid record
  • Check Field Level Security on the Recipient Object (Lead, Contact, or User)
  • Check Field Level Security on the Master Object
  • Ensure DocuSign for Salesforce is functioning in the org


Object reference is not set to an instance of an object (Release 7)

ERROR MESSAGE: View Data Excel workbook. Cause
This error message will appear in the View Data Excel workbook on one or more worksheets where a query has been used to retrieve data. It indicates that something is wrong with that particular query dataset –it's incorrectly referenced, inaccessible, or incorrectly written.
What to do

  • Confirm that the proper query ID has been referenced in the Conga Composer button or link URL. Copy the query ID from the button URL and paste it into your Salesforce URL to ensure that it's connected to a Conga Query record.
  • If you see a Salesforce error message indicating the record is not available, it's either been deleted, was copied from a Sandbox and needs to be re-created in production, or the user doesn't have permissions to access the Query record.
  • Confirm that the user profile has access to the Conga Queries custom object. Navigate there by clicking Salesforce Setup > Administer |Manage Users > Profiles > Object Settings > Conga Queries. "Read" is the minimum level of access required while "Edit," "Create," "Delete," "View All," and "Modify All" are optional. Confirm this level of access for all profiles running Conga Composer solutions.



Object reference is not set to an instance of an object (Release 8)

ERROR MESSAGE in Composer, Conductor, and Workflow. CAUSE
Related to a bad merge field or mismatching TableStart and TableEnd merge fields in a detail region. WHAT TO DO
A good start is to remove paragraphs (or entire pages for larger templates) and repeat the merge until you find the issue. Then you can correct the merge field or detail region causing the problem.
For example, you may receive the error message if the TableStart and TableEnd merge fields are not in the same row of the detail region. The correct usage of TableStart and TableEnd merge fields is shown below.





















CAUSE
You may also receive the error message if data with double quotes is being merged into an IF statement in a Microsoft Word template.
WHAT TO DO

  1. Remove the double quotes from the field.
  2. Create a new formula field or DV0 parameter and reference the value of the existing field in a Salesforce SUBSTITUTE formula to remove all double quotes from the field value. Then reference the new formula field or DV0 parameter within the IF statement.

Conga Conductor and Conga Workflow Release 8
Cause
For Conga Conductor and Conga Workflow, this error message is most commonly caused by field level security issues with the formula field that contains the Conga Conductor or Conga Workflow formula.
What to Do

  1. Navigate to Salesforce Setup > Security Controls > Field Accessibility.
  2. Select the object on which the field exists, select View Fields, and then select the field.
  3. Lastly, select the Profile of the user running the Conductor solution (or the Profile of the User to Send as user for Workflow) and ensure that Profile has visibility to the formula field.












One-Time Set ups after Conga Composer is Installed

If you are seeing this error, Step 1 is the place to start: OAuth Error:Failed to get the authorization response Step 1: https://support.getconga.com/Conga_C...lution_Manager

One or More Templates Failed to Merge or Operation Was Cancelled

ERROR MESSAGE. Related to a bad merge field or mismatching TableStart and TableEnd merge fields in a detail region. A similar message is the operation failed.

Issue

There are several possible causes for the following error message: One or more templates failed to merge or operation was cancelled:

  1. Related to a bad merge field or mismatching TableStart and TableEnd merge fields in a detail region.
  2. Data containing double quotes are being merged into a Microsoft Word IF Statement.
  3. Remove the double quotes from the field.
  4. Create a new formula field or DV0 parameter and reference the value of the existing field in a Salesforce SUBSTITUTE formula to remove all double quotes from the field value. Then reference the new formula field or DV0 parameter within the IF statement.


Ouch... something's definitely gone wrong. Please try again. (Error #1890: ORNF) (Release 7)

ERROR MESSAGE: Improperly formatted template. Cause
The error is triggered when you have an improperly formatted template: Examples of problems that may trigger this include:

  • Carriage Return in a merge field
  • An errant character in a merge field's label
  • Contact Conga support for assistance in identifying the specific problem in your template.

What To Do

  • Clear your cache

Upgrade to Conga Composer Release 8

Our Apologies . . . Your Conga URL contained illegal characters (Release 8 and 7)

ERROR MESSAGE: Illegal character used in Conga URL. Cause
You receive this error message when illegal characters are used in the Composer button URL. What To Do
The following illegal characters must be removed from the URL:

  • • Spaces
  • • & (anywhere other than at the beginning of a parameter)
  • • % (percent)
  • • | (pipe)
  • () (parenthesis)
  • " (double quotation marks)
  • ' (Apostrophe)


Page Cannot Be Found

ERROR MESSAGE: Page cannot be found. Cause
This error occurs when there are spaces in your URL. What To Do
Examine your button or link URL and look spaces when you have cut and pasted the button code from another source.
A Conga button, when launched, is essentially a URL being passed between servers. Spaces in the URL will cause the "string" to break. Use Notepad or a similar text editor when copying and pasting buttons in your Salesforce org to avoid formatting errors.

Read pdf error: Trailer is not found (Release 7)

ERROR MESSAGE: Read PDF Error: Trailer is not found (Release 7). Cause
This typically occurs when the associated PDF file is corrupted. What to do
Try regenerating the template and re-uploading it into Salesforce.

Reduce complexity of SOQL statement to avoid errors

You see the following error when viewing the standard Opportunity Line Items (Opplineitem object) data set in both the Template Builder and View Data workbook from a button on the opportunity object: QUERY TOO COMPLICATED: Query is either selecting too many fields or the filter conditions are too complicated.
Question or Problem
You see the following error when viewing the standard Opportunity Line Items (Opplineitem object) data set in both the Template Builder and View Data workbook from a button on the opportunity object: QUERY TOO COMPLICATED - Query is either selecting too many fields or the filter conditions are too complicated.
Causes or Possible Causes
Long, complex SOQL statements, such as statements that contain many formula fields, can sometimes result in a QUERY_TOO_COMPLICATED error. The error occurs because the statement is expanded internally when
processed by Salesforce, even though the original SOQL statement is under the 20,000 character limit. To avoid this, reduce the complexity of your SOQL statement.
When Composer performs queries on Opportunity Line Items, 3 objects are retrieved:

  1. OpportunityLineItem
  2. OpportunityLineItem.PricebookEntry
  3. OpportunityLineItem.PricebookEntry.Product2

The resulting query exceeds the 20,000 bytes and the query fails due to the excessive number of custom fields. For more information, see the Salesforce documentation for SOQL limits: {_}https://developer.salesforce.com/docs/atlas.en-_ us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select.htm

Report exceeds maximum supported rows from PointMerge (Release 7)

ERROR MESSAGE: Report exceeds maximum supported rows PointMerge. (Release 7). Cause
Conga enforces a data set limit of 1500 rows. This message occurs when you are attempting to use a data set that exceeds that maximum.
What to do

  • The work around for the data-set row limit is to break that data set up into multiple queries/reports, each limited to 1500 rows.
  • A common approach is to sort the query alphabetically and create multiple clones, each for a different portion of the alphabet; i.e. A-G, H-N, O-Z.


Report size cannot be determined, either because the report is excessively large, the report is unavailable or the report type is matrix. Please verify the Report Id.

ERROR MESSAGE. This error message appears in Conga Template Builder and View Data workbook.
Cause
This error message appears in the Conga Template Builder and View Data workbook.

  • The report is returning too many results (rows of data). Conga Composer Release 7 supports a maximum of 1,500 results per report while Release 8 supports a maximum of 2,500 results per report.
  • Matrix reports, joined reports, and historical trending reports are not supported. these report types. You may also receive this error message if you have exceeded the limit for rows or lines of data.
  • The report is not returning any data because the report filters are not configured properly.
  • The report ID referenced in the Conga Composer button or link URL is incorrect.
  • The report is inaccessible.
  • The report no longer exists.
  • There is a space in the Conga Composer button or link URL preventing the report ID from being read. What to do
  • Limit your report to align with the 1,500 or 2,500 result maximum. Please see the Know Your Conga Limits article for more information on limitations.
  • Use a summary or tabular type of report.
  • Conga Composer's default behavior is to pass the Salesforce record ID of the master object (usually the object from which you launch Conga Composer) to the first filter in each report. Ensure your report is configured to accept the master object ID or update the Composer button or link URL to override this behavior. Please see How to Use Salesforce Reports with Conga Composer for further details.
  • Ensure the report ID referenced in the button or link URL corresponds to the report you want Conga Composer to run. Copy the report ID from the button or link URL and paste it into the browser's Salesforce URL to confirm it is indeed the proper report.
  • Do you have access to the report? It may be saved in a report folder to which you don't have access. Copy the report ID from the button or link URL and paste it into the browser's Salesforce URL to confirm
  • The report may have been deleted. Copy the report ID from the button or link URL and paste it into the browser's Salesforce URL to confirm it is available. If it's not available, check the Salesforce Recycle Bin and undelete the report.
  • Edit the button or link URL and delete any spaces (there should be zero spaces in the URL). Spaces often "hide" at the ends of lines within the URL.



REQUEST LIMIT EXCEEDED:TotalRequests Limit exceeded

ERROR MESSAGE. Request limit exceeded: TotalRequests Limits exceeded.

Cause

This error is received when your organization has reached its 24-hour API Limit.

What to do

To check the limit, go to the Company Information page in Salesforce (Setup > Company Profile > Company Information). The API Requests line will indicate how much of your API allocation has been consumed.

Server was unable to process request. Value cannot be null. Parameter name: password

ERROR MESSAGE. This error message occurs when a Salesforce User does not have their DocuSign credentials entered on their User record.
Cause
This error message occurs when a Salesforce User does not have their DocuSign credentials entered on their User record.
What to do
When running a Conga routine involving DocuSign and Composer in background mode (DS7/Workflow/Conductor), a complete DocuSign password must be current on the User Profile in Salesforce.
If a version of DocuSign is upgraded, the Password for the Salesforce User Profile must be re-entered.

Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google Sign In

Error: Sign in with Google temporarily disabled for this app. This app has not been verified yet by Google in order to use Google Sign In.
Question or Issue
When you click to create a Google token button on the Setup pages for Composer, Conductor, or Workflow, you receive the following error during the login process: Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In.
Causes or Possible Causes
Recent updates made by Google resulted in this error. Related Known Errors and Workarounds
Our development team is investigating a fix. As a workaround, you can launch the process manually.

Something's gone wrong! An internal server error has occurred

ERROR MESSAGE. Salesforce API limit exceeded. Cause
This error occurs when you reach your Salesforce API limit. What to do
To check the limit, go to the Company Information page. The API Requests line will indicate how much of your API allocation has been consumed.
The API request field is not updated in real time. It has a lag time of up to 15 minutes.

Something's not quite right about your data – it can't be displayed in Excel. Column 'id' does not allow nulls. (Release 7)

ERROR MESSAGE: Something's not quite right about your data – it can't be displayed in Excel. Column 'id' does not allow nulls.
CAUSE
The Conga View Data Workbook generates an Excel workbook based on the dataset supplied to Conga in your solution. This error occurs when the dataset supplied to Conga is empty. There are a variety of reasons that can cause this such as:

  • A poorly formed query can filter out all data resulting in an empty dataset
  • A Salesforce report that filters out all data
  • Permissions that do not allow the user running the solution to see the required data

WHAT TO DO

  • Review your data for null values (ensure every record in your report has an ID)
  • Test on a different record
  • Run your Salesforce report outside of Conga Composer (by entering your record ID in the first filter on the report)
  • Unless you are using Mail Merge or Conductor, remove the ID column from your report


Something's wrong with your template (bad mojo). The merge template has serious problems

ERROR MESSAGE: This error indicates that something is wrong with the template(s).
Cause:
This error indicates that something is wrong with the template(s). Unfortunately the error doesn't correspond to one specific issue within the template so it can sometimes be challenging to diagnose and find the source of the problem; the below steps will help narrow down the cause.

  1. If you are using multiple templates in your merge process, merge to each of them separately to find out specifically which template is causing the "bad mojo" error. If the error message results from more than one of the templates, you'll need to take the following steps with each of the templates individually. Also, if you're merging to PDF output, you may want to try the below steps with merging to both PDF output and "same as template" output to see if the error message results are different one way versus the other.
  2. Save a new copy of the problem template (the one resulting in the error message) to your local computer (e.g. My Documents, Desktop) and run it through the merge process as a local template (no need to upload it to Conga Templates since we'll be testing this way over and over again) to ensure you still get the error after saving a new copy of the template (if you do receive the error message again, proceed to step 3). If you do not receive the error again, try simply re-uploading this new version of the file to your template record in Conga Templates and run your merge process using that version of the template.
  3. Open the template in its native program (e.g. Microsoft Word). Click to the end of the template, delete the last section (e.g. table, paragraph, etc.), do a Save As to save your changes, and run it through the merge process as a local template. If you receive the error message again, that indicates that the source of the problem was not located in the last section of the template (the section you just deleted).
  4. Proceed once again to the end of the template, delete the next section, save your changes, and run the template through the merge process as a local template. If you receive the error message again, you'll need to repeat this step (#4) until you run the template through the merge process and do not receive the error, at which point you can proceed to step 5.
  5. When you can run your template through the merge process and not receive the error, you should be able to isolate the section of the template that is causing the error (e.g. the table using TableGroup on page 2). You can confirm it is indeed that section by adding in the other sections you previously deleted but leaving out the section you believe is causing the error and run the template through the merge process again.
  6. You've now isolated which section of your template is causing the "bad mojo" error. Try deleting this section and recreating it from scratch to fix the error. For instance, if it's a table that's causing the problem, delete the entire table and its contents, insert a new table from scratch, and re-insert the merge fields and any static text

within the table. DO NOT copy and paste from the previous version(s) of the template as this likely could be what was causing the problem in the first place. Save your changes and run this new version of the template through the merge process as a local template. If it merges and does not result in the error message, upload it to Conga Templates and run the merge again to confirm that it still works without issue. If the merge results in the error message again, proceed to step 8.

  1. You've isolated the section of the template that is causing the error and have recreated that section but it still hasn't fixed the template. Therefore, try recreating that section in a brand new, fresh template with no other data in it, save it to your local computer and run it through the merge process as a local template. You can also try adding back in just one component of that section at a time. For instance, you might start with a blank table and if you don't receive the error then you can add the static text and run it again. If that works without error, then add back in a couple of merge fields, and so forth.

What To Do
After following the above instructions, you should be able to isolate and fix the source of the error. If not, then you can try the below steps as well:

  • If using a Word .docx file, save a new copy of the template as .doc and run that version through the merge process instead.
  • Are you merging the output file to PDF? If so, try merging to "same as template" (e.g. Word template to Word output) to see if the error still results. The contrary method can also be helpful - if you're merging to "same as template," try PDF output instead to see if the error results are different.
  • Are you using the &AWD parameter in your Conga Composer button URL? If so, remove the parameter or change it to &AWD=0 (either accomplishes the same behavior) and run the merge process again.

If you're still experiencing difficulties after following all of the above troubleshooting advice, please contact our support team.

Stack Empty (Release 7)

ERROR MESSAGE. Detail region tags (TableStart/End) placed within nested IF statements generates an error message when merging a Word Template.
Cause
When you receive a 'Stack Empty' error message when merging a Word Template, it usually means that there are detail region tags (TableStart/End) placed within nested IF statements.
IF fields in Word display content conditionally. If some of these detail region tags are shown incorrectly on a conditional basis, it can result in mismatched TableStart/End detail regions due to the conditional formatting. This can result in the "Stack Empty" error.
What to do
The best solution to this issue is to adjust your detail region tags so that they're not embedded within IF statements, or if they must be, ensure that each one will have a corresponding Start/End position.
If the above solution does not fix the issue, you may want to check your footers and headers for possible errors, as this can also cause the "Stack empty" error. To troubleshoot headers and footers, save a new copy of your template and then remove one header or footer at a time, doing a test merge operation using the local template each time. Once you can run the merge operation without an error, you should be able to narrow down which header or footer section is causing the issue.

String not recognized as a valid DateTime

ERROR MESSAGE. Conga cannot format a non-date field as a date. Cause
This error results when there is a merge field on the Word template that is formatted as a date (e.g. @ "MMMM d, yyyy") while that field in Salesforce is not a date field (e.g. instead it's text). The error results because Conga cannot format a non-date field as a date.
What to do
To fix the error, start by toggling all field codes on Word template (Alt + F9). Look for non-date fields that are formatted as dates. Beware, as some fields that sound like date fields (e.g. Deliverable Due Date) are in fact not. When you find the merge field in question, delete the date formatting (e.g. @ "MMMM d, yyyy"), right-click the field and select "Update Field." Alternately, you may delete the entire merge field and simply re-enter it without any date formatting.
The error may appear when merging from some records and not from others. This is because the field in question is not populated on the records where the merge works.

Template Id(s) do not exist


ERROR MESSAGE. Having a dash "-" or a forward slash "/" in the template alias produces the error: "Template Id/s do not exist." Dashes and slashes are not supported in the Template Alias.
CAUSE
Having a dash "-" or a forward slash "/" or an underscore "_" in the template alias produces the error. WHAT TO DO
Dashes and slashes are not supported in the Template Alias. If you need to use those characters you'll need to use the &OFN parameter instead.
This produces an error:
&TemplateId=[Pipeline+Report+_+2015-01-27]a0Cj0000001I1Xj This Works:
&TemplateId=a0Cj0000001I1Xj&OFN=Pipeline+Report+_+2015-01-27
It is important to note that all special characters can be problematic with using the &TemplateId parameter.


Template Id is Invalid

ERROR MESSAGE. Formatting template ID parameter. Cause
An extra space after a template ID parameter will cause an error when adding multiple template IDs. Example:
What to do
Remove the spaces and it will fix the error. If you are using formula fields/if statements, make sure to add the comma before the ID in the clause.
Best practice:
Note: There is a limit of 10 template IDs allowed. You will receive an error message you exceed this amount that says: You have exceeded the maximum allowed templates per merge. Allowed: 10

There hasn't been a file or email template ID defined, background mode cannot continue when trying to use (Release 8)


ERROR MESSAGE. Background mode parameter (&DS7) is used but a Template ID or Conga Email Template ID has not been specified.
Cause
This Conga Composer error message occurs when the background mode parameter (&DS7) is used but a Template ID or Conga Email Template ID has not been specified. Because background mode skips the user interface in which you can choose which template or email template to use in the merge process, the template or email template must be pre- defined in the button or link URL via its Salesforce ID.
In other words, anytime you use the &DS7 parameter, you must also have the &TemplateID and/or &CongaEmailTemplateID (a.k.a. &CETID) parameter(s) included.
What to do
The below button or link URL example includes a pre-defined template using the &TemplateID parameter as well as a pre-defined Conga Email Template via the &CongaEmailTemplateID parameter. The solution also runs in background mode (&DS7) meaning the typical Conga Composer user interface is skipped; in this case because the background mode value is 2 (&DS7=2), the merged output file is attached to the Conga Email Template for sending via email. https://composer.congamerge.com?sessionId=\{Unable to render embedded object: File (API.Session_ID\}&serverUrl=\{) not found. API.Partner_Server_URL_290}&id={!
Opportunity.Id}&Queryid=[ProductsTotal]a05i000000LfoYM&TemplateID=a04i000000GGSj8&CongaEmailTemplateID=a03i000
+for{!Opportunity.Account}_{!TODAY()}


There is no row at position 0

ERROR MESSAGE. Restricted Field-level security settings on user profiles.
Cause
This Conga error message will occur if the end users have Restricted Field Level Security set for their profile. If the end users are trying to generate a document that requires data from certain fields or reports that they do not have access to they will see this error message. Restricted Field-level security settings let administrators restrict user access to view and edit specific fields. In some cases there may be a change to security settings that can contribute to why some end users may have access verses others.
What to do
Contact your Salesforce Administrator to find out if there has been a change in the security settings. For more information see Salesforce Field-Level security.

There was an issue getting the Conga Authorization Response

Conga Error Message.
Cause
This error message is usually caused when there is an issue reaching the Conga servers. What to Do

  1. Clear your browser's cache and cookies.
  2. Ensure that there are no firewall or security settings that may be blocking your connection.
  3. Check the status page - {_}http://status.getconga.com/_
  4. You made need to "white-list" these two Conga URLs by adding them to your browser's Allowed Sites:
    • https://*.congamerge.com
    • https://*.appextremes.com
  5. Contact Conga Support



There was an issue processing the Composer request

Conga Composer error message when using Box. Issue
The following error messages may be sporadically generated when clicking Merge and Box in Conga Composer:There was an issue processing the Composer request. The remote server returned an error: (409) Conflict. A common reason for these errors is having more than 1,000 folders included at any given level of the Composer document's output file path (see OFP for more information). This is because the API call Box makes has a limit of 1,000 folders, so Composer is unable to query for folders beyond the 1,000th folder.
What to Do
The solution is to ensure there will never be over 1,000 folders at any given level in your Box account.

The ',' character, hexadecimal value 0x2C, cannot be included in a name


ERROR MESSAGE. This error message results when two parameters that use sequential numbering are included using the same number in a Conga Composer solution that's configured to run in Background Mode (using the &DS7 parameter).
Cause
This error message results when two parameters that use sequential numbering are included using the same number in a Conga Composer solution that's configured to run in Background Mode (using the &DS7 parameter).
An example of a parameter that uses sequential numbering is the Master Field to Set (&MFTS) parameter because you would begin with &MFTS0 and &MFTSValue0 but can include a second parameter that should be incrementally numbered, &MFTS1 and &MFTSValue1.
The error occurs when the sequentially ordered parameter is mistakenly not sequentially ordered but rather the same number is used more than once (e.g. &MFTS0, &MFTSValue0 and &MFTS0, &MFTSValue0 - both parameter sets using 0 instead of the first using 0 and the second using 1). The error message will only occur when such a Conga Composer solution is configured to run in Background Mode. A sample Composer button URL is included below with the offending Master Field to Set and Background Mode parameters. https://composer.congamerge.com?sessionId=\{Unable to render embedded object: File (API.Session_ID\}&serverUrl=\{) not found. API.Partner_Server_URL_290}&id={!
Opportunity.Id}&Queryid=[ProductsTotal]a05i000000LfoYM&TemplateID=a04i000000GGSj8&CongaEmailTemplateID=a03i000
+for{!Opportunity.Account}_{!TODAY()}&MFTS0=Description&MFTSValue0=Awesome
+description&MFTS0=Amount&MFTSValue0=10000&DS7=1
What to do
To correct this error, edit the sequentially numbered parameters so that they are incrementally numbered (e.g. 0, 1, 2). For example, to fix the above button URL we'd change the second occurrence of &MFTS0 and &MFTSValue0 Master Field to Set parameters to &MFTS1 and &MFTSValue1 instead. You may keep the Background Mode (&DS7) parameter. https://composer.congamerge.com?sessionId=\{Unable to render embedded object: File (API.Session_ID\}&serverUrl=\{) not found. API.Partner_Server_URL_290}&id={!
Opportunity.Id}&Queryid=[ProductsTotal]a05i000000LfoYM&TemplateID=a04i000000GGSj8&CongaEmailTemplateID=a03i000
+for{!Opportunity.Account}_{!TODAY()}&MFTS0=Description&MFTSValue0=Awesome
+description&MFTS1=Amount&MFTSValue1=10000&DS7=1


The report is invalid. Are you using My Domains or matrix style reports?

Conga Error Message.

Issue

If permissions to the reports are granted, sharing settings to the folder are set, and it is not a matrix style report and users still see this error, it is likely that they have High assurance session required enabled in their Salesforce org under Access Policies.

Workaround

Disable the High assurance session required policy in Salesforce Setup > Customize > Reports and Dashboards
> Access Policies. Use Conga Queries, which are unaffected by this Access Policy.

Parameter p3lkid value error

ERROR MESSAGE. This is a Salesforce error. It typically results because of a problem in the Conga Composer email parameters.
Cause
The p3_lkid parameter value contains a character that is not allowed or exceeds the maximum character value length.
The error is a Salesforce error that appears on the Salesforce page rather than the Conga Composer dialog box. The error typically occurs when a problem occurs with the Conga Composer email parameters.
What to do

  1. Remove any unacceptable characters from the p3_lkid parameter value or reduce the value length of the value and resubmit.
  2. Review the Composer button URL to resolve any of the following issues:
    • &EmailRelatedToId={!Lead.Id} The Salesforce email message generated from a Lead object does not include the "Related To" field, which results in the above "p3_lkid" error.
    • &EmailRelatedToId is set to a name field rather than an ID field.
    • You specified the same object ID in both &EmailToId and &EmailRelatedToId. For example:
      • &EmailToId={!Contact.Id}
      • &EmailRelatedToId={!Contact.Id}
    • &EmailToId should be used to specify the primary recipient ("To" field on the email message) while &EmailRelatedToId is used to populate merge fields in the email template body from a related object or for activity logging purposes. An example of the correct usage of both parameters would be:
      • &EmailToId={!Contact.Id}
      • &EmailRelatedToId={!Account.Id}
    • You used the &EmailTemplateId and &EmailSubject parameters. Remove &EmailSubject since it is redundant. The email template specified using &EmailTemplateID already includes an email subject.
    • If you use a Custom Object and have not enabled Track Activities, the Conga Button does not allow you to send email. Allow Activities must be enabled for Custom Objects in order to send Emails from Conga.



Unable to parse the query id entries, please check the URL syntax (Release 8)


ERROR MESSAGE. This error results from an invalid report or query alias. Cause
This error results from an invalid report or query alias. Report and query aliases must be enclosed in square brackets, cannot contain spaces or special characters and are limited to 20 total characters. The dataset names of "Master," "Org," "User," "ReportData" and "QueryData" cannot be used as aliases because they are reserved for the default datasets.
What to do
To resolve the error, please check your report and query aliases, change them as needed, save your changes, and test your Conga Composer solution once more. As a reminder, report and query aliases (below, highlighted in yellow) are included before the report or query ID. For example:https://composer.congamerge.com? sessionId={!API.Session_ID}&serverUrl={!API.Partner_Server_URL_290}&id={!Account.Id} &ReportId=[Cases]00Oi00000063Kae&QueryId=[TechBuyerContact]a05i000000L3p0W


Unexpected end of children nodes reached (Release 7)

ERROR MESSAGE. This error is usually caused by a carriage return (line break) located within a merge field. Cause
This error is usually caused by a carriage return (line break) located within a merge field. What to do

  1. Open yourWord template and toggle the field codes by pressing Alt+F9.
  2. Click ¶ to view paragraph formatting.
  3. Examine the display to locate carriage returns in any merge fields.
  4. Delete any carriage return within merge fields.



URLENCODE function for illegal characters in button URL

ERROR MESSAGE. The "#" symbol in your Invoice Key field causes a problem when it's used in the Conga Composer button URL as pv1 for the report, as it's not a "browser-friendly" character. We can use Salesforce's URL Encode function to fix this.
Cause
The "#" symbol in your Invoice Key field causes a problem when it's used in the Conga Composer button URL as pv1 for the report, as it's not a "browser-friendly" character. We can use Salesforce's URL Encode function to fix this.
What to do
To do so, edit your Composer button URL. Insert the URLENCODE function into the report ID's pv1 parameter. It should look something like this:
...~pv1={!URLENCODE(text)}
You'll replace "text" with the field for the Project Invoice Key. Note that you'll need to remove the {} from either side of your merge field name for Project Invoice Key, otherwise the URLENCODE function will throw an error.
The whole thing should look something like this:
...~pv1={!URLENCODE(Project.Invoice_Key c)}

User Management Access Error

ERROR MESSAGE: This message occurs when User Management has been enabled but Conga has not been enabled for the user's log-in (the user is not listed as an authorized user in User Management).
Cause

  • This message occurs when User Management has been enabled but Conga has not been enabled for the user's login (the user is not listed as an authorized user in User Management).
  • The same error message can also result if the &DC (disable Conga) parameter is included in the Conga custom button/link URL but the &DCL (disable Conga label) parameter has not been included. &DCL provides a custom message when Conga has been conditionally disabled using &DC. If &DCL is not included, the default message is:

"Access not authorized. Please contact your Salesforce administrator and ask to have your name added to Conga Setup > User Management."
What to do
To correct the error, go to Salesforce Setup > Installed Packages and then click Manage Licenses next to the Conga Composer package and ensure the user has been assigned a license.
Tip: To learn about the User Management tab see User Management Settings

If the &DC (disable Conga) parameter is included in the Conga custom button/link URL but the &DCL (disable Conga label) parameter has not been included, check the Conga button URL to evaluate the &DCL conditions and change as necessary.
For more Composer troubleshooting help, see Composer Troubleshooting Tips.

Composer Output Contains Blank Fields

Troubleshooting checklist for when output documents do not contain expected data.
Cause
Conga Composer will retrieve data from Salesforce.com for all of the fields specified in your template according to the profile permissions of the running user. If a user is merging a document and is not receiving the expected data in the output file, troubleshoot the issue with the following list:
What to do
Conga Composer will show a blank value in the merged output file if the field in Salesforce is blank,
The merge field name in the document template needs to exactly match the field name as it's listed in the Template Builder or View Data workbook. If you are unsure whether the field name from the Template Builder matches what's in your template, delete the merge field in the template and create a new one from scratch.
If your Word template uses traditional merge fields (e.g. «ACCOUNT_NAME») instead of text-based merge fields (e.g. ACCOUNT_NAME), ensure that you are comparing the field name, not the field label. The field name is what needs to match the field name that's listed in the Template Builder. Please see What is the difference between a Field Label and a Field Name for further information.
If a user does not have access to a field in Salesforce, then that user will not be able to merge that field using Conga Composer. For Salesforce Enterprise Edition and above, this means ensuring the user's Profile has access to the field via field-level security. For Professional Edition, this means ensuring that the field is included on the page layout.
The user will need access to the report and report folder for any fields that are being retrieved through a Salesforce report for a Conga Composer solution. When fields are retrieved via SOQL queries, the user will need access to the Conga Queries custom object and all of its fields.
For Enterprise Edition and above, this means users must have at least "read" access to the Conga Queries custom object as well as visibility to all fields via field-level security. For Professional Edition, all of the Conga Queries fields need to be included on the Conga Queries page layout. The specific Conga Query record will also need to be accessible by the user. Please see Profile Permissions needed to use Conga Composer for further information.
If you are still experiencing difficulties after troubleshooting the issue using the above checklist, please Contact Support.

Your Conga Session has Expired

ERROR MESSAGE. Users get "Your Conga Session has Expired" immediately upon starting Conga Composer Cause
Users receive the following error message when launching Composer: "Invalid Session or your session has expired. (Lock IPs may be enabled.)"
This error occurs when the "Lock IP Address" setting is enabled or when launching a non-OAuth button in Lightning. What to do
Disable the "Lock IP Address" setting for hosted AppExchange applications.

  1. Navigate to Salesforce Setup > Administration Setup > Security Controls > Session Settings.
  2. Ensure that the "Lock sessions to the IP address from which they originated" field is NOT checked.
  3. Save.

Convert your non-OAuth buttons to OAuth buttons for Lightning.
You must RESTART all instances of the browser for the setting to take effect.

Salesforce session expired or the Salesforce API Servers are offline - INVALID SESSION ID or SERVER URL (Release 7 and 8)

ERROR MESSAGE. This article lists the reasons for receiving the "Your Salesforce session has expired or the Salesforce API Servers are offline. INVALID SESSION ID or SERVER URL (Release 7, Release 8)" error.
Cause
This error message usually results because of one (or more) of the following reasons:

  • "Lock sessions to the IP address from which they originated" has been enabled in your Salesforce instance. With this setting enabled, Conga Composer cannot operate. To check this whether this setting is enabled, navigate to Salesforce Setup > Administration Setup > Session Settings.
  • The users running Conga Composer do not have the "API Enabled" permission on their profile. This setting is on the Profile > Administrative Permissions > API Enabled.
  • The maximum API request limit for your Salesforce instance has been exceeded for the day. If your Salesforce instance has exceeded its maximum API requests, then Conga Composer cannot run (as we require the API

to operate). This is a rolling 24 hour period so with each hour that passes, you will slowly accrue "fresh" API requests.

  • The server for your Salesforce instance (e.g. na3) is experiencing downtime/degradation issues.
  • You will also receive this error if you are launching a non-OAuth button in lightning.

What to do

  • Check your API usage under Salesforce Setup > Administration Setup > Company Profile > Company Information > API Requests, Last 24 Hours.
  • Ensure "Lock sessions to the IP address from which they originated" is NOT enabled
  • Ensure the user running the solution has "API Enabled" on their Profile
  • Ensure you have not reached your maximum API request limit
  • Check if the server for your Salesforce instance is experiencing downtime or degradation issues. See {_}http://_[ trust.salesforce.com/trust/status|http://trust.salesforce.com/trust/status].


"Conga can't communicate with Salesforce" error

Conga is unable to communicate with Salesforce. Cause
Conga is unable to communicate with Salesforce. What To Do

  • Ensure "Lock Sessions to IP Address from which they originated" is disabled (Setup > Administration Setup > Security Controls > Session Settings).
  • Verify that the Session Timeout value is at least 30 minutes.
  • Ensure the Conga Composer URL contains an "&Id=" parameter and that it is set to a valid Id.
  • Don't try to "Preview" a Conga Composer button. You must click it from a Salesforce record.