Alert emails for Unacknowledged records - Revision history

Nivin at 23:54, 24 November 2013

2013-11-24T23:54:48Z

← Older revision		Revision as of 23:54, 24 November 2013
Line 2:		Line 2:
	==Background==		==Background==
	These occur when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few reasons:<br />		These occur when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few reasons:<br />
	~~<br />~~
	* The data was never received by the store		* The data was never received by the store
	* The store received the data however the acknowledgements couldn't be send back to EEE		* The store received the data however the acknowledgements couldn't be send back to EEE
Line 8:		Line 7:
	* The data or acknowledgements got lost in transit		* The data or acknowledgements got lost in transit
	==How to investigate==		==How to investigate==
	When you receive these emails, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any <tt>isl-file.zip</tt> or <tt>isl-po.dat</tt> files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)		When you receive these emails, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any <tt>isl-file.zip</tt> or <tt>isl-po.dat</tt> files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store.)<br /><br />
	<br /><br />		If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated[[File:Alert_emails_for_Unacknowledged_records_Figure_1.png\|thumb\|Perform a manual re-export of unacknowledged data to Head Office]]<br /><br />
	If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.
	[[File:Alert_emails_for_Unacknowledged_records_Figure_1.png\|thumb\|Perform a manual re-export of unacknowledged data to Head Office]]<br />
	If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.
	<br /><br />		<br /><br />
	If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact ~~support~~] and we will be able to assist you with this.		If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact us] and we will be able to assist you with this.

Nivin: Edited for clarity, added image, sections

2013-11-24T23:30:00Z

Edited for clarity, added image, sections

← Older revision		Revision as of 23:30, 24 November 2013
Line 1:		Line 1:
	Created: 30 September 2009. Last Reviewed: 25 November 2013		Created: 30 September 2009. Last Reviewed: 25 November 2013
			==Background==
	~~This occurs~~ when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few reasons:<br />		These occur when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few reasons:<br />
	<br />		<br />
	* The data was never received by the store		* The data was never received by the store
Line 7:		Line 7:
	* The store got a newer version of the data sent to it, in which case it will not acknowledge older data		* The store got a newer version of the data sent to it, in which case it will not acknowledge older data
	* The data or acknowledgements got lost in transit		* The data or acknowledgements got lost in transit
	~~<br />~~		==How to investigate==
	When ~~this occurs~~, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any <tt>isl-file.zip</tt> or <tt>isl-po.dat</tt> files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)		When you receive these emails, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any <tt>isl-file.zip</tt> or <tt>isl-po.dat</tt> files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)
	<br /><br />		<br /><br />
	If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.		If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.
	~~<br />~~<br />		[[File:Alert_emails_for_Unacknowledged_records_Figure_1.png\|thumb\|Perform a manual re-export of unacknowledged data to Head Office]]<br />
	If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.
	<br /><br />		<br /><br />
	If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact support] and we will be able to assist you with this.		If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact support] and we will be able to assist you with this.

Nivin at 23:16, 24 November 2013

2013-11-24T23:16:34Z

← Older revision		Revision as of 23:16, 24 November 2013
Line 14:		Line 14:
	If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.
	<br /><br />		<br /><br />
	If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact support] ~~who~~ will be able to assist you with this.		If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact support] and we will be able to assist you with this.

Nivin at 23:15, 24 November 2013

2013-11-24T23:15:48Z

← Older revision		Revision as of 23:15, 24 November 2013
Line 1:		Line 1:
	Created: 30 September 2009. Last Reviewed: 25 November 2013		Created: 30 September 2009. Last Reviewed: 25 November 2013

	This occurs when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few ~~things~~:<br />		This occurs when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few reasons:<br />
	<br />		<br />
	* The data was never received by the store		* The data was never received by the store
Line 8:		Line 8:
	* The data or acknowledgements got lost in transit		* The data or acknowledgements got lost in transit
	<br />		<br />
	When this occurs, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any isl-file.zip or isl-po.dat files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)		When this occurs, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any <tt>isl-file.zip</tt> or <tt>isl-po.dat</tt> files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)
	<br />		<br /><br />
	If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.		If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.
	<br />		<br /><br />
	If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.
	<br />		<br /><br />
	If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table.		If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table. Please [mailto:support@magentaretail.com.au contact support] who will be able to assist you with this.

Nivin at 23:09, 24 November 2013

2013-11-24T23:09:58Z

