EEE Data Loader fails to import Enabler Configurations - Revision history

Robert at 05:23, 26 May 2011

2011-05-26T05:23:45Z

← Older revision		Revision as of 05:23, 26 May 2011
Line 1:		Line 1:
	Created: 26 May 2011 Last Reviewed: 26 May 2011		Created: 26 May 2011, Last Reviewed: 26 May 2011

	There are various reasons as to why EEE Data Loader may not be able to import the Enabler Till configurations from the Enabler Head Office Server. Below are some symptoms that have been experienced during Magenta Retail testing. If your scenario is not included, please contact Magenta Support.		There are various reasons as to why EEE Data Loader may not be able to import the Enabler Till configurations from the Enabler Head Office Server. Below are some symptoms that have been experienced during Magenta Retail testing. If your scenario is not included, please contact Magenta Support.

Robert at 05:23, 26 May 2011

2011-05-26T05:23:11Z

← Older revision		Revision as of 05:23, 26 May 2011
Line 1:		Line 1:
			Created: 26 May 2011 Last Reviewed: 26 May 2011

	There are various reasons as to why EEE Data Loader may not be able to import the Enabler Till configurations from the Enabler Head Office Server. Below are some symptoms that have been experienced during Magenta Retail testing. If your scenario is not included, please contact Magenta Support.		There are various reasons as to why EEE Data Loader may not be able to import the Enabler Till configurations from the Enabler Head Office Server. Below are some symptoms that have been experienced during Magenta Retail testing. If your scenario is not included, please contact Magenta Support.

Line 64:		Line 66:

	Both the NTFS and Share permissions should allow the SQL Server service account and EEEServices account to have full control of the folder.		Both the NTFS and Share permissions should allow the SQL Server service account and EEEServices account to have full control of the folder.

			==See Also==

Robert: /* Cause */

2011-05-26T05:07:56Z

Cause

← Older revision		Revision as of 05:07, 26 May 2011
Line 56:		Line 56:
	Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server service. Therefore, SQL Server will use the Data Loader Temp path to import the data. This path must exist for SQL Server to access.		Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server service. Therefore, SQL Server will use the Data Loader Temp path to import the data. This path must exist for SQL Server to access.

	However, if Data Loader and the Data Loader Temp path are located on a different server to the SQL Server, this error can occur if the Data Loader Temp path is configured as a local path which is local to the Data Loader ~~server~~(EG: C:\EEE\DLtemp). This issue can be avoided by having the Data Loader Temp path located on the SQL Server.		However, if Data Loader and the Data Loader Temp path are located on a different server to the SQL Server, this error can occur if the Data Loader Temp path is configured as a local path which is local to the server running Data Loader (EG: C:\EEE\DLtemp). This issue can be avoided by having the Data Loader Temp path located on the SQL Server.

	=====Solution=====		=====Solution=====

Robert: /* Cause */

2011-05-26T05:07:19Z

Cause

← Older revision		Revision as of 05:07, 26 May 2011
Line 54:		Line 54:
	Operating System Error Code 3 indicates that 'Path cannot be found'		Operating System Error Code 3 indicates that 'Path cannot be found'

	Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server service. Therefore, SQL Server will use the Data Loader Temp path to import the data.		Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server service. Therefore, SQL Server will use the Data Loader Temp path to import the data. This path must exist for SQL Server to access.

	However, if Data Loader and the Data Loader Temp path are located on a different server to the SQL Server, this error can occur if the Data Loader Temp path is configured as a local path which is local to the Data Loader server(EG: C:\EEE\DLtemp). This issue can be avoided by having the Data Loader Temp path located on the SQL Server.		However, if Data Loader and the Data Loader Temp path are located on a different server to the SQL Server, this error can occur if the Data Loader Temp path is configured as a local path which is local to the Data Loader server(EG: C:\EEE\DLtemp). This issue can be avoided by having the Data Loader Temp path located on the SQL Server.

	=====Solution=====		=====Solution=====

Robert: /* Solution */

2011-05-26T05:06:02Z

Solution

← Older revision		Revision as of 05:06, 26 May 2011
Line 31:		Line 31:
	To avoid the issue mentioned where delegation is not passed, configure the Data Loader Temp path in EEE Tools Configurator on the server running Data Loader to use a network folder located on the SQL Server. EG: \\sqlserver\eee\dltemp		To avoid the issue mentioned where delegation is not passed, configure the Data Loader Temp path in EEE Tools Configurator on the server running Data Loader to use a network folder located on the SQL Server. EG: \\sqlserver\eee\dltemp

	Both the NTFS and Share permissions should allow the SQL Server service account and Data Loader service account (i.e: EEEServices) ~~account~~ to have full control of the folder.		Both the NTFS and Share permissions should allow the SQL Server service account and Data Loader service account (i.e: EEEServices) to have full control of the folder.

	====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====		====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====

