In the event of the Configuration Package Manager not fitting your requirements, you can install the package manually, or just use the Configuration Package Manager to do part of the installation for you (for example, install the database manually, but use the Configuration Package Manager to install the local reports and configuration files for you).
The ‘.prpkg’ file is, essentially, a ‘Zip’ file with a special folder structure. To extract the contents, change the file extension to ‘.zip’ and extract it in the same way that you would any other zip file.
In a package file that contains database, configuration and local report files, the folders that will be extracted are:
1. Database. This contains a backup of a database containing the Preactor tables.
2. Files. This contains the files needed to run Preactor. This normally includes '.prcdf', '.prmdf','.prtdf', local report files and supporting files.
The database can be installed by using the Transact-SQL 'RESTORE' statement.
More information on using this can be found at:
http://msdn2.microsoft.com/en-us/library/ms186858.aspx
The files can simply be copied into the configuration folder. It is necessary to modify any ‘.prcdf’ files so that they have the correct ‘/DbConnect:’ connection string in them.
In addition to the above, a folder called 'Reports' will be extracted if the package file contains server reports.
3. Reports. This contains Microsoft RDL files, which define your reports.
The reports will have to be uploaded to the reports server. The SQL Server Reporting Services web page on the server has the option to upload files. You may notice that in the reports folder, each report definition file (.rdl) file has a corresponding ‘.prop’ file. This file is an XML file with certain properties about the report. Currently, it only stores whether the report was hidden on the server or not, but may be extended in the future. The settings in this file will need to be manually applied to uploaded reports, and the data source for the report will need to be set manually.
↧
Manual Installation of Packages
↧
Order Comparison Report shows #error (v12.1)
Problem
When running a report in v12.1, which uses a Due Date or Actual Due Date for a column calculation, '#error' will be shown in stead of the result of the calculation.
Cause
This is because it cannot format the value to ‘d’ as the field in SQL is now a floating fieldinstead of a DateTime.
Resolution
The SQL statement within the report definition file (.rdl) needs to be modified from:
OrdersView.ActualDueDate AS ActualDueDate
To this:
DATEADD(dd , OrdersView.ActualDueDate -1 , '1899-12-31 00:00:00.000' ) as ActualDueDateSurrounding with this will allow the report calculation to be performed without error.
↧
↧
How to Import Pegging Data in Preactor11
This document details how pegging data is imported into Preactor in versions 11 and higher. This is achieved using code to populate the 'Order Links' table.
In the 'Order Links' table there are 4 fields of interest for the actual peg:
In the 'Order Links' table there are 4 fields of interest for the actual peg:
'From External Supply Order'
'From Internal Supply Order'
'To External Demand Order'
'To Internal Demand Order'
The 'From External Supply Order' and 'From Internal Supply Order' fields are the supply records of the link. One of these fields will contain the primary key of the record it is linking to. If the 'From External Supply Order' field has a value greater than -1, then it means that the link is coming from an external supply order, such as a stock or purchase order in the 'Supply' database. If the 'From Internal Supply Order' field has a value greater than -1, it means that the link is coming from the 'Works Order' database (format is actually called Orders in prtdf). Only one of these two fields will contain a value > -1. If one field has a value > -1, then the other field will have the value -1.
Similarly, the 'To External Demand Order' and 'To Internal Demand Order' fields are the demand records of the link. One of these fields will contain the primary key of the record it is linking to. If the 'To External Demand Order' field has a value greater than -1, then it means that the link is coming from an external demand order, such as a sales order in the 'Demand' database. If the 'To Internal Demand Order' field has a value greater than -1, it means that the link is coming from the 'Works Order' database (format is actually called Orders in prtdf). Only one of these two fields will contain a value > -1. If one field has a value > -1, then the other field will have the value -1.
Other fields of interest include the 'Part No.' and 'Quantity' that the link is for.
The recommendation for importing the data is to first set up a field in 'Supply', 'Orders' and 'Demand' databases that uniquely identifies a record, such as a concatenation of 'Order No.', 'Op. No.' and if applicable 'Lot Number' (if an order contains multiple op 20's for example then 'Lot Number' can be used to distinguish the records). The import file should include enough data to match a unique record in any of the 'Supply', 'Orders' or 'Demand' databases. You will need to write code that searches these tables for a match and then writes the primary key to the appropriate field in the 'Order Links' table, the 'Part No.' and 'Quantity'.
Having populated the 'Order Links' table you need to set up an SMC rule that needs to run that will populate the appropriate fields with the EXPLICIT MADE FROM classification in the 'Orders' format. Here is how you need to set up the SMC Rule pass:
'Clear Current Links' toggle should be unchecked
'Internal Supply Queue Filter' and 'External Supply Queue Filter' set as 'NONE'
'Internal Demand Queue Filter' and 'External Demand Queue Filter' set as 'ALL'
'Include Scheduled Orders in Demand Queue' should be checked.
After running the above SMC Rules pass, the links should be made based on the imported data.
If you are using AMC you will need to run this method:
[PreactorObj].GenerateAdvancedMaterialControlVerificationCodes
Run this method after the links have been written to the 'Order Links' table.
As long as Preactor is running as a 500 APS the correct value will be written to the correct field automatically.
↧
Preactor v12.1 Crashing Before Splash Screen
Problem
When attempting to run Preactor v12.1 SP1 (30692) x64 or x86 on Windows 7, there is a Windows Crash - 'Preactor has stopped working'. This occurs before the Preactor splash screen. The resulting Event Viewer log gives an event name 'CLR20r3' and makes mention to the preactor.exe and Microsoft.Practices.Unity. Reinstalling/Repairing Preactor will not fix this issue.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: preactor.exe
Problem Signature 02: 12.1.0.30692
Problem Signature 03: 53188ce5
Problem Signature 04: Microsoft.Practices.Unity
Problem Signature 05: 2.1.505.0
Problem Signature 06: 4dc1df05
Problem Signature 07: 14a
Problem Signature 08: 50
Problem Signature 09: AVANCNVQQH3AW3N14UWVEHHCIAYOLYLS
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Cause
This is due to v4.5.1 of .Net Framework being installed as a standalone installation with no prerequisite .Net v4.0. Whilst v4.5.1 is a cumulative install (i.e. includes the resources from v4.0), this version of Preactor will attempt to find .Net v4.0 specifically and crash when it cannot. This occurs only on certain machines and is not a Global problem.
Resolution
Remove .Net v4.5.1 and reinstall chronologically; firstly v4.0 and afterwards v4.5.1 (after testing Preactor with v4.0). This should allow Preactor to recognize the .Net v4.0 install and start correctly.
When attempting to run Preactor v12.1 SP1 (30692) x64 or x86 on Windows 7, there is a Windows Crash - 'Preactor has stopped working'. This occurs before the Preactor splash screen. The resulting Event Viewer log gives an event name 'CLR20r3' and makes mention to the preactor.exe and Microsoft.Practices.Unity. Reinstalling/Repairing Preactor will not fix this issue.
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: preactor.exe
Problem Signature 02: 12.1.0.30692
Problem Signature 03: 53188ce5
Problem Signature 04: Microsoft.Practices.Unity
Problem Signature 05: 2.1.505.0
Problem Signature 06: 4dc1df05
Problem Signature 07: 14a
Problem Signature 08: 50
Problem Signature 09: AVANCNVQQH3AW3N14UWVEHHCIAYOLYLS
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Cause
This is due to v4.5.1 of .Net Framework being installed as a standalone installation with no prerequisite .Net v4.0. Whilst v4.5.1 is a cumulative install (i.e. includes the resources from v4.0), this version of Preactor will attempt to find .Net v4.0 specifically and crash when it cannot. This occurs only on certain machines and is not a Global problem.
Resolution
Remove .Net v4.5.1 and reinstall chronologically; firstly v4.0 and afterwards v4.5.1 (after testing Preactor with v4.0). This should allow Preactor to recognize the .Net v4.0 install and start correctly.
↧
Preactor Not Loading When Launched
Symptom
Preactor either crashes or does not load when launched.
Cause
Corrupt data in the configuration settings folder. Indications that the cause of this error is a corrupt configuration settings folder are:
Delete the configuration settings folder 'Preactor_International_Lt'
Preactor 10 -> 11.01
Preactor either crashes or does not load when launched.
Cause
Corrupt data in the configuration settings folder. Indications that the cause of this error is a corrupt configuration settings folder are:
- Windows event log (Start>Control Panel>Administrative Tools>Event Viewer) reports errors with .net framework 2.
- Contents at the bottom of the 'preactorError.log' file. This file is located in the user temp directory (enter %temp% in a Windows Explorer window to access this directory quickly). Error text at the end of the file such as ConfigurationSchemaError, schemaErrors, Inner exception on System.ConfigurationErrorsException will be present if the configuration settings are the cause of the error.
Delete the configuration settings folder 'Preactor_International_Lt'
Location of the configuration settings folder will vary depending on what Operating System and version of Preactor is installed (enter %appdata% in a Windows Explorer window to access the application data directory quickly, the Preactor_International_Lt will be located in this directory).
Preactor 11.1 and higher
- Windows 7 location: C:\Users\{UserName}\AppData\Roaming\Preactor_International_Lt
- Windows XP location: C:\Documents and Settings\{UserName}\Application Data\Preactor_International_Lt
Preactor 10 -> 11.01
- Windows 7 location: C:\Users\{UserName}\AppData\Local\Preactor_International_Lt
- Windows XP location: C:\Documents and Settings\{UserName}\Local Settings\Application Data\Preactor_International_Lt
↧
↧
Writing to a PESP Script Variable in Code
This article explains how to write to a PESP script variable in code and provides a code snippet as an example. An example where this functionality may be needed could be in the case where the custom action returns a certain value and this will determine which actions are followed in the remaining actions of the PESP script:
Do the following in the code project:
Do the following in the code project:
1. Reference Preactor.Extensibilty.EventScripts
2. Import the Preactor namespace (if you do not already have this specified)
3. Use EventScriptsFactory.CreateEventScriptCoreObject statically to get the IEventScriptCore interface.
A code snippet is included below. In this case the PESP script variable is called 'Return Value' and is getting set as 1. In the PESP script, after the custom action line, the 'Test Script Variable' action can be used, and then actions such as 'If False' or 'If True' can be used to determine the remaining steps of the PESP script.
Option Strict On
Option Explicit On
Imports System
Imports System.Runtime.InteropServices
Imports Preactor.Interop.PreactorObject
Imports Preactor
<ComVisible(True)> _
<Microsoft.VisualBasic.ComClass("6ebba097-4b68-46cb-851a-6ac69d41cf6c", "64a7c6d0-2836-4a9d-a4d5-cd36f33e32e2")> _
PublicClassCustomAction2
PublicFunction Run(ByRef preactorComObject AsPreactorObj, ByRef pespComObject AsObject) AsInteger
Dim preactor AsIPreactor = PreactorFactory.CreatePreactorObject(preactorComObject)
Dim PESP AsIEventScriptsCore = EventScriptsFactory.CreateEventScriptCoreObject(preactorComObject, pespComObject)
'TODO : Your code goes here
PESP.WriteScriptVariable("Return Value", 1)
Return 0
EndFunction
EndClass
↧
Value cannot be null Error on Loading Preactor After Upgrading Database to 12.1 SP2
Symptom
The following error (or a variation of the same error with just a different table name) is displayed on launching Preactor just after a successful database upgrade to 12.1 SP2:
Contents of the error message:
Cause
The above error may occur if there are REMOTE(TableName(FieldName)) lines defined in the PRTDF file that point to fields with EVALUATE expressions on them. For example:
In Orders table:
Priority,10,INTEGER,
BAR TEXT
BACKGROUND BAR GROUPING
LOW BAR GROUPING
LOW RIGHT BAR GROUPING
HELPPOPUPID (80)
PRIORITY
GLOBAL ASSIGN
INHERIT FROM PARENT
TIP DISPLAY
SORT RECORD
LOCATE
EVALUATE "{Quantity}":
In Resources table:
Preferred Sequence,-1,MATRIX,
HELPPOPUPID (2150)
PREFERRED SEQUENCE RULE
HIDDEN IF LITE
HIDDEN IF 200
HIDDEN IF 300
REMOTE(Orders(Due Date))
REMOTE(Orders(Priority))
REMOTE(Orders(Product Attribute 1 Rank))
REMOTE(Orders(Product Attribute 2 Rank))
REMOTE(Orders(Product Attribute 3 Rank))
REMOTE(Orders(Operation Attribute 1 Rank))
REMOTE(Orders(Operation Attribute 2 Rank))
REMOTE(Orders(Operation Attribute 3 Rank)):
Resolution
The current workaround is as follows:
Prior to launching Preactor as 12.1 SP2 and performing the database upgrade, temporarily remove the EVALUATE expression lines on any fields pointed to by REMOTE(TableName(FieldName)) in the PRTDF file. Save the changes, launch Preactor and perform the database upgrade.
After Preactor has finished loading, close, and add the EVALUATE lines back in the PRTDF. Save the changes and reload Preactor.
N.B.: If you have already attempted to perform the upgrade on the database, simply removing the EVALUATE lines will still result in the error when reopening Preactor. No prior 12.1 SP2 database schema upgrade attempts on that database must have occurred, so you will need to extract the database fresh from your package first, remove the EVALUATE lines, and then upgrade.
The following error (or a variation of the same error with just a different table name) is displayed on launching Preactor just after a successful database upgrade to 12.1 SP2:
Contents of the error message:
Detailed Exception Information:
The attempt to load matrices for table 'Resources' from the database failed.
Preactor.Data.PreactorDbException
=================================
The attempt to load matrices for table 'Resources' from the database failed.
Program Location:
Inner exception:
System.ArgumentNullException
============================
Value cannot be null.
Parameter name: table
Program Location:
at Preactor.StorageMapping.RelationalModel.FieldIdentifier..ctor(String table, String field)
at Preactor.StorageMapping.DbModel.DbRemoteFieldReadWriteStrategy.a(Int32 A_0)
at Preactor.StorageMapping.DbModel.DbRemoteFieldReadWriteStrategy.WriteRemoteFieldValue(IRemoteFieldValue target, Position position, IDataRecord row, RelationalField relationalField)
at Preactor.StorageMapping.DbModel.DbRankFieldReadWriteStrategy.ReadFromDatabase(Position position, IDataRecord row, Int32 rowIndex, RelationalField relationalField)
at Preactor.StorageMapping.DbModel.AutoListTableOperationStrategy.InsertPreactorRow(DbTableBase table, IDataRecord row, Int32 rowId)
at Preactor.StorageMapping.DbModel.DbTableBase.RetrieveTableData(Int32 timeout)
at Preactor.StorageMapping.StorageSubsystem.b(DbTableBase A_0, Int32 A_1)
at Preactor.StorageMapping.StorageSubsystem.ReadMatricesFromStorage(Int32 format)
Cause
The above error may occur if there are REMOTE(TableName(FieldName)) lines defined in the PRTDF file that point to fields with EVALUATE expressions on them. For example:
In Orders table:
Priority,10,INTEGER,
BAR TEXT
BACKGROUND BAR GROUPING
LOW BAR GROUPING
LOW RIGHT BAR GROUPING
HELPPOPUPID (80)
PRIORITY
GLOBAL ASSIGN
INHERIT FROM PARENT
TIP DISPLAY
SORT RECORD
LOCATE
EVALUATE "{Quantity}":
In Resources table:
Preferred Sequence,-1,MATRIX,
HELPPOPUPID (2150)
PREFERRED SEQUENCE RULE
HIDDEN IF LITE
HIDDEN IF 200
HIDDEN IF 300
REMOTE(Orders(Due Date))
REMOTE(Orders(Priority))
REMOTE(Orders(Product Attribute 1 Rank))
REMOTE(Orders(Product Attribute 2 Rank))
REMOTE(Orders(Product Attribute 3 Rank))
REMOTE(Orders(Operation Attribute 1 Rank))
REMOTE(Orders(Operation Attribute 2 Rank))
REMOTE(Orders(Operation Attribute 3 Rank)):
Resolution
The current workaround is as follows:
Prior to launching Preactor as 12.1 SP2 and performing the database upgrade, temporarily remove the EVALUATE expression lines on any fields pointed to by REMOTE(TableName(FieldName)) in the PRTDF file. Save the changes, launch Preactor and perform the database upgrade.
After Preactor has finished loading, close, and add the EVALUATE lines back in the PRTDF. Save the changes and reload Preactor.
N.B.: If you have already attempted to perform the upgrade on the database, simply removing the EVALUATE lines will still result in the error when reopening Preactor. No prior 12.1 SP2 database schema upgrade attempts on that database must have occurred, so you will need to extract the database fresh from your package first, remove the EVALUATE lines, and then upgrade.
↧
Failed to connect to the license server or Operations server
Problem
The following error occurs when trying to activate a license using activation over the internet:
Failed to connect to the license server or Operations server.
![]()
Cause
A connection to the license server or Operations server over the internet is failing, preventing the license from being activated.
Resolution
Make sure that the computer requesting the activation has internet access and there is no firewall actively blocking the connection.
If this computer doesn't have internet access, and needs to remain in this state, then generate the activation request as an offline activation request.
If the computer does have internet access, the problem may be due to a firewall blocking access. To test if the issue is firewall related, try to go to this address in your internet browser: http://licensing.preactor.com/flexnet/services/ActivationService?wsdl if no page loads, or you receive a timeout, then the issue is due to a firewall. Your firewall needs to allow the URL licensing.preactor.com, the port number is 80.
The following error occurs when trying to activate a license using activation over the internet:
Failed to connect to the license server or Operations server.
Cause
A connection to the license server or Operations server over the internet is failing, preventing the license from being activated.
Resolution
Make sure that the computer requesting the activation has internet access and there is no firewall actively blocking the connection.
If this computer doesn't have internet access, and needs to remain in this state, then generate the activation request as an offline activation request.
If the computer does have internet access, the problem may be due to a firewall blocking access. To test if the issue is firewall related, try to go to this address in your internet browser: http://licensing.preactor.com/flexnet/services/ActivationService?wsdl if no page loads, or you receive a timeout, then the issue is due to a firewall. Your firewall needs to allow the URL licensing.preactor.com, the port number is 80.
↧
Client activation is not allowed to activate
Problem
The following error occurs when trying to activate a license using activation:
Client activation is not allowed to activate:[activation code]. Check the license model to make sure a client can activate.
![]()
Cause
The local License Utility is being used to activate a network license.
Resolution
A network license can only be activated using the Network License Utility, therefore launch the Network License Utility and follow the on screen instructions to activate the network license.
The following error occurs when trying to activate a license using activation:
Client activation is not allowed to activate:[activation code]. Check the license model to make sure a client can activate.
Cause
The local License Utility is being used to activate a network license.
Resolution
A network license can only be activated using the Network License Utility, therefore launch the Network License Utility and follow the on screen instructions to activate the network license.
↧
↧
Can't Create Package
Symptom
The following message appears when attempting to create a Preactor package:
Package Manager Options:
/create:<file> /dbconnect:<connectString> [/configpath:<path>] --
creates a configuration package file (.prpkg) from an existing Preactor configuration.
/install:<file> -- installs a configuration package file (.prpkg)
![]()
Cause
The above message is caused by Package Manager not recognizing the arguments passed to it.
There can be different reasons that may trigger this message, but it may be because the configuration files have been extracted to the root of a drive, rather than into a folder, or if just the mapped drive letter has been specified as the Directory Name in the .prcdf file used to launch Preactor.
One way to see if either of the above is the cause of the issue, is to choose the 'Help>Trace Window' option from the top right on the Preactor Desktop, then to try creating the package file. The trace window will provide a log and the line that details the Package Manager arguments will include /configpath.
Example, the Trace Window contents may read similar to this:
11:37:31 AM : Workflow 'Generating application and environment information' started. Id=28, label=SUPPORT_FILE
11:37:32 AM : External application launched. Filename='C:\Program Files\Preactor International\Preactor12.1\PackageManager.exe', arguments='"/configpath:C:\" "/create:PS36535.prpkg" "/dbconnect:Data Source=.\SQLEXPRESS;Initial Catalog=C:\;Integrated Security=True;"', attached='True'
11:37:32 AM : Action step started.
Note how /configpath:C:\ shows that there is no folder name.
Resolution
Make sure that Preactor configuration files are held in a folder and not on the root of a drive.
or
Check to see whether just a mapped drive letter (such as X:) has been specified in the Directory Name field in the .prcdf file instead of a full path such as \\servername\FolderName. To check this, right click on the .prcdf file used to launch Preactor and choose the 'Modify With Preactor [Version Number]' option from the Pop up menu. The Preactor Command File Editor loads. Click on the Configuration tab and under the Working Directory section, check the contents of the Directory Name field. Make sure that the full path is specified and not just a mapped drive letter.
The following message appears when attempting to create a Preactor package:
Package Manager Options:
/create:<file> /dbconnect:<connectString> [/configpath:<path>] --
creates a configuration package file (.prpkg) from an existing Preactor configuration.
/install:<file> -- installs a configuration package file (.prpkg)
Cause
The above message is caused by Package Manager not recognizing the arguments passed to it.
There can be different reasons that may trigger this message, but it may be because the configuration files have been extracted to the root of a drive, rather than into a folder, or if just the mapped drive letter has been specified as the Directory Name in the .prcdf file used to launch Preactor.
One way to see if either of the above is the cause of the issue, is to choose the 'Help>Trace Window' option from the top right on the Preactor Desktop, then to try creating the package file. The trace window will provide a log and the line that details the Package Manager arguments will include /configpath.
Example, the Trace Window contents may read similar to this:
11:37:31 AM : Workflow 'Generating application and environment information' started. Id=28, label=SUPPORT_FILE
11:37:32 AM : External application launched. Filename='C:\Program Files\Preactor International\Preactor12.1\PackageManager.exe', arguments='"/configpath:C:\" "/create:PS36535.prpkg" "/dbconnect:Data Source=.\SQLEXPRESS;Initial Catalog=C:\;Integrated Security=True;"', attached='True'
11:37:32 AM : Action step started.
Note how /configpath:C:\ shows that there is no folder name.
Resolution
Make sure that Preactor configuration files are held in a folder and not on the root of a drive.
or
Check to see whether just a mapped drive letter (such as X:) has been specified in the Directory Name field in the .prcdf file instead of a full path such as \\servername\FolderName. To check this, right click on the .prcdf file used to launch Preactor and choose the 'Modify With Preactor [Version Number]' option from the Pop up menu. The Preactor Command File Editor loads. Click on the Configuration tab and under the Working Directory section, check the contents of the Directory Name field. Make sure that the full path is specified and not just a mapped drive letter.
↧
Data Load Warning on Entry to the Sequencer
Symptom
Following error occurs on entry to the Sequencer:
Data Load Warning
Errors were encountered loading 'Resource Data' from the database for the 'Orders' table. Some data was not loaded correctly.
This problem can be caused by deleting data that is being referenced in other places in the database. Please review recent operations such as data imports or table edits.
![]()
Cause
This error has been known to occur when there are fields in the 'Orders' table defined with the ASSOCIATE classification.
Resolution
If the ASSOCIATE classifications in the 'Orders' table are changed to DIRECT ASSOCIATE, the error no longer occurs.
Following error occurs on entry to the Sequencer:
Data Load Warning
Errors were encountered loading 'Resource Data' from the database for the 'Orders' table. Some data was not loaded correctly.
This problem can be caused by deleting data that is being referenced in other places in the database. Please review recent operations such as data imports or table edits.
Cause
This error has been known to occur when there are fields in the 'Orders' table defined with the ASSOCIATE classification.
Resolution
If the ASSOCIATE classifications in the 'Orders' table are changed to DIRECT ASSOCIATE, the error no longer occurs.
↧
The Format is locked and can not be changed
The following error occurs when attempting to import or create records in a table:
![]()
This error could occur if the number of records being imported or records being created in a table have exceeded the limit specified in the Preactor.prtdf file for that table.
The solution is to open up the Preactor.prtdf file, find the table that the data is being imported into/new records are being created in and increase the record limit i.e.
; Main schedule file definition.
;
Orders,.prsch,0,8000:
Belongs to Order No.,-1,STRING,
HELPPOPUPID (10)
FAMILY(Order No.)
DIALOG ONLY:
Number,0,INTEGER,
HELPPOPUPID (20)
PRIMARY KEY
#ifndef PR_NOCOST
COST KEY
#endif
DIALOG ONLY
HIDDEN:
etc.
Save the changes, restart Preactor and run the import again.
This error could occur if the number of records being imported or records being created in a table have exceeded the limit specified in the Preactor.prtdf file for that table.
The solution is to open up the Preactor.prtdf file, find the table that the data is being imported into/new records are being created in and increase the record limit i.e.
; Main schedule file definition.
;
Orders,.prsch,0,8000:
Belongs to Order No.,-1,STRING,
HELPPOPUPID (10)
FAMILY(Order No.)
DIALOG ONLY:
Number,0,INTEGER,
HELPPOPUPID (20)
PRIMARY KEY
#ifndef PR_NOCOST
COST KEY
#endif
DIALOG ONLY
HIDDEN:
etc.
Save the changes, restart Preactor and run the import again.
↧
Instructing PrSpy to Connect to Multiple Instances of Preactor on the Same Computer
Symptom
PrSpy is only displaying one instance of Preactor. How can I get PrSpy to recognize multiple instances of Preactor running on the same computer?
Resolution
Edit each Preactor.prmdf file for the Preactor systems that you want to appear in Prspy.
Temporarily add the following (shown in bold text).
; --------------------------------------------------------------------------
; Main Menu
; --------------------------------------------------------------------------
;
MENU_Main : {DIALOG},
,
Main Menu:
PUSHBUTTON,Run PrSpy,Run_PrSpy:
PUSHBUTTON | HELPPOPUPID (50100),Data Transfer,MENU_ImpExp:
PUSHBUTTON | HELPPOPUPID (50030),Generate Schedule,SEQ_Main:
PUSHBUTTON | HELPPOPUPID (58510),Release Schedule,Release_Schedule:
PUSHBUTTON | HELPPOPUPID (50120),Import Orders,Import_Orders:
PUSHBUTTON | HELPPOPUPID (50070),Data Maintenance,MENU_Maintenance;
;
Run_PrSpy : ActiveX PrSpy.EntryPoint Start,
,
PrSpy,
PrSpy,
Detached,
ALWAYS : {RETURN};
;
Save the changes, launch the Preactor systems.
Next, select the 'Run PrSpy' option on the Preactor Desktop that you added in each of the systems.
You should now see the different Preactor systems listed in PrSpy. These should appear when you choose the 'Preactor' menu option, for example:
![]()
PrSpy is only displaying one instance of Preactor. How can I get PrSpy to recognize multiple instances of Preactor running on the same computer?
Resolution
Edit each Preactor.prmdf file for the Preactor systems that you want to appear in Prspy.
Temporarily add the following (shown in bold text).
; --------------------------------------------------------------------------
; Main Menu
; --------------------------------------------------------------------------
;
MENU_Main : {DIALOG},
,
Main Menu:
PUSHBUTTON,Run PrSpy,Run_PrSpy:
PUSHBUTTON | HELPPOPUPID (50100),Data Transfer,MENU_ImpExp:
PUSHBUTTON | HELPPOPUPID (50030),Generate Schedule,SEQ_Main:
PUSHBUTTON | HELPPOPUPID (58510),Release Schedule,Release_Schedule:
PUSHBUTTON | HELPPOPUPID (50120),Import Orders,Import_Orders:
PUSHBUTTON | HELPPOPUPID (50070),Data Maintenance,MENU_Maintenance;
;
Run_PrSpy : ActiveX PrSpy.EntryPoint Start,
,
PrSpy,
PrSpy,
Detached,
ALWAYS : {RETURN};
;
Save the changes, launch the Preactor systems.
Next, select the 'Run PrSpy' option on the Preactor Desktop that you added in each of the systems.
You should now see the different Preactor systems listed in PrSpy. These should appear when you choose the 'Preactor' menu option, for example:
↧
↧
FindMatchingRecord Not Working on EVALUATE Fields in 12.1
FindMatchingRecord returns -6 when used on EVALUATE field in Preactor 12.1 (12.1.0.29956), 12.1 SP1 (12.1.0.30692), and 12.1 SP2 (12.1.0.32140).
Cause
Defect in Preactor 12.1 (12.1.0.29956), 12.1 SP1 (12.1.0.30692), and 12.1 SP2 (12.1.0.32140).
SolutionImplement user code using a loop and readfield, or do FindMatchingRecord on each of the strings involved in the EVALUATE, and find out the records where all values match. An alternative is to use a PESP script using the Find Matching Record By Expression PESP action.
The issue will be fixed in a future release.
↧
Invalid attempt to read when no data is present.
User gets this error when attempting to load Preactor:
Initialization Error
Failed to connect to the database. Preactor will shut down.
Error details:
Invalid attempt to read when no data is present.
This error may occur due to fields or tables being added to the UserData schema that have not been defined in the Preactor.prtdf file. To find out what table or field may have been added, set Preactor to run in debug mode (right click on the .prcdf file used to start up Preactor and select the 'Modify with Preactor 10.0' option from the popup menu, on the 'Runtime' tab select the 'Debug Mode' option then click 'Ok' to save the changes and exit), start up Preactor, when the error occurs hit 'Ok' then go to the current users temp directory, so for example 'C:\Documents and Settings\username\Local Settings\Temp', there will be a file in this directory called 'PreactorStorage.dbg'. Open up this file in a text editor such as WordPad, the last line of the file should indicate the table name that is causing the error.
Outside of the Preactor.prtdf file, any Preactor fields or tables cannot be modified in anyway. Tables can be added but they cannot have any relationship with Preactor tables (this includes triggers), and they can only be added using a different database schema name.
↧
Renewing a Preactor Express License
Renewing a Preactor Express License
Preactor Express licenses run for 1 year. After this time, a new ID should be requested to enable use of the software for a further year.
The following steps will assume that you have already received a Preactor Express license. If you do not already have this, then you can register your details via the below link to receive an activation ID.
http://www.preactor.com/Express/Register
http://www.preactor.com/Express/Register
Steps to renew:
1. Log into the www.preactor.com using the credentials supplied when originally registering for the license.
2. Select 'My Preactor'.
3. Hover over the 'Preactor Express' option, then select 'Renew'
![]()
4. The next page should display a list of your Express licenses. If your license has expired, or will expire in the next 30-days, select the 'Re-new Express License' link.
The page should then reload and display a message if the update was successful:
"License 493**** has been extended successfully. Please see updated details below"
The new activation ID should be displayed below this message and can be copied into the activation window when launching Preactor Express.
The page should then reload and display a message if the update was successful:
"License 493**** has been extended successfully. Please see updated details below"
The new activation ID should be displayed below this message and can be copied into the activation window when launching Preactor Express.
As always, any problems with Express can be reported via the forums at http://forums.preactor.com/
↧
Server activation is not allowed to activate
Problem
The following error occurs when trying to activate a license:
Server activation is not allowed to activate entitlement line item:[activation code]. Make sure the license model is a server license model.
![]()
Cause
The Network License Utility is being used to activate a local license model.
Resolution
A local license model can only be activated using the local License Utility, not the Network License Utility. Launch the local License Utility and follow the on screen instructions to activate the local license model.
The following error occurs when trying to activate a license:
Server activation is not allowed to activate entitlement line item:[activation code]. Make sure the license model is a server license model.
Cause
The Network License Utility is being used to activate a local license model.
Resolution
A local license model can only be activated using the local License Utility, not the Network License Utility. Launch the local License Utility and follow the on screen instructions to activate the local license model.
↧
↧
Upgrade schema to version 11.15.2.0 Failed Invalid column name '_inst_PESPActionsParameters'
Symptom
Upgrade schema to version 11.15.2.0 Failed with error Invalid column name '_inst_PESPActionsParameters'.
This error occurs during the database upgrade, when launching a Preactor configuration in Preactor version 12.0.0.28624 or higher.
Contents of the error message:
Upgrade schema to version 11.15.2.0 Failed with error Invalid column name '_inst_PESPActionsParameters'.
This error occurs during the database upgrade, when launching a Preactor configuration in Preactor version 12.0.0.28624 or higher.
Contents of the error message:
Detailed Exception Information:
The task 'Upgrade schema to version 11.15.2.0' failed. Details of the error are included below.
System.Data.SqlClient.SqlException
==================================
Invalid column name '__inst__PESPActionsParameters'.
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand command, DbTransaction transaction)
at Preactor.Data.DatabaseAccessLayer.ExecuteNonQuery(IDbCommand command, IDbTransaction transaction)
at Preactor.StorageMapping.SchemaUpgradeFromSimpleStatementsTask.PerformUpgrade(IDbTransaction transaction)
at Preactor.StorageMapping.SchemaUpgradeTask.RunImpl()
at Preactor.Task.Run()
at Preactor.StorageMapping.SchemaUpgradeTask.Run()
at Preactor.WinForms.Controls.TaskRunner.TaskRunner.a(Object A_0, DoWorkEventArgs A_1)
Data:
HelpLink.ProdName, Microsoft SQL Server
HelpLink.ProdVer, 11.00.2218
HelpLink.EvtSrc, MSSQLServer
HelpLink.EvtID, 207
HelpLink.BaseHelpUrl, http://go.microsoft.com/fwlink
HelpLink.LinkId, 20476
Cause
SystemData.PESPActionsParameters table is missing the __inst__PESPActionsParameters column.
Resolution
The __inst__PESPActionsParameters is a field that is defined in the SQL database only, it is not a field defined in the Preactor PRTDF file. The solution is to use SQL Server Management Studio and run the following as a query against the database that is giving the error:
ALTERTABLE[SystemData].[PESPActionsParameters]
ADD[__inst__PESPActionsParameters][int]NOTNULLDEFAULT (0)
Go
ALTERTABLE[SystemData].[PESPActionsParameters]DROPCONSTRAINT[PESPActionsParameters PK]
Go
ALTERTABLE[SystemData].[PESPActionsParameters]ADD CONSTRAINT[PESPActionsParameters PK]PRIMARYKEYCLUSTERED
(
[PESPActionsId]ASC,
[Parameters]ASC,
[__inst__PESPActionsParameters]ASC
)WITH (PAD_INDEX=OFF,STATISTICS_NORECOMPUTE=OFF,SORT_IN_TEMPDB=OFF,IGNORE_DUP_KEY=OFF,ONLINE=OFF,ALLOW_ROW_LOCKS=ON,ALLOW_PAGE_LOCKS=ON)ON[PRIMARY]
GO
↧
System.NullReferenceException
Symptom
When running a 'right click' PESP Event Script the following error occurs:
System.NullReferenceException
atd.a has thrown an exception: Object reference not set to an instance of an object.
![]()
![]()
Cause
The Open Planning Board needs to be initialized when executing a 'right click' PESP Event Script that uses an action that references the Open Planning Board object.
Resolution
Add an 'Initialise Open Planning Board' action to the 'right click' PESP script before the action that is using the Open Planning Board object.
When running a 'right click' PESP Event Script the following error occurs:
System.NullReferenceException
atd.a has thrown an exception: Object reference not set to an instance of an object.
Cause
The Open Planning Board needs to be initialized when executing a 'right click' PESP Event Script that uses an action that references the Open Planning Board object.
Resolution
Add an 'Initialise Open Planning Board' action to the 'right click' PESP script before the action that is using the Open Planning Board object.
↧
GetTypeInfoCount Failed and Various Other Errors
Symptom
The following errors occur when launching Preactor:
ConnectToServer
GetTypeInfoCount Failed
![]()
Preactor ActiveX Interface
The function CustomCheckServer in the ActiveX module PreactorMultiCheckServer.EntryPoint terminated abnormally or could not be run.
![]()
PREACTOR SHELL
Preactor was unable to start the Communications Object
![]()
On entry to the Sequencer, this error occurs:
No Interface
![]()
Cause
Preactor versions have not been installed in chronological order.
Resolution
1. Uninstall all Preactor versions.
2. Delete the Preactor International folder in Program Files.
3. Restart your machine.
4. Install Preactor versions in chronological order.
The following errors occur when launching Preactor:
ConnectToServer
GetTypeInfoCount Failed
Preactor ActiveX Interface
The function CustomCheckServer in the ActiveX module PreactorMultiCheckServer.EntryPoint terminated abnormally or could not be run.
PREACTOR SHELL
Preactor was unable to start the Communications Object
On entry to the Sequencer, this error occurs:
No Interface
Cause
Preactor versions have not been installed in chronological order.
Resolution
1. Uninstall all Preactor versions.
2. Delete the Preactor International folder in Program Files.
3. Restart your machine.
4. Install Preactor versions in chronological order.
↧