Breaking News
Loading...
Thursday, 9 October 2014

Info Post

SPCOD common Issues and Solution

  • SPCOD received through Speed Net and Transferred to Meghdoot Postman, Returns should be done in Postman Module and closing of bag may be done at Speed Net Module.
  • SPCOD article Transfer based on the linked server concept and the prerequisites for creation of linked server

SPCOD Issues 1 : 

  • eCounterLinkServer Does not exist in SQL Server 2000 or SQL 2008

Solution

  1. Update Speed Net One Updater once again to Create eCounterLinkServer
  2. If Speed Net one Updater does not allow to update, just execute all the scripts using MM Script Tool
after follow the above steps, if you are fail to create Linked Server visit below link


SPCOD Issues 2: in SQL 2005/2008

eCounterLinkServer exists but While transfer the SPCOD article it shows an error message "Could not find eCounterLinkServer... or "you have already scanned speed Post article is EZ.........IN"

Solution

  1. Check whether Messages are available in RXD> Data folder in EMS Client.
  2. If exists, Visit below link and follow the procedure to update remote connection.
Note: Above process only applicable for SQL 2K5 /SQL 2K8
SQL 2005 / 2008 Solution 

SPCOD Issues 3 : No data available

No data available for Speed Post COD article no.EZ.........IN

Solution

  1. Login As Supervisor in SpeedNet Module click On Tools>Request Resend COD Message Data
  2. Enter Article Number one by one and Check the entire article and click on OK. It will get transmitted to Central Server.
  3. Execute EMS Client(Speed Net communication) to receive the COD Article.
for more information and complete procedure of SPCOD article visit below link


0 comments:

Post a Comment