View source for EEE Data Loader fails to import Enabler Configurations

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.  

====Scenario 1:  EEE Data Loader fails to import Enabler Configurations due to access being denied (Operating System Error 5)==== 
=====Symptoms=====
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:
<pre>
Level:  Error
Source:  EEE Data Loader
Event ID:  124
The EEE Data Load service encountered an error in the Enabler configuration importer.  
Microsoft SQL Server Native Client 10.0 [Database: \\EEE_SQL_Server.EEE]: Cannot bulk load because 
the file "<dataloader temp path>\TILLS.imp" could not be opened. Operating 
system error code 5(failed to retrieve text for this error. Reason: 15105).  Extended Info 1: 
IDispatch error #3092
</pre>

'''<dataloader temp path>''' is the Data Loader Temp path configured in EEE Tools Configurator on the server where Data Loader is running

=====Cause=====  
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.  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 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=====
Configure the Data Loader Temp path that is configured in EEE Tools Configurator to allow the SQL Server service account to have full control.  

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) 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)====
=====Symptoms=====
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:
<pre>
Level:  Error
Source:  EEE Data Loader
Event ID:  124
The EEE Data Load service encountered an error in the Enabler configuration importer.  
Microsoft SQL Server Native Client 10.0 [Database: \\EEE_SQL_Server.EEE]: Cannot bulk load because 
the file "<dataloader temp path>\TILLS.imp" could not be opened. Operating 
system error code 3(failed to retrieve text for this error. Reason: 15105).  Extended Info 1: 
IDispatch error #3092
</pre>

'''<dataloader temp path>''' is the Data Loader Temp path configured in EEE Tools Configurator on the server where Data Loader is running

=====Cause=====  
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.  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 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=====
Check and confirm that the correct path has been configured in EEE Tools Configurator on the server running Data Loader.  

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.

==See Also==