00198238-01_VD_SIPLACE_Pro_14.0_R16-2_DE_EN - 第22页
SIPLACE Pro 14.0 (R 16 - 2) / V ersion Description 12/2016 Edition 22 7 Appendix The following sectio n contains gene ral information about the ASM Error Reporter Se rvice. 7.1 ASM Error Reporter Service ASM Error Report…
SIPLACE Pro 14.0 (R16-2) / Version Description 12/2016 Edition
21
6 Troubleshooting
Error Reporting Tool
The Error Reporting Tool allows you to transfer detailed information about any errors occurring in
SIPLACE Pro to the service team. For more information about this function, refer to section 7.1
ASM Error Reporter Service, the Online Help or the Support Media.
Error Reports with the ASM Error Reporter Service
The ASM Error Reporter Service can be started as follows:
– Via Start – Programs – ASM Net – Enterprise Service – ASM Error Reporter Service
– Via Help – Error Reporting in the menu of the GUIs.
Follow the instructions on the screen.
6.1 Problems and Solutions
This section describes known circumstances and general problems. If applicable, troubleshooting
is provided to help you working with SIPLACE Pro.
Solving Problems in Workgroup Mode
If you operate SIPLACE Pro in workgroup mode and if e. g. during the startup of the SIPLACE Pro
LineControl GUI application a message is displayed stating that:
It was not possible to establish a connection to the SIPLACE Pro
Interface. The cause for the error was: Unknown error (0x80004005).
► Check, if the following password requirements are met:
– The local user data must also be set up on the workgroup server.
– The local user must have the same password as on the workgroup server.
Printing SIPLACE Pro Reports
The generated reports can be sorted by various criteria (such as placement list etc.). Within the
printing preview the sort criteria can be modified as well.
► Check your specific printer properties (e.g. borderless printout) if you have printing problems
when printing reports.
Backup of System Feeder Inventory
When upgrading SIPLACE Pro (starting with SIPLACE Pro 3.0) an updated system feeder
inventory is imported (SystemFeederInventory.xml) in order to consider all new feeder types. The
feeder inventory that is already existing in SIPLACE is renamed (Backup of System Feeder
Inventory_X). All existing jobs are not changed.
All new jobs contain the updated (newly imported) feeder inventory.
SIPLACE Pro 14.0 (R16-2) / Version Description 12/2016 Edition
22
7 Appendix
The following section contains general information about the ASM Error Reporter Service.
7.1 ASM Error Reporter Service
ASM Error Reporter Service enables the user to collect information on errors. The following
explains the nature of the data, why it is collected, and what is done with it.
Why Is Error Data Collected?
Error report data is used to find and fix problems in the software you use. It is not used for
marketing purposes.
What Data Is Collected?
To fix problems in the software you use, we need information about what the software was doing
when it experienced the problem, and about your machine configuration. For a description of the
categories of data we collect, see the section below called "Types of Data".
When collecting information, it is possible for personal or confidential information to be present in
the report. For instance, a snapshot of memory may include your name, part of a document you
were working on, or data you recently submitted to a Web site. It is also possible for personal
information to be included in a log file, a portion of the registry, or other product specific files
needed to determine the cause of the problem. If you are concerned that the report may contain
personal or confidential information, please do not send the report.
You may be asked to answer a survey after sending an error report. Responding to the survey is
optional. If you send an error report without sending survey information, your error report remains
anonymous. If you choose to provide a phone number or email address then we may contact you
to ask for additional data that will help us solve the problem.
How Is Data Stored?
When you submit an error report, we protect it through the use of encryption, such as the Secure
Socket Layer (SSL) protocol. When we receive an error report, we use a variety of security
technologies and procedures to help protect your personal information from unauthorized access,
use, or disclosure. For example, we store the error reports you provide on computer servers with
limited access.
SIPLACE Pro 14.0 (R16-2) / Version Description 12/2016 Edition
23
Who Has Access to Error Report Data?
Error reporting information can be accessed by staff, contractual partners and suppliers with a
justified business-related need to view the error reports. If an error report should indicate that a
third-party product is part of the problem, we retain the right to make this report available to the
supplier concerned, who may then inform his own suppliers and partners about the matter.
Types of Data
The Error Reporting Service is used to document a wide range of errors. This section presents
many of the potential pieces of data that may be collected as part of the error report, but is not an
exhaustive list. The type of data and amount of data we request is dependent on the severity of the
error and relevance of the data to troubleshooting the problem.
Recent Actions
Data about recent actions taken by you or the software application, such as:
– The task you were working on at the time of the error.
– Menus or toolbars you clicked on.
– Dialogs that were displayed at the time of the error.
Networks
Data related to your network connections, such as:
– IP address (identifies your computer on the internet)
– Names of Web sites you recently visited.
– Information you submitted to Web sites.
Machine Configuration
Data about your physical machine, such as:
– Devices and components installed on your machine.
– Plug and Play ID (PnP ID) and description of devices
– Machine name/Type
– System name, type, model and manufacturer of the (operating) system
– Amount of RAM, hard disk size, number of processors
– BIOS version and data
– Registry data