Robert: /* Solution */

2011-05-26T05:05:48Z

Solution

← Older revision		Revision as of 05:05, 26 May 2011
Line 31:		Line 31:
	To avoid the issue mentioned where delegation is not passed, configure the Data Loader Temp path in EEE Tools Configurator on the server running Data Loader to use a network folder located on the SQL Server. EG: \\sqlserver\eee\dltemp		To avoid the issue mentioned where delegation is not passed, configure the Data Loader Temp path in EEE Tools Configurator on the server running Data Loader to use a network folder located on the SQL Server. EG: \\sqlserver\eee\dltemp

	Both the NTFS and Share permissions should allow the SQL Server service account and EEEServices account to have full control of the folder.		Both the NTFS and Share permissions should allow the SQL Server service account and Data Loader service account (i.e: EEEServices) account to have full control of the folder.

	====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====		====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====

Robert: /* Cause */

2011-05-26T05:03:33Z

Cause

← Older revision		Revision as of 05:03, 26 May 2011
Line 24:		Line 24:
	Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server. Therefore, the Windows user account that is configured to run the SQL Server service must have permission to access the Data Loader Temp path.		Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server. Therefore, the Windows user account that is configured to run the SQL Server service must have permission to access the Data Loader Temp path.

	In some scenarios, when Data Loader and the Data Loader Temp path is located on a different server to the SQL Server, the above error can be logged. This is caused because the SQL Server service account cannot be 'delegated' to perform the Bulk Load. This can be avoided by having the Data Loader Temp path located on the SQL Server.		In some scenarios, when Data Loader and the Data Loader Temp path are located on a different server to the SQL Server, the above error can be logged. This is caused because the SQL Server service account cannot be 'delegated' to perform the Bulk Load. This can be avoided by having the Data Loader Temp path located on the SQL Server.

	=====Solution=====		=====Solution=====

Robert: /* Cause */

2011-05-26T05:03:08Z

Cause

← Older revision		Revision as of 05:03, 26 May 2011
Line 22:		Line 22:
	Operating System Error Code 5 indicates that 'Access is denied'		Operating System Error Code 5 indicates that 'Access is denied'

	Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server ~~service~~. Therefore, the Windows user account that is configured to run the SQL Server service must have permission to access the Data Loader Temp path.		Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server. Therefore, the Windows user account that is configured to run the SQL Server service must have permission to access the Data Loader Temp path.

	In some scenarios, when Data Loader and the Data Loader Temp path is located on a different server to the SQL Server, the above error can be logged. This is caused because the SQL Server service account cannot be 'delegated' to perform the Bulk Load. This can be avoided by having the Data Loader Temp path located on the SQL Server.		In some scenarios, when Data Loader and the Data Loader Temp path is located on a different server to the SQL Server, the above error can be logged. This is caused because the SQL Server service account cannot be 'delegated' to perform the Bulk Load. This can be avoided by having the Data Loader Temp path located on the SQL Server.

	=====Solution=====		=====Solution=====

Robert at 05:02, 26 May 2011

2011-05-26T05:02:38Z

← Older revision		Revision as of 05:02, 26 May 2011
Line 3:		Line 3:
	====Scenario 1: EEE Data Loader fails to import Enabler Configurations due to access being denied (Operating System Error 5)====		====Scenario 1: EEE Data Loader fails to import Enabler Configurations due to access being denied (Operating System Error 5)====
	=====Symptoms=====		=====Symptoms=====
	Enabler Till configurations are not importing from the Enabler Head Office Server to the EEE configuration table.		Enabler Till configurations are not importing from the Enabler Head Office Server to the EEE.configuration table.

	You may receive the following error in the Windows Application Event Log:		You may receive the following error in the Windows Application Event Log:
Line 35:		Line 35:
	====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====		====Scenario 2: EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====
	=====Symptoms=====		=====Symptoms=====
	Enabler Till configurations are not importing from the Enabler Head Office Server to the EEE configuration table.		Enabler Till configurations are not importing from the Enabler Head Office Server to the EEE.configuration table.

	You may receive the following error in the Windows Application Event Log:		You may receive the following error in the Windows Application Event Log:

Robert at 05:01, 26 May 2011

2011-05-26T05:01:44Z

@@ Line 23: / Line 23: @@
 Although Data Loader is the application that begins the import process, the Bulk Load is actually performed by the SQL Server service.  Therefore, the Windows user account that is configured to run the SQL Server service must have permission to access the Data Loader Temp path.
 =====Solution=====
 Configure the Data Loader Temp path that is configured in EEE Tools Configurator to allow the SQL Server service account to have full control.
 ====Scenario 2:  EEE Data Loader fails to import Enabler Configurations due to path not found (Operating System Error 3)====