Event 1 Knowledgebase

Category » Integrator

There were 14 questions found in this category:

1. Cannot open connection after moving Prolog Manager database to a new server
   Background:Before moving a Prolog Manager database to a new SQL Server, you must first remove the SDKUser account from the database. Failing to do so will result in orphaned security records and prevent the normal operation of Event 1 Integrator.This article addresses how to resolve the problem ...
2. How do I copy an existing connection to another workstation running Integrator?
   Integrator connections are stored in the Integrator database that resides on the same server that contains your Prolog Manager database(s). When you create a new connection, the connection name and settings are stored in the Integrator database. At the same time, a file is also placed in the In ...
3. How do I migrate from one SQL Server to another?
   BackgroundThis article covers the process associated with relocating your Prolog Manager database from on SQL Server to another. This must be accompanied by the relocation of the Integrator database as well as updates to the Integrator connection file(s). The steps in this article assume a basi ...
4. Message 20001 - Could not convert the Prolog Manager project number to a valid Sage Timberline Office job number
   Description This message is reported when the Project Number of the contract does not result in a valid Job Number for Sage Timberline Office. In many implementations of Integrator, the Sage Timberline Office Job Number is identical to the Prolog Project Number however an alternate value may be ...
5. Message 20002 - Sage Timberline Office commitment ID is too long. The maximum size allowed by Sage Timberline Office is n characters
   Description The Commitment ID for Sage Timberline Office has a maximum size which is 12 characters by default. This can be smaller depending on your implementation of Sage Timberline Office. This message occurs if the contract in Prolog Manager would use a Commitment ID that is larger than the ...
6. Message 20003 - There are no Schedule-Of-Value items for this contract
   Description In order to send a Contract from Prolog Manager to Sage Timberline Office, the contract must have at least one item in its schedule of values. This message occurs when a contract is encountered that does not have any items. Resolution · Option 1 - Open the contract in Prol ...
7. Message 20004 - Job was not found in the Sage Timberline Office job list
   Description The Sage Timberline Office Job Number identified by the Contract in Prolog Manager could not be found in the list of jobs in Sage Timberline Office. Resolution It may be possible that the job has not yet been created in Sage Timberline Office Job Cost. You should review the reso ...
8. Message 60002 - Project [Number] does not have a cost period for the date [Date]
   Background In order for Integrator to create a General Invoice or Contract Invoice, the invoice must be assigned to a valid Cost Period that is setup in Prolog Manager. Each project contains its own list of Cost Periods. An individual Cost Period in the list is identified by a unique identifier ...
9. Message 60005 - Contract invoice is linked to a future change order
   Full Message Contract invoice is linked to a future change order. This is not allowed by Prolog Manager business-rules. The date of cost period of the invoice would be [Period] ([From Date] to [To Date]). The date of subcontract CO [SCO Number] (contract [Contract Number], project [Project Numb ...
10. Message 60015 - Contract [Contract] of project [Project] was not found in Prolog Manager
    Background When transferring costs from Sage Timberline Office to Prolog Manager, transactions that identify a Commitment ID are assumed to represent transactions that should result in the creation of Contract Invoices in Prolog Manager. For each transaction having a Commitment ID, Integrator u ...
11. Skipped Projects - The budget code structure for this project does not match the template project
    BackgroundThis article addresses the following message that may be listed on the Determine Modifications recap report when running Integrator: Skipped Projects Project "######" The budget code structure for this project does not match the template project (######). This project was skipped Prol ...
12. Why aren't Subcontract COs transfering and I get an 'Error 0' message?
    SymptomAfter running the Perform Modifications task in Integrator, you find that one or more Subcontract COs that were expected to transfer do not appear in Sage Timberline Job Cost. A review of the Perform Modifications recap report reveals the message "Error 0" at the end of the Subcontract C ...
13. Why do I get a 'Type mismatch #13' error when entering or changing invoices in Prolog?
    Background When attempting to add, update, or delete a General Invoice or Contract Invoice in Prolog Manager, the following message may be displayed: Type mismtach#13<OK>Explanation Integrator is typically configured to automatically create Cost Periods (found under Admin - Cost Periods) i ...
14. Why does Prolog Manager state that the new subcontract change order cannot be added because of the date?
    Background Upon attempting to save a new Subcontract Change Order in Prolog Manager, you receive the following message: The new subcontract change order cannot be added because the date (m/d/yyyy) falls before or within the period of locked Contract Invoices.This change can only be performed by ...