00197483-02_VD_SIPLACE-OIB-3.3_EN.pdf - 第25页
Version Descripti on SIPLAC E OI B 3.3 04/2014 E dition 25 13 T roub leshooti ng 13.1 M SMQ Fa il s t o S tar t There m ight be situ ations d uring po wer f ailures where the M SMQ st ore wil l be corr upted or is left i…
Version Description
SIPLACE OIB 3.3 04/2014 Edition
24
9.6 Setup Center Interface
This chapter describes restrictions concerning the whole functionality of the interface.
- The usage of SIPLACE OIB requires online verification.
- Splice chains have to be completed to be passed into the interface. If only one packaging unit of an
existing splice chain is used, the splice association will be deleted.
- Barcode rules won’t be executed.
- The following matrix shows invalid combinations for packaging unit quantity and original quantity:
Condition
Result
Quantity==Int32.MinValue && OriginalQuantity==Int32.MinValue
Denied
Quantity != Int32.MinValue && Quantity < 0
Denied
OriginalQuantity != Int32.MinValue && OriginalQuantity < 0
Denied
Quantity > 0 && OriginalQuantity==0
Denied
Quantity > OriginalQuantity
Denied
10 Errors that have been fixed
Please see the ReadMe.txt file in the installation media for the latest list of errors that have been fixed. The
ReadMe.txt file will be updated with every build.
11 Support of Previous Versions
Beginning with the release of OIB 3.0 support of OIB 1.4 will be discontinued. To continue receiving
support it will be required to upgrade to a newer version of OIB.
12 Important terms and abbreviations
OIS
Operator Information System
SIS
Setup Information System
ICL
Identical Component Lot: When the packaging units does not have
unique id, but share the same batch id.
SPI
SIPLACE Pro Programming Interface
Version Description
SIPLACE OIB 3.3 04/2014 Edition
25
13 Troubleshooting
13.1 MSMQ Fails to Start
There might be situations during power failures where the MSMQ store will be corrupted or is left in an
inconsistent state. Then the MSMQ service is unable to start, which implies that the SIPLACE OIB Service
does not start as well, because they depend on MSMQ service. Please follow the instructions from the
knowledgebase article http://technet.microsoft.com/en-us/library/cc733512.aspx
Event Details
Product:
Windows Operating System
ID:
2053
Source:
MSMQ
Version:
6.0
Symbolic
Name:
EVENT_ERROR_QM_INIT_INSEQ_FILE
Message:
The incoming sequences checkpoint file failed to initialize. The file
MQInSeqs.lg1 or MQInSeqs.lg2 in the Msmq\Storage folder is corrupted or
absent. Error %1: %2
Delete incoming sequence checkpoint files
Checkpoint files must be available for Message Queuing to function properly. To resolve this issue, you
must delete the incoming sequence checkpoint files, as well as the QMLog file in the Message Queuing
storage directory. This can result in some messages being duplicated. However, this will get the service
running as soon as possible and usually without data loss.
To perform these procedures, you must have membership in Administrators, or you must have been
delegated the appropriate authority.
Version Description
SIPLACE OIB 3.3 04/2014 Edition
26
Delete checkpoint files
To delete checkpoint files:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to
the registry, you should back up any valued data.
→
Open Microsoft Windows Explorer, and then browse to your storage directory. This directory is typically
located under C:\Windows\System32\msmq\storage.
→
Delete the following files: MQInSeqs.lg1, MQInSeqs.lg2, and QMLog file.
→
Open Registry Editor. To open Registry Editor, click Start. In the search box, type regedit, and then
press ENTER.
→
Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters, and then click
Parameters.
→
On the Edit menu, point to New, and then click DWORD (32-bit) Value.
→
In the Name field, enter "LogDataCreated," and then ensure that the value is set to 0.
→
Close Registry Editor.
Restart the MSMQ Service
To restart the MSMQ Service:
→
Open the Services console. To open Services, click Start. In the search box, type services.msc, and
then press ENTER.
→
Right-click Message Queuing, and then click Restart. You must restart all the dependent services, as
well.
Verify
Verify that the MSMQ Service is installed and running.
To perform this procedure, you must have membership in Administrators, or you must have been
delegated the appropriate authority.
To verify that the MSMQ Service is installed and running:
→
Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and
then press ENTER.
→
Locate the Message Queuing service, and then confirm that the value in the Status column is Started.
→
For further confirmation, run a test application that uses the Active Directory features that you require.