← Older revision		Revision as of 23:09, 24 November 2013
Line 1:		Line 1:
	Created: 30 September 2009. Last Reviewed: 25 November 2013		Created: 30 September 2009. Last Reviewed: 25 November 2013

	This occurs when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few things:		This occurs when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few things:<br />
			<br />
	* The data was never received by the store		* The data was never received by the store
	* The store received the data however the acknowledgements couldn't be send back to EEE		* The store received the data however the acknowledgements couldn't be send back to EEE
	* The store got a newer version of the data sent to it, in which case it will not acknowledge older data		* The store got a newer version of the data sent to it, in which case it will not acknowledge older data
	* The data or acknowledgements got lost in transit		* The data or acknowledgements got lost in transit
			<br />
	~~The unacknowledged records are held in the ExportMaintenance table in EEE and alerts are sent out whenever there are records older than 7 days for any stores.~~		When this occurs, you should check the store's export folder on the EEE server (which is usually in a folder <tt>\EEEData\Export\<Store directory>\</tt>). If there are any isl-file.zip or isl-po.dat files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in <tt>\EEEData\Archive\<Store directory></tt> to see if EEE has recently received any files from the store)
			<br />
	When this occurs, you should check the store's export folder on the EEE server (which is usually in a folder \EEEData\Export\<Store directory>\). If there are any isl-file.zip or isl-po.dat files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in \EEEData\Archive\<Store directory> to see if EEE has recently received any files from the store)		If there are no files in the Export folder on the EEE Server, check the <tt>\enabler\comms\ackout</tt> folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.
			<br />
	If there are no files in the Export folder on the EEE Server, check the \enabler\comms\ackout folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.

	If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.
			<br />
	If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table.		If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table.

Nivin at 23:07, 24 November 2013

2013-11-24T23:07:02Z

← Older revision		Revision as of 23:07, 24 November 2013
Line 1:		Line 1:
	Created: 30 September 2009. Last Reviewed: ~~30 September 2009~~		Created: 30 September 2009. Last Reviewed: 25 November 2013

			This occurs when EEE sends some data out to the stores and the stores do not send acknowledgements back that they have received it. EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. This can be due to a few things:

	'~~''Alert emails for Unacknowledged Records'''~~		* The data was never received by the store
			* The store received the data however the acknowledgements couldn't be send back to EEE
			* The store got a newer version of the data sent to it, in which case it will not acknowledge older data
			* The data or acknowledgements got lost in transit

			The unacknowledged records are held in the ExportMaintenance table in EEE and alerts are sent out whenever there are records older than 7 days for any stores.

	EEE ~~will automatically send alert emails when~~ a ~~store has unacknowledged records older than 7 days~~. ~~These alerts occur when~~ there are ~~records~~ in the ~~ExportMaintenance table~~ that ~~are older than 7 days~~.		When this occurs, you should check the store's export folder on the EEE server (which is usually in a folder \EEEData\Export\<Store directory>\). If there are any isl-file.zip or isl-po.dat files in this folder, then the alerts are occurring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated. (You can also verify this is the case by looking in \EEEData\Archive\<Store directory> to see if EEE has recently received any files from the store)

			If there are no files in the Export folder on the EEE Server, check the \enabler\comms\ackout folder on the store server. This is where acknowledgement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.

	~~When this occurs~~, you should ~~check the stores~~ export ~~folder on~~ the ~~EEE server~~. ~~If there are isl~~-~~file.zip's or isl-po.dat files~~ in this ~~folder~~, ~~then the alerts~~ are ~~occuring because~~ the ~~exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between~~ the ~~store and~~ EEE ~~that should be investigated~~.		If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.

			If the alerts still occur the day after this re-export is performed, it is likely that the store already has newer versions of the data that was exported which is why no acknowledgements are sent. In this case, the concerned records may need to be manually deleted from the ExportMaintenance table.
	If ~~there are no files in~~ the ~~Export folder on~~ the ~~EEE Server~~, ~~check~~ the ~~\enabler\comms\ackout folder on~~ the ~~store server. This~~ is ~~where acknowlegement files~~ are ~~created for transferring back to EEE~~. ~~If there are files in~~ this ~~folder~~, ~~then there is a communications issue between the store and EEE server that should be investigated.~~


	~~If none of~~ the ~~above apply, then you should perform an export of unacknowledged~~ records ~~only~~ to ~~the affected store. This will re-export all records in~~ the ExportMaintenance table ~~for this store, that are older than the “Resend After” hours in the EEE Configurator~~.

Trevor: New page: Created: 30 September 2009. Last Reviewed: 30 September 2009 '''Alert emails for Unacknowledged Records''' EEE will automatically send alert emails when a store has unacknowledged reco...

2009-09-30T23:49:02Z

New page: Created: 30 September 2009. Last Reviewed: 30 September 2009 '''Alert emails for Unacknowledged Records''' EEE will automatically send alert emails when a store has unacknowledged reco...

New page

Created: 30 September 2009. Last Reviewed: 30 September 2009

'''Alert emails for Unacknowledged Records'''

EEE will automatically send alert emails when a store has unacknowledged records older than 7 days. These alerts occur when there are records in the ExportMaintenance table that are older than 7 days.

When this occurs, you should check the stores export folder on the EEE server. If there are isl-file.zip's or isl-po.dat files in this folder, then the alerts are occuring because the exported data from EEE is not being loaded into Enabler at the store. This means that there is a communication issue between the store and EEE that should be investigated.

If there are no files in the Export folder on the EEE Server, check the \enabler\comms\ackout folder on the store server. This is where acknowlegement files are created for transferring back to EEE. If there are files in this folder, then there is a communications issue between the store and EEE server that should be investigated.

If none of the above apply, then you should perform an export of unacknowledged records only to the affected store. This will re-export all records in the ExportMaintenance table for this store, that are older than the “Resend After” hours in the EEE Configurator.