Could not open table 'ECounter.dbo.EVPArticlesReceived' while transfer SPCOD

SPCOD File Transfer error in Speed Net Module 

ERROR 

Error in creating message file 187 for COD Articles - Could not open table
'ECounter.dbo.EVPArticlesReceived' from OLE DB provider 'SQLOLEDB'

Also read :SPCOD Delivery and Paid Update : working procedure

Error in creating message file 136 for COD Articles - Could not open table

Also read :Solution for This is a not a Speedpost COD Article. Please Check

'ECounter.dbo.EVPArticlesReceived' from OLE DB provider 'SQLOLEDB'

Solution

The reported issue occurs due some of the default settings not set for linked server concept, which is required to fetch data related to SP-COD articles. Please do the following: 

1. Go to Providers option under Server Objects --> Linked Servers in the SQL Server Management Studio. 
2. Select the entry for 'SQLOLEDB' under Providers, right click and select 'Properties' option. 
3. Check the entry for 'AllowIn Process' option for the SQLOLEDB properties. Save the above and run Speednet Communication once again. The reported errors should not be coming again. 

For SQL version 2000, please do the following: 

1. Open 'Enterprise Manager' and select 'Linked Servers' option under Security. 

2. Right-click on 'Linked Servers' option and select new linked server option. 

3. Select 'Other Data Sources' option under General tab. 

4. Select provider name as 'Microsoft OLE DB Provider for SQL Server' and click on 'Provider options' button. 

5. Set the 'Allow InProcess' property to true, click on OK and exit enterprise manager. Once the above configurations are done, please do the following and check:

a) Download the attached zip file and unzip it. 

b) Run the script file POSPCC_CODStatus_Solution_03022015.exl using Meghdoot ScriptTool.exe after taking full backup of POSPCC and ECounter databases. 

c) Check the log file generated after execution of the script file for any errors. If any error is noticed in log file, then send the log file for analysing the issue under reference. 

d) Run the SpeedNet Communication and check the Error Log for any errors. If any error is noticed in Error Log file or Status of the SP COD article is not updated in India Post Speed Post Tracking / SpeedNet MIS / local SpeedNet even after elapse of one hour, then supply the latest copy of EMSClient folder for analysing the issue under reference. 

Then run speednet communication and check whether the reported error comes or not. If neither of the settings are working in SQL Server Version 2000, then you may consider upgrading to SQL Server Version 2005 or above

Download