Hello,
Connect-It: How to efficiently report a problem
Indicate the Steps to Reproduce
For WINDOWS OS
List the exact steps to create the error, such as:
Open Connect-It.
Open the AssetCenter to ServiceCenter scenario.
Add an array of character field from ServiceCenter.
An error ("Error goes here"
will pop up when you click OK.
For Unix OS
Launch your Connect-It service.
All connetors are correctly opened..
Connect-It hang while processing <Your_Document_Type> document type.
Gather server configuration information
For WINDOWS OS
Click About from the Help menu (or press CTRL-F1).
Click More in the pop-up screen.
Click Copy to copy your system information to the clipboard.
Paste the information into a text file.
Add the installation path at the end of your text file.
For Unix OS
Give us the build number and the language of Connect-It
Give us the system name and version
Give us Oracle or sybase .so path and version
Add the installation path at the end of your text file.
If there is an error message, create a screen capture of the issue
Only for WINDOWS OS
Generate the error.
Press ALT-PRINT SCREEN to copy the image to the clipboard.
Open Paint or any image editor and paste in the image.
Save the image.
Gather the following documents (where applicable)
FOR all OS
Send a copy of your conitgui.log file or any other log files. Note: When run as a service, a scenario is attached to a log file that is named after the service (<servicename>.log).
Send a copy of the scenario file (.scn).
Send a copy of license.txt file (authorization certificate).
Send a copy of the configuration file (.cfg).
Send a copy of any String Files (.str), Maptables (.mpt), Basic scripts (.bas) or User Format (.fmt) related to the scenario.
Send a copy of any pivot documents (.piv) related to the issue.
Send a copy of your conit.ini file (.ini) located in the WINNT directory for WINDOWS OS and at the root of the user for Unix OS.
Send a copy of the cache files (*.cch) for the source and target systems (v2.6 and above)
This manipulation can only be realized under WINDOWS OS.
For Unix OS, in case your scn in rightly configured, you can start at step 15.
Open the scenario.
From the Edit menu, click CTRL + Options.
Click on Display.
Set Display advanced configuration wizards to Yes.
Right click on the Source connector.
Select Configure Connector.
Press Next until the Configure Cache screen is displayed.
Check Use cache.
Click Finish.
Right click on the Source connector.
Select Open Connector.
In the Connect-It Log window, note the path and name of the cache file.
Right click on the Source connector.
Select Cache, then Synchronize.
Copy the file noted in Step 12 to include with the report.
Repeat Steps 5 - 15 for the Target connector.
Provide Document logs from scenario
Note: These are in addition to the conitgui.log.
This manipulation can only be realized under WINDOWS OS.
For Unix OS, in case your scn in rightly configured, you can start at step 5.
Select Configure document log from the Log menu.
Check Use files.
Click once on the gray Generic name text box to activate it.
Type the full path and file name where the logs are to be stored and named, without any extension (for example: C:\tmp\test\Workorders). Connect-It will add the .dat .log and .idx extension to the three files generated (for example: C:\tmp\test\Workorders.log, C:\tmp\test\Workorders.idx, and C:\tmp\test\Workorders.dat).
Run the scenario. The 3 files mentioned above will be created.
Copy these files to include with the report.
Copy the XML format of a rejected document without sending database files
Only for WINDOWS OS
Click one time on the source or target connector that contains the rejected document.
Click on the Document Log tab.
Right click on the rejected document
Select Copy this XML document.
Paste this document into a text file.
Note: When done, compress all the files collected above using a program like WinZip. This will make the set of files smaller and easier to send.
Mail: support@peregrine.com
